NETWARE CLIENT 32 FOR WINDOWS 95
RELEASE NOTES
1/29/96
CONTENTS
1.0 Long Filename Support
2.0 Primary Documentation Is Help
3.0 Upgrading from a Beta Version
4.0 Compatibility Issues
5.0 Installation Issues
6.0 General Issues
7.0 Printing Issues
8.0 ODI and NDIS LAN Driver Issues
9.0 International Issues
10.0 Troubleshooting
11.0 Trademarks
12.0 Disclaimer
1.0 Long Filename Support
1.1 Long Filename Support on NetWare 4.1
To enable long filename support on NetWare 4.1 servers:
1. Copy PM410.NLM and NSWILDFX.NLM from the
ADMIN\PATCHES\NW410 folder on the Client 32
CD-ROM or the PATCHES\NW410 folder on the Admin1
diskette to the SYS:\SYSTEM folder on the server.
2. At the server console prompt, enter
LOAD OS2.NAM
3. At the server console prompt, enter
LOAD PM410
LOAD NSWILDFX
4. At the server console prompt, enter
ADD NAME SPACE OS2 TO VOLUME <volume>
5. Add the load commands for the patches to the
AUTOEXEC.NCF file.
1.2 Long Filename Support on NetWare 3.11
To enable long filename support on NetWare 3.11 servers:
1. Copy PATCHMAN.NLM, SHORTAFX.NLM, and
OS2OPNFX.NLM from the ADMIN\PATCHES\NW311
folder on the Client 32 CD-ROM, or from the PATCHES\NW311
folder on the Admin1, diskette to the SYS:\SYSTEM folder on
the server.
2. Load the OS/2 name space.
At the server console prompt, enter
LOAD OS2.NAM
3. Load the patches.
At the server console prompt, enter
LOAD PATCHMAN
LOAD SHORTAFX
LOAD OS2OPNFX
4. Add the OS/2 name space to the server volumes.
At the server console prompt, enter
ADD NAME SPACE OS2 TO VOLUME <volume>
5. Add the load commands for the patches to the
AUTOEXEC.NCF file.
NOTES
PM410.NLM and PATCHMAN.NLM are the server patch
managers.
1.3 Name Space Errors on 3.1x Servers
On NetWare 3.1x servers, the following message might be
displayed on the server console:
GetOriginalNameSpace could not find the originating name space.
The DOS name space was assumed. You should run VRepair to fix this!
If this message is displayed under both of the following
circumstances, no harm or corruption has occurred to the name
space and the message can be ignored:
* The OS/2 name space is loaded on the volume.
* On a workstation running NetWare Client 32 for Windows 95,
a user displayed the "NetWare Folder" tab on the volume
property sheet, which is accessible from Network Neighborhood
and Windows Explorer.
2.0 Primary Documentation Is Help
The help files for Client 32 contain information on installing,
configuring, using, understanding, and troubleshooting Client
32. They are the primary documentation. To see the Client 32
help, open the SETUPNW.HLP file. (For example, on a Windows
95 workstation, choose "Start," choose "Run," and then enter
C:\NOVELL\CLIENT32\SETUPNW.HLP.) All the Client 32
help information is accessible from the SETUPNW.HLP file.
3.0 Upgrading from a Beta Version of Client 32
3.1 Upgrading Permanent Mappings and Network Printers
The naming format for NDS has changed. If you have permanent
drive mappings or network printers that you set up using the
Windows 95 graphical interface and they have NDS names,
remap the drives and set up the network printers again.
Drives mapped and printers captured in login scripts are not
affected by this change.
3.2 Dynamic Parameter Range Errors
When upgrading from beta versions of Client 32, some errors
might be displayed when viewing or changing some of the
dynamic parameters on the "Advanced Settings" property page.
This only occurs if you choose "Customize" at the end of Setup.
These dynamic parameters should be viewed or changed
only after rebooting the workstation.
4.0 Compatibility Issues
4.1 NetWare Login Program CTL3D32.DLL Requirement
The NetWare Login program (LOGINW95.EXE) requires
the version of the CTL3D32.DLL file that is shipped with
Client 32. Client 32 installs CTL3D32.DLL in the Windows
System folder (typically, C:\WINDOWS\SYSTEM).
If the NetWare Login program is not working properly,
ensure that the CTL3D32.DLL file is the correct version
(26,624 bytes, 9/16/95, 0:30:18 AM). If the version is not
correct, reinstall Client 32 or copy CTL3D32.DLL from
the ENGLISH folder of the CD-ROM to the Windows
System folder on the workstation.
4.2 NetWare 2.2 Compatibility Issues
There are known issues using Briefcase, Explorer, and Network
Neighborhood. Basic login and utilities are supported for
NetWare 2.2.
4.3 Named Pipes Support
Named Pipes support is available only through the components
provided by Windows 95. DOSNP.EXE is not supported under
Windows 95.
4.4 NetBIOS Support
NetBIOS applications are supported through the components
provided by Windows 95. You must enable this component
through the properties of the "IPX/SPX-compatible Protocol."
Novell's NETBIOS.EXE cannot be used with Client 32 under
Windows 95.
5.0 Installation Issues
5.1 Cannot Install from Path with Long Filename
The Client 32 installation program (SETUP.EXE) cannot be
run successfully from a path that includes a folder or folders
with a long filename.
5.2 Cannot Install from Path with Directory Map Object
The Windows 95 install services does not support Directory Map
objects. When running the Client 32 installation program
(SETUP.EXE), if you get a File Copy Error and the path given in
the message is in UNC format with a Directory Map object in it
(such as \\Tree1\.MapObject.OrgUnit.Org\Dir1\setupnw.hlp),
map a drive to the folder that has the file. Then, rerun
SETUP.EXE.
5.3 Hardware Profiles and Updating ODI Drivers
The process of updating an ODI driver during SETUP.EXE performs
an install of the ODI driver to update the registry and copy the
latest LAN driver. When a driver is installed, the driver is
marked as active for all hardware profiles. Previous hardware
profiles are not maintained.
If, for example, the workstation running SETUP.EXE currently
has an adapter installed for the docking station hardware profile
and a PC Card installed for the undocked hardware profile, upon
completion of SETUP.EXE both the docking station adapter
and the PC Card will be marked as active for both the docked and
undocked hardware profiles. Using the "Device Manager" tab of the
System control panel, the network adapters can be associated with
the desired hardware profiles.
5.4 Existing OEM.CNT File Overwritten
If there is an OEM.CNT file in the Windows Help folder
(typically, C:\WINDOWS\HELP) on your workstation, it will be
overwritten during Client 32 installation.
To preserve, your existing OEM.CNT file, copy or rename it.
Then run Client 32 installation (SETUP.EXE). After Client 32 is
installed, merge the Client 32 OEM.CNT file with the file that
you copied or renamed.
5.5 Upgrading from the VLM NetWare Client
If Client 32 installation (SETUP.EXE) generates the error message
"Novell NetWare Client 32 cannot be installed together with Client
for NetWare Networks," rerun SETUP.EXE.
5.6 Corrections to Sample MSBATCH.INF File
The sample MSBATCH.INF file, in the
ADMIN\BATCH95\NLS\ENGLISH folder on the Client 32
CD-ROM, has some incorrect settings under the [NWIP.REG]
section.
* NWIP_DOMAIN_NAME should be NWIP DOMAIN NAME
* AutoRetry_Secs should be AutoRetry Secs
* NSQ_BROADCAST should be NSQ BROADCAST
6.0 General Issues
6.1 Windows 95 Installation Services
The Windows 95 install services does not support Directory Map
objects. When installing an application, if you get a File Copy
Error and the path given in the message is in UNC format with a
Directory Map object in it (such as
\\Tree1\.MapObject.OrgUnit.Org\Dir1\file.txt), map a drive to the
folder that has the file. Then, reinstall the application.
6.2 Avoid Multi-Tasking while Logging In
Although Windows 95 allows you to perform other tasks while
Client 32 processes a login script, you should avoid doing so.
For example, opening Network Neighborhood while Client 32
is processing a login script causes the Multi-Provider Router
(MPR.EXE) to page fault.
6.3 Changing File and Folder Attributes
If you change a file or folder attribute on the "NetWare File" or
"NetWare Folder" tab and then choose "Apply," that attribute cannot
be changed using the "General" tab unless you close and reopen
"File" or "Folder Properties."
For example, if you check the "Read-only" check box on the
"NetWare File" tab and then choose "Apply" and then go to the
"General" tab, unchecking the "Read-only" check box and then
choosing "Apply" or "OK" does not reset the Read-only attribute.
To avoid this situation, it is recommended that the "NetWare File"
or "NetWare Folder" tabs be used whenever marking file or
folder attributes on a NetWare volume.
7.0 Printing Issues
7.1 NPRINTER
The NetWare 4 NPRINTER or NetWare 3 RPRINTER terminate-
and-stay-resident (TSR) programs do not work under Windows
95.
7.2 Print Capture on Windows 95
Windows 95 does not require local ports to be captured to send
print jobs to a network printer (deviceless printing). You can
send print jobs to an LPT port or to a network printer device.
Capture commands are global in Windows 95, but the settings
for captured ports are separate from the settings for network
printer devices.
7.3 NDS Print Queues
NDS print queues are not displayed in the browse dialog boxes
for the Add Printer Wizard. To install a printer from an NDS
print queue, find the queue using Network Neighborhood or
Explorer. Double-click the print queue icon and use the Add
Printer Wizard to install the printer on your computer.
Microsoft offers a file (SHELLUPD.EXE) that displays NDS
print queues in Windows 95 browse dialog boxes. You can
download the file from these Internet sites:
http://www.microsoft.com/windows/software/shellupd.htm
ftp://ftp.microsoft.com/peropsys/Win_News/FreeSoftware/shellupd.exe
7.4 HP JetAdmin Support
The HP JetAdmin (NetWare Support) service contains calls to the
registry that exist only when the Microsoft NetWare Client is
loaded. If you want to use HP JetAdmin with Client 32, install
JetAdmin for Windows 3.x on your Windows 95 computer.
8.0 ODI and NDIS LAN Driver Issues
See SETUPNW.HLP for a list of ODI LAN drivers included in this
release. The list of 32-bit, third-party LAN drivers changed after
the help was completed. The 32-bit, third-party LAN drivers
included in this release are:
ACC41.LAN
PCI40.LAN
8.1 Using LAN Drivers Other Than Those Included with This Release
If you have a LAN driver for your LAN adapter that is newer
than the one included in this release, you can install the driver
during Client 32 Setup. You can also update the driver after
Client 32 is installed.
To install a third-party ODI LAN driver during Setup:
1. Copy the driver to the \ENGLISH folder (or the install folder
you created) before installing Client 32.
2. Follow the directions in the next section for installing
third-party LAN drivers.
To update a LAN driver after installing Client 32:
1. Do either of the following:
* For 32-bit (*.LAN) drivers, copy the new driver to the client
computer's NOVELL\CLIENT32 folder.
* For a 16-bit (*.COM) driver, copy the new driver to the
client computer's NOVELL\NWCLIENT folder.
2. Follow the directions in the next section for installing
third-party LAN drivers.
8.2 Installing 3rd-Party LAN Drivers
If you want to use an ODI LAN driver from a vendor other than
Novell, you need to specify the driver in the Client 32 Setup
initialization file.
If you have a newer driver than the one provided with this
release, copy all the files from the ENGLISH folder on the
Client 32 CD-ROM to a Client 32 install folder on your hard
disk or on a network drive and copy the driver to this install
folder.
To install a third-party ODI LAN driver:
1. Before running Client 32 Setup, open NWSETUP.INI (in the
install folder) in a text editor.
2. Search for the .INF file that corresponds to LAN driver you want
to use. The .INF files for third-party LAN drivers are named
ODIxxxx.INF, where "xxxx" is the manufacturer of the network
adapter. For example, ODI3COM.INF.
3. Delete the semicolon at the front of the line.
4. Save your changes and exit the editor.
5. Run Client 32 Setup.
8.3 Do Not Remove Novell ODINSUP
Do not remove Novell ODINSUP from the Network control panel,
unless you know the ODI adapter it is bound to. Removing Novell
ODINSUP also removes NetWare Client 32 for Windows 95 if
there is only one adapter in use.
8.4 16-bit ODI Driver Limitations
Windows 95 might remove support for 16-bit drivers if you remove
or update a 16-bit driver. If you have another LAN adapter using a
16-bit driver, the driver might fail to load after you boot the
computer.
For example, if your computer has two adapters using 16-bit ODI
drivers, and you switch one of the LAN adapters to use a 32-bit
driver, the remaining 16-bit driver might not load.
To correct this problem, open the AUTOEXEC.BAT file and add
lines to load LSL.COM and NESL.COM. Add these lines before
the line that loads the 16-bit driver. For example:
LSL.COM
NESL.COM
N16ODI.COM
NE2000.COM
If two or more adapters use the same 16-bit ODI driver,
Windows 95 loads the driver from AUTOEXEC.BAT only once.
You should edit AUTOEXEC.BAT and copy the driver load
command so that AUTOEXEC.BAT loads the driver once for
each adapter.
8.5 LAN Drivers That Don't Support INT 9
LAN drivers that don't support interrupt 9 but do support
interrupt 2 will fail to load and initialize if their "Interrupt
(IRQ)" is set to 9/2 on the "Resources" tab of the property
sheet for the LAN driver's network adapter. If this happens,
the "Novell NetWare Login" dialog box is not displayed
because network connections cannot be established if the
LAN driver doesn't successfully load.
In this event, change the "Interrupt (IRQ)" setting to 2, by
doing the following:
1. Add a new network adapter using the Network control
panel.
2. Set the "Interrupt (IRQ)" setting on the "Resources" tab
to 2.
3. Remove the old network adapter, which had "Interrupt
(IRQ)" set to 9/2.
8.6 Large Packet Sizes with 16-bit ODI Token-Ring Drivers
Although token-ring networks can operate with a packet size of
17954 bytes, the initial release of Client 32 will only support
packet sizes up to 10240 bytes for 16-bit ODI token-ring drivers.
NOTE: Novell has found that the optimum packet size is
approximately 4222 bytes (the default for NTR2000.COM).
To specify the packet size, set the MAX FRAME SIZE
parameter in the NOVELL\NWCLIENT\NET.CFG file to
a value from 638 to 10240. For example:
LINK DRIVER NTR2000
MAX FRAME SIZE 2174
Also, set "Link Support Layer Max Buffer Size," which is
on the "Advanced Settings" tab of "Novell NetWare Client 32
Properties," to a value greater than or equal to the value of
MAX FRAME SIZE. For more information about the
"Link Support Layer Max Buffer Size" parameter, see the
NWCFG95.HLP file.
9.0 International Issues
9.1 Text-Mode Utilities Might Not Display Correctly
Text-mode utilities (such as FILER, PCONSOLE, and NETADMIN)
might not display correctly for Korea, China, and Taiwan. The
overlay files needed to correct this problem will be provided
in a future release.
9.2 Korean Unicode Files
The ISO standards organization has not made final decisions
about Korean Unicode mapping. Because of this, Novell has
decided not to include a Unicode mapping table with this
release of Client 32. Use the information in section 9.3
to copy the files for Korean codepage 949. Novell will make
a Korean Unicode mapping table available as soon as possible.
9.3 Windows 95 Codepages Supported
The following language codepages are supported in Novell
Client 32:
874 Thai
932 Japanese
936 Chinese Simplified
950 Chinese Traditional
1250 Eastern Europe
1251 Cyrillic
1252 English and Western Europe
1253 Greek
1254 Turkish
1255 Hebrew
1256 Arabic
1257 Estonian, Latvian
If you are using another version of Windows 95, you might see
the following message during startup where "<cc>" is your
country code and "<cp>" is your codepage:
NWDRV-3.00.30: Initialization of the Unicode tables failed
Country id = <cc> and code page = <cp>
All NetWare Directory Services functions are disabled.
If your system uses a codepage that is not yet supported,
copy the following files from the Client 32 CD-ROM's
ENGLISH folder to both the \NOVELL\NLS and \WINDOWS\NLS
folders:
COPY UNI_000.001 UNI_<cp>.001
COPY 000_UNI.001 <cp>_UNI.001
These Unicode mapping tables will restrict object naming to ASCII
characters 0x20 through 0x7E (except 0x5C) for old applications
that use NETWARE.DRV. The following characters are the ASCII
characters that can be used:
Backspace Tab Line-Feed Carriage-Return Space
! " # $ % & ( ) * + , - . /
0 1 2 3 4 5 6 7 8 9 : ; < = > ?
@ A B C D E F G H I J K L M N O
P Q R S T U V W X Y Z [ ] ^ _
` a b c d e f g h I j k l m n o
p q r s t u v w x y z { | } ~
9.4 Older Applications
In some cases you might see the message in section 9.3 for existing
applications that are not installed on the server. In this case,
place SYS:PUBLIC into your PATH or copy the four (4) .<cc>
files for your country code from the server to your \WINDOWS\NLS
directory. If your country code is 44, then copy *.044 to
\WINDOWS\NLS from the server SYS:LOGIN\NLS directory.
10.0 Troubleshooting
10.1 Resolving Application Communication Problems
Complete the following steps if your IPX/SPX applications
are not functioning:
1. Determine the frame type used for IPX communications at your
site either by asking your network manager or by examining a
NET.CFG file on another computer.
2. Select "Network" from the "Control Panel" and double-click
"IPX 32-bit Protocol for Novell Client 32."
3. Select the "Advanced IPX" page.
4. Check "Primary logical board" and select a frame type to match
the frame type used on your network. Type a frame type name
if the frame type that you need is not listed.
5. Click "OK" until you exit the "Network" dialog box.
6. Restart your computer and try running the application again.
10.2 Changing CDs
If you have a CD mounted on a server and someone dismounts the CD
and mounts a new one, you won't see the newly mounted CD in the
Network Neighborhood unless you detach the server and reattach. If
you turn caching off by setting "File Cache Level" to 0, you won't
have this problem. For more information about the "File Cache
Level" parameter, see the NWCFG95.HLP file.
10.3 Refreshing the Windows Explorer Display
To refresh the Windows Explorer display, press <F5>. Changes to files
and folders outside the Windows Explorer might not be shown in the
Windows Explorer until you refresh the display. Such changes include
creating, copying, moving, deleting, and renaming.
10.4 Long Filenames Might Be Truncated
If you move a file with a long filename to a network folder that
has a long name using the DOS-compatible names for each, the
filename is truncated. For example, if there is a
LONGFILENAME.TXT file and a LONGFOLDERNAME folder,
the following command would result in the filename being
truncated to LONGFILE.TXT:
MOVE LONGFI~1.TXT LONGFOLD
You can move the file without having its name truncated by
using the long filenames of the file or folder.
11.0 Trademarks
11.1 Novell Trademarks
Novell and NetWare are registered trademarks of
Novell, Inc. in the United States and other
countries.
Client 32, Internetwork Packet Exchange and IPX, IPX/SPX,
NetWare 3, NetWare 4, NetWare Client, NetWare Directory
Services and NDS, Open Data-Link Interface and ODI, and
Sequenced Packet Exchange and SPX, Virtual Loadable
Module and VLM are trademarks of Novell, Inc.
11.2 Third-Party Trademarks
HP is a registered trademark of Hewlett-Packard Company.
NMS is a trademark of PC-Plus Communications LP.
OS/2 is a registered trademark of International Business
Machines Corporation. Microsoft and Windows are registered
trademarks, and Windows 95 is a trademark, of Microsoft
Corporation.
12.0 Disclaimer
Novell, Inc., makes no representations or warranties
with respect to any NetWare software, and specifically
disclaims any express or implied warranties of
merchantability, title, or fitness for a particular
purpose. Distribution of any NetWare software is
forbidden without the express written consent of
Novell, Inc. Further, Novell reserves the right to
discontinue distribution of any NetWare software.
Novell is not responsible for lost profits or revenue,
loss of use of the software, loss of data, costs of
recreating lost data, the cost of any substitute
equipment or program, or claims by any party other
than you.
Novell strongly recommends a backup be made before
any software is installed. Technical support for this
software may be provided at the discretion of Novell.
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.