|
PureBytes Links
Trading Reference Links
|
Vitaly,
thank you for your hints.
On Sun, 09 Jan 2000 12:18:38 -0500, you wrote:
>Some years ago I had a similar problem. After I ran DOS code, my Windows clock
>showed much delayed time: as if during DOS run it almost stopped. Delays were
>significant - 15-20 min depending how long and how many times DOS box had been run.
>As a result, I had to set the Windows time anew each time that was very frustrating.
>No change of date as far as I remember, but my DOS code didn't handle dates per se.
My problem is somewhat different: The time of day (of the Windows
clock) is unchanged, but the date changes in accordance to a VBA
routine, when it steps through a given time frame, which is
represented by some numbers (e.g. 36196 for 05.02.1999). Strange &
boring ...
>By then my computer was on warranty, so I started to torture a technical support
>(at Quantex). As it turned out (very slowly and after talking with many technicians),
>the problem was with Power Management of Win 3.11 (by that time). A technician
>walked me through reinstallation of PM software and probably made a few changes
>in BIOS CMOS Setup. It made a trick!
Because the error showed up on two different computers, imo it is
likely that there is no special hardware failure.
Thank you again for your input.
mfg rudolf stricker
| Disclaimer: The views of this user are strictly his own.
|