OS/2 Shareware BBS: 8 Other/08-Other.zip/REQCFG.ZIP/INSTALL.DOC

Text File | 1991-06-17 | 8KB | 164 lines

    June 17, 1991

    This file and the REQCFG.ZIP file provided by Novell Technical
    Support.

    INSTALL.DOC for REQCFG.ZIP


***********************  DESCRIPTION of REQCFG.ZIP  ***********************

    REQCFG.ZIP contains sample CONFIG.SYS and NET.CFG files for OS/2
    Extended Edition 1.30.1 (this release includes IBM CSD Level WR05015;
    prior CSD Level was WR05001) when used with Dual Requesters.  The Dual
    Requesters are IBM's LAN Requester and Novell's NetWare Requester for
    OS/2 version 1.30C with NetWare Service Disk NSD001 applied.

    REQCFG.ZIP also includes a modified \CMLIB\PROTOCOL.INI file which is
    REQUIRED when using 3COM's 3C503 Adapter.  This modified PROTOCOL.INI
    file corrects some errors caused by IBM's OS/2 INSTALLATION process.


************************  CONTENTS of REQCFG.ZIP  *************************

CONFIG.503

    Sample CONFIG.SYS for 3C503 Adapter used with OS/2 EE 1.30.1 and
    NetWare Requester for OS/2 version 1.30C+NSD001

CONFIG.TRN

    Sample CONFIG.SYS for IBM Token Ring Adapter used with OS/2 EE 1.30.1
    and NetWare Requester for OS/2 version 1.30C + NSD001.  Includes
    Source Routing support as well as an expanation of how to disable
    Source Routing.

NET.CFG

    Sample NET.CFG for NetWare Requester for OS/2; includes both Standard
    Edition and Extended Edition LINK DRIVER entries for 3C503 and CMGRLAN
    drivers.

SQL_NET.CFG

    Sample NET.CFG for NetWare Requester for OS/2 when running
    Microsoft/Sybase SQL Server.

CMNT_NET.CFG

    Fully commented NET.CFG for the NetWare Requester.  Contains ALL
    comments for all valid entries in NET.CFG.  While this is a valid
    executable file, it does NOTHING except explain the available NET.CFG
    entries.  It is an "on-disk" version of the Requester NET.CFG
    documentation.

PROTOCOL.INI

    Modified \CMLIB\PROTOCOL.INI file showing necessary corrections to
    IBM's PROTOCOL.INI file when used with a 3COM 3C503 Adapter.  Changes
    include explanatory comments.

    Please note that the above files are valid executable files.  You can
    just copy them onto your boot drive if they contain appropriate
    entries for your configuration.  These files were tested with a Compaq
    Deskpro 486/25 (with a 3C503) and an IBM Model 95 (with a 16/4
    Adapter).  The Model 95 was tested attaching through two IBM Token
    Ring (802.2 MAC Layer) Bridges using IBM Token Bridge Program version
    2.2.  Both computers were attaching to a fileserver running NetWare
    3.11.


******  INSTALLATION OF OS/2 EXTENDED EDITION AND NETWARE REQUESTER  ******

    1. Install OS/2 EE.  Include IBM's LAN Requester and any other options
    you need.

    2. Install the NetWare Requester USING THE INSTALL PROGRAM PROVIDED IN
    NSD001.  The INSTALL.EXE program provided with the original 1.30
    Requester will not properly terminate IBM's NetBIOS and thus will not
    run.  The new NSD INSTALL.EXE runs properly, as far as IBM's NetBIOS
    is concerned.  You can run INSTALL from the NSD disk; INSTALL will
    prompt you to insert the REQUESTER disk.

    Whether you use the NSD001 INSTALL.EXE from the NSD001 disk or copy it
    onto your NetWare Requester disk does not matter, but DO NOT USE THE
    INSTALL.EXE program originally supplied with the NetWare Requester
    1.30.  It will NOT run with IBM's NetBIOS.

    At this point in the installation process it DOES NOT matter what
    driver you choose.  Both INSTALL programs do NOT install the correct
    driver for Extended Edition.  You must install the correct driver in
    CONFIG.SYS manually.

    3. Run NSDINSTL.EXE from the NSD001 disk.  This will install the
    updated drivers, dynamic link libraries, and executable program files
    into your NetWare Requester directory.  It will also copy the new
    CMGRLAN.SYS driver for OS/2 EE into your NetWare Requester directory.

    Please note that you CAN run NSDINSTL against the REQUESTER disk
    itself if you have two floppy drives, thus updating the REQUESTER
    disk.  This may be the preferred method as then you only have to run
    NSDINSTL once and all other subsequent installations using the
    REQUESTER disk will be using the updated files.

    4. Modify CONFIG.SYS to use the CMGRLAN.SYS driver instead of whatever
    driver was installed before.  The sample CONFIG.SYS files included with
    REQCFG.ZIP will indicate where these modifications will be needed.

    5. If you are using an Ethernet Adapter a NET.CFG file in the root
    directory of the boot drive is REQUIRED.  This file MUST include an
    adapter NODE ADDRESS entry.  See the sample NET.CFG file provided in
    this REQCFG.ZIP file for an example entry.  Also you must modify the
    \CMLIB\PROTOCOL.INI according to the sample PROTOCOL.INI file if you
    are using a 3COM 3C503 Adapter to correct errors caused by the OS/2
    INSTALLATION process.  See the example PROTOCOL.INI file for details.

    Now you need to go into Communication Manager and modify the Transmit
    Buffer Size for the Ethernet adapter as the Transmit Buffer IBM uses is
    smaller than the NetWare Requester uses (defaults) and the Requester
    will give you an error.  Default for Requester is 1130 bytes.  Comm
    Manager wants this to be a number divisible by 8. 1136 bytes will work
    fine.

    If you are using an Ethernet adapter you also need to pay CLOSE attention
    to your packet type.  Communications Manager's LAN Features configuration
    utility has a Dialog Screen under the "Select Adapter Type" screen which
    is headed "Select Etherand network protocol."  This is PACKET TYPE, NOT
    whether you are using an external (DIX) tranceiver.  This can be VERY
    misleading as the default "network protocol" or packet type is "Ethernet
    DIX version X.X".  The Ethernet DIX option is for a Ethernet II packet
    type.  If you select this packet type and are using Ethernet 802.3 packets
    on your NetWare server you will NOT connect to the server.  Select IEEE
    802.3 network protocol if you are using Ethernet 802.3 packets, Ethernet
    DIX network protocol if you are using Ethernet II type packets.  If you
    are using an external transceiver (DIX cable to external transceiver to
    10BaseT cable) then change the TRANSCEIVER entry in PROTOCOL.INI to
    external.  To emphasize, ETHERNET DIX NETWORK PROTOCOL HAS NO ASSOCIATION
    WITH THE TYPE OF CABLE ATTACHED TO YOUR NETWORK ADAPTER!

    If you have any doubts or questions about packet types PLEASE read the
    CMT_NET.CFG "link driver" section VERY carefully.  This is very important
    and MUST be configured correctly for your LAN connection to be
    successfully established.

    Make these modifications by starting Communication Manager (ignoring any
    error messages for now), Choose "Advanced" from the menu bar at top of
    screen, select "Configuration", then select "Lan feature profiles" from
    the Communications Configuration Menu, then select "change" from the LAN
    Profile Configuration menu, select the appropriate adapter type, memory
    address, network protocol (frame type in Novell).  If you have ANY
    question about which network protocol to select re-read the foregoing
    paragraph carefully.  Details on choosing the appropriate network
    protocol/frame type can be found in the CMNT_NET.CFG file supplied in
    REQCFG.ZIP.  Then you will be in the "Change ETHERAND Network Profile (1
    of 2)" screen.  Arrow down to "Transmit buffer size" and change this to
    1136 bytes.  Press enter twice, then <F3> to exit (it will automatically
    save your new profile).  This will take you back to the Communication
    Configuration menu.  Verify your new settings, then exit back to the
    Communications Main menu and exit that.  When you re-boot your changes
    will be in effect.


    <END OF FILE>