Ethernet PCMCIA Adapter Driver Support
TOPICS
======
1. Netware DOS/ODI Driver
2. NDIS Driver
3. LAN Manager
4. LAN Server (IBM LAN Requester)
5. DEC Pathworks
6. SUN PC-NFS
7. Windows For Workgroups 3.11
8. Banyan VINES
9. Packet Driver
10. PC-NFS
11. Microsoft Windows 95
12. Micorsoft Windows NT 3.5x and upper version
13. Lantasti system.
***************************************************************
* TOPIC: 1 *
* Netware DOS/ODI Driver *
***************************************************************
This section is an explanation of the files contained in the
\NETWARE subdirectory of this diskette. For more information,
please refer to the "NOVELL NetWare ODI Shell for DOS" manual.
LSL.COM:
This file implements the Link Support Layer for DOS ODI
(Open Data-Link Interface) workstations, and is the program that
is generally loaded first after booting. The Link Support Layer
file enables the workstation to support several protocols.
PCMMLID.COM
This is the MLID (Multiple Link Interface Driver) driver that
handles the sending and receiving of packets to and from the
Ethernet adapter. This driver is contained in directory
\NETWARE\DOSODI. It supports NetWare 3.x and 4.x, NetWare Lite,
and other ODI interface applications.
IPXODI.COM:
This is Novell's protocol stack for DOS/ODI workstations.
It performs the same functions as what IPX.COM does for DOS
workstations. It is loaded after the MLID driver.
NETx.COM
Netware workstation shell.
You can copy all these files to a directory, and then enter the following
commands:
LSL <Enter>
PCMMLID <Enter>
IPXODI <Enter>
NETx <Enter>
You can then login to a file server.
A batch file, STARTNET.BAT, with the above commands is included
in the \NETWARE directory for your convenience.
Normally, you do not need the configuration file, NET.CFG, because the
established defaults should be adequate. One exception is when your
workstation has more than one adapter. In this situation, for each
adapter, there must exist a separate MLID section in the NET.CFG file.
Below is a sample NET.CFG file:
link driver PCMMLID
port 300
int 5
frame Ethernet_802.2
frame Ethernet_802.3
frame Ethernet_II
frame Ethernet_snap
protocol IPX 0 Ethernet_802.2
-- THE END --
***************************************************************
* TOPIC: 2 *
* NDIS Driver *
***************************************************************
NDIS Driver Installation Overview
=================================
The drivers contained in directories \MSLANMAN.DOS and \NDIS are
used with this Ethernet PCMCIA adapter in the Network Driver
Interface Specification (NDIS) environment.
The driver "ETHPCM.DOS" conforms to NDIS 2.0 Specification
defined by Microsoft/3Com. It is used with 3Com's 3+Open,
Microsoft's OS/2 LAN Manager OEM, distribution packages Release
1.x or 2.x, and other compatible OEM versions of LAN Manager.
The driver "ETHPCM.OS2" is used with IBM's LAN Server products
in the IBM OS/2 version 2.1 and above environment.
File Descriptions:
\MSLANMAN.DOS\DRIVERS\PCMCIA\ETHPCM\
ETHPCM.DOS DOS NDIS 2 MAC driver
PROTOCOL.INI A sample section of the PROTOCOL.INI file
\MSLANMAN.DOS\DRIVERS\NIF\
ETHPCM.NIF Network Information File for LAN Manager
\NDIS
README.TXT This file
\NDIS\DOS
PCMCIAD.NIF Network Information File for LAN Server (DOS)
ETHPCM.DOS DOS NDIS 2 MAC driver
OEMSETUP.INF Network Information File for Windows for Workgroups
PROTOCOL.INI A sample section of the PROTOCOL.INI file
\NDIS\OS2
PCMCIAO.NIF Network Information File for LAN Server (OS/2)
ETHPCM.OS2 OS/2 2.1 NDIS 2 driver for IBM LAN Server
(1) Hardware checking
Proper hardware operation can be verified by running the
diagnostic program CARDTEST.EXE in the \DIAG directory under DOS.
(2) Sample PROTOCOL.INI file and parameters
[ETHPCM_NIF]
; Default section of PROTOCOL.INI file for the Adapter
drivername = ETHPCM$
irq = 5
iobase = 0x300
; End of this sample file
Several parameters are included in the ETHPCM_NIF section of the
PROTOCOL.INI file. However, the only required parameter is
"drivername".
irq Specifies the interrupt channel used by the adapter.
Acceptable values for this parameter are 2, 3, 4, 5,
10, 11, 12, and 15.
iobase Specifies the iobase address used by the adapter.
This parameter is given in hexadecimal values.
Acceptable value for this parameter are 0x240, 0x280,
0x2C0, 0x300, 0x320, 0x340, 0x360.
(3) Additional Parameters in the PROTOCOL.INI file for
the NDIS Driver Configuration
Keyword Parameter
MaxMultiCast 1 .. 1000 Default 10
Maximum number of MultiCast Addresses.
This configures the size of the MultiCast
Address Table.
MaxRequests 6 .. 64 Default 8
Maximum number of outstanding General Requests.
This configures the size of the General Request
Queue.
MaxTransmits 6 .. 64 Default 12
Maximum number of outstanding TransmitChain commands.
This configures the size of the TransmitChain Request
Queue.
ReceiveChains 6 .. 96 Default 12
Maximum number of outstanding ReceiveChain commands.
This configures the size of the ReceiveChain Request
Queue.
ReceiveBuffers6 .. 96 Default 12
Configures the number of the Receive buffers in the
Receive Buffer Pool.
TransmitBufSize 128 .. 1514 Default 1514
Configures the size (in bytes) of buffers in the
Transmit Buffer Pool.
*****
Note : Values for the preceding parameters are seldom changed by
the user. Most of the time, the default values are used.
*****
(4) The following describes installation steps for ETHPCM.OS2
under OS/2 2.1 and the IBM LAN Server environment.
Before attempting to install the driver, the user should have installed
the Card Service and Socket Service drivers properly.
In OS/2 2.1, the card service driver PCMCIA.SYS is included in the
retail package. The socket service driver is supplied by notebook
vendors. Each notebook needs a socket service driver that adapts to
the specific hardware configuration of the notebook.
The user should contact the notebook vendor or IBM about which socket
service driver to use. IBM also puts the latest version of many drivers
on its Compuserve OS/2 forum and Internet FTP sites for the user to
download.
This version of the OS/2 driver needs to have a supported Ethernet Adapter
in the PCMCIA socket at system bootup time. During the course of
operation, if the adapter is removed, the network will cease to function.
The rest of the system will not be disturbed.
Note that since OS/2 does not have PCMCIA support until version 2.1, this
driver does not work under previous versions of OS/2.
OS/2 LAN Server 3.0 and upper version Installation
==================================================
1. Copy ETHPCM.OS2 and PCMCIAO.NIF files from the
Driver diskette (\NDIS\OS2) to D:\IBMCOM\MACS.
D is the drive where the LAN Adapter and Protocol Support (LAP)
is installed.
2. Click the OS/2 LAN Service icon.
3. Select "Installation and configuration." The IBM logo appears.
4. Click <OK>.
5. Select <Advance> and press <Enter>.
6. Select "Install or Configuration this Workstation."
7. Select "server type", "adding a server or domain controller".
The "install or remove" selections appears.
8. Select "Configure a component."
9. Click the "Configure" button.
10. Select "Configure workstation."
11. Select "Ethernet PCMCIA Adapter" when prompted to identify your
Network Adapter. Click the <Add> button.
12. Select "802.2" from the list and click the <Add> button.
13. Select "IBM NETBIOS" from the list and click the <Add> button.
14. Select <OK> to confirm all the selections.
15. Follow the instructions to complete the process.
Select <OK> to accept default selections.
16. Continue pressing <OK> until your screen prompts you to backup
old CONFIG.SYS and AUTOEXEC.BAT and create a new CONFIG.SYS
and AUTOEXEC.BAT. Select <OK> to confirm.
17. The default interrupt number for the Ethernet PCMCIA
Adapter is 5, and the default I/O base address is 0x300.
If you are contented with the default settings, skip to step 18,
otherwise you have to modify the \IBMCOM\PROTOCOL.INI file.
Find the [pcmciao_nif] section in this file, and add the
'irq' and 'iobase' entries under this section as exemplified
below:
[pcmciao_nif]
DriverName = ETHPCM$
irq = 5
iobase = 0x300
18. The installation is complete. Reset your PC.
Sample OS/2 CONFIG.SYS
==========================
RUN=D:\IBMCOM\PROTOCOL\NETBIND.EXE
RUN=D:\IBMCOM\LANMSGEX.EXE
DEVICE=D:\IBMCOM\PROTOCOL\NETBEUI.OS2
DEVICE=D:\IBMLAN\NETPROG\RDRHELP.200
IFS=D:\IBMLAN\NETPROG\NETWKSTA.200 /I:D:\IBMLAN /N
DEVICE=D:\IBMCOM\PROTOCOL\NETBIOS.OS2
DEVICE=D:\IBMCOM\PROTOCOL\LANDD.OS2
DEVICE=D:\IBMCOM\PROTOCOL\LANDLLDD.OS2
DEVICE=D:\IBMCOM\MACS\ETHPCM.OS2 ---> PCMCIA Adapter OS/2 driver
RUN=D:\IBMCOM\PROTOCOL\LANDLL.EXE
REM ************* P C M C I A S E C T I O N **************
BASEDEV=PCMCIA.SYS ----> Card Service. Comes with OS/2 2.1
BASEDEV=NEC2RMU1.SYS ----> Resource Map Utility for your notebook
BASEDEV=IBM2NEC1.SYS /s0=2 ----> Socket Service Driver for your notebook
BASEDEV=PCM2ATA.ADD
DEVICE=D:\OS2\AUTODRV2.SYS D:\OS2\AUTODRV2.INI
DEVICE=D:\OS2\MDOS\VPCMCIA.SYS
REM ********* E N D P C M C I A S E C T I O N *********
RUN=D:\IBMLAN\NETPROG\LSDAEMON.EXE
Sample LAN Server PROTOCOL.INI file
===================================
[PROT_MAN]
DRIVERNAME = PROTMAN$
[IBMLXCFG]
pcmciao_nif = pcmciao.nif
LANDD_nif = LANDD.nif
NETBEUI_nif = NETBEUI.nif
[LANDD_nif]
DriverName = LANDD$
Bindings = pcmciao_nif
ETHERAND_TYPE = "I"
SYSTEM_KEY = 0x0
OPEN_OPTIONS = 0x2000
TRACE = 0x0
LINKS = 8
MAX_SAPS = 3
MAX_G_SAPS = 0
USERS = 3
TI_TICK_G1 = 255
T1_TICK_G1 = 15
T2_TICK_G1 = 3
TI_TICK_G2 = 255
T1_TICK_G2 = 25
T2_TICK_G2 = 10
IPACKETS = 250
UIPACKETS = 100
MAXTRANSMITS = 6
MINTRANSMITS = 2
TCBS = 64
GDTS = 30
ELEMENTS = 800
[NETBEUI_nif]
DriverName = netbeui$
Bindings = pcmciao_nif
ETHERAND_TYPE = "I"
USEADDRREV = "YES"
OS2TRACEMASK = 0x0
SESSIONS = 40
NCBS = 95
NAMES = 21
SELECTORS = 5
USEMAXDATAGRAM = "NO"
ADAPTRATE = 1000
WINDOWERRORS = 0
MAXDATARCV = 4168
TI = 30000
T1 = 500
T2 = 200
MAXIN = 1
MAXOUT = 1
NETBIOSTIMEOUT = 500
NETBIOSRETRIES = 8
NAMECACHE = 0
PIGGYBACKACKS = 1
DATAGRAMPACKETS = 2
PACKETS = 350
LOOPPACKETS = 1
PIPELINE = 5
MAXTRANSMITS = 6
MINTRANSMITS = 2
DLCRETRIES = 5
[pcmciao_nif]
DriverName = ETHPCM$
irq = 5
iobase = 0x300
-- THE END --
***************************************************************
* TOPIC: 3 *
* LAN Manager *
***************************************************************
NDIS Driver for LAN Manager Installation
==========================================
1. Installation Procedure for LAN Manager V2.0
--------------------------------------------------
a. Type Setup In the Lan Manager Directory. Press <Enter>.
b. Press <Enter>.
c. Select "Import Network Drivers..." in "Action". Press <Enter>.
d. Enter the source drive name. (A:\> or B:\>).
e. Insert Driver Disk in the specific drive. (A:\> or B:\>). Press <Enter>.
"Import Network Drivers" appears.
f. Press <SPACEBAR> to select Network Adapter Card, "PCMCIA
Adapter Card". Press <Enter>.
g. Press the <NO> button.
h. Press <Enter> three times. "Network Driver" appears.
i. Select "PCMCIA Ethernet Card" in "Network Adapter Cards" selection
menu, then press the <Add driver> button. Press <Add protocol>.
Press <OK>. "Workstation Primary parameters" appears. Press <OK>.
j. Press <OK> three times.
k. Select "Save" in "Action".
l. Press <F3> to Exit.
*******************************************************************************
2. Installation Procedure for LAN Manager V2.1
--------------------------------------------------
a. Type "lmsetup" In the LanManager Directory.
Microsoft LAN Manager Setup appears.
b. Select "Network Drivers..." in " Configuration ".
c. Select <Add New Configs>. Press Enter.
"Network Adapter Driver" appears.
d. Select <Other Driver>. Press Enter.
e. Insert the Driver Disk in either A: or B:. Enter the
drive name (A:\> or B:\>). Push the <OK> button.
f. Select the available Network Adapter Driver, PCMCIA Ethernet adapter.
Push <OK> button.
g. Press the SPACEBAR to select the protocol.
h. Push the <OK> button. "Configuration Complete" appears.
i. Push the <Save> button.
j. Press "F3" to exit.
k. Press Enter.
Sample configuration files:
3. CONFIG.SYS
a. <V2.0>
LASTDRIVE=Z
BUFFERS = 35
FILES = 35
SHELL=C:\DOS50\COMMAND.COM C:\DOS50\e:1000 /p /E:1024
DEVICE=C:\HIMEM.SYS
DEVICE=C:\DOS50\SETVER.EXE
DOS=HIGH,UMB
DEVICE=C:\LANMAN.DOS\DRIVERS\PROTMAN\PROTMAN.DOS /i:C:\LANMAN.DOS
DEVICE=C:\LANMAN.DOS\DRIVERS\PCMCIA\ETHPCM\ETHPCM.DOS
DEVICE=C:\LANMAN.DOS\DRIVERS\PROTOCOL\NETBEUI\NETBEUI.DOS
b.<V2.1>
LASTDRIVE=Z
BUFFERS = 35
FILES = 35
SHELL=C:\DOS50\COMMAND.COM C:\DOS50\e:1000 /p /E:1024
DEVICE=C:\HIMEM.SYS
DEVICE=C:\LANMAN.DOS\DRIVERS\DOSUTILS\EMM386.EXE NoEMS
DEVICE=C:\DOS50\SETVER.EXE
DOS=HIGH,UMB
DEVICE=C:\LANMAN.DOS\DRIVERS\PROTMAN\PROTMAN.DOS /i:C:\LANMAN.DOS
DEVICE=C:\LANMAN.DOS\DRIVERS\PCMCIA\ETHPCM\ETHPCM.DOS
4. PROTOCOL.INI file for LAN Manager.
a. V2.0
[PROTOCOL MANAGER]
DRIVERNAME = PROTMAN$
[NETBEUI_XIF]
Drivername = netbeui$
BINDINGS = "ETHPCM_NIF"
[ETHPCM_NIF]
; PROTOCOL.INI for PCMCIA ethernet adapter
drivername = ETHPCM$
irq = 5
iobase = 0x300
; End of this sample file
b. V2.1
[PROTMAN]
DRIVERNAME = PROTMAN$
DYNAMIC = YES
PRIORITY = NETBEUI
[NETBEUI_XIF]
Drivername = netbeui$
SESSIONS = 6
NCBS = 12
BINDINGS = "ETHPCM_NIF"
LANABASE = 0
[ETHPCM_NIF]
; PROTOCOL.INI for PCMCIA ethernet adapter
drivername = ETHPCM$
; irq = 5
; iobase = 0x300
; End of this sample file
5. AUTOEXEC.BAT file for LAN Manager.
a. V2.0
@echo off
PROMPT $P$G
PATH=c:\PE2;C:\DOS50;C:\NC;
APPEND=C:\PE2;C:\DOS50;
REM ====== LANMAN 2.0 === DO NOT MODIFY BETWEEN THESE LINES ===== LANMAN 2.0 ====
SET PATH=C:\LANMAN.DOS\NETPROG;%PATH%
C:\LANMAN.DOS\DRIVERS\PROTMAN\NETBIND
NET START WORKSTATION
REM ====== LANMAN 2.0 === DO NOT MODIFY BETWEEN THESE LINES ===== LANMAN 2.0 ====
b. V2.1
@echo off
PROMPT $P$G
PATH=c:\PE2;C:\DOS50;C:\NC;
APPEND=C:\PE2;C:\DOS50;
@REM ====== LANMAN 2.1 === DO NOT MODIFY BETWEEN THESE LINES === LANMAN 2.1 ===
SET PATH=C:\LANMAN.DOS\NETPROG;%PATH%
NET START WORKSTATION
LOAD NETBEUI
@REM ====== LANMAN 2.1 === DO NOT MODIFY BETWEEN THESE LINES === LANMAN 2.1 ===
-- THE END --
***************************************************************
* TOPIC: 4 *
* LAN Server *
***************************************************************
NDIS Driver for LAN Server Installation
=========================================
1. DOS LAN REQUESTER
-------------------------------------
a. At the DOS prompt, insert the IBM LAN Support Program (LSP)
Version 1.30 (or 1.31) Diskette into your disk drive. (A: or B:)
b. Type "dxmaid" at the A:\> or B:\> prompt, then press <Enter>.
The IBM logo appears. Press <Enter>.
c. Press <Enter> twice. The Environment Information screen appears.
d. Specify the following values for the fields on this screen:
Use <Space Bar> to toggle between choices:
Configuration for this computer? Yes
Use existing configuration information? Yes
Do you have adapter option diskettes? Yes
Are you configuring for two adapters? No
Do you need 802.2 interface support? Yes
Enter the proper drive and directory values to the fields below:
Source for LSP A:\
Target for new configuration C:\lsp
e. Make sure the values are correct. Press <Enter> to save your choices.
"Process Adapter Option Diskette" screen appears.
f. Insert the Driver Diskette in your source drive and specify the
path: A:\NDIS\OS2 (or b:\NDIS\OS2). Press <Enter>.
g. The necessary files are copied from the Driver Diskette to your
target directory on the hard disk.
h. Press <Enter> three times.
i. Insert the LSP diskette and press <Enter>.
The "Current Configuration" screen appears with the PCMCIA
series adapter and protocols already selected ("IBM IEEE 802.2"
and "IBM OS/2 NETBIOS").
j. Press F4. LSP is installed completely.
k. Use a text editor to edit the CONFIG.SYS file. Specify at least
20 files in the FILES= line, like this:
FILES=20
Save the CONFIG.SYS file, and reboot the computer.
l. Insert the DOS LAN Requester Install Diskette 1.
m. Type "install". Wait for IBM logo to appear.
n. Press <Enter> twice more.
The program prompts you for the pathname of the DOS LAN
Requester directory.
o. Specify the pathname for the DOS LAN Requester directory.
(C:\DOSLAN is the default.) Press <Enter>.
The program asks you which services you require.
p. Highlight either the "Send messages" or "Send, View, Edit, and
Log messages" option. (Normally, you select the second option.)
Press <Enter> to confirm your choice.
q. Specify the machine's ID and the domain ID. The domain ID must
be the domain server ID and must be the same for all
workstations on the network.
r. Follow the prompts to complete the installation.
---THE END----
***************************************************************
* TOPIC: 5 *
* DEC PATHWORKS *
***************************************************************
NDIS Driver for DEC Pathworks Installation
==========================================
1. INSTALLATION PROCEDURE:
a. Insert the DEC PATHWORKS Client Setup diskette #1 into your
diskette drive (A: or B:)
b. type Netsetup at the A:> or B:> prompt.
c. Unless you have an LK250 keyboard, Select "NO".
d. Select the DECNET transport option and press <Enter>.
e. Insert the DNET TRNSPRT diskette #1 into the diskette drive (A: or B:).
f. Specify the destination drive letter (C: or D:)
g. Are you creating an initial workstation diskette? Select "NO".
h. Type in the node name and address (i.e. node number). Press <Enter>.
i. Type in the server node name and address (i.e. node number), Press <Enter>.
j. Select "Ethernet" when prompt "Select the network adapter type" appears.
k. Select "(Other NDIS)" when prompt "Select the network adapter" appears.
l. Enter full DRIVE:\PATH\FILENAME for NDIS driver:
A:\ or B:\MSLANMAN.DOS\DRIVERS\PCMCIA\ETHPCM\ETHPCM.DOS
m. Enter full DRIVER:\PATH\ for the PROTOCOL.INI file:
A:\or B:\MSLANMAN.DOS\DRIVERS\PCMCIA\ETHPCM\
n. If they are all accurate, select "WRITE KEY DISK" to start installation.
When prompted to copy files ETHPCM.DOS and PROTOCOL.INI, please insert
driver program diskette in drive
A: or B: depending on the path set at step l. and m.
o. Follow the prompts until installation is complete.
p. At the Configuration screen, press F10 to exit.
q. Use a text editor to edit PROTOCOL.INI at the DECNET sub-directory.
Remove the semicolon (;) from the statement "NI_IRQ = 5"
under [DATALINK], then check if the IRQ value in
the new [ETHPCM.DOS] IRQ statement (maybe omitted) matches the NI_IRQ
value in the [DATALINK] statement and the Adapter IRQ setting.
Sample configuration files:
2. CONFIG.SYS
shell=c:\command.com /P /E:526
device=c:\decnet\hiMEM.sys
device=C:\dos\EMM386.EXE ram 1024
dos=high, UMB
devicehigh=c:\decnet\protman.sys /I:D:\DECNET
devicehigh=c:\decnet\ethpcm.dos
rem device=c:\decnet\nddrv.sys
rem device=c:\decnet\npdrv.sys
FILES=50
BUFFERS=50
LASTDRIVE=v
STACKS=9,256
3. PROTOCOL.INI file for PATHWORKS v 4.1
; PROTOCOL.INI file created by DNETOMO.V41 V4.1.060
; via DNETWIK.V41 V4.1.047
[protocol manager]
DRIVERNAME = PROTMAN$
[IPX4MAC]
DRIVER = IPX$MAC
BINDINGS = ETHPCM.DOS
[DATALINK]
DRIVERNAME = DLL$MAC
LG_BUFFERS = 16
SM_BUFFERS = 6
OUTSTANDING = 32
HEURISTICS = 0
BINDINGS = ETHPCM.DOS
;Specify IRQ level used by workstations network adapter
NI_IRQ = 3
[ETHPCM.DOS]
; PROTOCOL.INI for ETHERCoax/Pair-NE(2) adapter
drivername = ETHPCM$
; irq = NI_IRQ = Adapter IRQ Setting
irq = 5
iobase = 0x300
; End of this sample file
4. AUTOEXEC.BAT
echo off
break on
cls
prompt $p$g
REM Insert any keyboard internationalization and character set information here.
if not exist \decnet\STARTNET.BAT goto nostartup
call \decnet\STARTNET
goto end
:nostartup
echo ** WARNING ** STARTNET.BAT file not found. Network functions not performed
-- THE END --
***************************************************************
* TOPIC: 6 *
* SUN PC-NFS *
***************************************************************
NDIS Driver for SUN PC-NFS Installation
=========================================
1. INSTALLATION PROCEDURE
a. Add Device=c:\dos\ansi.sys command at CONFIG.SYS. Reboot PC.
b. Insert the PC-NFS Installation diskette into the diskette drive (A: or B:)
and type "install" <Enter>.
c. Enter the "destination Drive letter:" (usually C:).
d. Select "Ethernet".
e. Select the "NDIS" option of "Ethernet Adapter" menu.
f. Follow all the prompts.
g. Specify the PC name, IP address, server name, and server
IP address.
h. Follow all the prompts to finish the installation.
i. The system creates \LANMAN and \NFS directories on the destination drive.
j. Copy the ETHPCM.DOS file from the
subdirectory \MSLANMAN.DOS\DRIVERS\PCMCIA\ETHPCM on your
driver program diskette to the \LANMAN (C: or D:)
directory on your destination drive.
k. Use a text editor, edit the CONFIG.SYS file. Add this
line above the NFS_NDIS driver entry:
DEVICE=C:\LANMAN\ETPCME.DOS
l. Edit the PROTOCOL.INI file at \LANMAN directory.
1). Replace [your-mac-module] with [ETHPCM]
2). Replace drivername = YOURMAC$ with drivername = ETHPCM$
Specify the correct IRQ and IOBASE values (May be omitted)
for this adapter.
IRQ = 5
IOBASE = 0x300
...
3). Replace bindings = YOUR-MAC-MODULE with bindings = ETHPCM$
m. Reboot the computer.
n. Use NFSCONF.EXE to mount a virtual drive, or TELNET.EXE to do terminal
emulation.
Sample configuration files:
2. CONFIG.SYS
shell=c:\command.com /P /E:526
dos=high, UMB
rem ----pcnfs install
Device=c:\dos\ansi.sys
DEVICE=C:\NFS\PCNFS.SYS /m
DEVICE=C:\NFS\SOCKDRV.SYS
DEVICE=C:\LANMAN\PROTMAN.SYS /i:C:\LANMAN --> specify PROTOCOL.INI directory.
device=C:\LANMAN\ETHPCM.DOS -----------> NDIS driver name
DEVICE=C:\LANMAN\NFS-NDIS.SYS
FILES=50
BUFFERS=50
LASTDRIVE=v
STACKS=9,256
3. PROTOCOL.INI at \LANMAN directory
[protocol manager]
drivername = PROTMAN$
[ETHPCM]
drivername = ethpcm$
irq = 5
iobase = 0x300
[NFS-NDIS]
drivername = NFSLINK1
bindings = ETHPCM
4. AUTOEXEC.BAT
...
SET TZ=PST8
SET path=C:\;C:\NFS;C:\LANMAN
SET NFSDRIVE=D
C:lanman\netbind ----> Add this line to Binding NDIS driver
PRT *
NFSRUN
-- THE END --
***************************************************************
* TOPIC: 7 *
* Windows for Workgroups 3.11 *
***************************************************************
NDIS Driver for Windows for Workgroups 3.11 Installation
=========================================================
1. INSTALLATION PROCEDURE
a. Select "Control Panel" icon in Main group in the Windows environment.
b. Select "Network" icon.
c. Select "Adapters" item in "Option" dialog.
d. push <Add> button.
e. Select "Unlisted or Updated Network Adapter" .
"install driver" appears.
f. Type in the drive and path name where the NDIS driver resides
(e.g. A:\ndis\dos or B:\ndis\dos.)
g. Insert the Driver Disk in the specified drive.
h. press <OK>.
i. press <close>.
j. press <OK> twice.
k. Restart computer.
2. Example of CONFIG.SYS file
FILES=30
buffers=30
STACKS=9,256
DEVICE=c:\windows\HIMEM.sys
device=C:\WINDOWS\protman.dos /i:C:\WINDOWS
device=C:\WINDOWS\workgrp.sys
device=C:\WINDOWS\ethpcm.dos
LASTDRIVE=y
3. Example of PROTOCOL.INI file in Windows for Workgroups
[network.setup]
version=0x3100
netcard=pcmciad,1,PCMCIAD
transport=ms$netbeui,MS$NETBEUI
lana0=pcmciad,1,ms$netbeui
[protman]
DriverName=PROTMAN$
PRIORITY=MS$NETBEUI
[PCMCIAD]
DriverName=ETHPCM$
[MS$NETBEUI]
DriverName=netbeui$
SESSIONS=10
NCBS=32
BINDINGS=PCMCIAD
LANABASE=0
4. Example of autoexec.bat
C:\WINDOWS\SMARTDRV.EXE
C:\WINDOWS\net start
@ECHO OFF
PROMPT $p$g
PATH C:\WINDOWS;
SET TEMP=C:\WINDOWS\TEMP
-- THE END --
***************************************************************
* TOPIC: 8 *
* Banyan VINES *
***************************************************************
NDIS Driver for Banyan VINES Installation
=========================================
1. Installation Procedure for Banyan VINES
---------------------------------------------
a. Type Pcconfig <Enter>.
"Configuring A PC for the Network" appears.
b. Select "1 - Network Card Setting".
"The possible hardware configuration option are" appears.
c. Select "NDIS Ethernet".
d. Enter the interrupt number, and PCMCIA to the "PROTOCOL bindings =" prompt.
e. Press 'F10' when done. Press <Esc> to exit this screen.
f. Select "2 - Login Environment Settings."
g. Select "1 - Select Default Communications Driver."
h. Select "NDIS Ethernet". Press <Esc> to exit.
i. Press 'F10' when all done.
"Please wait ...." appears.
j. Modify the CONFIG.SYS and PROTOCOL.INI files as needed.
Sample configuration files:
2. CONFIG.SYS
device=c:\banyan\protman.dos/i:c:\banyan
device=c:\banyan\ethpcm.dos
3. PROTOCOL.INI file
[protocol manager]
DriverName = PROTMAN$
[PCMCIA]
DriverName = ethpcm$
-- THE END --
***************************************************************
* TOPIC: 9 *
* Packet Driver *
***************************************************************
Packet Driver Installation
==========================
To load the packet driver, type PCMPD 0X60.
PCMPD syntax:
PCMPD [-d] [-n] [-w] [-u] [-h] <PD_INT_NO> [IRQ] [IO_BASE]
where:
[-d] The "-d" option does not start LAN card until this driver is
called by the higher layer programs first.
[-n] Your NOVELL server uses NOVELL ISO-like packets. Your NOVELL
workstation uses NOVELL 8137 packets. You can use this option
to convert NOVELL 8137 packets into NOVELL ISO-like packets.
[-w] Steve Wallace added a hack to let the packet drivers run under
Windows. This is not to be construed with the proper solution,
which is to write a TCP/IP package for Windows.
This hack is enabled only when you use the '-w' switch.
[-u] This option unloads the Packet Driver.
[-h] This option displays the on-line help.
<PD_INT_NO> This specifies the software interrupt (IRQ) where you'll
load the packet driver. It must be in the range 0x60 to 0x80.
The PC/TCP kernel, by default, is loaded at interrupt 0x61 (so
don't load the packet driver there!)
[IRQ] This specifies the hardware interrupt (IRQ) where your card
will be indicated whether the ring buffer is empty or not.
[IO_BASE] This specifies the I/O address .
Example:
The following command line loads the PCMCIA Packet Driver at software
interrupt 60h, I/O address 300, and hardware interrupt 5 (NE2000 MODE).
PCMPD 0x60 5 0x300
Note: The default I/O address is 300.
Note: The default hardware interrupt is 5.
Note: The placement of 0x prior to the parameters. This indicates the
parameter specified is a hexadecimal number.
After the Packet Driver is loaded, you can run the PC/TCP kernel ETHDRV.EXE.
The PC is then ready for PC/TCP communications.
To run PC/TCP applications, You need to load the PC/TCP Kernel
("ETHDRV.EXE").
a. Refer to the PC/TCP manual, Command Reference
section, Chapter 2.3.
b. The following example will load the Kernel and
allocate 8 packet buffers. Increasing the
number of packet buffers (from the default of 5) prevents
packet loss due to buffer shortage.
ETHDRV -p 8 <Enter>
c. At this point, you are ready to run PC/TCP applications
(e.g., 'ftp', 'telnet').
Example: ftp 192.72.24.202
(192.72.24.202 is the host address)
For information regarding the "FTP's PC/TCP Network
Software for DOS" packages, please contact:
FTP Software, Inc.
26 Princess Street
Wakefield, MA 01880
(617) 246-0900
How to Communicate using NCSA Telnet:
1. Make sure you have the correct version of NCSA Telnet
for the PC. You need version 2.3 or later to support
the packet driver interface.
2. Install the NCSA software on your system. Please
refer to the NCSA documentation for detailed instructions.
3. Load Packet Driver (pcmpd 0x60):
a. Refer to the "Packet Driver Syntax" section above.
b. To view the hint screen, type
pcmpd -h <Enter>
c. The following example will load the packet driver
using interrupt vector 60 (hex).
pcmpd 0x60 <Enter>
4. At this point you are ready to run NCSA applications
(e.g., 'ftp', 'telnet', etc.)
Example: ftp 192.72.24.202
(192.72.24.202 is the host address)
For information regarding NCSA's products, please
contact:
National Center for Supercomputing Applications
264 Computing Applications Building
605 E. Springfield Ave.
Champaign, Ill. 61820
(217) 244-0638
telbug@ncsa.uiuc.edu
-- THE END --
***************************************************************
* TOPIC: 10 *
* PC-NFS *
***************************************************************
PC-NFS Software Interface Program Installation
==============================================
The following files will be used in this installation:
Files Contents
--------------------------------------------------------------
PCNFSIF.SYS PC-NFS Software Interface Program
PCMPD.COM Packet Driver
INSTALLATION PROCEDURE:
1. Start the installation process by following the procedure described in the
PC-NFS Manual for installing the Sun Microsystems PC-NFS program in your
PC's hard disk. When asked to identify the type of network interface
card, select "WD8003" from the list. When asked for the
interrupt level and the base I/O address, select:
Interrupt Level (IRQ) 5
I/O Base Address 300h
2. Copy the following files to the \NFS directory on your hard disk:
PCNFSIF.SYS
PCMPD.COM
3. Modify the CONFIG.SYS file to include the following:
DEVICE=C:\ANSI.SYS
DEVICE=C:\NFS\PCNFS.SYS
DEVICE=C:\NFS\SOCKDRV.SYS
DEVICE=C:\NFS\PCNFSIF.SYS
LASTDRIVE=V
4. Create or modify an existing AUTOEXEC.BAT file to include the following:
C:\NFS\PCMPD 98
SET PATH = C:\; C:\NFS
SET TZ=CST6
SET NFSDRIVE=C
PRT *
NFSRUN
For your system to work properly, make sure the C:\NFS\PCMPD 98
command line is placed before the NFSRUN command. For more information
on the PCMPD.COM program, refer to the Packet Driver section elsewhere
in this file.
Allowable values for the software interrupt vector range from 96 to 128.
The default software interrupt vector value is 98.
5. Reboot the PC and start the PC-NFS program. You may now run PC-NFS
commands on your PC to communicate with other computers on the network
that use the TCP/IP protocol.
***************************************************************
* TOPIC: 11 *
* WIN95 *
***************************************************************
NDIS Driver for Microsoft Windows 95
For Ethernet PCMCIA Adapters
======================================
File Descriptions:
ETHPCM.SYS NDIS3 Device Driver For Windows 95.
INSTALLATION PROCEDURE:
1) Insert the PCMCIA Adapter into the slot. The system displays
the "New Hardware Found" window, with "PCMCIA-PCMCIA-ETHERNET-CARD" as
the device name.
2) Select "Drivers from disk provided by hardware manufacturer".
3) At the "Install From Disk" window, enter the drive letter and path
where the device information file (.INF file) and device driver can be
found (e.g. A:\win95). Press "OK". The driver then installs itself.
4) Occasionally, the system may ask for files from the Windows 95
distribution disks. Follow the prompt until the installation is
complete.
5) Reboot the machine to start the network.
***************************************************************
* TOPIC: 12 *
* WINNT *
***************************************************************
NDIS Driver for Microsoft Windows NT
For Ethernet PCMCIA Adapters
========================================
The driver named ETHPCM.SYS is used with Microsoft Windows NT Release 3.5X.and
Windows NT 4.0.
The driver conforms to the Network Driver Interface Specification (NDIS) 3.0.
INSTALLATION PROCEDURE:
1) In the Main group of NT, select the Control Panel icon.
2) In the Control Panel window, select the Network icon.
3) In the Network Settings dialog box, select the Add Adapter button.
The Add Network Adapter dialog box appears.
4) In the list of network cards, select "<other> Requires disk from
manufacturer", and press the <Enter> button.
5) Insert the driver diskette in a diskette drive. Enter drive and
pathname (e.g. A:\) and select the OK button.
6) In the Select OEM Option dialog box, you will see "Ethernet
PCMCIA-Series Adapter" in the menu. Use the OK button to install it.
7) Next, the Network Card Setup dialog box appears.
You must specify the "IRQ level" and "I/O Port Address" of the
adapter.
8) The installation is now complete. The PCMCIA adapter becomes one
of the Installed Adapter Cards and the driver becomes one of the
Installed Network Software. You can see "[0x]Ethernet PCMCIA-Series
Adapter" in the Installed Adapter Cards menu, and "Ethernet
PCMCIA-Series Adapter Driver" in the Installed Network Software menu.
9) The SETUP program has copied ETHPCM.SYS from the A:\WINNT\INTEL35X directory
to C:\WINNT\SYSTEM32\DRIVERS, and the OEMSETNT.INF file from A:\
to C:\WINNT\SYSTEM32; but renamed it to another installation
information file. The next time when you add the PCMCIA adapter
to your system, you do not need the driver diskette again.
10) To complete network installation, remember to bind the adapter to
transport drivers by selecting the "Bindings" button under the
"Network Setting" dialog box.
11) Restart the system to bring up the network.
-- THE END --
***************************************************************
* TOPIC: 13 *
* LANTASTI *
***************************************************************
A) Install drivers for LANtastic 5.0
========================================
Using NDIS driver:
------------------
For NDIS driver, It support "ETHPCM.DOS" driver for PCMCIA product
series. User can use "ETHPCM.DOS" driver to replace AEXNDIS.DOS
which is the NDIS driver offered by ARTISOFT.
Example ----- CONFIG.SYS
DEVICE=C:\LANTASTI\PROTMAN.DOS /I:C:\LANTASTI
DEVICE=C:\LANTASTI\ETHPCM.DOS ------> This Driver
Example ----- AUTOEXEC.BAT / STARTNET.BAT
C:\LANTASTI\AI-NDIS BIND_TO=ETHPCM_NIF
C:\LANTASTI\AILANBIO
C:\LANTASTI\REDIR MachineName
Example ----- PROTOCOL.INI
[PROTMAN]
DRIVERNAME = PROTMAN$
DYNAMIC = YES
[ETHPCM_NIF]
DRIVERNAME = ETHPCM$
Comments:
If you are using PROTMAN.DOS V1.x, you must use the NO_BIND option
on the AI-NDIS command line in the STARTNET.BAT, and you must run
NETBIND.EXE V1.x before AILANBIO.EXE.
B) Install NDIS2 drivers for LANtastic 6.0
==============================================
Using NDIS driver:
------------------
To install NDIS driver "ETHPCM.DOS", user can use LANtastic
6.0 install program, and select "NDIS support for network adapters"
then insert this driver diskette, and type path "A:\LANTASTI".
Install program will search "ETHPCM.DOS" and "PROTOCOL.INI" and copy
these two files to target directory.
IF user already install LANtastic 6.0 and want to install this
PCMCIA adapter, just replace AEXNDIS.DOS with NDIS driver
"ETHPCM.DOS" at CONFIG.SYS
"ETHPCM.DOS" is NDIS driver
"AEXNDIS.DOS" is NDIS driver which supported by ARTISOFT
Example ----- CONFIG.SYS
DEVICE=C:\LANTASTI\PROTMAN.DOS /I:C:\LANTASTI
DEVICE=C:\LANTASTI\ETHPCM.DOS -------> This Driver
Example ----- AUTOEXEC.BAT / STARTNET.BAT
@echo ===== Begin LANtastic configuration =====
SET LAN_CFG=C:\LANTASTI
PATH C:\LANTASTI;%PATH%
SET LAN_DIR=C:\LANTASTI.NET
rem Please obtain the NETBEUI.EXE program from Microsoft
NETBEUI
AI-NDIS BIND_TO=AEXNDIS_NIF
AILANBIO @STARTNET.CFG
REDIR THOMAS @STARTNET.CFG
SERVER C:\LANTASTI.NET @STARTNET.CFG
NET LOGIN \\THOMAS
@echo ===== End LANtastic configuration =====
Example ----- Protocol.ini
[PROTMAN]
Priority=NETBEUI
DriverName = PROTMAN$
Dynamic = Yes
[NETBEUI_XIF]
DriverName = netbeui$
Sessions = 6
NCBS = 12
Bindings = ETHPCM_NIF
LANABASE = 1
[ETHPCM_NIF]
DriverName = ETHPCM$
--------------------------------------------------------------------------------
All trademarks or brand names mentioned are properties
of their respective companies.
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.