IBM WorkSpace On-Demand
Example of Configuring 3Com Fast Etherlink XL Adapter

15 November 1997

Software Servers Integration Test (SSIT)

©. Copyright IBM Corp. 1997

This section, a supplement to the "IBM Integration Test Report for IBM WorkSpace On-Demand", defines actual experience configuring a "3Com Fast EtherLink/EtherLink XL Family OS/2" PCI adapter (3C90-TX).

Note: The parameter values used in the protocol and other files may not be optimized, or in some cases needed. The intent of this document is to define the steps that were used successfully, not necessarily to indicate that this is the only or most efficient method.

Execution steps

The following steps assume that the IBM WorkSpace On-Demand remote IPL component of LAN Server is installed on the "D:" drive.

Directory Creation

The following directories were created:

• "d:\ibmlan\rpl\dos\3c90xpci\os2"
• "d:\ibmlan\rpl\ibmcom\3c90xpci"

Note: the subdirectory can be any unique name, "3c90xpci" was utilized for the 3Com Fast Etherlink XL adapter.

---

Adapter Option/driver/diagnostics Diskette

Copy the following types of files to the indicated directories, the files indicated were for the 3Com Fast Etherlink XL adapter:

• Dos files to "d:\ibmlan\doslan\lsp\dos"
  • Dos device driver - (EL90X.DOS)
  • Dos NIF file - (EL90XIDS.NIF)
  • Note: copy DOS adapter "msg" files if applicable.
    The .MSG and .NIF files, if present, can have a different name than the device driver file.

• OS/2 files to "d:\ibmlan\rpl\bb10.us\ibmcom\macs"
  • OS/2 device driver - (EL90X.OS2)
  • OS/2 NIF file - (EL90XIO2.NIF)
  • Note: copy OS/2 adapter "msg" files if applicable.
    The .MSG and .NIF files, if present, can have a different name than the device driver file.

---

File Creations

The following files must be created:

• DOS PROTOCOL.INI

  file must be created in the "d:\ibmlan\rpl\dos\3c90xpci\os2" subdirectory.
  The following was utilized for the 3Com Fast Etherlink XL adapter:

  [PROTMAN_MOD] DriverName = PROTMAN$ [DXMJ0_MOD] DriverName = NETBEUI$ Bindings = EL90XIDS_MOD PiggyBackAcks = 0 Sessions = 6 NCBS = 6 Names = 6 Stacksize = 512 Maxdatarcv = 512 [DXME0_MOD] DriverName = DXME0$ Bindings = EL90XIDS_MOD [EL90XIDS_MOD] DriverName = EL90X$

• IBM WorkSpace On-Demand ".CNF"

  file must be created for the adapter within the "d:\ibmlan\rpl" subdirectory.:
  The following file named (BB1US3PC.CNF) was created for the 3Com EtherLink adapter:

  ; OS/2 Boot Block Configuration ; (3COM Etherlink XL and Fast EtherLink XL Family) RPL DOS\RPLBOOT.SYS DAT DOS\MFSD20.SYS ORG 1000H LDR BB10.us\OS2LDR ~ OS2LDR UFSD.SYS MFSD20.SYS DAT DOS\UFSD.SYS DAT DOS\3C90XPCI\OS2\PROTOCOL.INI DAT d:\IBMLAN\DOSLAN\LSP\DXM.MSG EXE d:\IBMLAN\DOSLAN\LSP\NETBIND.COM ~ ~ ~ DRV d:\IBMLAN\DOSLAN\LSP\DXMJ0MOD.SYS ~ 6 ~ DRV d:\IBMLAN\DOSLAN\LSP\DXMA0MOD.SYS 001 ~ ~ DRV d:\IBMLAN\DOSLAN\LSP\DOS\EL90X.DOS ~ 3 ~ DRV d:\IBMLAN\DOSLAN\LSP\PROTMAN.DOS /I: ~ ~ ; --------------- end-of-file -------------------

  The file naming convention is as follows:

  The first three characters are BB1.
  Characters 4 and 5 identify the language version of IBM WorkSpace On-Demand.
  Characters 6, 7, and 8 are any characters used to make the name unique.

• Additional files

  Two additional files were created within the "d:\ibmlan\rpl\ibmcom\3c90xpci" subdirectory.
  1. PROTOCOL.INI

     [PROT_MAN] DriverName = PROTMAN$ [IBMLXCFG] IBMENI_nif = EL90XIO2.nif LANDD_nif = LANDD.nif NETBEUI_nif = NETBEUI.nif ;*----------------------------------------------* ;*------------- PROTOCOL SECTION ---------------* ;*----------------------------------------------* [LANDD_nif] DriverName = LANDD$ Bindings = EL90XIO2.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 = EL90XIO2.nif ETHERAND_TYPE = "I" USEADDRREV = "YES" OS2TRACEMASK = 0x0 SESSIONS = 72 NCBS = 118 NAMES = 39 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 = 10 PACKETS = 350 LOOPPACKETS = 1 PIPELINE = 5 MAXTRANSMITS = 6 MINTRANSMITS = 2 DLCRETRIES = 5 ;*----------------------------------------------* ;*--------------- MAC SECTION ------------------* ;*----------------------------------------------* [IBMENI_nif] DriverName = EL90X$ IOBase = 0x280 Interrupt = 10

  2. CONFIG.NET

     
     Note:How this file was used was not determined.

     DEVICE=Z:\IBMCOM\LANMSGDD.OS2 /I:Z:\IBMCOM DEVICE=Z:\IBMCOM\PROTMAN.OS2 /I:Z:\IBMCOM DEVICE=Z:\IBMCOM\MACS\EL90X.OS2 DEVICE=Z:\IBMCOM\PROTOCOL\LANDD.OS2 DEVICE=Z:\IBMCOM\PROTOCOL\NETBEUI.OS2 DEVICE=Z:\IBMCOM\PROTOCOL\LANDLLDD.OS2 RUN=Z:\IBMCOM\PROTOCOL\LANDLL.EXE RUN=Z:\IBMCOM\LANMSGEX.EXE DEVICE=Z:\IBMLAN\NETPROG\RDRHELP.200 IFS=Z:\IBMLAN\NETPROG\NETWKSTA.200 /I:Z:\IBMLAN DEVICE=Z:\IBMCOM\PROTOCOL\NETBIOS.OS2

---

File Modifications

The following files must be updated:

• "d:\ibmlan\rpl\ndisdd.pro" - must have an entry for the new adapter.
  The following was added for the 3Com Fast Etherlink XL adapter:

  Legend=	1 2 3 4
  Data=	EL90X.DOS 3C90XPCI EL90XIO2.NIF OET3C9

  Legend (Field Definitions)

  • 1 = (el90x.dos) specifies the DOS NDIS device driver name.
  • 2 = (3c90xpci) specifies the subdirectory name that contains the configuration file(s) needed to remote boot the IBM WorkSpace On-Demand client.
    - d:\IBMLAN\RPL\IBMCOM\xxx\ contains the configuration files needed to remote boot OS/2 clients.
    - d:\IBMLAN\RPL\DOS\xxx\ contains the configuration file(s) needed to remote boot both DOS and OS/2 clients.
    were xxx = the text located in the second field.
  • 3 = (el90xio2.nif) specifies the NIF file name for OS/2 device driver
  • 4 = (OET3C9) is the CNF file name id reference for server record id within rpl.map file.

• "d:\ibmlan\rpl\rpl.map" - must have an entry for the new ".CNF" file.
  The following was added for the 3Com Fast Etherlink XL adapter:

  Legend=	1 2 3 4 5 6 7 8 9 A B C D E
  Data=	yyyyyyyyyyyy bb1us3pc.cnf 3 10 N ~ 3COM~3C90PCIX~ETHER~PCI ~ ~ ,,, ~ R_BB10_US_OET3C9 ~ ~

  Legend (Field Definitions)

  • 1 = yyyyyyyyyyyy
  • 2 = boot block configuration file (.cnf)
  • 3 = number of retries before default boot
  • 4 = time window for retries (in seconds)
  • 5 = acknowledge (A,N)
  • 6 = loader parameters (~ for os2, image share name for dos)
  • 7 = descriptive comment, all blank spaces within comment must be replaced with "~" characters.
    - Token-Ring records must include the string "TOKEN".
    - Ethernet records must include the string "ETHER".
    - PC Network records must include the string "PCNET".
  • 8,9, = ~
  • A = ,,,
  • B = ~
  • C = workstation type;
    1 char = "R"
    2-10 chars = "_BB10.US_"
    11-n chars = must match the 4th parameter within the "NDISDD.PRO" file entry.
  • D,E = ~

Hints and Tips

1. Several failures in starting the IBM WorkSpace On-Demand Server were encountered with messages indicating that the "protocol.ini" file could not be opened. This resulted from typos within the ".CNF" file on the subdirectory names in which the adapter files were located. The NET START REMOTEBOOT command validates the ".CNF" file by insuring that all referenced files can be accessed.

2. The most common problem is forgetting to synchronize the adapter's "IOBase" and "Interrupt" settings on the client with the same settings in both the DOS and OS/2 PROTOCOL.INI files on the IBM WorkSpace On-Demand Server.