[data] type=network version="3.11.262" [disks] 1=\mslanman.dos\drivers\ethernet\eth16i,"EtherTeam 16i/32 LAN Support Software Diskette" 2=\ndis3\win,"EtherTeam 16i/32 LAN Support Software Diskette" [netcard] icl$eth16i="ICL EtherTeam 16i Adapter",1391,ndis,ethernet,0x07,eth16i,icl$eth16i_nif icl$eth32="ICL EtherTeam 32 Adapter",1391,ndis,ethernet,0x07,eth16i,icl$eth32_nif [eth16i] ndis2=1:eth16i.dos ndis3=2:eth16i.386 mlid=*:eth16i.com ;-------------------------------------------- ; PROTOCOL.INI keywords for ICL EtherTeam16i. ;-------------------------------------------- [icl$eth16i_nif] drivername=ETH16I$ ; NOTE! The IOAddress is not added by default to PROTOCOL.INI, but ; only if any of the available values is selected. ; io=IOAddress,,text,"0x240,0x260,0x280,0x2A0,0x300,0x340,0x380","AUTO",0x32 ; NOTE! The Interrupt is not added by default to PROTOCOL.INI, but ; only if any of the available values is selected. (It can be even ; commented from this OEMSETUP, because any definition here cannot ; override the Setup value on the adapter). ; irq=Interrupt,,text,"5,9,10,15,","AUTO",0x32 ; NOTE! These parameters are for both NDIS2 and NDIS3 driver. As ; a default they are not added to PROTOCOL.INI. ; param=Transceiver,"Transceiver",text,"BNC,AUI,TP,AUTO","AUTO",0x32 param=TxBuffSize,"TransmitBufferSize",text,"4,8,16","8",0x32 ; NOTE! These parameters are specific to NDIS2 driver only. As a ; default they are not added to PROTOCOL.INI. ; param=MaxTransmits,"MaximumTransmits",int,"6,50,1",6,0x12 ; NOTE! These parameters are specific to NDIS3 driver only. As a ; default they are not added to PROTOCOL.INI. ; param=StagedReceive,"StagedReceive",text,"No,Yes","No",0x22 ; NOTE! The NetAddress parameter overrides the permanent network ; address of the adapter (this feature is hardly ever needed). If ; specified, must be given as a string of excatly 12 characters ; (enclosed in quotes), e.g. "00004B112233". ; ;param=NetAddress,"Net Address",chars,14,,0x17 ;------------------------------------------- ; PROTOCOL.INI keywords for ICL EtherTeam32. ;------------------------------------------- [icl$eth32_nif] drivername=ETH16I$ ; NOTE! The SlotNumber is not added by default to PROTOCOL.INI, but ; only if any of the available values is selected. ; slot=SlotNumber,"Adapter Slot Number",int,"1,8,1",1,0x22 ; NOTE! It is not necessary to give the Interrupt number but the ; driver can resolve it automatically. ; Remove the comment sign if you want it appear in the Setup. ; irq=Interrupt,,text,"3,5,7,9,10,11,12,15,","AUTO",0x32 ; NOTE! These parameters are for both NDIS2 and NDIS3 driver. As ; a default they are not added to PROTOCOL.INI. ; param=Transceiver,"Transceiver",text,"BNC,AUI,TP,AUTO","AUTO",0x32 param=TxBuffSize,"TransmitBufferSize",text,"4,8,16","8",0x32 ; NOTE! These parameters are specific to NDIS2 driver only. As a ; default they are not added to PROTOCOL.INI. ; param=MaxTransmits,"MaximumTransmits",int,"6,50,1",6,0x12 ; NOTE! These parameters are specific to NDIS3 driver only. As a ; default they are not added to PROTOCOL.INI. ; param=StagedReceive,"StagedReceive",text,"No,Yes","No",0x22 ; NOTE! The NetAddress parameter overrides the permanent network ; address of the adapter (this feature is hardly ever needed). If ; specified, must be given as a string of excatly 12 characters ; (enclosed in quotation marks), e.g. "00004B112233". ; ;param=NetAddress,"Net Address",chars,14,,0x17Download 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.