Installing D-Link network adapters for MS Windows for Workgroups
================================================================
February 1993
D-Link network adapters are supplied with a driver disk which includes the
NDIS driver. The NDIS driver file naming convention used by D-Link is
<NICtype.DOS>, where NICtype stands for DE650, DE100, DE200, DE220, and etc.
The D-Link NDIS driver programs for DOS are developed following Microsoft
NDIS specification version 2.0.1. This document is a detailed step-by-step
installation procedure for using D-Link network adapters with MS Windows
for Workgroups operating system.
Naming Conventions
==================
1. Starting at this point, we will refer to Windows for Workgroups as
WFW for simplicity. Any appearance of WFW within this text will refer
to the Microsoft Windows for Workgroups operating system.
Installation Procedures
=======================
1. Preinstall WFW using the included Novell NE2000 compatible driver. WFW
will generate a default PROTOCOL.INI and CONFIG.SYS file using the
selected NE2000 network driver.
2. You must modify the generated PROTOCOL.INI and CONFIG.SYS files using
any text editor. (i.e. MSDOS EDIT)
--------- modify PROTOCOL.INI ----------
3. The PROTOCOL.INI file will have multiple references to the "ms$ne2clone"
name. Change all occurances of this name to "D-Link". In a standard
PROTOCOL.INI, there should be a total of 7 replacements.
There would be 4 replacements in the [network.setup] section. Please
take note of the following lines in [network.setup] section,
netcard=...
lana0=...
lana1=...
There will be a [ms$ne2clone] section. This should also be changed to
[D-Link].
In both [MS$NETBEUI] and [MS$IPX] sections, there will be a BINDINGS=
command line. The BINDINGS command must be bound to "D-Link".
4. There will also be a reference to "ms2000$" in the [D-Link] section
which needs to be changed to the D-Link NIC type name. (i.e. DE100$,
DE200$, DE220$, DE300$, DE320$, DE400$, DE600$, DE620$, DE650$, etc.)
5. In the [D-Link] section, the "IOBASE" keyword must be changed to
"IOADDRESS".
The succeeding pages include working sample of CONFIG.SYS and PROTOCOL.
INI files for WFW using D-Link DE-650 network adapter.
--------- modify CONFIG.SYS ----------
6. Modify CONFIG.SYS for PCMCIA card initial:
*** PC installed Socket service, Card services, and Client driver ***
Skip this step.
OR
*** PC installed Socket service or Databook Cardtalk ***
DEVICE=C:\WINDOWS\AE.EXE [/iop:P0] [/mem:P1] [/irq:P2] [/slt:P3]
OR
*** PC's PCMCIA controller is Intel 82365SL ***
DEVICE=C:\WINDOWS\PCIC.EXE [/iop:P0] [/mem:P1] [/irq:P2] [/slt:P3] [/grp:P4]
OR
*** PCr is Toshiba T3300SL ***
DEVICE=C:\WINDOWS\ICCNT.EXE [/iop:P0] [/mem:P1] [/irq:P2]
*** For Phoenix PCM ***
DEVICE= PCMSS.EXE
DEVICE= PCMCCU.EXE
DEVICE= PCMDLINK.COM (irq:5, mem:d600, io base:320, only PCMCCU v1.3 needed)
Please refer to \OPEN_ADP\README.DOC or \install.doc for detail information.
*** parameters description ***
/iop :I/O base
/mem :Attribute memory base
/irq :IRQ value
/slt :Slot type
/grp :Group value
P0 :The selectable window I/O base with 0x20 range.
The default value is 0x300.
P1 :The selectable window memory base.
The default value is 0xd000.
P2 :The selectable irq value.
The default value is 0x5.
P3 :The selectable slot number.
The default number is 1.
P4 :The selectable grp value.
The default value is 0.
Group 0 means Index IO is 3E0h, Data IO is 3E1h, Base is 00h
Group 1 means Index IO is 3E0h, Data IO is 3E1h, Base is 80h
Group 2 means Index IO is 3E2h, Data IO is 3E3h, Base is 00h
Group 3 means Index IO is 3E2h, Data IO is 3E3h, Base is 80h
PCIC.EXE
PCIC.EXE is used to enable Intel 82365SL PC Card Interface Controller
(PCIC) chipset.
ICCNT.EXE
ICCNET.EXE is used to enable ICCNT (I/O Card Controller) chipset in
TOSHIBA T3300SL Model Notebook.
AE.EXE
AE.EXE is used to enable PCMCIA Ethernet Card on which Socket Service has
been installed.
PCMDLINK.COM
PCMDLINK.COM is PCM client driver and only Phoenix PCMCCU v1.3 needed.
7. Your CONFIG.SYS will have the following statement for loading the
"ms2000.DOS" device driver.
DEVICE=C:\WINDOWS\MS2000.DOS
Change this line to load the appropriate D-Link NDIS device driver
of your network adapter. Using D-Link DE-650 adapter, the line would
appear as,
DEVICE=C:\WINDOWS\DE650.DOS
Note: You would have to copy the appropriate D-Link NDIS driver and PCMCIA
initial program to your WFW directory. (i.e. C:\WINDOWS)
D-Link NDIS PROTOCOL.INI User Guide
===================================
This guide lists the available PROTOCOL.INI keywords for all
D-Link NDIS device drivers. Most of the keywords are optional
and have default values. The asterisk symbol (*) indicates the
list of D-Link adapters where the keyword is applicable.
IOADDRESS - This keyword specifies the base I/O port address used
by the D-Link Network Interface Card. This value must
match the base I/O address of printer port on your PC,
if the adapter is DE-620 or DE-600. Otherwise, it must
match the IRQ setting on the NIC. If this keyword is
not present, the default value will be 300h.
* all D-Link network adapters
INTERRUPT - This keyword specifies the interrupt line used by the
D-Link NIC. This value must match the IRQ of printer
port on PC when NIC is DE-620 or DE-600. Otherwise
, this value must match the IRQ jumper setting on the
NIC. If this keyword is not present, the default
value will be 5.
* all D-Link network adapters
DRIVERNAME- This keyword specifies the NIC driver's name. The NIC
driver name follows the NIC adapter type. (i.e. DE100,
DE200, DE220, DE650, etc.)
*all D-Link network adapters
BASEMEMORY- This keyword specifies the mapped memory address used
by the D-Link NIC. This value must match the base
memory jumper setting on your NIC. Base memory will
only be in effect if the remote boot ROM jumper is
enabled.
*DE-100, DE-200
ADAPTERID - This keyword specifies the adapter ID used by D-Link
MCA bus card. This value must match the card ID jumper
setting on your MCA adapter.
*DE-300, DE-320
NETADDRESS- This keyword specifies the node address (hex) used by
your network interface card. This option is used only
if you want to override the node address burned in your
NIC. In this case, the specified address will be used
instead of the NIC's actual node address.
*all D-Link network adapters
Working samples of WFW CONFIG.SYS and PROTOCOL.INI
==================================================
CONFIG.SYS (using D-Link DE-650 NIC)
------------------------------------
:
device=c:\windows\himem.sys
device=c:\windows\pcic.exe <ÄÄÄÄÄÄÄ DE-650 initial program
device=c:\windows\protman.dos /i:c:\windows
device=c:\windows\workgrp.sys
device=c:\windows\msipx.sys
device=c:\windows\de650.dos <ÄÄÄÄÄÄÄ D-Link NDIS driver
:
AUTOEXEC.BAT
------------
:
c:\windows\net start
c:\windows\msipx
c:\windows\netx
:
C:\WINDOWS\PROTOCOL.INI (using D-Link DE-650 NIC)
-------------------------------------------------
[network.setup]
version=0x3100
netcard=D-Link,1,D-Link <ÄÄÄÄÄÄÄ¿
transport=ms$netbeui,MS$NETBEUI | Use D-Link NIC
lana0=D-Link,1,ms$netbeui <ÄÄÄÄÄÄÄÅÄ for Netbios and
transport=ms$ipx,MS$IPX | IPX
lana1=D-Link,ms$ipx <ÄÄÄÄÄÄÄÙ
[protman]
DriverName=PROTMAN$
PRIORITY=MS$NETBEUI
[D-Link] <ÄÄÄÄÄÄ¿
DriverName=de650$ ÃÄ This section for
;INTERRUPT=5 ³ D-Link NIC
;IOADDRESS=0x300 <ÄÄÄÄÄÄÙ
[MS$NETBEUI]
DriverName=netbeui$
SESSIONS=5
NCBS=10
BINDINGS=D-Link <ÄÄÄÄÄÄÄ¿
LANABASE=0 |
|
[MS$IPX] ÃÄ Bind to [D-Link]
DriverName=IPX$ |
MediaType=Novell/Ethernet |
BINDINGS=D-Link <ÄÄÄÄÄÄÄÙ