IBM/XT Y2K Compliancy

From: Russ Blakeman <rhblake_at_bigfoot.com>
Date: Thu Aug 5 12:49:42 1999

best bet is to set the machine to a few minutes before midnight of the rollover
date, then let it flop and see what you get, and then work with the operating
system and software as well. I had a patch/replacement for the file manager in
Win 3.1x for Y2K but otherwise I've not seen much. The only real problem I've
seen is in machines that onl look for a 2 digit year when setting the calendar.
All of my PS/2's work Y2K OK.

allisonp_at_world.std.com wrote:

> > Are the IBM/XT, IBM/AT and PS/2 computers hardware Y2K compliant? I'm not
> > really into the old Clone machines, and don't really know... (and
> > personally I couldn't care -- but we had a customer ask about them and I
> > could really use an answer...)
>
> Generally no but that does not mean unusable. Some will not have much
> trouble as the XT machines don't have a TOD clock just a tick the OS
> accumulates. That means the OS must be y2k...
>
> The later AT and PS/2 machines do have a TOD clock and that can have one
> of three bugs. Clock rolls over to 1980 and connot be set to 2000, the
> clock rolls over and can be set to 2000 manually and the last is if
> feb2000 is leap year. The only one that is severe is the cannot be set to
> 2000 bug. the others are merely annoying. There are plugin cards climing
> to fix TOD errors (JDR 49.95).
>
> Even if the hardware is fine then there are the questions for the
> software. The bootom line is if the machine is doing work that is not
> date centric no problem, should date be used it may not be a real
> issue depending on how it's used. The later is an app that simple does
> data logging and prints the current date an time.
>
> Allison
Received on Thu Aug 05 1999 - 12:49:42 BST