NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: Windows Update Kit for VLM and NETX DOCUMENT ID: TID014296 DOCUMENT REVISION: B DATE: 27DEC93 ALERT STATUS: Yellow INFORMATION TYPE: Symptom Solution README FOR: WINUP9.EXE NOVELL PRODUCT and VERSION: NetWare Client for DOS/Windows ABSTRACT: This file contains updated Windows client files for workstations using either NETX or the VLMs. This file includes the NetWare driver set v2.02 for workstations using NETX and Windows 3.0 or 3.1. This file also includes the NetWare driver set v3.02 for workstations using the VLMS and Windows 3.0 or 3.1. The updated VIPX.386, used with LSL.COM v2.05 and IPXODI.COM v2.12 from DOSUP9.EXE, solves "Black Screen of Death" and other Windows hang symptoms. It also includes support for IPX/SPX under Windows 3.0 and 3.1. 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴 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 Fixes symptoms associated with the "Black Screen of Death", where the w/s hangs with a blinking cursor in the upper left hand corner of the monitor, when entering a dos-prompt under Windows. Fixes other Windows hang issues similar in symptom to the "Black Screen of Death". Fixes an SPX slow down under Windows. Also provides the latest Windows drivers and DLLs for use with workstations using the NetWare shells (i.e. NETX.EXE, XMSNETX.EXE or EMSNETX.EXE), a well as workstations using the NetWare DOS Requester (VLMs). SOLUTION Copy the updated files to the appropriate directories, and restart Windows. Files marked with an '*' are new since WINUP8.EXE. Files marked with a '^' have been updated since WINUP8.EXE. NOTE: When you expand WINUP9.EXE, it will automatically create three sub-directories: NETXDRVS (containing Windows drivers specific to NETX, EMSNETX and XMSNETX workstations); OLDDLLS (containing DLLs that may needed for specific applications, but are no longer maintained by Novell); VLMDRVS (containing Windows drivers specific to NetWare DOS Requester (VLM) workstations). All other files contained in the root of WINUP9.EXE can be used on workstations using either NETX or the VLMS. Self-Extracting File Name: WINUP9.EXE Revision: B Files Included Size Date Time Version \ WINUP9.TXT (This File) VIPX.386 23855 10-11-93 9:00a ^ VIPX.DOC 32304 12-16-93 12:16p ^ NWNET.DLL 205104 11-02-93 5:12p v4.04 ^ TBMI2.COM 24884 06-03-93 4:36p v3.14 NWPSRV.DLL 161302 05-14-93 5:29p v4.01 TASKID.COM 7539 01-22-93 10:47a v1.10 VPICDA.386 11063 01-30-91 10:58a v3.02 BINDFIX.EXE 63297 02-12-91 2:10p v3.52 NWCALLS.DLL 146544 11-02-93 2:30p v4.04 NWPOPUP.EXE 4592 10-28-93 8:06a v3.01 ^ DEADLOCK.TXT 18077 12-21-93 2:25p * NWIPXSPX.DLL 38544 11-02-93 5:47p v4.04 ^ NWLOCALE.DLL 38576 11-02-93 6:12p v4.04 ^ VNETWARE.386 15133 11-19-93 8:39a v2.03 ^ \NETXDRVS\ NETWARE.DRV 126144 10-27-92 7:38a v2.02 NETWARE.HLP 34348 02-12-92 3:12p \OLDDLLS\ NETAPI.DLL 7168 06-24-91 11:05a v1.3d NWPSERV.DLL 20929 01-29-92 10:50a v1.30 NWNETAPI.DLL 106884 01-07-93 1:31p v1.30 \VLMDRVS\ NWGDI.DLL 81792 11-19-93 4:50p v1.0 * TBMI2.MSG 3658 01-28-93 1:30p * NWUSER.EXE 5072 10-28-93 8:12a v1.02 * TASKID.MSG 1654 01-22-93 10:47a * NETWARE.DRV 146736 11-24-93 9:02a v3.02 * NETWARE.HLP 50455 06-17-93 12:17a * NETWARER.DRV 146736 11-24-93 9:02a v3.02 * Installation Instructions: Make a backup of any files currently on your workstation or File Server that appear in the list above. FOR THE FILES AT THE ROOT OF THE [WINUP9] FILE: Note: The files at the root of [WINUP9] are not shell specific, and are for use with either NETX or VLM workstation configurations. Copy the following files to the WINDOWS\SYSTEM directory: NWCALLS.DLL APIs for NCP communication between the f/s and w/s. NWIPXSPX.DLL APIs for IPX/SPX communication. NWLOCALE.DLL APIs for localization and internationalization of applications. NWNET.DLL Network API support for NDS, etc. NWPOPUP.EXE Windows utility to "POP-UP" network messages in Windows. NWPSRV.DLL Contains print server services APIs. TASKID.COM Version Task Identification Program (for WINDOWS 3.0) TBMI2.COM Task Switched Buffer Manager for IPX/SPX (for Windows v3.0 and v3.1). VIPX.386 Virtual IPX/SPX driver for Windows enhanced mode. VNETWARE.386 Virtual NetWare driver for Windows enhanced mode. VPICDA.386 Virtual PIC driver for NIC cards at INT 2 or 9 and above. (For Windows 3.0 only) Note: Depending on your previous installation, the DLL or other files listed above may be located in the \WINDOWS directory. Make sure that you have a copy of the files listed above only in the \WINDOWS or the WINDOWS\SYSTEM directory, as you may have spurious results if you have different versions of the same DLL located in each of the directories. The preferred configuration is to place all the file listed in the section above only in the WINDOWS\SYSTEM directory. The *.386 files should only be placed in the WINDOWS\SYSTEM directory. SYMPTOM With the NetWare shell (NETX.EXE, etc) and the related MS Windows drivers, users could configure the client to allow for private or global drive mappings in Windows DOS prompts. The NetWare client for DOS and Windows (VLMs), however, implemented this function differently, and the ability to specify private drive mappings was lost. Under this scenario if a change was made to a mapped drive in one DOS prompt, it was changed in all others at the same time. SOLUTION VNETWARE.386 v2.03 allows private mappings. By default, mappings are private. To change this to global, enter the following in your SYSTEM.INI file: [NetWare] NWShareHandles=TRUE FOR THE FILES IN THE SUB-DIRECTORY [NETXDRVS] UNDER THE [WINUP9] ROOT DIRECTORY: Note: The files located in the [NETXDRVS] sub-directory are specific to NETX, EMSNETX and XMSNETX workstations. DO NOT USE THESE FILES ON WORKSTATIONS USING THE NETWARE DOS REQUESTER (VLMs). Copy the following files to the WINDOWS\SYSTEM directory: NETWARE.DRV 126,144 10-27-92 7:38a v2.02 NETWARE.HLP 34,348 2-12-92 3:12p NetWare Pop-Up Menu - The Windows 3.1 NetWare driver v2.02 provides an optional pop-up menu that allows you to perform common NetWare-related operations. To enable the pop-up menu, add a section to the NETWARE.INI file in the Windows directory (you might need to create this file) with the following lines: [Options] NetWareHotKey=1 This maps the pop-up menu to the F6 key. The menu has a button that allows you to change the hot-key to any of the twelve F-keys. FOR THE FILES IN THE SUB-DIRECTORY [OLDDLLS] UNDER THE [WINUP9] ROOT DIRECTORY: Note: The files located in the [OLDDLLS] sub-directory are older DLLs that are no longer maintained by NOVELL. They are included as a resource for applications that may require their use. NOTE: If the DLL that ships with the application is newer than the one included in WINUP9, use the newer of the two files. Copy the following files to the WINDOWS\SYSTEM directory: NETAPI.DLL v1.3D API support for the SQL Server front end. NWNETAPI.DLL v1.30 Same as NWCALLS.DLL. Will be phased out. NWPSERV.DLL v1.30 Contains older print server services APIs. Some applications specifically call this DLL. It is being replaced by NWPSRV.DLL .DLL files - These files are updated versions of the NetWare API dynamic link libraries (DLLs). These DLLs are used by applications. NWIPXSPX.DLL uses VIPX.386. A good rule of thumb to follow is to check your WINDOWS and WINDOWS\SYSTEM directories to see if these files exist. If they do, and they are older than the DLLs on this diskette, update them with the files on this diskette. If they are not in the WINDOWS or WINDOWS\SYSTEM directory, then they are not needed and do not need to be copied. If you do install an application which uses any of these DLLs, you can use these files to update the DLLs, provided these DLLs are newer than the ones shipped from the application vendor. FOR THE FILES IN THE SUB-DIRECTORY [VLMDRVS] UNDER THE [WINUP9] ROOT DIRECTORY: Note: The files located in the [VLMDRVS] sub-directory are specific to the NetWare DOS requester (VLM) workstations. DO NOT USE THESE FILES ON WORKSTATIONS USING NETX, EMSNETX or XMSNETX. Copy the following files to the WINDOWS\SYSTEM directory: NETWARE.DRV v3.02 NETWARE.HLP 6-17-93 NWGDI.DLL NetWare Graphical Device Interface (required for Netware.drv v3.02) NWUSER.EXE Provides an entry point into Netware.drv v3.02 Copy the following files to the WINDOWS\NLS\ENGLISH directory: NETWARER.DRV v3.02 NetWare enabled driver. TASKID.MSG English message file for TASKID.COM TBMI2.MSG English message file for TBMI2.COM To access the Netware.drv v3.02 driver, install the files listed above. If you do not have a NWUser icon, select a Windows group to add the icon to. From the File menu, select New. Create a program Item with NWUser as the description and [Drive_Letter]:\WINDOWS\SYSTEM\NWUSER.EXE as the Command Line. This will allow you to access various network functions by selecting the NWUser icon. You can enable a hot-key for NWUSER.EXE by first double clicking on the NWUser icon. From the button bar at the top, select the "KEY" icon. There is an option to "Enable Hotkey", and to select the "Hotkey Value". Note: Mappings created using NetWare.drv\NWUser.exe are map rooted by default. To change the location of the map root, click on the < > arrows located on the Path: line under the Drive Mapping Icon. The < arrow will move the root toward the "Root" of the volume. The > arrow will move the root toward the "end of the path". A white space in the path denotes the current map root location. Copy the following files to your [FILE_SERVER]\SYS:SYSTEM directory: BINDFIX.EXE - If you are running a version of BINDFIX shipped with NetWare version 2.11 or below, you need to update it with the BINDFIX.EXE on this diskette. For further information, see Novel Technical Bulletin 255 and 256, dated October 26,1989 and November 3, 1989, respectively. GENERAL INFORMATION AND CONFIGURATION PARAMETERS: Support for IPX/SPX under Windows 3.0 and 3.1 is included as well as VPICDA.386 for Windows 3.0 interrupt conflicts. TBMI2.COM - This file is for use with DOS v5.0 Task Swapper, Windows v3.0 or Windows v3.1 (running in standard or real mode). For Windows v3.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 are required. To determine whether your application requires TBMI2, follow these steps: o Load TBMI2.COM o Start Windows (In standard or Real mode) o Open a MS-DOS prompt o (for Windows 3.0, load TASKID.COM) o Start the DOS application in question o Run the application and then exit. o Display diagnostic information by typing the following: TBMI2 /D o 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 v5.0 README.TXT. VPICDA.386 - This Microsoft patch for Windows 3.0 is an enhanced mode virtualization file necessary when running a network card that uses interrupt (IRQ) 2, or IRQ 9 or higher. This file replaced the Windows supplied VPIC driver in the 386 Enhanced section of the SYSTEM.INI file. To install this driver, edit your SYSTEM.INI file: [386Enh] ;device=*vpicd (a semi-colon will comment out the line) device=vpicda.386 (copy this driver to your Windows 3.0 subdirectory or System subdirectory) DO NOT USE VPICDA.386 WITH WINDOWS 3.1. Solution Specifics: DEADLOCK.TXT contains information on solving issues dealing with Windows hangs commonly known as the "Black Screen of Death". In addition, it contains suggestions for curing other Windows hangs outside of the scope of "Black Screen of Death". Also included is documentation on LSL, IPXODI and VIPX.386 enhancements and parameters. VIPX.DOC is a VIPX.386 configuration, limitation, description and programming document. �