TITLE: Third Party LAN Support Programs with NWL DOCUMENT ID: TID1002365 DOCUMENT REVISION: 0 DATE: 27MAR95 ALERT STATUS: Yellow README FOR: NA NOVELL PRODUCT and VERSION: NETWARE LITE V1.1 ABSTRACT: NA --------------------------------------------------------------------- DISCLAIMER: THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL MAKES EVERY EFFORT WITHIN ITS MEAN TO VERIFY THIS INFORMATION. HOWEVER, THE INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY. NOVELL MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION. --------------------------------------------------------------------- ISSUE: SYMPTOMS: PC-SUPPORT, PC-AS/400, PC-3270, or Other LAN Support Programs (LSP), or LSP from IBM with NetWare Lite v1.1 This configuration has not been officially tested, so it cannot and will not be supported by Novell. This information is being presented as a "try at your own risk document" and no further support for this document or configuration will be given by Novell. The biggest problem that users of NetWare Lite v1.1 run into while running NetWare Lite and a mini-computer or mainframe access program is that these access programs are CPU hogs. They require and use all CPU cycles of the PC. This causes the server piece of NetWare Lite to be suspended until the access program is exited. The result of this suspension is that all the other users on the NetWare Lite network appear to have hung, and sometimes even the server machine itself hangs. After the access program is exited and the server can again get CPU cycles, the other users can continue unhindered. Another problem seen when a machine with server running with an access program is that all print jobs being sent by other users will get stuck in the print queue and will not get printed automatically. They would need to be released manually one by one. SOLUTION: Novell does not recommend running SERVER.EXE on a machine that one of these access programs is going to be used because of the "CPU hog" symptom discussed above. The preferred setup is to have the machine that is going to run SERVER.EXE be a machine that is not used with an access program and could just support the NetWare Lite network. Then all other machines should be set up as client-only systems. The configuration of one server, not using an access program, and all other machines running as clients would allow the access of NetWare Lite services and the use of an access program without affecting any one else on the network. If NetWare Lite v1.1 is going to be used with a mini-computer or mainframe access program, the following issue needs to be addressed: "Is the network board that will be used for NetWare Lite v1.1 the same network board being used to access the mini-computer or mainframe?" If there is a separate board in the machine attached to the mini-computer or mainframe, then no special configuration would be necessary, except for a potential problem of an interrupt conflict between that board and the network board being used by NetWare Lite. However, if the network board in the machine is going to be used to access a mini-computer or mainframe and NetWare Lite v1.1, then the following changes must be made. The following changes are specific to IBM LAN Support Programs like PC/support, AS/400, and 3270. -o- The CONFIG.SYS should be set up with one of the following two network board driver options. These LSP drivers should be v1.25 or greater. Option 1: Token-Ring network board DEVICE=DXMA0MOD.SYS DEVICE=DXMC0MOD.SYS (These two drivers are for Token-Ring.) Option 2: Ethernet network board DEVICE=DXMA0MOD.SYS DEVICE=DXME0MOD.SYS (These two drivers are for Ethernet.) If a device with the .DOS extension is in the CONFIG.SYS, disable it by using REM. -o- The NetWare Lite STARTNET.BAT should be set up as follows for both Token-Ring and Ethernet: Old STARTNET.BAT New STARTNET.BAT ----------------------- ------------------------ LSL LSL TOKEN.COM or NE2000.COM LANSUP.COM IPXODI A IPXODI A CLIENT CLIENT NetWare Lite uses the Novell standard of ODI (Open Data-Link Interface) drivers. These ODI drivers replace the old IPX.COM. NETX.COM is still used with the ODI drivers to allow the NetWare Lite server or client connectivity to NetWare 2.x, 3.x, and 4.x. The ODI drivers include LSL.COM, (the Link Support Layer), TOKEN.COM, NE2000.COM, or other board drivers, (the network board driver), and IPXODI.COM (the IPX protocol stack). LANSUP.COM is not a network driver; however, it does replace TOKEN.COM or NE2000.COM, which are network drivers. LANSUP supports the DXMA0MOD.SYS, DXMC0MOD.SYS (Token Ring), or DXMA0MOD.SYS, and DXME0MOD.SYS (Ethernet), which are the network drivers provided by LSP, PC-SUPPORT, PC-3270, and PC-AS/400 programs. These drivers are loaded in the CONFIG.SYS file during the booting process. LANSUP provides an interface between the Token-Ring or Ethernet drivers that come with LSP, PC-SUPPORT, PC-3270, or PC-AS/400 programs and the Novell IPX protocol stack. LANSUP also provides the sharing of network board drivers thus allowing NetWare Lite to work with these LSP programs in client mode. LANSUP.COM can be obtained by downloading VLMUPx.EXE from Novell's Forum 'NetWire' on Compuserve or from Novell's BBS in the CLIENT library. The Novell BBS number is 801-221-5197. The last issue that must be addressed is the use of the LSP driver called DXMT0MOD.SYS, which is NetBIOS. NetWare Lite also comes with a NetBIOS.COM, which is completely compatible as a DXMT0MOD.SYS replacement for running NetBIOS applications. Only one or the other should be used on all workstations that need NetBIOS functionality. --------------------------------------------------------------------- Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information. ---------------------------------------------------------------------