Novell Client For Windows 95/98 Release Notes
3/10/00
Table of Contents
1.0 Overview
2.0 Installing
3.0 Logging In
4.0 General
5.0 Printing
6.0 Primary Administrative Documentation is HTML
7.0 Legal Information
Note: Additional issues associated with this release are
located in TID #2955975 at www.support.novell.com.
1.0 Overview
These notes describe new features and some issues that
have not been resolved for this release of the Novell*
Client* for Windows** 95/98 software. Most of these
issues will be resolved in future releases.
This release supports workstations running the following
versions of Windows:
* Windows 95a
* Windows 95b
* Windows 95c
* Windows 98
* Windows 98 SE
This release does not support the original release of
Windows 95.
2.0 Installing
2.1 Update Required on NetWare 4.11 and NetWare 4.2 Servers
NetWare 4.11 and NetWare 4.2 servers require an
update on the server prior to the installation of
this Client. The server update information is
located in TID 295244 in the Novell Technical
Support database at www.support.novell.com.
2.2 ODI Drivers Not Installed
ODI* drivers have not been available since Novell
Client for Windows 95/98 v2.2.
If you are upgrading an older version of Novell
Client and you have ODI drivers currently installed,
these ODI drivers may still work. If you are
installing Novell Client for the first time, NDIS
drivers will be installed. If you do not already
have the necessary NDIS driver, you might need to
obtain it from the Windows CD-ROM or from the
network board manufacturer.
2.3 "The DeviceIDDeleteOrder section in NWSETUP.INI is
either incomplete, or incorrect."
During installation on Windows 95a, an error occurs
if the network board is not configured properly
(that is, if the IRQ and port numbers are not
correct or they conflict with another device).
To solve this problem, configure the network board
manually or apply the OSR2 patch from the
Microsoft** Web site.
2.4 MFC42.DLL Error
Novell Client runs with MFC42.DLL version 4.21.7022
or later. MFC42.DLL version 6.00.8267.0 is installed
when you install Novell Client. If an older version
is installed over the version installed by Novell
Client, the client login fails with an error message
similar to the following:
"The ordinal 6453 could not be located in the
dynamic link library MFC42.DLL."
The actual message might vary, depending on the
version of MFC42.DLL you are using.
To recover from this error, reinstall the correct
version of MFC42.DLL. You can find the correct file
on the ZENworks* CD at:
D:\PRODUCTS\WIN95\IBM_ENU\MFC42.DLL
Copy the DLL to the following directory on your
workstation:
C:\WINDOWS\SYSTEM
2.5 Incompatibility with Built-In Audio and Video Drivers
on Hewlett-Packard Vectra and Compaq Presario Computers
Some Hewlett-Packard** Vectra** and Compaq**
Presario** computers use drivers for their built-in
audio and video features that are incompatible with
Novell Client for Windows 95. This incompatibility
can cause a general protection fault (GPF)on the
workstation.
If you use a Hewlett-Packard Vectra or Compaq
Presario computer and experience a GPF after
installing Novell Client for Windows 95/98, use one
of the following methods to avoid a GPF:
1. Update your audio and video drivers. Current drivers can
be obtained from your workstation's manufacturer.
2. Install generic audio and video drivers.
3. After installing the client, do not restart the
workstation. Return to Windows and shut down the workstation
using the Start > Shut Down option. Finally, restart the
workstation.
2.6 Unable to find NWUSE.HLP During Installation
If you are upgrading Novell Client on a workstation
running
Windows 95b, you might be prompted for the NWUSE.HLP
file during installation. This message occurs due
to certain hardware configurations.
If you receive this message, you must abort the
current installation and uninstall your existing
client software using the version of UNC32.EXE that
shipped with the Novell Client software that you
already have on your workstation. Then, delete the
Client32 directory on your hard disk.
You can now install the latest version of Novell
Client.
2.7 ZENworks 2 Remote Control and Workstation Inventory Not
Installed
Only the full version of ZENworks 2 includes the
Novell Client software that installs Remote Control
and Workstation Inventory capabilities to desktops.
ZENworks 2 (full) ships on a product CD. If you
download a version of the Novell Client from the
Novell Web site or if you update to a version of the
client that is later than those that shipped with
ZENworks 2, you may not have the option to install
Remote Control and Workstation Inventory components.
3.0 Logging In
3.1 Login Restrictions Set for IPX/SPX Prevent User From
Logging In
Symptom: Login restrictions are set for IPX/SPX* and
the node address. When the administrative
workstation is reset, the new client files are
automatically updated and the reboot prompt is
displayed. After restarting, the workstations that
are placed in the restriction list as being able to
log in as admin and which now have the new client
cannot log in and no administration of the server
can be done.
Cause: This is a problem with preferring the IP
protocol. The allowed addresses assigned in NDS*
are IPX* addresses. If the server is bound to IP,
the clients are designed to prefer this protocol by
default. The result is that the client is
attempting to log in to the server using IP but the
address is restricted to only allow IPX addresses,
causing an authentication failure. This is due
ultimately to the IP address not being stored in
NDS.
Solution: Do not bind IP to the server until static
IP addresses have been assigned. Or, change your
protocol preference to IPX.
3.2 Associating Login Restrictions with Workstation Objects
Login restrictions can be associated with
Workstation objects and OUs, but not with groups of
Workstation objects. If a policy is associated with
a group of Workstation objects, the policy is not
effective.
Do not associate login restrictions with a group of
Workstation objects. Associate login restrictions
only with a single Workstation object or OU.
4.0 General
4.1 Dial-Up Networking With LAN Connections
Using Dial-Up Networking concurrently with a LAN
connection might cause name resolution problems.
Servers on the LAN or the Dial-Up connection might
not be found. To solve this problem, disable the
LAN adapter by doing the following:
1. Click Start > Settings > Control Panel.
2. Double-click System, and then click the Device Manager
tab.
3. Double-click the network adapter** you want to disable.
4. In the Device Usage field, check Disable in this
Configuration, and then click OK.
4.2 WINSOCK2 Not Set Up Correctly on Windows 95 with Early
Versions of DCOM'95
WINSOCK2 is not set up correctly if the clientworkstation has
DCOM'95 installed and the version is not 812 or
later. WS2Setup.exe closes but no feedback is given
to the user about the problem.
The following is from the Microsoft Web page:
http://www.microsoft.com/Windows95/downloads/content
s/WUAdminTools/S_WUNetworkingTools/W95Sockets2/Relea
seNotes/ReleaseNotes.asp
WS2SETUP.EXE AND DCOM'95
WS2SETUP.EXE will only install on machines that
have DCOM'95 build 812 or higher, or no version
of DCOM'95 at all. If a version of DCOM'95
prior to build 812 is detected, WS2SETUP.EXE
will abort without installing Winsock2 for
Windows 95 and an error message will be written
to WS2SETUP.LOG. To obtain an updated version
of DCOM'95, see:
http://www.microsoft.com/com/dcom95/download-
f.htm for availability, download instructions
and release notes.
4.3 IPX Compatibility and Server Versions
This client version requires that the servers
hosting Migration Agents be installed with the SP1
(or later) version of NetWare 5.
You can also configure CMD servers as Migration
Agents to force the client to obtain routing/service
information about the IPX network from those
servers.
4.4 NetWare Administrator 5.19f Doesn't Run
Because Novell Client for Windows 95/98 version 3.2
client sets Use Extended File Handles to OFF by
default, the TLS manager in NetWare Administrator
5.19f will not function properly. Setting Use
Extended File Handles to ON fixes the problem
temporarily, but this setting is reset every time
the workstation is rebooted.
To resolve this issue, upgrade to Novell Client for
Windows 95/98 version 3.21. This version is included
with NetWare 5.1 Support Pack 1 and is available for
download at www.novell.com/dowload.
5.0 Printing
5.1 Printing to a Volume with Insufficient Space
When you print a large file to a volume with
insufficient space, Novell Client returns an error
that might hang the computer. This occurs because
Novell Client cannot retry printing because the
volume is out of disk space, and it will not delete
the print job in order to make sure that important
data will be lost. To resolve this problem, make
sure that you have sufficient disk space before you
start to print a large file.
5.2 Printer Driver Setup
Associating a printer driver with a printer or queue
in the printer policy packages requires driver files
to be copied to a server. The path that these files
are copied to is displayed in the Path box in the
Setup Printer Driver dialog box (which is displayed
when you select New Driver in the Printer Policy
dialog box). Users or workstations must have Read
and File Scan rights to this path (SYS:PUBLIC on the
server where the queue resides) if the workstation
or user package is to be able to download these
drivers to the workstation. The printers associated
with a package will not be installed if the drivers
are not downloaded.
When you select a driver to be associated with a
printer, you might be asked to enter a path where a
.INF file or driver is located. If you are setting
up drivers for an NT package while running Windows
95/98, you are asked to enter the path where the
NTPRINT.INF file is located. This file is located in
the WINDOWS\INF directory (the WINDOWS directory is
where NT 4.0 is installed). The easiest thing to do
is to copy all of the files from the I386 directory
of your NT installation CD to an area on a server or
on the workstation and then to copy the NTPRINT file
to that same directory.
Once you have given the path to the .INF file, a
list of drivers displays. Select the driver that you
want. You might then be asked where the driver files
are located. (If the drivers and the .INF file are
in the same directory, you might not be prompted for
the location.) If the drivers are somewhere else
(usually on the NT install CD if you have not copied
them to a different path), then browse to the path
or type it in. The files are then copied to the path
on the server.
If you are setting up drivers for Windows 95/98
while running Windows NT, you are prompted to enter
the path to the MSPRINT.INF file location. This file
is located in the WINDOWS\INF directory (the WINDOWS
directory is where Windows 95/98 is installed). The
easiest thing to do is to copy all of the .CAB files
from the WIN95 or WIN98 directory of your Windows
installation CD to an area on a server or the
workstation, and then copy the MSPRINT.INF,
msprint2.inf, and LAYOUT.INF files to that same
directory. If you are installing drivers for a
Windows NT package on Windows NT or a Windows 95/98
package on Windows 95/98, you will not be asked for
the .INF files. However, you must still point the
install to where the drivers are located, usually
the Windows installation CD.
If you attempt to copy drivers that are set as Read-
Only, then the Microsoft API will copy the files as
.TMP files. This will cause problems when users
attempt to download the driver because the driver
will not be found. Make sure the files in the area
that you copy from are not Read-Only. This usually
will not be a problem if you follow the above
directions.
5.3 "Error writing to <printer>: Space to store the file
waiting to be printed is not available on the server" or "A
write fault occurred while printing"
You may experience difficulties printing through
NDPS* if your network connection is dropped and
later auto-reconnects. To resolve this problem, you
must download and install NetWare 5 Support Pack 2
(NW5SP2.EXE) from www.novell.com/download.
Instructions for downloading and installing the
Support Pack are included with the download.
After installing NetWare 5 Support Pack 2
1. At the server console, load NDPSM.NLM to load NDPS
Manager on the server.
2. From the NDPS Manager main menu, select Printer Agent
List.
3. Select a Printer Agent.
4. Once the Printer Agent information is displayed, select
Configuration: (See Form).
5. From the configuration screen, change the Security Level
from High to Medium.
6.0 Primary Administrative Documentation is HTML
The HTML documentation for Novell Client for Windows
95/98 contains information on installing, configuring,
using, understanding, and troubleshooting Novell
Client. The HTML documentation is available on the
Novell Web site, at
http://www.novell.com/documentation.
In addition to the HTML documentation, user
documentation can be found in Novell Client User Guide
located on the red N in the toolbar.
7.0 Legal Information
7.1 Disclaimer, Patents, and Copyright
Novell, Inc. makes no representations or warranties
with respect to the contents or use of this
documentation, and specifically disclaims any
express or implied warranties of merchantability or
fitness for any particular purpose. Further, Novell,
Inc. reserves the right to revise this publication
and to make changes to its content, at any time,
without obligation to notify any person or entity of
such revisions or changes.
Further, Novell, Inc. makes no representations or
warranties with respect to any software, and
specifically disclaims any express or implied
warranties of merchantability or fitness for any
particular purpose. Further, Novell, Inc. reserves
the right to make changes to any and all parts of
Novell software, at any time, without any obligation
to notify any person or entity of such changes.
U.S Patent Nos. 5,349,642; 5,594,863; 5,633,931; and
5,692,129. U.S. and International Patents Pending.
Copyright (C) 1996, 1998-2000 Novell, Inc. All
rights reserved. No part of this publication may be
reproduced, photocopied, stored on a retrieval
system, or transmitted without the express written
consent of the publisher.
7.2 Trademarks
Novell and NetWare are registered trademarks of
Novell, Inc. in the United States and other
countries.
Client 32, Internetwork Packet Exchange and IPX,
NDS, NetWare/IP, Novell Client, and Open Data-Link
Interface and ODI are trademarks of Novell, Inc.
All third-party trademarks are the property of their
respective owners.
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.