DriverName = "ELPC656$" ; ; %VER 3Com Megahertz Global 10/100 LAN + 56K Modem CardBus PC Card OEMSETUP.INF v3.0 ; ; below are examples and explanations of some of the keywords supported by ; the NDIS 2.01 driver. most of the lines are simply comments. the ; marked with "-->" are lines that can be edited (removing the ";-->" and ; lines replacing it with spaces, and modifying the right hand side as ; appropriate. ; ;--> IOADDRESS = 0x3800 ; adapter base address (optional) ; If parameter not present in protocol.ini, driver uses the value ; saved from running Diagnostic/Configuration program. ; This parameter is only used to specify a single adapter in a multi- ; adapter configuration. Must match value set by Diagnostic/Config. ; Use 0x400 - 0xFF00 in steps of 0x100 ; ;--> INTERRUPT = 0xA ; interrupt channel number (optional) ; Use 3,5,7,9,0xA,0xB,0xC,0xF ; ; ;--> MAXTRANSMITS=40 ; ; MAXTRANSMITS=n, n=6..50, specifies the number of transmits which can be ; queued up by the driver when the TxFIFO is full or the adapter is otherwise ; busy. When we run out of queue entries, an OUT_OF_RESOURCES error will be ; returned to the protocol on a transmit attempt. Most protocols will handle ; running out of resources will little performance degradation. However, ; some implementations will drop packets and consequently lower performance ; if OUT_OF_RESOURCES is returned too often. The default value is 6, which ; should be sufficient for most cases, and is adequate for window sizes up to ; about 6 or so. On a heavily loaded server with a lot of active connections, ; you may want to increase this number since with large windows on multiple ; active connections you may need a bigger transmit queue to handle them all. ; Each queue entry takes about 128 bytes of memory, so increasing this number ; will increase the resident size of the driver. ; ;--> NETADDRESS="006097123456" ; ; NETADDRESS allows the user to configure the network address of the adapter, ; rather than using the one in EEProm. If not specified the address on the ; adapter will be used. If specified, the right hand side must be exactly ; 12 hex ASCII characters which will be converted to the network address. ; The only restrictions we impose is that the address not have the multicast ; bit set (an odd number in the second digit) and the network address have ; bit one of the most significant byte of the address set. This bit ; signifies a locally administered address. ; ;--> MEMADDRESS=0xD800 ; MEMADDRESS is the adapter memory base address (optional) ; If the parameter is not specified in protocol.ini, driver searches for ; available memory block. Use 0xC000 - 0xE800 in steps of 0x100 ; ;--> FORCESPEED=0 ; ; PXEBIOS keyword needs to be set to 1 if system has a PXE-compliance BIOS. ; ;--> PXEBIOS=0 ; ; FORCESPEED allows the user to force card in 10M, 100M, Half/Full duplex ; or auto mode. ; Valid values are: ; 100 = 100Mbps/Half-duplex mode ; 10 = 10Mbps/Half-duplex mode ; 200 = 100Mbps/Full-duplex mode ; 20 = 10Mbps/Full-duplex mode ; 0 = AutoSense speed mode ; No keyword = AutoSense speed mode ;Download 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.