***************************************************** Gateway Version History: Revision 2.0 06/23/2000 PHATLE FILE: 9508321.ZIP Update to latest BIOS: Version 13.0 Build 125 Update to latest FIRMWARE: Version 1.13 Update to latest FRUSDR: Version 4.2.3 Revision 1.1 02/21/2000 SARRAJOH FILE: 9507246.ZIP Initial revision ***************************************************** Revision History: 06/23/2000 BIOS: Version 13.0 Build 125 FILE: 9508314.ZIP 1. Support for 1GHz Pentium III Processors. NOTE: All .18u Pentium III B0 stepping QSpec parts are clock locked. 2. Fixed issue where 640K Base Memory test was being overwritten on POST Diagnostic screen. 3. Fixed issue with speed mismatched processors not being disabled. Now, the slower of the 2 processors will be disabled on reboot. This has a side effect of not allowing and unlocked processor that was set a different speed having a locked processor added to the configuration. 4. Fixed issue where CMOS was not being properly restored when corrupted. 5. Fixed issue where 133MHz FSB processors were being allowed to operate in the system. NOTE: This feature does not work with Q spec part but will work with S spec and production parts. 6. Added feature to prevent boards lower that FAB7 from booting processors faster than 850MHz. 7. Upgraded PXE 0.99c option ROM to PXE 2.x Build 78. 8. Added updated Japanese Setup translations. 9. Fixed issue with mixing 681 A2 and 683 B0 processors of the same speed displaying a processor speed mismatch error erronously. 10. Removed corrupted Japanese strings from Setup. They will appear in English until updated translations are provided. 11. Fixed WOR for COM2 under ACPI OS. 12. Fixed INT15h handler for microcode updates. Now multiple processors can be updated. 13. Fixed virus protection and Master Boot Record write protect feature. Now, these will only protect the hard drive when booted from a floppy. ---------- 06/23/2000 FIRMWARE: Version 1.13 FILE: 9508316.ZIP 1. Previous versions of the firmware did not report the status of the SUSSTAT1 signal in the response to the Get ACPI Configuration command. BMC 1.13 now reports a "1" for SUSSTAT1 when the signal is active, indicating that the server is in S1 sleep. 2. When Windows 2000 (or any ACPI OS) put the server into Standby mode (ACPI S1 sleep), the BMC did not automatically disable the watchdog timer. If server management software was using the timer when the system went into standby, the BMC would then reset or power cycle the server when the timer expired. To avoid this, the BMC now turns off the timer when the server enters S1 sleep. 3. Modified Get Device ID command, when in firmware transfer mode, to return an additional 6th byte for capabilities. The sixth byte indicates that no IPMI capabilities for accessing the SEL, SDR, FRU, or ICMB exist during firmware update. 4. When a Chassis Control power down or power cycle command was sent to the BMC, the system would power down but would not power up again until AC power was removed and re-applied. This has been fixed in BMC 1.11. 5. The server would not recover from a short term AC power loss in which 5 volt standby power to the BMC was not lost. BMC 1.11 correctly detects this and power cycles the server. 6. The server would not power up when certain non-ATX compliant power supplies were installed. Support for such supplies has been improved in BMC 1.11, however operation with non-ATX compliant power supplies is not guaranteed. 7. Added the following new sensors; sensor 0x29 Power Unit : power cycle, AC lost sensor 0x2A Redundancy Lost : regained, lost sensor 0x2B Power Supply #1 : presense & failure detected sensor 0x2C Power Supply #2 : presense & failure detected sensor 0x2D PDB Temperature : threshold If a power supply failure is detected the power fault LED signal is asserted. Similarly, if a power supply fan fails the cooling fault LED signal is asserted. 8. Updated the I2C communications library to the latest version. This reduces the chances of communication failure under high I2C traffic loads. 9. Added a synchronization between power state changes and the I2C sensor tasks, and I2c traffic. This should also improve I2C communications reliability. ---------- 06/23/2000 FRUSDR: Version 4.2.3 FILE: 9508319.ZIP 1. Added SDRs to support different processor voltages and speeds. ---------- 04/12/2000 BIOS: Version 12.1 Build 115 FILE: 9507067.ZIP 1. Added support for 683 B0 Pentiumr(r) III processors 2. Added support for Pentiumr III 850 MHz processors 3. Fixes will be added to support the Microsoft WHQL HCT 9.5 test suite 4. Help text will be added to the BIOS setup utility to help identify EMP setup dependencies. 5. Fix: to support ISC issue if BIOS is not set to English 6. Fix: to support dual SRCU21 RAID cards 7. Fix: SBE SEL record data 8. Fix: BIOS ID not in English 9. Fix: Non-ECC memory identified as ECC at POST 10. Fix: Processors model mis-match error 8188 11. Added help text to distinguish which processors are supported on different boards 12. Move Floppy option from multi-boot to removable devices in BIOS Setup utility 13. Removed unused debug components and outs to Port 80h 14. Fix: issue: if a critical POST error occurs and Quiet Boot is enabled, the system hangs at logo screen 15. Fix: POST Hang after exiting BIOS setup and discarding changes twice ---------- 03/24/2000 Initial Release BIOS: Version 11.2 Build 105 FILE: 9506592.ZIP FIRMWARE: Version 1.08 FILE: 9506915.ZIP FRUSDR: Version 4.01.2 FILE: 9507088.ZIPDownload Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.