IBM DLR and NOVELL CLIENT coexistence           1/27/94

CONSIDERATIONS FOR LOADING DLR AND
NOVELL CLIENT CONCURRENTLY USING ODI AND NETX



DESCRIPTION OF SYMPTOMS:
    Can an IBM DOS LAN Requester and a Novell Client
    coexist?

SUMMARY OF RESOLUTION:
    Adjust the LASTDRIVE statement and the DXMT0MOD.SYS
    driver in the CONFIG.SYS, create a NET.CFG file
    in the same subdirectory as the Novell files, and
    load DLR before the Novell client.

DETAILS OF RESOLUTION:
    (Assumes DOS 5.0 or higher--for memory management--
    and Novell NETX Version 3.26 or higher.)

    The following outlines the prime considerations in
    loading IBM's DOS LAN Requester (DLR) and Novell's
    Client concurrently on a PC DOS workstation:

    1.  The LASTDRIVE statement in the CONFIG.SYS must
        be set to allow the Novell drives to be assigned
        after the local and DLR assignments.

            Example:  LASTDRIVE=K

    2.  The ES parameter for the DXMT0MOD.SYS driver (in
        the CONFIG.SYS) must be set high enough to allow
        the Novell driver access to the token ring.

            Example:  ES=6 allows the 2 SAPs for DLR
                      plus 4 SAPS for the Novell.
                      (Novell may require only 1 SAP.)

    3.  Create a NET.CFG file in the same directory as the
        Novell files.

            Example:
                NOTE:  The lines must be indented at least
                       three spaces.  (Do not use a tab;
                       when parsed, it only shows one space.)

                PROTOCOL IPX
                    BIND LANSUP
                LINK DRIVER LANSUP
                    FRAME TOKEN-RING
                    FRAME TOKEN-RING_SNAP
                    SAPS 4

    4.  The DOS LAN Requester must be loaded before the
        Novell Requester code.

    Following are examples of the CONFIG.SYS, DOSLAN.INI,
    and AUTOEXEC.BAT.

    Sample CONFIG.SYS

        DEVICE=C:\DOS50\HIMEM.SYS
        DOS=HIGH
        DEVICEHIGH=C:\DOS50\SETVER.EXE
        FILES=30
        BUFFERS=20
        SHELL=C:\DOS50\COMMAND.COM /E:2000 /P
        LASTDRIVE=K
        DEVICE=\LSP\PROTMAN.DOS /I:\LSP
        DEVICE=\LSP\IBMTOK.DOS
        DEVICEHIGH=\LSP\DXMA0MOD.SYS 001
        DEVICEHIGH=\LSP\DXME0MOD.SYS
        DEVICE=\LSP\DXMT0MOD.SYS O=N S=12 C=14 ST=12 ES=6 EST=2
        DEVICE=C:\DOS50\SMARTDRV.EXE /DOUBLE_BUFFER
        STACKS=0,0

    Sample AUTOEXEC.BAT

        C:\DOS50\SMARTDRV.EXE /L
        @ECHO OFF
        \LSP\NETBIND
        SET COMSPEC=C:\DOS50\COMMAND.COM
        PROMPT $p$g
        PATH C:\DOS50;C:\EXCEL;C:\DLR30;E:\WIN30
        SET TEMP=C:\DOS50
        C:\DOS50\MOUSE.COM /Y
        LOADHIGH C:\DOS50\DOSKEY.COM
        @ECHO OFF
        REM ******************************************
        REM Prompt to start the DOS LAN Requester.
        YNPROMPT Y N 30 Start DOS LAN Requester (Y/N)?
        IF ERRORLEVEL 1 GOTO NODLR
        NET START
        IF ERROR LEVEL 1 GOTO NODLR
        CALL INITFSI.BAT
        :NODLR
        REM ******************************************
        REM Prompt for Start of Novell Client software.
        YNPROMPT Y N 30 Start Novell Client (Y/N)?
        IF ERRORLEVEL 1 GOTO NONOV
        C:\NOVELL\DOSODI\LSL
        C:\NOVELL\DOSODI\LANSUP
        C:\NOVELL\DOSODI\IPXODI
        C:\NOVELL\DOSODI\NETX
        :NONOV

        NOTE: The LSL, LANSUP, IPXODI, and NETX can be either
              .COM or .EXE files depending on the shell being
              used.  The statement as written above should call
              the applicable file.

    Sample DOSLAN.INI

        RCV TheMachineName DomainName
        /SRV:8   /ASG:29   /NBC:4   /NBS:1K   /BBC:1   /BBS:4K
        /PBC:4   /PBS:128  /PFS:32  /PFT:900  /PWT:250
        /KUC:600 /KST:600  /API     /NMS:3    /MLO     /HIM
        /WRK:111121101021210


DATE LAST UPDATED:  01/27/94
XA23009 - CPFPM

12/31/99