🚀 go-pugleaf

In article <2485@batcomputer.tn.cornell.edu> chow@tcgould.tn.cornell.edu (Christopher Chow) writes:
>
>There are good reasons for NOT using JClock:
>
>1.  JClock just writes to the menu bar w/o checking for things which are
>	there.  Most notably, Pyro! dosen't work very well with JClock since
>	Pyro! will blank out the screen, but JClock will continue to write
>	the time on the upper right hand corner (of an Plus/SE/512k).
>
>2.  JClock dosen't check screen size, so it in the wrong place on a Mac II
>	(I know this can be patched, but it then won't work on a
>	Plus/SE/512k)  It also appears in the wrong place or outright dosen't
>	work with some virtual large-screen INITs for the very same reason.
>
>So what should you use for a clock?  I use Menu Clock 3.0 - it works with 
>virtual large-screens, Pyro!.  I think it'll also work on a Mac II, but I
>
>Christopher Chow

I have been using JClock.31, the init you put in the system folder, for
several months with no problems in a system with a hard disk. I just put it
on 2 Mac SE's at work with Pyro. I first tried something called MenuTimeInit
but the time stays on the screen when Pyro blanks it. With JClock.31 I can at
least turn off the time by click on it but this isn't ideal. Is Menu Clock 3.0
something different or a newer version of MenuTimeInit? I WOULD like something
that works with BIG screens because we are getting 2 SuperMac SuperView
monitors installed today.

Where can I get Menu Clock 3.0?

-- 
Russell Schwausch, Motorola Inc., OakHill, Tx. (A suburb of Austin)
UUCP: {harvard,ihnp4,seismo,gatech,nbires}..!ut-sally!oakhill!russ
Ma Bell: (512)440-2426

It's a ticket agent, it's a fare collector, no ... it's SUPERCONDUCTOR!!!