home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.mac.misc
- Path: sparky!uunet!paladin.american.edu!gatech!mailer.cc.fsu.edu!wealthy.ocean.fsu.edu!user
- From: aggie@wealthy.ocean.fsu.edu (I R A Aggie)
- Subject: Re: SuperClock 4.0.1
- Message-ID: <aggie-220193072031@wealthy.ocean.fsu.edu>
- Followup-To: comp.sys.mac.misc
- Sender: news@mailer.cc.fsu.edu (Usenet News File Owner)
- Nntp-Posting-Host: wealthy.ocean.fsu.edu
- Organization: An Ol Ag surrounded by a bunch of unfriendly Seminoles
- References: <llrut2INNp16@news.bbn.com> <jholland.727647959@sol.UVic.CA> <1jniov$ps4@agate.berkeley.edu> <C18otK.7p0@usenet.ucs.indiana.edu>
- Distribution: usa
- Date: Fri, 22 Jan 93 12:23:27 GMT
- Lines: 10
-
- In article <C18otK.7p0@usenet.ucs.indiana.edu>,
- jawalsh@silver.ucs.indiana.edu (John A. Walsh) wrote:
- >
- > BTW, SuperClock 4.0.2 does NOT fix the conflict w/ Moire screensaver on
- > a B&W Mac (Classic II). That is, when the screen saver kicks in, the
- > clock is still visable.
-
- Why is it that SuperClock has to fix the conflict, and not Moire?
-
- James
-