Hello All Binkley Users;


=== Cut ===

The DATE command shows my PC is Y2K compliant
A common, but extremely misleading way to test for Year 2000 compliance is
to set the date in DOS or Windows to 12/31/1999 and the time to around
23:59:50. After waiting 20 seconds or so, the date shows 1/1/2000 and
therefore the PC hardware is Year 2000 compliant. Maybe, but probably not.
In most cases, the PC will not change the date properly when the Year 2000
arrives.

Why not? While recent versions of DOS and Windows support year 2000 dates,
they only display the correct date when the system is left on. However,
over 70% of PCs do not have Year 2000-compliant hardware. On these systems,
when the computer is powered on in the year 2000, DOS and Windows get an
incorrect date from the hardware. There are other problems with Year 2000
leap year support, Real-Time Clock compatibility, Y2K BIOS support and CMOS
century settings. Yes2K detects these problems and when possible offers an
automatic correction.

How much money will it cost to fix the Y2K problem? For Hardware: The Yes2K
application can detect and repair the CMOS, BIOS, and RTC glitches on
almost every computer running Windows 98, 95, 3.x or DOS.  Yes2K is FREE
for home users. For the Yes2K fix and for business, government and
educational users, Yes2K is promotionally priced at US $10 per PC.

How can I determine if a desktop  has a Y2K hardware problem?
Download Yes2K, the remedy to the year 2000 hardware problem. In almost
every case Yes2K can fix your system if a Y2K hardware error is detected.  
If Yes2K cannot fix the error, it will generate a report stating what needs
to be done in order to make the computer Y2K ready.

Why doesn't the system date get set to 2000?
Every computer (AT class or higher) contains a CMOS, BIOS and RTC
(Real-Time Clock).   The CMOS, BIOS and RTC are responsible for maintaining
the system date and time when the computer is turned off.  This is why the
computer knows the date and time when it is booted.

The RTC stores the the date in a two digit field and does not have the
ability to increment the first two digits of the year.   Therefore the
century remains constant at 19.  At the turn of the century only the last
two digits will roll over to 00 and the system date will be set to 1900
instead of 2000.  Because many BIOSes recognize 1900 as being out of range,
the system date, will be set to 1980, 1984 or some other incorrect date
dependent on the BIOS and operating system being used.

How do I know if my Real Time Clock is OK?

Here is a list of Motorola Real time Clock parts that are non Y2K compliant.

Will Yes2K also check my software for compliance?

No.That is another problem all together, and there are other specialised
tools out there to fix a multitude of software related problems. Actually,
there are five Y2K related problems. Obviously there is computer hard- ,
and software. Thes there are about 50 billion embedded systems and between
1 and 5 percent are non-compliant. Fourth is connectivity: One system that
is Y2K compliant might still not be able to communicate with another
system. That also needs to be tested. Last but not least: TIME. There is no
time left to fix it all. Focus on your mission critical systems and do
those first.

http://www.sunbelt-software.com/yes2k.htm
=== Cut ===

Regards,
George Vandervort
InterNet EMail: georgev{at}itouch.net
WebSite: http://gv.itouch.net  FTP: gv.itouch.net
Tech Support:   http://gv.itouch.net/tech.html

-+- Proud owner of a QuickBBS 4.0 (Vaporware) Reg-Key

... the Beatles said it best, Obla-Dee, Obla-Daa, Life Goes On...
--- GoldED 2.50+