NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: NETWARE.DRV 3.03 Windows NetWare Shells (VLM) README FOR: WINDR3.EXE NOVELL PRODUCTS and VERSIONS: NetWare Client for DOS/MS Windows 1.2 ABSTRACT: This file contains updated Windows Driver files for workstations using either VLMs or NETX. This file includes NETWARE.DRV v3.03 Rev A released for workstations using the VLMS with Windows 3.1x or Windows for Workgroups 3.11. NETWARE.DRV v2.02 and its HLP file are version specific for NETX and have been moved to NET33X.EXE. The updated VIPX.386 v1.19 included in this file, needs to be used with LSL.COM v2.12 or higher, and IPXODI.COM v3.01 or higher from VLMUP4.EXE. ----------------------------------------------------------------- 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: SYMPTOM This file is specifically distributed for users that use MS Windows and the NetWare Dos Requester VLMs (Virtual Loadable Modules). This file corrects a problem "Lotus Notes Vip Runtime v" and "FX-Works v1.1" that would cause the following error: "Application Error, VIP caused a GPF in module NETWARE.DRV @0001:1243" SOLUTION Fixed "Get information for a specified device". The function would scan for the device name and look at all 16 bytes, now it looks for null termation or 16 bytes of the device name whichever comes first. SYMPTOM When exiting Windows after losing a connection to a server, the machine would appear to be hung or in a Black Screen of Death (BSOD) state. SOLUTION In the Windows shutdown sequence, if the server was still registered with VLMs, this would cause NETWARE.DRV to generate a INT 24 that would prevent Windows from finishing the shut down process. With this update, when the shutdown process is called, NETWARE.DRV does not require a check from VLMs when exiting Windows. SYMPTOM Updated VIPX.386 fixes symptoms associated with the "Black Screen of Death", where the workstation hangs with a blinking cursor in the upper left hand corner of the monitor. Fixes other Windows hangs similar in symptom to the "Black Screen of Death". Also provides the latest Windows drivers for workstations using the NetWare DOS Requester (VLMs) and workstations using the NetWare shells (excluding NETWARE.DRV which can be found in NET33X.EXE) (i.e.NETX.EXE, XMSNETX.EXE or EMSNETX.EXE). SOLUTION Copy the updated files to the appropriate directories, and restart Windows. Files marked with an '*' are new to WINDR3.EXE. Files marked with a '^' have been updated since WINDR1.EXE. SOLUTION: Install the files in Windr3.exe. Self-Extracting File Name: windr3.exe Files Included Size Date Time ..\ WINDR3.TXT (This file) NWPOPUP.EXE 4592 9-30-94 10:58:28 am WINDR3.WPD 25141 11-17-95 12:55:42 pm WINDR3.WRI 24064 11-17-95 12:54:58 pm ..\NTSWD\ NTSWD.EXE 109056 10-6-94 1:32:02 pm NTSWD.TXT 4803 11-14-95 3:56:34 pm ..\READMES\ VLMWIN.TXT 2548 11-14-95 8:56:32 am WINVLM.TXT 10604 11-14-95 3:55:46 pm ..\STANDARD\ TASKID.COM 7648 6-3-93 4:37:32 pm TASKID.MSG 1603 6-3-93 4:37:22 pm TBMI2.COM 24973 8-4-94 8:02:28 am TBMI2.MSG 3315 11-10-93 8:42:16 am ..\VLMDRVS\ 1252_UNI.001 727 5-31-94 12:39:46 pm 437_UNI.001 727 4-4-94 12:22:20 pm 850_UNI.001 727 4-4-94 12:22:24 pm NETWARE.DRV 165792 2-23-95 1:44:24 pm NETWARE.HLP 419701 8-29-94 1:15:00 pm NWUSER.EXE 5072 10-28-93 8:12:42 am UNI_1252.001 2264 5-31-94 12:39:48 pm UNI_437.001 2904 4-4-94 12:22:24 pm UNI_850.001 2776 4-4-94 12:22:28 pm UNI_COL.001 1752 4-4-94 12:22:18 pm UNI_MON.001 4312 4-4-94 12:22:18 pm ..\VXDS\ DEADLOCK.TXT 15927 11-14-95 9:02:14 am VIPX.386 23855 5-23-94 9:51:40 am VIPX.DOC 43732 10-1-94 7:45:54 pm VNETWARE.386 15645 10-13-95 11:04:14 am VPICDA.386 11063 1-30-91 10:58:44 am Installation Instructions: ================================================================= NOTE: When you expand WINDR3.EXE, it will automatically create five sub-directories: ================================================================= [VLMDRVS] Contains Windows drivers specific to NetWare DOS Requester (VLM) workstations. [NTSWD] Includes a Windows diagnostics utility provided by Novell Technical Support. [READMES] Contains additional READMES for using Windows from the NETWORK and information for Windows for Workgroups 3.11. [STANDARD] Contains the TSRs necessary to run Windows in Standard Mode. [VXDS] Contains the *.386 Virtual Device Drivers (VXDS) needed to run a Novell Windows client in 386 Enhanced Mode. NWPOPUP.EXE Contained in the root of WINDR3.EXE is used to display NETWARE messages in a Windows dialog. ================================================================= Note: NETWARER.DRV (146,736 11-24-93 9:02a) was not included in the [VLMDRVS] sub-directory. This file is not needed for ENGLISH users and can be removed from previous WINUPX.EXE installations. By removing this driver from the WINDOWS\SYSTEM directory, additional resources will be freed up. ================================================================= SPECIFIC INSTALLATION INSTRUCTIONS FOR WINDR3.EXE: Make a backup of any files currently on your workstation or File Server that appear in the list above. FOR THE FILE AT THE ROOT OF THE [WINDR3] FILE: Note: NWPOPUP.EXE at the root of [WINDR3] is not shell specific, and is for use with either NETX or VLM workstation configurations. Copy NWPOPUP.EXE to the WINDOWS\SYSTEM directory but first check and make sure that this file does not exist in the WINDOWS directory. If they do then you will need to delete it from that directory first. NWPOPUP.EXE Windows utility to "POP-UP" network messages in Windows dialog box. ================================================================= FOR THE FILES IN THE [VXDS] SUB-DIRECTORY: Note: The files in [VXDS] sub-directory are not shell specific, and are for use with either NETX or VLM workstation configurations. Copy the following files to the WINDOWS\SYSTEM directory: 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, VIPX.386 replaces this functionality in Windows 3.1) Note: Depending on your previous installation, these files listed above may be located in the \WINDOWS directory. Make sure that you a copy of these files listed above only in the WINDOWS\SYSTEM directory, as you may have spurious results if you have different versions of the same files located in different directories. 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 included in this update allows private mappings. By default, mappings are private. To change this to global, enter the following in your SYSTEM.INI file: [NetWare] NWShareHandles=TRUE The NWUSER utility allows you to select and change this option under the hot-key button by selecting Global Drives and directories. ================================================================ FOR THE FILES IN THE SUB-DIRECTORY [VLMDRVS] UNDER THE [WINDR3] 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 NetWare Client Windows Driver. NETWARE.HLP Help file for information on NWUSER tool. *NWGDI.DLL NetWare Graphical Device Interface *(REQUIRED for NETWARE.DRV v3.03 Rev A this file is found in NWDLL2.EXE not in WINDR3.EXE) NWUSER.EXE Provides an entry point into NETWARE.DRV v3.03 Rev A that provides a graphical tool set for NetWare specific functions. Copy the following files to the WINDOWS\NLS directory: 1252_UNI.001 Unicode file for US code page 1252 UNI_1252.001 Unicode file for US code page 1252 UNI_COL. 001 Unicode file for US code page 437 UNI_MON. 001 Unicode file for US code page 437 437_UNI. 001 Unicode file for US code page 437 UNI_437. 001 Unicode file for US code page 437 UNI_850. 001 Unicode file for US code page 859 850_UNI. 001 Unicode file for US code page 850 ================================================================= FOR THE FILES IN THE SUB-DIRECTORY [STANDARD] UNDER THE [WINDR3] ROOT DIRECTORY: Note: The files located in the [STANDARD] sub-directory are specific to running workstations in standard mode (WIN /S). THESE FILES ARE NOT USED BY WORKSTATIONS IN Windows 386 ENHANCED MODE. Copy the following files to the WINDOWS\SYSTEM directory: 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). TASKID.COM- This file keeps track of the TASK IDs for NetWare shells and redirectors in Windows 3.0 real and standard mode. Copy the following files to the WINDOWS\NLS\ENGLISH directory: TASKID.MSG- English message file for TASKID.COM if it is being used TBMI2.MSG - English message file for TBMI2.COM MORE INFORMATION ON THE FILES IN THE [STANDARD] SUB-DIRECTORY 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 as a TSR in the AUTOEXEC.BAT o Start Windows (In standard or Real mode) o Open a MS-DOS prompt o For Windows 3.0, load TASKID.COM as a TSR in the AUTOEXEC.BAT 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. ================================================================= HOW TO ACTIVATE THE NWUSER TOOLS FOR VLMS: To access the NETWARE.DRV v3.03 Rev A driver, install the files as described 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" which defaults to F6. 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 "end of the path". A white space in the path denotes the current map root location. Note: The following fixes have been made to NETWARE.DRV since the 3.02 version that was available in WINUP9.EXE. SYMPTOM For the VLM v3.02 NETWARE.DRV if a path with more than 64 characters is map rooted, the FILE/OPEN option in Windows would show a blank line where the drive should be listed, under the DRIVES option pull down box. SYMPTOM If NETWARE.DRV v3.02 is loaded on an HP OMNI Book, the OMNI Book's hot-key function would not work. SYMPTOM ALIAS objects were unable to be viewed with NWUSER. SYMPTOM INVALID PATH was returned when using OLE functions inside applications such as Excel and Word for Windows. The UNC (Universal Naming Convention) path function for NETWARE.DRV was corrected to return a valid path. In some cases, it would return \\\SERVER\VOLUME\. In this update, it returns the correct UNC syntax of \\SERVER\VOLUME\. SOLUTION Install the NETWARE.DRV v3.03 Rev A contained in the WINDR3.EXE file. ================================================================= THE FOLLOWING SECTION DEALS WITH INSTALLING DRIVERS FOR NETWORKED WINDOWS: o Setting up the VLMs and/or NETX workstations with the NetWare Windows drivers necessary to run Windows from the network. 1. Copy the following files from WINDR3.EXE file to the networked WINDOWS shared directory: WINDR3.EXE\NWPOPUP.EXE WINDR3.EXE\VXDS\VIPX.386 WINDR3.EXE\VXDS\VNETWARE.386 2. Also copy the following files from the WINDR3\VLMDRVS directory, located below the root of the expanded WINDR3.EXE file, to the network WINDOWS root directory: NETWARE.DRV NETWARE.HLP NWUSER.EXE 3. Create a "NLS" subdirectory under the network WINDOWS directory. Copy all the files and subdirectory(s) from a user's personal WINDOWS\NLS directory (located on a workstation's local drive) into the WINDOWS\NLS path on the server. Use either NCOPY /s /e or XCOPY /s /e to copy all the files and subdirectory(s) below the NLS directory. OR INSTEAD OF STEP 3, COMPLETE THE FOLLOWING: Create a "NLS" subdirectory under the network WINDOWS directory, and copy the following files to the NLS directory from the WINDR3\VLMDRVS directory: 1252_UNI.001 UNI_1252.001 UNI_COL.001 UNI_MON.001 437_UNI.001 UNI_437.001 UNI_850.001 850_UNI.001 Create an "ENGLISH" subdirectory under the network WINDOWS\NLS directory, and copy the following files to the ENGLISH directory from the WINDR3\STANDARD directory: TASKID.MSG TBMI2.MSG Note: After this is completed, all users on the network must use the VLMs. If NETX workstations are also accessing the shared Windows files, then refer to the file VLMWIN.TXT found in the [READMES] sub-directory. ================================================================= 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. 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, VIPX.386 from Novell replaces this file. 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 and a BSOD patch available from Microsoft. VIPX.DOC is a VIPX.386 configuration, limitation, description and programming document. WINVLM.TXT contains configuration information for Windows for Workgroups 3.11 users wanting connectivity to NetWare servers. VLMWIN.TXT contains specific information on how to configure NETX and VLMs users to run Windows from a common shared directory. The [NTSWD] sub-directory contains the README and EXE for a tool developed by Novell Technical Support (NTS). For more information on how to install this utility, refer to the README in the [NTSWD] sub-directory. ================================================================= Any comments or suggestions on how we can improve the delivery of these client update files are welcomed. Any enhancement request to these drivers are welcomed at the same address. Please send your responses to enhclient@novell.com via Internet Mail. ----------------------------------------------------------------- Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information. ----------------------------------------------------------------- ----------------------------------------------------------------- Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information. -----------------------------------------------------------------