[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference siog::year2000

Title:Year 2000
Moderator:SIOG::SYSTEM
Created:Mon Dec 09 1996
Last Modified:Thu Jun 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:23
Total number of notes:70

22.0. "Firmware" by WOTVAX::model60.lzo.dec.com::hiltong ([email protected]) Mon Jun 02 1997 15:20

Is there any issues regarding firmware and Y2k? 

Specifically my customer has a number of AlphaServer 2100a systems, 
and will be running UNIX 4.0d when released. There Y2k people are 
asking them to make sure the firmware is y2k compliant!

Any 'official' info on this?

Greg
T.RTitleUserPersonal
Name
DateLines
22.1Try the Sable Conference, or Sable PMXDELTA::HOFFMANSteve, OpenVMS EngineeringTue Jun 03 1997 23:495
   I think you'll want to contact the Sable engineers more directly,
   via the MVBLAB::SABLE conference, or you'll want to contact the
   Sable product manager.

22.2?SIOG::FITZPATRICKWed Jun 04 1997 18:5814
>>Specifically my customer has a number of AlphaServer 2100a systems, 
>>and will be running UNIX 4.0d when released. There Y2k people are 
>>asking them to make sure the firmware is y2k compliant!

Am I missing something here or does the fact that all of Digital's
VAX & Alpha (& more!) processors are Year 2000 ready answer this ?

From the www.digital.com/year2000 web page....

All of DIGITAL's Alpha, Intel, VAX, and MIPS-based computer systems 
hardware is Year 2000 Ready now. All of the software that DIGITAL 
actively markets as well as all network, components, storage, and 
systems option hardware will be Year 2000 Ready by the end of 1997. 

22.3CelebrisNNTPD::"[email protected]"Paolo CattolicoWed Jun 04 1997 19:1623
Just to let you know....

  Take a Digital PC: Celebris XL 5I66 DP,
  Phoenix Bios 4.04.

  Set date/time to 12/31/99, 23:58.
  Turn it off. wait 3 minutes. Turn it on.

  It will not boot anymore.
  Instead, whenever you try to turn it on,
  it will turn off automatically after 3-4 seconds.

  For fixing the problem, probably due to invalid CMOS
  checksum, I had to open the PC box and do an HW reset of CMOS.
  I tried first to strongly believe in our statements
  on the WWW, but it was not enough.......:-)



Paolo Cattolico
Euopean Tech Support
Valbonne, France
[Posted by WWW Notes gateway]