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 : Apple Inc. -- Ignore unavailable to you. Want to Upgrade?


To: louis mason who wrote (8432)2/12/1998 2:10:00 PM
From: Bill Jackson  Respond to of 213177
 
Louis; I think that certain PCs use date and time internal clock chips that have a problem with dates and times after 2000. Some are OK if they are powered up and allowed to advance through 2000 normally. Some choke and die if they are turned off in 1999 and turned on in 2000, even though their internal battery should take them through this.
So you need to see what actual time and date chip is on each motherboard. Each machine can be opened up and a knowing tech can read it. The supplier if reputable can tell you. Screwdriver shops might not rememeber what version is in there, and will have to open it up and look.
All new boards and time/date chips are OK, however some old programs might choke?

Can be a big pain in the *ss. I tested my machine by setting the time and date for Dec 31, 11;58 PM and turning them off, waiting for 5 minutes and turned them on, it worked. I then let it clock through to 2000 with the power on, it worked. However I have a new pentium 233 MMX and recent BIOS and windows 95B. I do no accounting.
If you have old data base and accounting programs you coulkd save all data and try the two clock throughs, power off and power on. After each try your accounting and other programs to see if they choke.
A simulated year 2000, do it now, but save data first. This will ID the problems now. After you ID them, restore your times to the old times and restore from back up. You will them have a couple of years to nag the IS dept with a known problem.

Bill



To: louis mason who wrote (8432)2/12/1998 2:19:00 PM
From: Jonathan Bird  Read Replies (2) | Respond to of 213177
 
Is this true? Does this approaching panic actually only applying to Intel based PC's? I really don't know the answer to this question, I'm just trying to find if our controller has his facts straight.

Mostly true. There is no hardware or OS limitation that would cause problems in year 2000. But that doesn't mean that the programs you run wont have problems. But it's VERY unlikely. It simply remains in the realm of "posibility". If it occurs it certainly would not be the Macs fault. Just wacky programing of a database or something.

The Macs clock was previously expected to overflow sometime in the the second or third decade of 2000 I believe. But there was a recent OS revision that will let it run correctly for substantially longer. As you can see I don't recall any of the specifics. But it was so far in the future that it won't matter.

Jon Bird



To: louis mason who wrote (8432)2/13/1998 10:45:00 AM
From: Josef Svejk  Respond to of 213177
 
Humbly report, louis, regarding Macs and the year 2000 problem (y2k):

Message 3244963
Message 3246485
Message 3247092
Message 3248920

Svejk
(GL-15 applies: digiserve.com ;-)



To: louis mason who wrote (8432)2/15/1998 4:36:00 PM
From: Edward Boghosian  Respond to of 213177
 
If it only applies to Intel machines, what an advertising campaign this could make.

Ed