home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Network Support Encyclopedia 96-1
/
novell-nsepro-1996-1-cd2.iso
/
download
/
netware
/
pnwupw.exe
/
WINDR2.TXT
< prev
Wrap
Text File
|
1994-12-19
|
18KB
|
423 lines
NOVELL TECHNICAL INFORMATION DOCUMENT
TITLE: Novell Windows Drivers Update File
DOCUMENT ID: TID500457
DOCUMENT REVISION: A
DATE: 19DEC94
ALERT STATUS: Yellow
INFORMATION TYPE: Symptom Solution
README FOR: WINDR2.EXE
NOVELL PRODUCT and VERSION:
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 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 VLMUP2.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
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 WINDR2.EXE. Files marked with a '^' have
been updated since WINDR1.EXE.
=================================================================
NOTE: When you expand WINDR2.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 WINDR2.EXE is used to display NETWARE
messages in a Windows dialog.
Self-Extracting File Name: WINDR2.EXE Revision: A
Files Included Size Date Time Version SDK
\
WINDR2.TXT (Readme in ASCII text format)
WINDR2.WRI (Readme in Windows Write format)
WINDR2.WPD (Readme in WordPerfect 5.1 format)
NWPOPUP.EXE 4,592 09-30-94 10:58a 3.01 n/a ^
\VLMDRVS\
1252_UNI.001 727 05-31-94 12:39p 2.00 n/a
UNI_1252.001 2,264 05-31-94 12:39p 2.00 n/a
UNI_COL.001 1,752 04-04-94 12:22p 2.00 n/a
UNI_MON.001 4,312 04-04-94 12:22p 2.00 n/a
437_UNI.001 727 04-04-94 12:22p 2.00 n/a
UNI_437.001 2,904 04-04-94 12:22p 2.00 n/a
UNI_850.001 2,776 04-04-94 12:22p 2.00 n/a
850_UNI.001 727 04-04-94 12:22p 2.00 n/a
NWUSER.EXE 5,072 10-28-93 8:12a 1.02 n/a
NETWARE.HLP 419,701 08-29-94 1:15p n/a n/a
NETWARE.DRV 165,632 10-24-94 2:29p 3.03 n/a ^
\NTSWD\
NTSWD.EXE 109,056 10-06-94 1:32p 1.04 n/a
NTSWD.TXT 4,814 10-04-94 10:58p n/a n/a
\READMES\
WINVLM.TXT 13,026 09-15-94 5:00p n/a n/a
VLMWIN.TXT 2,369 10-01-94 2:37p n/a n/a
\STANDARD\
TBMI2.COM 24,973 08-04-94 8:02a 3.15 n/a ^
TASKID.COM 7,648 06-03-93 4:37p 1.10 n/a ^
TBMI2.MSG 3,315 11-10-93 8:42a n/a n/a
TASKID.MSG 1,603 06-03-93 4:37p n/a n/a
\VXDS\
VIPX.386 23,855 05-23-94 9:51a 1.19 n/a
VIPX.DOC 40,790 06-09-94 9:57a n/a n/a
DEADLOCK.TXT 20,899 09-15-94 4:49p n/a n/a
VPICDA.386 11,063 01-30-91 10:58a n/a n/a
VNETWARE.386 15,645 08-17-94 3:38p 2.04 n/a
=================================================================
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 WINDR2.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 [WINDR2] FILE:
Note: NWPOPUP.EXE at the root of [WINDR2] 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 [WINDR2] 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 this file is found in
NWDLL2.EXE not in WINDR2.EXE)
NWUSER.EXE Provides an entry point into NETWARE.DRV v3.03 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
*Note: These UNICODE files are new to WINDR2.EXE
=================================================================
FOR THE FILES IN THE SUB-DIRECTORY [STANDARD] UNDER THE [WINDR2] 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 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 "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.
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 contained in the WINDR2.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 WINDR2.EXE file to the networked WINDOWS
shared directory:
WINDR2.EXE\NWPOPUP.EXE
WINDR2.EXE\VXDS\VIPX.386
WINDR2.EXE\VXDS\VNETWARE.386
2. Also copy the following files from the WINDR2\VLMDRVS directory, located
below the root of the expanded WINDR2.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 WINDR2\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 WINDR2\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.
-----------------------------------------------------------------