MS Windows for Workgroups Installation With D-Link Cards ======================================================== There are 3 methods to install D-Link cards with MS Windows for Workgroups. I. Use the driver from a compatible card, that Microsoft provides. For Cards: DA-100, DA-100+, DA-200+, DX-100, DT-100, DT-300, DE-100 series, DE-200 series, DE-205TP, DE-220 series. II. Use the NE2000 Compatible driver, then modify it to use a D-Link driver instead. For Cards: DE-100 series, DE-200 series, DE-205TP, DE-220 series, DE-300 series, DE-320 series, DE-400, DE-600 series, DE-620 series, DE-650 series. III. Use the OEMSETUP.INF file obtained from D-Link's BBS, or your Card's driver disk (NDIS directory). For Cards: DE-100 series, DE-200 series, DE-205TP, DE-220 series, DE-300 series, DE-320 series, DE-400, DE-600 series, DE-620 series, DE-650 series. The D-Link NDIS driver programs for DOS are developed following Microsoft's NDIS specification version 2.0.1. METHOD I: Use the driver from a compatible card, that Microsoft provides. For Cards: DA-100, DA-100+, DA-200+, DX-100, DT-100, DT-300, DE-100 series, DE-200 series, DE-205TP, DE-220 series. 1. Install Windows. (If you have already installed it, then use the Control Panel Icon) 2. When Windows asks for the name of your network card, it will give you a list of the cards Windows already has drivers for. Choose: For the card: ---------------------------- ------------------- IBM Token Ring 4/16Mbs DT-100 IBM Token Ring 4/16Mbs (MCA) DT-300 NE1000 Compatible DE-100 series, DE-220 series (8-bit slot) NE2000 Compatible DE-200 series, DE-205TP, DE-220 series (16-bit slot) SMC ARCNET PC100, PC200 DX-100, DA-100, DA-100+, DA-200+ METHOD II: Use the NE2000 Compatible driver, then modify it to use a D-Link driver instead. For Cards: DE-100 series, DE-200 series, DE-205TP, DE-220 series, DE-300 series, DE-320 series, DE-400, DE-600 series, DE-620 series, DE-650 series. 1. Install Windows. (If you have already installed it, then use the Control Panel Icon) 2. When Windows asks for the name of your network card, it will give you a list of the cards Windows already has drivers for. Choose 'NE2000 Compatible'. 3. After Windows is finished installing, edit the C:\WINDOWS\PROTOCOL.INI text file. You can use DOS 5's EDIT, or Windows Notepad. 4. In the PROTOCOL.INI, there will be a reference to "ms2000$" which needs to be changed to the D-Link card driver name. ex: DE100, DE200, DE300, DE400, DE600, etc. YOU MUST HAVE A $ AFTER THE DRIVER NAME OR IT WILL RETURN MAC00001 ERROR. 5. In the PROTOCOL.INI Section heading [D-Link], the word IOBASE needs to be changed to IOADDRESS. It is advisable to use our supplied PROTOCOL.INI (on the D-Link Driver Disk) as a reference to the [D-Link] section options and settings. IF YOU HAVE A DE-220, DE-400, DE-600, or DE-650 THEN DELETE IRQ and IOADDRESS (IOBASE) LINES . 6. Next edit the C:\CONFIG.SYS text file. You can use DOS 5's EDIT, or Windows Notepad. 7. In the CONFIG.SYS, there will be a statement to load the "ms2000.DOS" device driver. This needs to be changed to the card driver name. ex: DE100.DOS, DE200.DOS, DE300.DOS, etc. 8. Next, copy the D-Link NDIS driver from the D-Link driver floppy to C:\WINDOWS\. This driver is usually located in the A:\NDIS\DOS\ directory. ex: COPY A:\NDIS\DOS\DE200.DOS C:\WINDOWS\ 9. Now reboot the computer to make the new changes take effect. METHOD III: Use the OEMSETUP.INF file obtained from D-Link's BBS. For Cards: DE-100 series, DE-200 series, DE-205TP, DE-220 series, DE-300 series, DE-320 series, DE-400, DE-600 series, DE-620 series, DE-650 series. 1. Get the OEMSETUP.INF file from either the D-Link USA BBS, or by typing it in from the listing below. A. Downloading the OEMSETUP.INF file from the D-Link BBS. (1) Obtain a modem (2) Hook up the modem to your computer and install communication software. ex: Procomm, QModem, etc. (3) Make the modem dial (714) 455-1779 Settings: Bit: 8 Parity: None Stop bits: 1 Baud rate: 9600 or less (4) When you get connected to the BBS, enter your name as a new user. (5) When you get to the Main Menu: (a) Type 'F' then [ENTER] for file section (b) Type 'D' then [ENTER] for download (c) Type 'OEMSETUP.INF' then [ENTER] (d) When it gives a list of Download Protocols, choose the one you want to use. ex: Xmodem. (e) It will start to send the file. Now, you must make your program receive the file. Usually you need to press the [Pg Dn] key. (f) tell your program the file name and the protocol. B. Typing in the OEMSETUP.INF text file, if you can't get it from the D-Link USA BBS. (1) Use a Wordprocessor that can save a file as an ASCII text file. ex: DOS 5's EDIT, etc. (2) Type in the entire file as it is listed at the bottom of this document. (3) Then save it to the name OEMSETUP.INF. (4) Remember what directory you save it to, because Windows will ask you for it later on. 2. Install Windows. (If you have already installed it, then use the Control Panel Icon) 3. When Windows asks for the name of your network card, it will give you a list of the cards Windows already has drivers for. Choose 'Unlisted or Updated Network Adapter'. 4. Now Windows will look for your OEMSETUP.INF file. Tell it the directory where you put it. (Using the BROWSE button makes it easier.) 5. Next it will look for the .DOS file. Tell it the directory where your D-Link NDIS driver is located. ex: 'A:\NDIS\DOS\' (Use the BROWSE button again) 6. When it's finished copying that file, the driver is installed. The rest of the Windows install is up to your preferences. =============================================================================== D-Link NDIS PROTOCOL.INI User Guide This guide specifies the PROTOCOL.INI keywords used for the D-Link NDIS device driver. IOADDRESS - This keyword specifies the I/O base address used by the D-Link Network Interface Card. This value must match the base I/O address jumper setting on your NIC. *DE-100, DE-200, DE-300 INTERRUPT - This keyword specifies the interrupt used by the D-Link NIC. This value must match the IRQ jumper setting on your NIC. *DE-100, DE-200, DE-600 DRIVERNAME- This keyword specifies the NIC driver's name. *DE-100, DE-200, DE-220, DE-300, DE-320, DE-600, DE-620, DE-650 PRINTPORT - This keyword specifies the printer port used by the D-Link Pocket LAN Adapter. *DE-600 BASEMEMORY- This keyword specifies the expanded memory address used by the D-Link NIC. This value must match the base memory jumper setting on your NIC. *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. However, you can specify a node address different from that burned in your NIC, in which case, the specified address will be used instead of the NIC's actual node address. Following is an example PROTOCOL.INI for the DE-200 Ethernet card: [DE200] Drivername = DE200$ Ioaddress = 0x300 Basememory = 0xd000 Interrupt = 3 =============================================================================== ;D-Link's OEMSETUP.INF File: [oemdisks] D=A:\,"D-Link Driver Disk",LAN_DRV_DLK [netcard] d$de100="D-Link DE-100/TP",0,ndis,ethernet,real,d$de100,d$de100_nif d$de200="D-Link DE-200/TP, DE-205TP",0,ndis,ethernet,real,d$de200,d$de200_nif d$de220="D-Link DE-220/TP/CT/C/T/CAT",0,ndis,ethernet,real,d$de220,d$de220_nif d$de300="D-Link DE-300/TP",0,ndis,ethernet,real,d$de300,d$de300_nif d$de320="D-Link DE-320/TP/CT/C/T",0,ndis,ethernet,real,d$de320,d$de320_nif d$de400="D-Link DE-400",0,ndis,ethernet,real,d$de400,d$de400_nif d$de600="D-Link DE-600/TP/AUI",0,ndis,ethernet,real,d$de600,d$de600_nif d$de620="D-Link DE-620/TP/CT/AUI",0,ndis,ethernet,real,d$de620,d$de620_nif d$de650="D-Link DE-650/C/T",0,ndis,ethernet,real,d$de650,d$de650_nif ; D-Link Cards [d$de100] devdir= D:de100.dos device=de100.dos,@devdir\de100.dos [d$de100_nif] drivername=DE100$ io=IOADDRESS,,hex,"0x100,0x3E0,0x20",0x300 [d$de200] devdir= D:de200.dos device=de200.dos,@devdir\de200.dos [d$de200_nif] drivername=DE200$ io=ioaddress,,hex,"0x100,0x3E0,0x020",0x300 [d$de220] devdir= D:de220.dos device=de220.dos,@devdir\de220.dos [d$de220_nif] drivername=DE220$ [d$de300] devdir= D:de300.dos device=de300.dos,@devdir\de300.dos [d$de300_nif] drivername=DE300$ io=IOADDRESS,,hex,"0x100,0x3E0,0x20",0x300 [d$de320] devdir= D:de320.dos device=de320.dos,@devdir\de320.dos [d$de320_nif] drivername=DE320$ io=IOADDRESS,,hex,"0x200,0x360,0x20",0x300 [d$de400] devdir= D:de400.dos device=de400.dos,@devdir\de400.dos [d$de400_nif] drivername=DE400$ [d$de600] devdir= D:de600.dos device=de600.dos,@devdir\de600.dos [d$de600_nif] drivername=DE600$ [d$de620] devdir= D:de620.dos device=de620.dos,@devdir\de620.dos [d$de620_nif] drivername=DE620$ [d$de650] devdir= D:de650.dos device=de650.dos,@devdir\de650.dos [d$de650_nif] drivername=DE650$ =============================================================================== 'WINWG' by MWK & RCZJ updated on 4/20/93