Microsoft KB Archive/98492

= How to Install Intel EtherExpress Card =

Article ID: 98492

Article Last Modified on 10/31/2006



This article was previously published under Q98492



SUMMARY
This article explains how to install the Intel EtherExpress card. This article assumes that your RPL workstations are running MS-DOS version 5.0 or later (remote OS/2 workstations are not supported) and that the server is using LAN Manager's default file structure.



Getting Started
Chapter 13 of the &quot;Microsoft LAN Manager Administrator's Guide&quot; discusses Remoteboot workstations. Follow the instructions in these three sections:


 * Preparing the Server, page 243
 * Installing LAN Manager with Remoteboot Selections, page 244
 * Setting up for MS-DOS and MS OS/2 Workstations, page 246

Step 4 of &quot;Setting Up for MS-DOS and MS OS/2 Workstations&quot; refers to MSDOS.SYS, IO.SYS, IBMBIO.COM, and IBMDOS.COM. Use File Manager to turn off the system and hidden file attributes for these files. Check that these attributes are correct by displaying a directory listing for:   c:\lanman\rpl\rplfiles\binfiles\dos500 If the MSDOS.SYS and IO.SYS files are not visible in this virtual root directory when you boot an RPL workstation, this message is displayed:

NON-SYSTEM DISK insert DOS disk and strike any key.

The name of the server MUST conform to the MS-DOS naming convention (eight characters or less for the name, three characters for the extension).

Be sure RPLINST runs successfully before you continue. It indicates that the MS-DOS directory is installed correctly.

Installation Procedure
 Make sure the Remoteboot service is NOT running. To do this, log on as ADMIN and enter the command NET STOP REMOTEBOOT at the server's OS/2 prompt. Remove all references to the Intel EtherExpress (EXP16) card in the RPL.MAP and RPLMGR.INI files located in C:\LANMAN\RPL. (If you haven't entered any references, there may not be any.) Use this procedure to find any there are:

 Look for the lines that begin with &quot;00AA00??????&quot; in the RPL.MAP file. Remove any you find. Look for configurations that contain &quot;bblink = RDOSIN&quot; or&quot;adapters=00AA00??????&quot;. Remove any you find.   In the RPL.MAP file, enter information about the EtherExpress adapter (the path is \LANMAN\RPL\RPL.MAP).

Use existing entries in the RPL.MAP file. Modify them to look like the examples below.

Note: The examples are broken into two lines because of display restrictions--DO NOT break your entries in the RPL.MAP file. Check the syntax and spacing carefully.

In the Boot Block Records
<pre class="fixed_text">  yyyyyyyyyyyy BBLOCK\NETBEUI\EXP16\DOSBB.CNF 2 6 A ~ DOS~INTEL~EXP16 00AA00 ~ ,,, ~ RDOSIN ~ ~ ~ ~ ~ ~

In the Workstation Records
<pre class="fixed_text">  00AA00?????? INTEL D FITS\DOS500 (RPL_SERVER_NAME) S ~ ~ ~ ,,, ~ RDOSIN ~ DEFAULT *~New~Intel~Exp16~*~ ~ ~ Note: The RPL_Server_Name must conform to the MS-DOS naming convention. </li> In the Configuration section of the RPLMGR.INI file, add these new sections for the EtherExpress adapter:

[configuration]

name = INTEL

os = DOS500

dirname = DOS

dirname2 = DOS500

bblink = RDOSIN

fitfileshared = fits\DOS500

comment = DOS 5.00 EtherExpress card

adapter = 00AA00??????

</li> Copy the EtherExpress MS-DOS NDIS driver from the Intel disk (A:\MSLANMAN.DOS\DRIVERS\ETHERNET\EXP16\EXP16.DOS) to the (C:\LANMAN\RPL\BBLOCK\NDIS) directory.</li>  Create the directory C:\LANMAN\RPL\BBLOCK\NETBEUI\EXP16. In this directory, create a PROTOCOL.INI and a DOSBB.CNF file. <pre class="fixed_text">  Example PROTOCOL.INI File -

[protman] drivername = protman$ dynamic = yes priority = netbeui

[netbeui] drivername = netbeui$ bindings = EXP16 names = 5 ncbs = 8 packets = 20 pipeline = 10 sessions = 4 stacksize = 512 lanabase = 0

[EXP16] IOADDRESS = 0x300 DRIVERNAME = EXP16$ RPL Note: The IOADDRESS line should match the I/O address you chose for the EtherExpress card. <pre class="fixed_text">  Example DOSBB.CNF File --

; DOS on INTEL ETHEREXPRESS RPL BBLOCK\RPLBOOT.SYS LDR BBLOCK\RPLSTART.COM ~ DAT BBLOCK\NETBEUI\EXP16\PROTOCOL.INI DRV BBLOCK\RPLDISK.SYS ~ 4 M  EXE BBLOCK\RPLPRO1.COM ~ 2~ EXE BBLOCK\RPLBIND2.EXE ~ ~ EXE BBLOCK\PROTMAN.EXE ~ ~ EXE BBLOCK\RPLBIND1.EXE ~ ~ DRV BBLOCK\TCPDRV.DOS /I:C:\LANMAN.DOS ~ ~ EXE BBLOCK\NETBEUI\NETBEUI.EXE ~ 10 ~ DRV BBLOCK\NDIS\EXP16.DOS ~ ~ ~ DRV BBLOCK\PROTMAN.DOS /I:C:\LANMAN.DOS ~ M Note: You can copy the DOSBB.CNF file from the subdirectory of another network card then modify it to match this example. </li>  Create this directory structure: <pre class="fixed_text">     C:\LANMAN\RPL\RPLFILES\MACHINES\INTEL\DEFAULT\WKSTA Copy the PROTOCOL.INI you created in the previous step to the WKSTA directory. </li> Update RPLMGR.

 Change to the C:\LANMAN\RPL and invoke RPLMGR.</li> From the Remoteboot menu, choose New Profile.</li> Enter Profile Name, comment, and configuration.

Profile name: Intel

Comment: Your comment here

Configuration: DOS500 EtherExpress card

The configuration line should match the COMMENT line entry in the RPLMGR.INI file.</li> Choose OK.</li> When disk activity stops, exit RPLMGR.</li></ol> </li> Start the Remoteboot service by entering the NET START REMOTEBOOT command at the OS/2 command prompt.

Note: After the RPL installation is complete, configure the server to automatically start the Remoteboot service.</li> Install the EtherExpress card and ROM as described in the Intel manual.</li> Attach the workstation to the network and turn it on.</li> The workstation will attach to the server and eventually return you to the command prompt. The &quot;C:\&quot; prompt is a virtual link to the C:\LANMAN\RPL\RPLFILES\MACHINES\INTEL\DEFAULT\WKSTA directory on the server.

Note: The workstation has limited file permissions until the user executes a NET LOGON command.</li></ol>

As you can see, this is a long process. If the RPL workstation does not find the server (for example, the error message &quot;Searching for a DLC RPL server&quot; is displayed), go back through each step and check the syntax, spelling, capitalization, and directory structures. If the workstation comes up with an error such as &quot;NOT USER LEVEL SECURITY,&quot; try changing the boot PROM's ROM address to use another.

<div class="references_section">