***************************************************************************** Eiger labs, Eiger PC LAN Card Release Version 2.1 July 17, 1997 ***************************************************************************** Thank you for purchasing the Eiger labs, Eiger PC LAN Card. By purchasing the Eiger PC LAN Card, you have invested in one of a line of feature-rich PC Card products from Eiger that offers outstanding features, compatibility and value. BEFORE YOU START WINDOWS 3.X INSTALLATION ------------------------------------------ SETUP.EXE is used only for Windows 3.X installation. DO NOT RUN SETUP.EXE ON WINDOWS 95!!! HOT TIP - Install Card & Socket Services (CSS) on your computer prior to running the SETUP.EXE in Windows 3.X. The Eiger labs, Eiger PC LAN Card requires CSS to operate. All major laptop computers running Windows 3.X are shipped with CSS. If you have problems configuring CSS on your computer or do not have CSS, please contact the Eiger labs, Customer Response Center. *********************************************************************** * Eiger PC LAN Card Enablers and Drivers Technical Notes and Information *********************************************************************** Technical Note 1. There are examples of NET.CFG and PROTOCOL.INI in the respective directory. Use them for the corrent Link Driver Name and override of all other resources such as Interrupt and I/O Port. 2. For PCMCIA card, enablers for DOS and OS/2 will be provided and they are available upon request. Also they are included together with a sample PCMCIA design in this release. 3. Novell directory has the device driver needed for the DOS client connecting to a Netware server, including Netware 3.xx and 4.xx. 4. Under Microsof\wfw311 directory, all the files needed for WfWG 3.11 are included. To install the driver for WfWG, run the Network Setup and choose the "Unlist Adapter". It then prompts for a directory " A:\ " Enter A:\Microsof\wfw311 and hit <return> to going through the installation. *********************************************************************** *** How to use DOS enabler *** *********************************************************************** The enabler can be either the DOS device driver or the DOS executable. As device driver, it has to be installed after the CSS in config.sys. device = dosenab.exe <parameter-list> As the DOS executable, running under DOS prompt with the following: dosenab <parameter-list> example: dosenab /s1 /f=c:\netware\net.cfg <parameter-list> are the command line switches telling the enabler how to use PCMCIA sockets and where to look for the configuration parameters. It should be in order as example. The following switches are supported: 1. Socket selection switch: It will be used by the enabler when Card and Socket Services (CSS) is present that the enabler in OS/2 and the driver is ODI (the ODI driver will use the socket number to get the permanent node address during its initialization). It specifies one socket being available to the enabler. The default setting is socket 1. /sn -- socket n can be used by the enabler, where n ranging from 1 to 2. If this switch is absent, socket 1 is allocated to the enabler. Note: The default setting will cater for most of computer systems where PCIC base address is 0x3e0, and socket 1 is starting from register offset 0 and socket 2 is from 0x40; and databook TCIC base address is 0x240. 2. port selection switch: /Port=xxx : port address. Supported values are 0x200 to 0x3e0 in 0x20-byte boundary. Default setting is 0x300. 3. Interrupt selection switch: /Int=xx : IRQ level. Default setting is 5. The supported values are 3, 4, 5, 7, 9, 10, 11, 12, 14, and 15 for Intel PCIC. 3, 4, 5, 6, 7, 10, and 14 for DataBook TCIC. 4. Memory address selction switch: /Mem=xxxxx: Starting memory address for 16k-byte common memory. Supported values are 0xd0000 to 0xdf000 in 16k-byte boundary. Default setting is 0xd0000. 5. Configuration file selection switch: The file-path tells the enabler where to read the file containing the configuration parameters. The parameters specified in the file will override that in command line. /f=<file-path> If the file name is NET.CFG, the enabler will find the "link driver EGEPX10BT" line in the file (EPX10BT ODI driver's link name is "EGEPX10BT") and use the configuration parameters following the line to enable the Eiger PC LAN Card. The keywords identified by the enabler are as follows: a. port xxx : port address. Supported values are 0x200 to 0x3e0 in 0x20-byte boundary. Default setting is 0x300. b. int x : IRQ level. Default setting is 5. The supported values are 3, 4, 5, 7, 9, 10, 11, 12, 14, and 15 for Intel PCIC. 3, 4, 5, 6, 7, 10, and 14 for DataBook TCIC. c. mem xxxxx: Starting memory address for 16k-byte common memory. Supported values are 0xd0000 to 0xdf000 in 16k-byte boundary. Default setting is 0xd0000. If the file name is PROTOCOL.INI, the enabler will find the "DriverName = EGEPX10BT$" line in the file (the driver name of Eiger PC LAN Card NDIS driver is EGEPX10BT$) and use the configuration parameters followed by the line to enable the Eiger PC LAN card. You MUST make sure that driver name statement should be the first statement in the parameter block. The following keywords in the protocol.ini are identified by the enabler: a. port = xxx : port address. Supported values are 0x200 to 0x3e0 in 0x20-byte boundary. Default setting is 0x300. b. Int = x : IRQ level. Default setting is 5. The supported values are 3, 4, 5, 7, 9, 10, 11, 12, 14, and 15 for Intel PCIC. 3, 4, 5, 6, 7, 10, and 14 for DataBook TCIC. c. Mem = xxxxx: Starting memory address for 16k-byte common memory. Supported values are 0xd0000 to 0xdf000 in 16k-byte boundary. Default setting is 0xd0000. If the other file name is specified, the enabler will directly identify the following keywords as NET.CFG: a. port xxx : port address. Supported values are 0x200 to 0x3e0 in 0x20-byte boundary. Default setting is 0x300. b. int x : IRQ level. Default setting is 5. The supported values are 3, 4, 5, 7, 9, 10, 11, 12, 14, and 15 for Intel PCIC. 3, 4, 5, 6, 7, 10, and 14 for DataBook TCIC. c. mem xxxxx: Starting memory address for 16k-byte common memory. Supported values are 0xd0000 to 0xdf000 in 16k-byte boundary. Default setting is 0xd0000. Example 1: As DOS TSR interfacing to CSS. At DOS prompt, use the following command line: dosenab.exe /s1 /f=\windows\protocol.ini Assume PROTOCOL.INI contains the following parameter lines: [PROTMAN_MOD] DriverName = PROTMAN$ [DXMAIDXCFG] ...... [EGEPX10BT_MOD] DriverName = EGEPX10BT$ Port = 0x300 Int = 5 The Eiger PC LAN card will be enabled using the following resources: port is 0x300, interrupt is 5, and memory address 0xd0000. ***************************** ** How to Use OS/2 Enabler ** ***************************** a. Install your Socket Services provided by SystemSoft if you would need Card Services (CS). b. Assuming you want to use CSS (Card and Socket Services) in OS/2 Warp connect version 3, you should have the following statements, in the order illustrated, in the config.sys: (assume all drivers are in C: drive): ...... (Card Services) - DEVICE=C:\OS2\PCMCIA.SYS ...... (OS/2 enabler) - DEVICE=C:\Netware\os2enab.os2 <parameter-list> example: device=c:\netware\os2odi /s1 /f=c:\netware\net.cfg note: It should be in order as example. ...... (OS/2 NDIS/ODI driver) - DEVICE=C:\netware\os2odi.SYS ...... (Socket Services) - DEVICE=C:\OS2\IBM2SS02.SYS - DEVICE=C:\OS2\ICRMU02.SYS - DEVICE=C:\OS2\$ICPMOS2.SYS ...... ************************************** ** Technical Notes for OS/2 enabler ** ************************************** a. The enabler will read the configration file specified by configuration file selection switch to enable the LAN card. If NET.CFG is specified, The enabler will find the "link driver EGEPX10BT" statement in the file and use the configuration parameters following the statement to enable the Eiger PC LAN card. BE SURE that there is only ONE occurrence of this statement in the file. If PROTOCOL.INI is specified, the enabler will find the statement "DriverName = EGEPX10BT$" in the file and use the configuration parameters following the statement to enable the Eiger PC LAN card. BE SURE that there is only ONE occurrence of this statement in the file. ******************************************** ** How to use ODI drivers in DOS ** ******************************************** a. The ODI drivers should be executed after the enabler. For instance: SET NWLANGUAGE=ENGLISH rem PCMCIA dos enabler begin d:\netware\os2enab.exe /s1 /f=d:\netware\net.cfg rem PCMCIA dos enabler end D:\netware\LSL.COM D:\netware\dosodi.COM D:\netware\IPXODI.COM D:\netware\VLM.EXE b. The link driver name is EGEPX10BT in net.cfg, and its parameter keywords in net.cfg are defined as in ODI spec.: a. link driver EGEPX10BT b. interrupt: default is 5 INT xx c. IO port address: Supported values are 0x200 to 0x3e0 in 0x20- byte boundary. Default setting is 0x300. PORT xxx d. memory address: supported values are from 0xd0000 to 0xdf000 with 16k-common memory. Default is 0xd0000. MEM xxxxx e. node address override: NODE ADDRESS xxxxxxxxxxxx For instance: LINK DRIVER EGEPX10BT INT 5 PORT 0x320 MEM 0xd0000 NODE ADDRESS 001234567890 *************************************************** ** How to use ODI 2.0.1 driver for OS/2 ** *************************************************** a. The driver should be executed after the enabler. There is a sample file "config.sys", list the order for PCMCIA card service, PCMCIA enabler and device driver. b. The driver's name is EGEPX10BT$ in net.cfg, and its parameter keywords in net.cfg is defined as follows: a. driver name: DriverName = EGEPX10BT$ b. interrupt: default is 5 INT = xx c. IO port address: Supported values are 0x200 to 0x3e0 in 0x20-byte boundary. Default setting is 0x300. PORT = xxx d. memory address: supported values are from 0xd0000 to 0xdf000 with 16k-common memory. Default is 0xd0000. MEM = xxxxx e. node address override: NODE_ADDRESS = string For instance: DriverName = EGEPX10BT$ INT = 5 PORT = 0x320 MEM = 0xd0000 NODE_ADDRESS = "001234567890" Note: the drivername statement should be the first line in this parameter block. ********************************** ** Use EGEPX10BT Packet Driver ** ********************************** a. The enabler (dosenab.exe) should be loaded before packet driver is executed. b. Packet driver is DOS executable. At DOS prompt, use the following command line: pktdrv <parameter-list> c. The parameter-list include the following switches starting with slash '/': 1. swint=xx -- the software interrupt used by the packet. The default is 0x62. 2. node address=xxxxxxxxxxxx -- node address overrided 3. port=xxx -- port address. Default is 0x300. 4. int=xx -- interrupt level, default is 11. 5. mem=xxxxx -- memory address. Default is 0xd0000. 6. parameter file switch f=<file-path> -- specify the file which define the above parameters used by packet driver. The parameters specified in the file will override that in the command. For examble, use the following command line to start packet driver: pktdrv /swint=0x63 /f=pktdrv.ini Assume file PKTDRV.INI: port 0x300 int 5 mem 0xd0000 The driver will use port address 0x300, interrupt 10 and memory address 0xd0000; and software interrupt is 0x63. ***************************************************************************** Release Note For PCMCIA CIS Utility HARDWARE SPECIFICS 1. Plug the PCMCIA Extender Card to the second socket of PCMCIA Card Reader. 2. Plug Eiger PC LAN Card to the PCMCIA Extender Card socket. 3. Before programming CIS, turn the switch on PCMCIA Extender Card to ON position. 4. Run \utility\CIS.BAT under DOS environment. It will program the Eiger PC LAN Card automatically. 5. The hardware may be used as a regular PCMCIA Extender Card, when turn the switch to OFF position. 5. Every time before program new LAN PC Card, programmer need to increase NETDATA file contains by one. NOTE : The batch file CIS.BAT may not execute properly under high speed CPU (e.g. Pentium 100Mhz). We recommand that CPU do not over 75Mhz or 486 will be fine for the execution. *****************************************************************************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.