On (14 Dec 96) Bruce Clark wrote to Stephen Haffly...
 BC> The Timeguard works. At least it keeps Ensemble from
 BC> resetting the CMOS clock. The GEOS clock still quits
 BC> when I suspend and just takes up where it left off,
 BC> upon resuming. Kind of funny, I start GEOS from in
 BC> Windows and when I Alt-Tab to Windows, the Windows
 BC> clock is correct. Go back to GEOS and it's clock is
 BC> still slow.
The same happens with OS/2.  I believe it is because the GEOS clock only
is active when GEOS gets its timeslices from the controlling program be
that OS/2 or Windows.  It will by nature run slow then when run as a
task in a multitasking OS.
 BC> Made a launcher for Kirk Lawrence's getaclk.com. After
 BC> suspending, all I have to do is double click on that
 BC> icon and it resets the GEOS clock.
I'm not familiar with this application.  I am assuming it is a DOS
application since you type "launcher".  Since it would be operating in
the same DOS session, I can see where it might work.
 BC> Unfortunately, it turns out that starting any DOS program
 BC> does the same thing. GEOS shuts down and restarts when a
 BC> DOS program is run. Any progam that runs and exits would
 BC> do the same thing.
True.  The only thing I can think of that would make your GEOS clock
keep more accurate time would be to either launch Windows from GEOS, or
to give GEOS such a high priority in timeslices that it would just about
bring everthing else to a halt.  It is just one of the things we have to
put up with running a multitasking OS from a multitasking OS.
TTYL,
Stephen
Team OS/2, Team GEOS     
OS/2 & Geoworks Ensemble - What a combo!
slhaffly@bora.dacom.co.kr    FIDO 6:760/4.3
... indows cons ice ointers...heesh
--- PPoint 2.02
---------------