### TechNote

Number:06608-01
Date:April 1994

## Smart II Software: installing interfaces

This TechNote tells you how to install the Smart II Software and how to create a SMART.CFG file to configure the interfaces and protocols you require. Read it if you want to install your driver software manually, instead of by using the Install program. For assistance in choosing the correct interfaces and protocols for the DOS workstations on your network, see TechNote 06607.

Caution

If you are running Microsoft Windows version 3.1 or 3.0 on your workstations, make sure that you use the WIN=31 or WIN=30 parameter when you are configuring your Smart II Software. If you are running Microsoft Windows for Workgroups version 3.10 or 3.11, make sure that you use the WIN=31 parameter when you are configuring your Smart II Software.

For information about:

- Installing and configuring the NOVAPI host-interface for Novell LAN WorkPlace for DOS, see TechNote 06616.

- Installing and configuring a RARP server, see TechNote 06617.

- Backwards compatibility, see TechNote 06621.

- Linking together the components of the Smart II Software, see TechNote 06603.

- Configuring the Smart II Software for multiple Ringnodes, see TechNote 06602.

### 1 Installing SMART.EXE

1. Create a DOS boot disk (either a hard disk or a floppy disk) with which to boot your workstation onto the network. Copy your network software onto the boot disk.

2. Copy the SMART.EXE program, together with the .SMT protocol modules you require, from the Madge release disk onto your boot disk. For the location of SMART.EXE on the release disk, refer to the README file.

3. Create a SMART.CFG file specifying the interfaces you require (see Section 2). If you are using Microsoft Windows version 3.1 or 3.0, make sure that you put the WIN=31 or WIN=30 parameter in the [HOST] section of your SMART.CFG file. For Microsoft Windows for Workgroups versions 3.10 and 3.11, use the WIN=31 parameter.

4. Ensure that SMART.EXE loads before your network software. Insert the SMART command into the AUTOEXEC.BAT file on your boot disk as follows:

   `SMART [path=]`

   The optional path parameter specifies where SMART.EXE finds your SMART.CFG file (if SMART.CFG is not in the same directory as SMART.EXE).

   If you do not have an AUTOEXEC.BAT file, create one containing the SMART command line.

   Alternatively, run SMART.EXE from the CONFIG.SYS file. Use the following line:

   `DEVICE=SMART.EXE [path=]`

5. Boot your computer using the boot disk you have created.

Note

If you want to run SMART.EXE in DOS Upper Memory, you must run it from the AUTOEXEC.BAT file. For details of the HIGH parameter, see TechNote 06609.

Note

If you are using the ODI.SMT module, run SMART.EXE from the AUTOEXEC.BAT file and ensure that LSL.COM loads first.

### 2 The SMART.CFG file

When you run SMART.EXE, you do not need to specify any protocol modules on the command line. We recommend you specify them in a SMART.CFG file. If you use a SMART.CFG file that is in the same directory as SMART.EXE, your command line need contain only the word:

`SMART`

Sample SMART.CFG files are printed in Figures 2 and 3.

We recommend that you use a SMART.CFG file. This makes it easier for you to organize and maintain your configuration. However, for simple installations (for example, using default parameters), you can run SMART.EXE by specifying your protocols on the command line. The following example downloads IPX and NetBIOS onto your Ringnode:

`SMART IPX NETB`

Note

If you are using the Smart TCP/IP software, specify the individual interfaces in a SMART.CFG file. You cannot run the TCP/IP modules from the command line. The components of the Smart TCP/IP software are: TCP.SMT, IP.SMT, UDP.SMT, NOVAPI.SMT, and RARPD.SMT.

#### 2.1 Syntax of the SMART.CFG file

The syntax of the SMART.CFG file divides your configuration into sections. These are denoted by a heading between [ and ] characters on a new line. The syntax is not case- sensitive, spaces are ignored, and comments can appear on any line after a semi-colon. Specify the interfaces you require in any order. Do not include sections for interfaces that you do not want loaded. For information about the combinations of interfaces that you can download onto your Ringnode, see TechNote 06607. Figure 1 illustrates the format of the SMART.CFG file.

    [HOST]                                    <; comments>
    <host-specific parameters>
         [CARD]
         <card-specific parameters>
              [LLC]
              <LLC parameters>
              [IPX]
              <IPX parameters>
              [NETB]
              <NETB parameters>
              [ODI]
              <ODI parameters>                ; ODI parameters can go in NET.CFG
              [NOVAPI]
              [TCP]
              <TCP parameters>                ; TCP parameters can go in NET.CFG
              [IP]
              <IP parameters>                 ; IP parameters can go in NET.CFG
              [UDP]
              <UDP parameters>                ; UDP parameters can go in NET.CFG
              [RARPD]
              <RARPD parameters>

Figure 1 Format of the SMART.CFG file

#### 2.2 Parameters for the Smart II Software

We recommend that you do not change protocol parameters from the defaults unless you have experience of configuring adapters. For full details of the parameters available, see the TechNotes listed in the table below:

    TechNote   Title

    06609      Smart II Software: host parameters
    06610      Smart II Software: card parameters
    06611      Smart II Software: LLC parameters
    06612      Smart II Software: NetBIOS parameters
    06613      Smart II Software: IPX parameters
    06614      Smart II Software: ODI parameters
    06615      Smart II Software: TCP/IP parameters
    06616      Smart II Software: NOVAPI parameters
    06617      Smart II Software: RARPD parameters
    06618      Smart II Software: configuring for source routing bridges

Note

If you specify protocol parameters that cannot be accommodated, SMART.EXE terminates with an error message.

#### 2.3 Sample SMART.CFG file: IPX, ODI, LLC, NETB

Figure 2 shows a sample file for the configuration of a single Smart 16/4 Ringnode with 256- or 512kbytes of on-board memory. The protocols downloaded are IPX, ODI, LLC, and NetBIOS. For full details of parameters, refer to the INFO utility.

    [HOST]                          ; Host-specific parameters.
    win=31                          ; Set up for Windows 3.1
    high                            ; Run SMART.EXE in Upper Memory.
         [CARD]                     ; Ringnode-specific parameters.
         node.address=400012345678  ; Override burnt-in address.
         frame.size=4096            ; Max framesize is 4096 bytes.
         lomem                      ; Copy DMA exchanges through
                                    ; buffers in low memory.
         [IPX]                      ; IPX interface enabled.
         source.routing=y           ; IPX source routing enabled.
         [ODI]                      ; ODI interface enabled.
         frame=token-ring_snap      ; ODI to support SNAP frames.
         [LLC]                      ; LLC interface enabled.
         rx.size=2000               ; LLC receive frames limited to
                                    ; 2000 bytes.
         stations=80                ; 80 LLC links available to NetBIOS.
         est = 10                   ; 10 extra links available to
                                    ; other LLC applications.
         [NETB]                     ; NETB interface enabled.
         sessions =35               ; 35 NetBIOS sessions available.

Figure 2 Sample SMART.CFG file for the configuration of a single Ringnode

### 2.4 Sample SMART.CFG file: ODI and TCP/IP

Figure 3 shows a sample file for the configuration of a single Smart 16/4 Ringnode with 256- or 512kbytes of on-board memory. The interfaces downloaded are for ODI and TCP/IP.

    [HOST]                          ; Host-specific parameters.
    win=31                          ; Set up for Windows version 3.1.
    high                            ; Run SMART.EXE in Upper Memory.
         [CARD]                     ; Ringnode-specific parameters.
         io.location=1a20           ; Locate Ringnode at address 1a20.
         [NOVAPI]                   ; LAN WorkPlace for DOS interface.
         enable.statistics=no       ; Disable MIB information (saves
                                    ; 2kbytes of DOS memory).
         [TCP]                      ; TCP interface enabled.
         tcp.requests=32            ; Allow the Ringnode to operate with a
                                    ; high number (32) of outstanding TCP commands.
         [IP]                       ; IP interface enabled.
         ip.address=193.35.4.21     ; IP address of host computer.
         ip.router=193.35.4.99      ; IP address of default router.
         enable.mib=no              ; Disable MIB (to improve performance).
         [UDP]                      ; UDP interface enabled.
         udp.ports=2                ; Only two UDP ports required.
         [ODI]                      ; ODI interface enabled.
         frame=token-ring_snap      ; ODI to support SNAP frames.
         odi.source.routing=y       ; ODI ource routing enabled.

Figure 3 Sample SMART.CFG file for the configuration of a single Ringnode using the suite of TCP/IP modules