Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!killer!rgj From: rgj@killer.UUCP (Randy Jouett) Newsgroups: comp.sys.amiga Subject: Re: priorities (was Re: (none)) Message-ID: <4601@killer.UUCP> Date: 25 Jun 88 18:57:13 GMT References: <1814@van-bc.UUCP> <128@quintus.UUCP> Reply-To: rgj@killer.UUCP (Randy Jouett()) Organization: The Unix(R) Connection BBS, Dallas, Tx Lines: 30 In article <128@quintus.UUCP> pds@quintus.UUCP (Peter Schachte) writes: >In article <1814@van-bc.UUCP> lphillips@lpami.van-bc.UUCP (Larry Phillips) writes: >>In <3043@louie.udel.EDU>, CRONEJP%UREGINA1.BITNET@cornellc.ccs.cornell.edu (Jonathan Crone) writes: >> >ACtually the problem with RSL Clock was that the twit who wrote it >> >had the program set itself up with a prioiryt of 20. >>Nice attitude Jonathan. Someone writes you a nice clock and you call him a >>twit for making a mistake. > >Maybe this is a naive question, but why is it a mistake to make a clock >program run at priority 20? If you really want the clock kept up-to-date, >and it runs pretty fast, why not run at priority 20? Isn't that what >priorities are for? Who misses a couple of milliseconds every second? >-Peter Schachte >pds@quintus.uucp >..!sun!quintus!pds This is one of the reasons why VoiceClock does not stay resident. Using vclock along with a macro/hot-key (I use ALT-ESC with dmouse -- great prog, Matt!) program makes sure that the 68K gets every cycle it deserves. Other major advantages vclock has over other clock progs are: size (1392 bytes); it can be used by the blind, and, as stated above, it does not require a high process priority for accuracy. NOTE: "It is now" is a bug -- posted wrong version :(. It should been "It is" followed by the time. -- Randy ...!killer!rgj