Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!mailrus!tut.cis.ohio-state.edu!bloom-beacon!gatech!uflorida!beach.cis.ufl.edu!jdc From: jdc@beach.cis.ufl.edu (Jeff Capehart) Newsgroups: comp.os.vms Subject: Re: Continuously running clock Message-ID: <13227@uflorida.cis.ufl.EDU> Date: 19 Mar 88 21:51:36 GMT References: <91rrk@byuvax.bitnet> Sender: news@uflorida.cis.ufl.EDU Reply-To: jdc@beach.cis.ufl.edu (Jeff Capehart) Organization: UF CIS Department Lines: 17 Keywords: clock I already have a fairly short program that runs as a subprocess with 256 pages of page file quota, needs only 1 minute of cpu to run about 4 hours, and sets the scrolling region so that it won't scroll off, provides a symbol, freeze, which will reset the scrolling region when the editor messes it up, and it updates once every second unless you start typing on the command line. I have found that the only way to keep it from scrolling is to not use the IO$M_BREAKTHRU and just let the IO's pass during I/O but not typing IO. The only other problem it has is that sometimes it will jump. This is particularly noticeable when the cursor is set beyond the 80 cols and an attempt to restore the position with 7 and 8 resets it to the beginning of next line. I will send anyone who wants a copy, or if there are enough requests, I can just post to the net since it is only about two pages long. -- Jeff Capehart Internet: jdc@beach.cis.ufl.edu University of Florida UUCP: ..!ihnp4!codas!uflorida!beach.cis.ufl.edu!jdc