Search
Support & Downloads
Networking Connectivity
Token Ring Adapters
IntranetWare Client for DOS/Windows* 3.1 Workstation Installation

This installation document applies to the TokenExpress™ 16/p LAN Adapter software release v7.0 which is available in the archive TE16DISK.EXE.

Location of Driver: \NETWARE\TE16.LAN

General Installation

  1. From the Novell* IntranetWare Client software, run INSTALL.EXE from DOS.

  2. Select the Novell* IntranetWare Client products you want to install on your workstation from the list:

    [X] NetWare* Client 32 for DOS
    [X] NetWare Client 32 for Windows
    [  ] NetWare TCP/IP protocol stack
    [  ] NetWare IP (TCP/IP Required)
    [  ] Desktop SNMP
    [  ] HOSTMIB for SNMP (SNMP Required)
    [  ] NetWare TSA for SMS

    Note: "NetWare Client 32 for DOS" and "NetWare Client 32 for Windows" are usually selected by default.

  3. From the Customize Support for Windows* menu, specify if you want to use multiple country codes or if you want to set the shared Windows path. The default for both of these is NO.

  4. From the Select LAN Driver Type menu, select "32-bit LAN drivers".

  5. From the 32-Bit Network Board Drivers menu, select "USER SPECIFIED 32 BIT DRIVER".

  6. From the Insert Driver Disk window, specify the driver path as "javascript:void(null);". Then select the "Intel TokenExpressTM Adapters" from the 32-Bit Network Board Drivers window.

  7. Specify the settings for the Intel TokenExpress LAN adapter:

    Parameter Default
    Frame Type FRAME TOKEN-RING MSB
    Info message control SHOWINFO 0
    Node Address

  8. From the Installation Configuration Summary, verify the default settings for Novell IntranetWare Client are correct, or modify as necessary.

    Modify AUTOEXEC.BAT and CONFIG.SYS [YES]
    Client Directory: C:\NOVELL\CLIENT32
    Windows Directory: C:\WINDOWS
    LAN driver type: 32-bit LAN drivers
    LAN driver: Intel TokenExpressTM Adapters

  9. Novell* IntranetWare Client will now copy the files to your workstations and modify the configuration files to match your selected configuration.

Hints and Tips
  1. Check for a LASTDRIVE statement in the CONFIG.SYS file. You must have LASTDRIVE=Z in config.sys when using Novell's Client 32.

  2. Verify that you have FIRST NETWORK DRIVE = F in the NET.CFG file under the NetWare DOS Requester section.

    NOTE: NET.CFG is position sensitive, so be careful to indent lines with one space or one tab as shown above in the example.

  3. Verify that the TokenExpress™ adapter passes the diagnostics test by running TE16DIAG.EXE on the TokenExpress driver disk and selecting "Test Adapter". If the adapter fails diagnostics it will not function correctly running Novell IntranetWare Client.
    Sample Configurations
    Below are sample files from a Novell* IntranetWare Client workstation with a TokenExpress adapter installed using the default installation:

    CONFIG.SYS
    DEVICE=C:\WINDOWS\HIMEM.SYS
    BUFFERS=30,0
    FILES=60
    LASTDRIVE=Z

    AUTOEXEC.BAT
    prompt $P$G
    path=C:\WINDOWS;c:\dos;C:\NOVELL\CLIENT32\
    SET TEMP=C:\TEMP
    @CALL C:\NOVELL\CLIENT32\STARTNET

    STARTNET.BAT
    SET NWLANGUAGE=ENGLISH
    C:\NOVELL\CLIENT32\NIOS.EXE
    LOAD C:\NOVELL\CLIENT32\LSLC32.NLM
    LOAD C:\NOVELL\CLIENT32\CMSM.NLM
    LOAD C:\NOVELL\CLIENT32\TOKENTSM.NLM
    LOAD C:\NOVELL\CLIENT32\TE16.LAN PORT=A40 FRAME=TOKEN-RING MSB
    LOAD C:\NOVELL\CLIENT32\TE16.LAN PORT=A40 FRAME=TOKEN-RING_SNAP MSB
    LOAD C:\NOVELL\CLIENT32\IPX.NLM
    LOAD C:\NOVELL\CLIENT32\CLIENT32.NLM

    NET.CFG
    NetWare DOS Requester
    FIRST NETWORK DRIVE F
    NETWARE PROTOCOL NDS BIND
    Protocol IPX
    IPX SOCKETS 40

This applies to:
TokenExpress™ 16/p Adapter
TokenExpress™ EISA 16/4 Adapter
TokenExpress™ EISA 32 Adapter
TokenExpress™ MCA Adapter



Solution ID: CS-012018
Date Created: 31-May-2004
Last Modified: 27-May-2009
Back to Top