Hello Anne,
Edward Di Geronimo has asked me to take over the cross-posting
from comp.os.geos so he can devote himself to programing.
Following is the posting from Steve Main that you discussed.
Cross posted from comp.os.geos:
From : GW STEVE
To   : ALL
Subj : Re: windows 95, geos, and the system clock
<<< Since upgrading to Windows 95, I've noticed that my clock is screwy.
     I've
reset it several times at DOS, in Windows 95, and in Geos, but it always
seems
to drift. It keeps track of the day, but not the time.
I recall from old posts that there was some kind of problem/conflict
with Geos
and laptops. I also recall that there was a fix for it. >>>
One problem is that Windows does not actually multitask Geos.
Therefore, when you task out of Geos back to Windows, the clock
in Geos stops running. It starts running again when you switch back
to Geos. Then when you exit Geos, Geos writes the wrong
time back out to your hardware clock.
There are several fixes and work arounds. One is to never exit Geos
properly, but always crash out of Geos instead -- not very elegant.
Marcus Groeber wrote a little DOS file called Time Guardian that
prevents all software (including Geos) from writing to your hardware
clock. It works, but it interferes with some other software (Magellan
won't even launch with Time Guardian in place, for example).
Marcus also wrote a "patch" for the Geos kernel that prevents just
Geos from writing to your clock. This is the most elegant solution,
though keep in mind that thereafter you can no longer use Geos'
Preferences to change the clock.
Steve
In a previous post, I said that Marcus Groeber had developed
a patch to the Geos kernel to prevent it from writing to the
hardware clock. I was wrong. The patch was authored by
James A Zuan. I apologize, James.
The filename, on AOL, is CLKPATCH.ZIP.
Steve
--- Platinum Xpress/Wildcat! v1.2k
---------------