|
PureBytes Links
Trading Reference Links
|
Rudolf,
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.
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!
This is all I can recall.
Good luck.
Vitaly
rudolf stricker wrote:
> Thank you for jumping in!
>
> On Sat, 8 Jan 2000 19:23:01 +0100, you wrote:
>
> >-Your PC -main- clock can only be accessed via your BIOS software on start up
> > (the CMos settings software, eg the Computer Management operating system)
> > and this clock is usualy stored in a chip (most will have it "baked" in a chip itself)
> > on the motherboard, and it runs on the on the motherboard build (tiny round flat) battery.
>
> As a typical (stupid) Windows user, I have to admit that I didn't
> make a difference between all those clocks. What I'm talking about is
> what I see, and that seemingly is the Windows clock:
>
> >-Your Windows clock (protected mode) can be accessed via the Window's Control Panel,
> > via the Window's RUN box(Win Prompt) and via the Window's VDOS box(VDOS Prompt).
> > It gets its information from the real PC clock(above), and presents this as though it is
> > the PC clock(eg a VPC clock, a virtual clock), now on your DeskTop (eg thus in Windows).
> >
> >-Your DOS clock (real mode) can be accesed via the DOS prompt, eg with the DATE and
> > TIME commands.
>
> Can you please tell me, what DOS could be? ...B-))...
>
> >Excel doesn't get mentioned here, because it is only getting "information" from Windows
> >and its Window's clock, eg it cannot directly access the Windows clock, let alone your
> >PC clock, let alone your PC's BIOS.
> >It is "read only" information given by Windows.
>
> That imo is the way it _should_ work, but it's not in accordance to
> reality.
>
> Again and again my system tests in Excel make changes to the Windows
> clock. To be more precise: Changes to the _date_ are made in
> accordance to the date of the system test when my Excel/VB procedures
> step through an out-of-sample back-test. The time-of-day is untouched.
>
> It may be unbelievable, but this effect shows up at least on two
> computers (Win NT and Win98) and two versions of Excel (97 and 2000).
>
> mfg rudolf stricker
> | Disclaimer: The views of this user are strictly his own.
|