SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : How high will Microsoft fly? -- Ignore unavailable to you. Want to Upgrade?


To: ToySoldier who wrote (13061)12/8/1998 9:37:00 AM
From: John Chen  Read Replies (1) | Respond to of 74651
 
ToySoldier,:"y2k...". Thanks. As long as the 'patch' is early enough,
no big problem. We have some serious data that can't be lost, ie:
those 'games' history'. PC is a 'game port' and 'internet port' in
my usage model.



To: ToySoldier who wrote (13061)12/8/1998 10:29:00 AM
From: Robert E. Lee, Jr.  Read Replies (2) | Respond to of 74651
 
How is Win98 Not Y2K Compliant

Does anybody know exactly *what* is broken in Win98's Y2K Compliancy?
Does it somehow interpret a date as being off by 100 years, or did they forget 2000 is not a leap year so they're off by 1 day, or do they get the date correct, but the day of the week wrong, or what?

Has there been any simple testcase published so that I can verify my system has the problem, and verify the problem is corrected after I download MicroSoft's fixes?

'The General', Robert E. Lee, Jr.



To: ToySoldier who wrote (13061)12/8/1998 8:02:00 PM
From: Andy Thomas  Respond to of 74651
 
It seems amazing to me that MSFT's products could have Y2K problems.

I thought that the BIOS/CMOS on a PC went from something like 1981 through 2037.

Did the BIOSes/CMOSes on some machines get their starting/ending dates changed at some point?

If the CMOS/BIOS indeed goes to 2037 on every PC, how did MSFT manage to introduce Y2K problems into the mix?

FWIW
Andy