RELNOTE.TXT Driver File Contents (sis900.zip)

============
Release Note
============

1.02 ==> 1.03

  1. Display message : SiS 900/7016 ....
  2. Diskette Name in readme file : SiS PCI Fast Ethernet Adapter Drivers Disk
  3. Clear Multicast hash table when SW reset.
     ( 900 A2 fix this bug )
  4. Clear wake-up frame byte mask register.
     ( 900 A2 fix this bug )
  5. To improve server performance ( NT server & Novell server ),
     Modify interframe gap in TXCFG bit 26-27: 00 ==> 01

1.03 ==> 1.04

  1. Modify EEPROM read sequence.
  2. Support NT 5.0 driver.
  3. Support Netware 5.0 driver.
  4. Support SCO UNIX MDI driver.
  5. BootROM : add PCI data structure.
  6. Windows 9x driver: Enable magic packet support in driver.
  7. Add information for forcing mediatype in readme.txt.
  8. Fixed problems:
     DOS NDIS 2.0 driver: Remote-boot DOS from OS/2 server.
     OS/2 NDIS 2.0 driver : Remote-boot OS/2 from OS/2 server.
     ODI32: Fix Checksum error problem.

1.04 ==> 1.05

** Summary **
  1. Support MS LAN Manager 2.x for DOS.
  2. Support LINUX driver.
  3. Remove "install information" from diagnostic program.
  4. Modify readme.txt, dosbb.cnf, protocol.ini in \bootrom directory.
  5. Fixed problems:
     All drivers: LED mismatch between SiS900 and NWAY hub/switch when
       forcing mediatype.
     ODI32: Novell Testcon fails in Frame Integrity test.

** DOS Diagnostic program **
   Remove "install information" from diagnostic program.

** Windows 95 driver **
   Fix problem: LED mismatch between SiS900 and NWAY hub/switch when
       forcing mediatype.

** Windows 95 OSR2 driver ** 
   Fix problem: LED mismatch between SiS900 and NWAY hub/switch when
       forcing mediatype.

** Windows 98 driver ** 
   Fix problem: LED mismatch between SiS900 and NWAY hub/switch when
       forcing mediatype.

** Windows NT 3.5x driver ** 
   Fix problem: LED mismatch between SiS900 and NWAY hub/switch when
       forcing mediatype.

** Windows NT 4.0 driver ** 
   Fix problem: LED mismatch between SiS900 and NWAY hub/switch when
       forcing mediatype.

** Windows 2000 or NT 5.0 driver ** 
   Fix problem: LED mismatch between SiS900 and NWAY hub/switch when
       forcing mediatype.

** Windows for Workgroup 3.11 driver **
   Fix problem: LED mismatch between SiS900 and NWAY hub/switch when
       forcing mediatype.

** Netware 3.12 server **
   1.Fix problem: LED mismatch between SiS900 and NWAY hub/switch when
       forcing mediatype.
   2.Fix problem: Novell Testcon fails in Frame Integrity test.

** Netware 4.1x server **
   1.Fix problem: LED mismatch between SiS900 and NWAY hub/switch when
       forcing mediatype.
   2.Fix problem: Novell Testcon fails in Frame Integrity test.

** Netware 5.0 server **
   1.Fix problem: LED mismatch between SiS900 and NWAY hub/switch when
       forcing mediatype.
   2.Fix problem: Novell Testcon fails in Frame Integrity test.

** Netware client **
   Fix problem: LED mismatch between SiS900 and NWAY hub/switch when
       forcing mediatype.

** Netware client32 **
   1.Fix problem: LED mismatch between SiS900 and NWAY hub/switch when
       forcing mediatype.
   2.Fix problem: Novell Testcon fails in Frame Integrity test.

** DOS NDIS 2.0 driver **
   Fix problem: LED mismatch between SiS900 and NWAY hub/switch when
       forcing mediatype.

** OS/2 NDIS 2.0 driver **
   Fix problem: LED mismatch between SiS900 and NWAY hub/switch when
       forcing mediatype.

** SCO 5.0.0 driver **
   Fix problem: LED mismatch between SiS900 and NWAY hub/switch when
       forcing mediatype.

** Packet driver **
   Fix problem: LED mismatch between SiS900 and NWAY hub/switch when
       forcing mediatype.

** BootROM **
   Modify readme.txt, dosbb.cnf, protocol.ini in \bootrom directory.

** MS LAN Manager **
   New.

** LINUX **
   New.

1.05 ==> 1.06
** Summary **
  1.Support AMD 79c901 PHY(10Base-T and HomePNA). WFW311, NT35, NT40,
    Windows 95, 95 OSR2, 98, 2000 and LINUX driver support this feature.
  2.Support Remote-boot Windows 95 from NT40 server.

** Windows 2000 driver **
** Windows 98 driver **
  1.Support AMD 79c901 PHY(10Base-T and HomePNA).
  2.Reduce the driver initialization time.
  3.Support 3 Wake-up frames, not 4.
  4.Fix WOL problems for HCT 9.0 & 9.1.

** Windows for Workgroup **
** Windows 95 driver **
** Windows 95 OSR2 **
** Windows NT 3.5 **
** Windows NT 4.0 **
  1.Support AMD 79c901 PHY(10Base-T and HomePNA).
  2.Reduce the driver initialization time.

** Bootrom **
  1.Support remote-boot Windows 95 from NT40.
  2.Support 16K RPL BootROM.

** LINUX **
  1.Support AMD 79c901 PHY(10Base-T and HomePNA).
  2.Fix problem: Network disconnect after copying large file(>100MB).

** OS/2 NDIS2 **
  1.Fix problem: Fail to copy files when 2 or more tasks copying files
    through network simultaneously.

1.06 ==> 1.07

** Summary **
  1.Fix some issues in HCT 9.5
  2.Fix remote-boot Windows 3.2 issue.
  3.Add some basic tests in DOS diagnostic program.
  4.Support PXE BootROM.
  5.Support Window 9x driver setup utility.

** Windows 2000 **
  1.Fix problem: 1c_ofldn test fails(HCT 9.5).

** Windows 98 **
  1.Fix problem: Dozer & Waker test fails(HCT 9.5).

** DOS NDIS2 **
  1.Fix problem: Cannot remote-boot Windows 3.2.

** DOS diagnostic **
  1.User can select media type(10/100 Half/Full).
  2.Add Register tests, EEPROM test and IRQ test in "Basic test".

** PXE BootROM **
   New.

** Windows 9x setup utility **
   New.

1.07 ==> 1.08

** Summary **
  1.Fix some UNH issues.
  2.Fix problems for SiS900 LAN card.
  3.Fix Windows 98 setup issue.
  4.Support Window 2000 setup utility.
  5.Support Netware server 4.2.
  6.Fix packet driver issue.
  7.Remove Windows 9x diagnostic program.

** Windows 2000 **
  1.Fix problem: Fix UNH issues.  
  2.Fix problem: It takes too long to resume from S3 when cable is
    disconnected.
  3.Reduce driver initialization time for SiS900 LAN card on PCI
    bridge.
  4.Fix problem: Can not receive all packets when testing HCT9.5 
    2m_stndb with SiS900 LAN card on ASUS P2B-D M/B.

** Windows 98/98SE **
  1.Fix problem: Fix UNH issues.  
  2.Fix problem: It takes too long to resume from S3 when cable is
    disconnected.
  3.Fix problem: System will hang when resuming from S3.

** Windows NT 4.0 **
  1.Fix problem: Fix UNH issues. 

** Packet driver **
  1.Fix problem: Some applications fail if they use IRET in UPCALL
    handler.
  2.Modify for new specification: Does not require handle argument for
    driver_info(), get_address(), reset_interface() and get_statistics().

** Netware server 4.2 **
   New.

** Netware server 5.0 **
  1.Fix problem: "Promiscuous Good Packet" test fails in TestConsole 1.0.

** SiSDiag **
   Not Supported since this revision.

** Windows 9x/2000 setup utility **
  1.Fix problem: System hang or protection fault when running this program.
  2.Support Windows 2000.

1.08 ==> 1.09

** Summary **
  1.Support SiS630E(LAN without EEPROM) chipset.

** Windows 2000 **
  1.Support SiS630E chipset.
  2.Set some MII default values for 630E0.
  3.For initializing face, wait for PHY auto-negotiation done and then return
    initializing precedure.
  4.Support up to 5 Wake-Up frames in 630E.
  5.Use strict Match Algorithm for Magic Packet Wakeup.
  6.Add support for Driver Uninstall.
  7.Modify INF to Win2000 only.

** Windows 98/98SE **
  1.Support SiS630E chipset. 
  2.Set some MII default values for 630E0.
  3.For initializing face, wait for PHY auto-negotiation done and then return
    initializing precedure.
  4.Support up to 5 Wake-Up frames in 630E.
  5.Use strict Match Algorithm for Magic Packet Wakeup.

** Windows Millennium **
   New.

** Windows NT 4.0 **
  1.Support SiS630E chipset. 
  2.Set some MII default values for 630E0.
  3.For initializing face, wait for PHY auto-negotiation done and then return
    initializing precedure.
  4.Support Unattended Install.

** Windows 95 driver **
** Windows 95 OSR2 **
  1.Support SiS630E chipset. 
  2.Set some MII default values for 630E0.
  3.For initializing face, wait for PHY auto-negotiation done and then return
    initializing precedure.

** Packet driver **
  1.Support SiS630E chipset.
  2.Set some MII default values for 630E0.

** Windows 9x setup utility **
  1. Fix problem: Uninst.exe delete system's uninst.exe

** Netware server 3.12 **
** Netware server 4.1x **
** Netware server 4.2 **
** Netware server 5.0 **
** Client32 **
  1. Support SiS630E chipset.
  2. Initialize some PHY Registers in SiS630E0.

** Novel Client **
  1. Support SiS630E chipset.
  2. Initialize some PHY Registers in SiS630E0.

** BootRom **
  1. Support SiS630E chipset.
  2. Initialize some PHY Registers in SiS630E0.

** DOS NDIS2 driver **
  1. Support SiS630E chipset.
  2. Fix problem: Copy file very slow to server when TCPIP is loaded.

** OS/2 NDIS2 driver **
  1. Support SiS630E chipset.

** SCO UNIX driver **
  1. Support SiS630E chipset.

1.09 ==> 1.10

** Summary **
  1.Support SiS630S(LAN without EEPROM) chipset.
    Currently, We suport ICS1893 PHY. PHY address should be 1.
  2.Workaround: Adjust Equalizer value for LAN low yield issue.

** Windows 98/98SE **
  1.Fix problem: Blue screen occurs when connect ethernet adapter to ADSL modem.

** Windows Millennium **
  1.Fix problem: Dozer-waker test stop abnormally.

** Windows 9x/2000 setup utility **
  1.Support Windows Millennium
  2.Fix problem: If use setup utility to install driver, the device manager will show
    SiS900 LAN adapter as unsigned(No digital signature).
Download Driver Pack

How To Update Drivers Manually

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.

server: web2, load: 1.25