Intel Corporation (INTC) Message Board

STOCKTALK

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 : Intel Corporation (INTC)

INTC 35.52

-1.2%

3:59 PM EST

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next

To: Amy J who wrote (94883)	1/3/2000 3:31:00 PM
From: Gerald Walls	Read Replies (2) of 186894

To reproduce this Y2k bug, select F1 after rebooting Compaq/Pentium (120mhz, etc.) system with a 1995 Micron motherboard. Result: system date in the PhoenixBios is 1/3/1900. The system date didn't roll over correctly. Yes, I have an old junk Packard Bell 486 from about that time (my Linux Internet Gateway machine) that I knew wasn't Y2K compliant. I merely shut it off beforehand, later rebooted it and reset the date in the BIOS. Voila! Problem solved. My other machines were all compliant. I think it's time for everyone to admit that the only Y2K bugs that have or will show up are rinky-dinks like this one and we should stop worrying. A minor problem here or there is nothing to be concerned about. I must admit, though, that while I expected nothing major to happen I'm surprised that nothing notable happened. I wonder if the reset is good enough, or should I upgrade the PhoenixBios from Micron for this (assuming they've got a BIOS upgrade to a 95 mb)? To the best of my knowledge resetting the clock is sufficient. Besides, I don't believe that the BIOS is flashable and it isn't worth paying for new BIOS chips to upgrade such an old machine.

Report TOU Violation

Share This Post

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next