Hi....

The primary problem with dos... Timing Out, is in the applications where
the last update field is important.

If your program does not bother about the last update field, and it
doesn't sense the last update field, at any point, then... why would it
care, if the dos update field is "Out of date".

The problem comes primarily at installation when, you are attempting to
update an existing program. Often software venders use the last update
field, to determine which version of a file you are using. In the case
where you are using a DLL file that has a date AFTER the roll over, the
computer will not be able to recognize it as being the update, and you
will get one of those famous "The file you are installing is older than
the existing file" type messages.

So, the primary problem will be during installation of your program after
the date of roll-over.

There might be other problems, but it is primarily the file-system that is
limited. The calculation of the date stamp for that however, is part of
the BIOS time/date routines, so you might have problems if you are not
doing the low level timebase yourself.

                                GREY

GRAEME SMITH                         email: grysmith@freenet.edmonton.ab.ca
YMCA Edmonton

Address has changed with little warning!
(I moved across the hall! :) )

Email will remain constant... at least for now.


On Wed, 22 Sep 1999, Andy Kunz wrote:

> >I do not believe DOS has the same problem.
>
> It does.
>
> Andy
>
> ==================================================================
>  Eternity is only a heartbeat away - are you ready?  Ask me how!
> ------------------------------------------------------------------
> andy@rc-hydros.com      http://www.rc-hydros.com     - Race Boats
> andy@montanadesign.com  http://www.montanadesign.com - Electronics
> ==================================================================
>