Y2K and Windows Help

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

>>>>> "Floyd" == Floyd E Avery <feavery@worldnet.att.net> writes:

    Floyd> Greetings in Jesus Name Brian Berger wrote:
    >>  That means, according to manufacture websites, that on Jan 1,
    >> I have to simply enter the date in the BIOS. The easiest fix is
    >> to change the date _now_ to read 1972, as the date rollover
    >> will be the same from 72 to 73 as 99 to 00. Quick and painless,
    >> then you can change it back on Jan 1. Bro Tyler has been
    >> following this a bit closer, but I don't fear much from Y2K,
    >> except that gasoline will be going up a quarter a gallon this
    >> last week!
    >> 
    >> At least it appears on the way up here in New England.
    >> 
    >> Brian Berger Manchester, NH

    Floyd> Floyd sticks his nose in: Bro. Berger, are you sure you
    Floyd> didn't mean 1971 to 1972? Y2K has me talking to myself, and
    Floyd> sometimes I listen to myself and realize I am confused.  I
    Floyd> could be mixed up, but I believe 1971 is equivalent to 1999
    Floyd> and 1972 is equivalent to 2000.

Are we talking about the date stored in the CMOS clock chip?  How is
that going to keep a system from booting?  If it doesn't have the
right date after it boots, then just set the clock manually.  Machines 
on a network should be using NTP to set their clocks, especially if
NFS or some other network file sharing scheme is being used, otherwise 
dates will get messed up and make may fail to build a target
correctly.  I have seen this happen before.

-- 
--------  "And there came a writing to him from Elijah"  [2Ch 21:12]  --------
R. J. Brown III  rj@elilabs.com http://www.elilabs.com/~rj  voice 847 543-4060
Elijah Laboratories Inc. 457 Signal Lane, Grayslake IL 60030  fax 847 543-4061
-----  M o d e l i n g   t h e   M e t h o d s   o f   t h e   M i n d  ------