NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: DOS Client Files Update Kit Number Eight DOCUMENT ID: TID013923 DOCUMENT REVISION: A DATE: 27OCT93 ALERT STATUS: Yellow INFORMATION TYPE: Symptom Solution README FOR: DOSUP8.EXE NOVELL PRODUCT and VERSION: NetWare Client for DOS/Windows ABSTRACT: Contains updated DOS client files. This file includes NetWare shells v3.32 (NETX.EXE, EMSNETX.EXE, XMSNETX.EXE), compatible with DOS 3.0 and above (including MS DOS 6.0), DR DOS 6.0 and Windows 3.0 and 3.1. Support for both ODI and dedicated IPX are included as well as NETBIOS and other DOS client files. 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴 DISCLAIMER THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL MAKES EVERY EFFORT WITHIN ITS MEANS 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. 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴 SYMPTOM: When using LSL, IPXODI, and MLID drivers, several known anomalies occur. SOLUTION: Copy the updated files to the appropriate directories, and reboot the workstation. Files marked with an "*" are new since DOSUP7.EXE. Files marked with a "^" have been updated since DOSUP7.EXE. Self-Extracting File Name: DOSUP8.EXE Revision: A Files Included Size Date Time Version \ DOSUP8.TXT (This File) BSD.TXT 17466 11-03-93 11:17a ^ DOSNP.EXE 10,547 07-19-93 3:17p 2.10 * DOSODIWS.DOC 4916 11-03-93 2:19a * EMSNETX.EXE 90,430 06-24-93 2:18p 3.32ptf ^ HISTORY.DOC 22041 11-04-93 8:46a INT2F.COM 640 07-28-88 11:48a IPX.OBJ 20,340 11-21-91 12:50p 3.10 IPXODI.COM 30,247 10-07-93 4:52p 2.12 ^ LANSUP.COM 21,943 02-02-93 11:54a 1.27 LSL.COM 17,805 09-10-93 3:50p 2.05 ^ NE1000.COM 19,807 07-30-93 9:40a 1.28 ^ NE1500T.COM 29,258 07-30-93 9:41a 1.27 ^ NE2.COM 20,192 07-30-93 9:36a 1.27 ^ NE2000.COM 21,188 07-30-93 9:38a 1.53 ^ NE2100.COM 29,256 07-30-93 9:41a 1.27 ^ NE2_32.COM 19,903 07-30-93 9:39a 1.30 ^ NE3200.COM 26,568 07-30-93 9:41a 1.17 ^ NETBIOS.EXE 24,392 06-22-93 4:09p 3.14 ^ NETX.EXE 78,606 06-24-93 2:18p 3.32ptf ^ NTR2000.COM 24,909 03-31-93 9:46a 1.04 * ODIINFO.DOC 24499 12-09-92 2:43p ODINSUP.COM 33,867 02-23-93 8:58a ODINSUP.DOC 42016 10-28-93 1:07a PCN2L.COM 21,294 04-28-93 1:12p 1.41 ^ ROUTE.COM 4,882 05-11-93 8:59a 2.10 ^ RPLFIX.COM 1,746 09-30-91 9:39a 1.02 RPLFIX.DOC 2255 02-21-91 2:47p RPLODI.COM 1,652 03-21-91 2:24p 1.02 TASKID.COM 7,539 01-22-93 10:47a 1.10 * TBMI2.COM 24,884 06-03-93 4:36p 3.14 ^ TOKEN.COM 27,381 04-12-93 6:27p 1.27 TOKODI.DOC 6882 11-03-93 2:08a * TRXNET.COM 18,765 12-21-92 2:27p 1.35 ^ XMSNETX.EXE 87,094 06-24-93 2:19p 3.32ptf ^ Solution Specifics: This README file accompanies DOSUP8.EXE that comprises DOS client files for NetWare 3.x, 2.1x and 2.2x operating systems. Brief description of the binary files included in the kit: FILE DESCRIPTION DOSNP.EXE: NetWare DOS NP Extender EMSNETX.EXE: NetWare EMS Workstation Shell INT2F.COM: Novell Network BIOS Interrupt 2Fh Emulator IPX.OBJ: Novell IPX/SPX (No further development is being done on IPX.OBJ. Novell recommends you use the ODI client software. See ODIINFO.DOC for details.) IPXODI.COM: NetWare IPX/SPX Protocol LANSUP.COM: IBM LAN Support MLID LSL.COM: NetWare Link Support Layer NE1000.COM: Novell NE1000 Ethernet MLID NE1500T.COM: Novell NE1500T Ethernet MLID NE2.COM: Novell NE2 Ethernet MLID NE2_32.COM: Novell NE2-32 Ethernet MLID NE2000.COM: Novell NE2000 Ethernet MLID NE2100.COM: Novell NE2100 Ethernet MLID NE3200.COM: Novell NE3200 Ethernet MLID NETBIOS.EXE: Novell NetBIOS Emulation Package NETX.EXE: NetWare Workstation Shell NTR2000.COM: Novell NTR2000 Token-ring MLID ODINSUP.COM: ODI Support Interface for NDIS PCN2L.COM: IBM PC Network II and II/A MLID ROUTE.COM: NetWare Source Routing Driver RPLFIX.COM: NetWare Boot Disk Image Patch Program RPLODI.COM: Novell RPL ODI TASKID.COM: Version Task Identification Program TBMI2.COM: Task Switched Buffer Manager for IPX/SPX TOKEN.COM: IBM Token-Ring MLID TRXNET.COM: Novell Turbo RxNet and RxNet/2 MLID XMSNETX.EXE: NetWare XMS Workstation Shell Brief description of the document files included in the kit: FILE DESCRIPTION BSD.TXT: Black Screen of Death/Windows Hang suggestions. Also includes LSL, IPXODI and VIPX parameters and changes. DOSODIWS.DOC: Brief description of ODI, Token and LANSUP drivers DOSUP8.TXT: This file HISTORY.DOC: History of Shells, changes/fixes ODIINFO.DOC: Discussion on why Novell is promoting ODI ODINSUP.DOC: Information and configuration examples for ODINSUP RPLFIX.DOC: Information on how and when to run RPLFIX TOKODI.DOC: Token and LANSUP LSB mode and Bit reversal Installation Instructions: 1. Make a backup at the workstation of the associated files listed above. 2. Copy the needed files to the workstation, and reboot the workstation to have the new files take effect. IMPORTANT INFORMATION: The following drivers included in this ZIP file now default to the 802.2 frame type. When using these drivers, it is necessary to use the 802.2 frame type on your server or change the frame type for the workstation in your NET.CFG (or SHELL.CFG) file. NE1000.COM 19,807 7-30-93 9:40a 1.28 NE1500T.COM 29,258 7-30-93 9:41a 1.27 NE2.COM 20,192 7-30-93 9:36a 1.27 NE2000.COM 21,188 7-30-93 9:38a 1.53 NE2100.COM 29,256 7-30-93 9:41a 1.27 NE2_32.COM 19,903 7-30-93 9:39a 1.30 NE3200.COM 26,568 7-30-93 9:41a 1.17 If you wish to continue to use the 802.3 frame type, place the following two lines in the NET.CFG (or SHELL.CFG) file: Link Driver Frame Ethernet_802.3 If you were using the NE2000.COM driver, you would replace with NE2000. Be sure to indent the second line and place a carriage return after the second line. PBURST.NLM PBURST.NLM has been removed from this version of the client update kit. Note: PBURST.NLM is also used with the BNETX.EXE shell; however, BNETX.EXE has been deleted from the client update due to a rare problem that can result in data corruption. For Packet Burst support at the client, the workstation will need to be upgraded to the VLM DOS requester technology. TBMI2.COM - This file is for use with DOS 5.0 Task Swapper, Windows 3.0 or Windows 3.1 (running in standard or real mode). For Windows 3.0, use TBMI2.COM and TASKID.COM. In the workstation NET.CFG add the following parameter: USING WINDOWS 3.0=ON TBMI2 is intended for those users running programs which use the IPX or SPX communications protocols from the DOS prompt in Windows (standard or real mode). TSRs running under DOS prompts in Windows Enhanced mode do not need TBMI2, since VIPX.386 will track IPX and SPX functions. If no DOS applications are being run which require IPX or SPX support, then neither of these programs should be run. To determine whether your application requires TBMI2, follow these steps: 1. Load TBMI2.COM. 2. Start Windows. 3. Open a MS-DOS prompt. (for Windows 3.0, load TASKID.COM.) 4. Start the DOS application in question. 5. Run the application and then exit. 6. Display diagnostic information by typing the following: TBMI2 /D 7. If the value in the field named Far Calls Processed is not 0, you need to run TBMI2.COM. To get help with TBMI2.COM, type the following: tbmi2 /? The default configuration for TBMI2.COM is correct for most applications. For use with the MS-DOS 5.0 task swapper, this file is documented in the MS-DOS 5.0 README.TXT. DOSNP.EXE This is the Named Pipes Extender for DOS. It allows you to run Named Pipes applications under DOS. Novell Named Pipe Route Enhancements DOS Clients The default has been changed to not maintain a local Named Pipe server router table. When a request for a DosOpen, DosWaitNmPipe, or DosCallNmPipe is received the protocol will query the network for the whereabouts of the Named Pipe server specified. This means NCP services must be available, for example, NETX.EXE or VLMs must be loaded before DOSNP.EXE The following parameters can be used in the NET.CFG to configure DOSNP.EXE. NP Max Machine Names = n where n is a number between 4 and 50. Replace n with how many named pipe servers you want in the table. (This statement in the NET.CFG will make the client maintain a local Named Pipe server router table.) (This parameter should not to be used with NP Max Sessions) The default is 10. NP Max Sessions = n where n is a number between 4 and 50. Replace n with the number of Named Pipe servers you want to communicate with at once from the remote router. (This parameter should not to be used with NP Max Machine Names) The default is 10. NP Max Open Named Pipes = n where n is a number between 4 and 128. Replace n with the maximum number of named pipes that can be opened at once. The default is 4. RPLFIX.COM RPLFIX is used to allow workstations to remote program load (RPL) properly with MS-DOS 5.x and above. This utility must be run after the boot image file (usually NET$DOS.SYS) has been created using the DOSGEN utility. RPLFIX will directly modify the boot image file; the boot image file's size and last modified date will be different after RPLFIX has been run. RPLFIX only needs to be run against the boot image file once. Attempts to run RPLFIX against an already modified boot image file are detected by the utility, and no further modifications will be made to the boot image file. Follow the instructions for DOSGEN (setting up remote reset workstations) in the Novell reference manuals. For NetWare 2.x, this information can be found in Chapter 9 of the Supervisor Guide, or Chapter 2 of the Using the Network manual. For NetWare 3.x, this information is found in Appendix D of the Installation manual. After performing all steps as outlined in the appropriate manual to create the boot image file, run RPLFIX.COM. The remote workstation will likely hang during the reset process if you are resetting using DOS 5.x or above and the boot image file has not been modified by RPLFIX. RPLFIX can be found on the WSGEN diskette, or in the WSGEN subdirectory if you are installing using a network drive. After you have located RPLFIX.COM, map a drive to the LOGIN subdirectory on the file server you wish to remote reset from. The DOSGEN procedure instructed you to create a boot image file in that subdirectory (usually named NET$DOS.SYS). If the drive you mapped to SYS:LOGIN was the F: drive, then you would enter the following: RPLFIX F:NET$DOS.SYS RPLFIX only needs to be run if the version of DOS loaded on the floppy diskette used with DOSGEN is 5.x or greater. Earlier versions of DOS do not require that this utility be run. Note: If you renamed your boot image file, then you must use the new filename with RPLFIX: RPLFIX [d:] where [d:] is the drive letter where the image file is located, and is the name of the file created with the DOSGEN utility. �