Novell Client For Windows 95/98 Release Notes 8/31/98 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 98 This release does not support the original release of Windows 95. To install Novell Client for Windows 95/98, you must have access to the Windows 95/98 CD or be able to access Windows 95/98 installation files over the network. ---------------------------------------------------------------- Contents ---------------------------------------------------------------- 1.0 Installing 2.0 Logging In 3.0 General 4.0 Printing 5.0 IP/IPX Gateway 6.0 Primary Documentation Is HTML 7.0 Trademarks 8.0 Disclaimer, Copyright, Export Notice, Patents ---------------------------------------------------------------- 1.0 Installing ---------------------------------------------------------------- ---------------------------------------------------------------- 1.1 Installing from Diskettes ---------------------------------------------------------------- An option to install from diskettes is not available for this release. ---------------------------------------------------------------- 1.2 ODI Drivers Not Installed ---------------------------------------------------------------- ODI drivers are not installed in the latest version of the Client. If you are upgrading an older version of the Client and you have ODI drivers currently installed, these ODI drivers are still supported. If you are installing the 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 card manufacturer. ---------------------------------------------------------------- 1.3 "The DeviceIDDeleteOrder section in NWSETUP.INI is either incomplete, or incorrect." ---------------------------------------------------------------- During installation on Windows 95a, an error occurs if the network interface card is not configured properly (the IRQ and Port Numbers are not correct or they conflict with another device). To solve this problem, configure the network adapter manually or apply the OSR2 patch from the Microsoft Web site. ---------------------------------------------------------------- 1.4 MFC42.DLL Error ---------------------------------------------------------------- The Novell Client runs with mfc42.dll version 4.21.7022 or later. Mfc42.dll version 4.21.7303 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 Z.E.N.works CD at: d:\products\win95\ibm_enu\mfc42.dll Copy the DLL to the following directory on your workstation: c:\windows\system ---------------------------------------------------------------- 1.5 Drag-and-Drop Might Not Work Immediately ---------------------------------------------------------------- Drag-and-drop operations between applications or the desktop might not work immediately after the client is installed and the workstation is rebooted. To solve this problem, reboot again to ensure proper registration of the ActiveX controls included in the client. ---------------------------------------------------------------- 1.6 Using ACU to Upgrade from the Microsoft Client for NetWare ---------------------------------------------------------------- If you are upgrading from the Microsoft client for Netware to any version of the Novell Client for Windows 95/98 using the setup.exe /acu method in a login script, you must use the # sign in the login script and the user must manually restart the workstation after the Novell client installation has finished. ---------------------------------------------------------------- 1.7 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 on the workstation. If you use a Hewlett-Packard Vectra or a Compaq Presario 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. ---------------------------------------------------------------- 1.8 MSBATCH Installation Not Supported in This Release ---------------------------------------------------------------- This release of Novell Client for Windows 95/98 does not support MSBATCH installation. Please disregard the MSBATCH instructions in the documentation. However, a patch to support the MSBATCH process on Windows 98 will be made available on the Novell web site at a later date. ---------------------------------------------------------------- 1.9 "IP with IPX Compatibility" Dependancy ---------------------------------------------------------------- When using the client configuration "IP with IPX Compatibility" make sure the TCP/IP stack has been configured with a TCP/IP Gateway. This can be configured through DHCP or locally defined. The IPX Compatibility driver and IP routing will not work properly without a TCP/IP Gateway configured. Under Windows 95/98 the Gateway can be configured by opening the TCP/IP Properties page, from the Network Properties page. If your network is configured to use DHCP you do not need to configure the Gateway locally. ---------------------------------------------------------------- 1.10 "IP with IPX Compatibility" needs Migration Agent ---------------------------------------------------------------- If you are using "IP with IPX Compatibility" on the client and are trying to see IPX only servers, you need to make sure that you've configured a Migration Agent (MA) on the network. See the NetWare 5 documentation for more information on setting up a Migration Agent on the network. To troubleshoot a NetWare client's MA visibility or configuration, run the CMDINFO command from an MS-DOS Prompt. The command should list all configured or discovered MAs, depending on the IPX Compatibility configuration. ---------------------------------------------------------------- 2.0 Logging In ---------------------------------------------------------------- ---------------------------------------------------------------- 2.1 No Login with 3Com 3C589C PCMCIA Adapter ---------------------------------------------------------------- After installing Novell Client for Windows 95/98, if you are using a 3Com 3C589C PCMCIA Ethernet board, you might not receive the NetWare login screen during startup. To solve this problem: 1. Go to DOS. 2. Change to the client folder (for example: novell\client32). 3. Enter LOAD 3C589.LAN. 4. Execute the NetWare login by clicking Start > Programs > Novell > NetWare Login. ---------------------------------------------------------------- 2.2 Loginw32.exe is the Preferred Login Program ---------------------------------------------------------------- Login.exe does not work in some situations. In those cases, use loginw32.exe. ---------------------------------------------------------------- 2.3 Online help for Username and Password Contains Windows NT Information ---------------------------------------------------------------- The Novell Clients for Windows 95/98 and Windows NT share some help files. In the help for the Username and Password fields, some information was not marked as being NT-specific. The help text for Username and Password in Windows 95/98 says that the username and password can be used for logging in to a workstation, but a workstation can only be logged in to in Windows NT. Windows 95/98 has Windows login, but this is a separate dialog box from Novell Login. The username and password from Novell Login can't be used for Windows login in Windows 95/98. Also, the help text says that a workstation can be locked and unlocked in Windows 95/98, but this is an NT-specific feature. ---------------------------------------------------------------- 2.4 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 workstation and all of the other workstations that are placed in the restriction list as being able to login 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 IP. The allowed addresses assigned in NDS are IPX. 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 and so the address is restricted to only allow IPX addresses, causing an authentication failure. This is due ultimately to the IP address not being store in NDS. Solution: Do not bind IP to the server until static IP addresses have been assigned. Or, change your protocol preference to IPX. ---------------------------------------------------------------- 2.5 DOS Utilities Supported Only When Used with IPX or IP Compatibility Mode ---------------------------------------------------------------- The DOS Utilities (CX, MAP, CAPTURE, etc.) are supported only when used with IPX or IP Compatibility Mode. Use the equivalent GUI-based utilities when accessing resources that are only available from IP servers. ---------------------------------------------------------------- 3.0 General ---------------------------------------------------------------- ---------------------------------------------------------------- 3.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 filed, check Disable in this Configuration, and then click OK. ---------------------------------------------------------------- 3.2 SLP Configuration Over IP ---------------------------------------------------------------- In order to use SLP name resolution with Dial-Up Networking, you must add the directory agent's IP address to the directory agent list on the Novell NetWare Client Properties Service Location tab. To do this: 1. Click Start > Settings > Control Panel. 2. Double-click Network, and then double-click the Novell NetWare Client. 3. Click the Service Location tab. 4. Add the directory agent IP address to the directory agent list, and then click OK. ---------------------------------------------------------------- 3.3 Dial-Up Networking over IP, Unable to see Network ---------------------------------------------------------------- If you are trying to use Dial-Up Networking on the client and are unable to login or browse the Network, try the following troubleshooting suggestions. 1. Make sure that you can resolve NetWare 5 IP server names. a. For dynamic discovery of server make sure that your client can see an SLP Directory Agent. The agent can be statically configured, (see previous section), or if your Dial-Up host supports DHCP and is configured with the proper DA, then that should also work. Note: By default, the client uses DHCP to discover a DA. (This assumes that there is a DA configued on the Dial-Up host network.) b. The client will use an NWHOST file, if present, which contains server names and their addresses. This might be a preferred way to run your client. (The file is created in the "\NOVELL\CLIENT32" directory on the workstation.) c. The client also supports DNS names. After connecting to the Dial-Up host make sure your DNS server is working properly by trying to PING your server using its DNS name. If the ping was successful, then use that same DNS name as your server name in the login dialog. d. Isolate the problem down to name resolution by using an IP address instead of the server name. If the login works, the problem is in name resolution. 2. Make sure that the IP stack is still functioning properly by pinging known active IP nodes that are on the Dial-Up host network. 3. If you are using IP with Compatibility mode on the client and cannot see any IPX servers, make sure that the client has an MA conigured properly. See section 3.4. ---------------------------------------------------------------- 3.4 Dial-Up Networking with Compatibility Mode ---------------------------------------------------------------- In order to use Compatibility mode to see IPX services over a Dial-Up connection, you should statically configure the Migration Agent on the Compatibility Mode Driver property page. Note: If your Dial-Up host supports DHCP Inform requests, and it's configured to hand out Migration Agents, you shouldn't need to statically set the MA. To statically set the MA address: 1. Click Start > Settings > Control Panel. 2. Double-click Network > Compatibility Mode Driver (CMD) 3. Uncheck Use DHCP and then add a Migration Agent, using an IP address in dotted format (for example: 137.65.1.5). You can also use a DNS name, keeping in mind the dial-up environment you are trying to use. 4. Press OK to save the changes. ---------------------------------------------------------------- 3.5 Online Help Shows Wrong Default for Several Properties ---------------------------------------------------------------- The defaults for several client parameters were changed after the online help was finalized. The following list shows the corrected information. * Contextless Login The correct default is OFF. * Enable Banner The correct default is OFF. * Form Feed The correct default is OFF. * Max Cache Size The correct range is 0 to 49152. * Name Cache Level The correct default is 1. * Notify The correct default is ON. * Retries to DSS During Startup The correct range is 0 to 10. * Show Novell System Tray Icon The Correct default is ON. * Show Scheduler System Tray Icon The correct default is ON. * Shrink Path To Dot The correct default is ON. ---------------------------------------------------------------- 3.6 Advanced Settings Not Documented in Help File ---------------------------------------------------------------- Two Novell Client for Windows 95/98 advanced settings are not documented in the online help file: * File Write Through * Use Extended File Handles ---------------------------------------------------------------- 3.6.1 File Write Through ---------------------------------------------------------------- File Write Through controls whether or not all files are opened in write-through mode. If a file is opened in write-through mode, the writes to that file will not be cached on the client. In effect, File Write Through = ON disables file write caching, which reduces overall client performance but ensures data integrity in the event of catastrophic failure of the client workstation. The default setting (File Write Though = OFF) is recommended. ---------------------------------------------------------------- 3.6.2 Use Extended File Handles ---------------------------------------------------------------- Use Extended File Handles controls whether the client uses extended file handles. If Use Extended File Handles = OFF then the number of files the client can open is limited by the space available in the JFT to 170 files. If Use Extended File Handles = ON the number of files that can be opened is limited only by the value of the server's Maximum Locks Per Connection setting. Except in special cases, the default of Use Extended File Handles = OFF is recommended. ---------------------------------------------------------------- 3.7 Winsock2 not Set Up Correctly on Windows 95 with Early Versions of DCOM'95 ---------------------------------------------------------------- Winsock2 is not set up correctly if the client workstation has DCOM'95 installed and the version is not 812 or later. WS2Setup.exe closes but there is no feedback given to the user about the problem. The following is from the Microsoft Web page: http://www.microsoft.com/windows/downloads/contents/updates/ w95sockets2/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. ---------------------------------------------------------------- 3.8 Map.exe Might Fail When Mapping a Drive to an NDS Object ---------------------------------------------------------------- Map.exe is not IP-aware for NDS objects. As a result, map.exe might fail if you try to use it to map a drive to an NDS object, for example with a command like the following: map n .mydir.organization.company The failure will result in a message such as: MAP-4.13-195: Directory [N .mydir.organization.company] cannot be located This error can be avoided by using one of the following solutions: * Use "map n server\vol:\directory" instead of "map n .mydir.organization.company". * Unbind IP from the server that the NDS object points to. * Configure the Protocol Preferences of Novell Client property page to use IPX only. ---------------------------------------------------------------- 3.9 Unable to Autodetect NetWare/IP Under Some Conditions ---------------------------------------------------------------- When using NWIP with an IP & IPX Client configuration, under some configurations, NWIP will fail to get its DHCP information. The problem will be fixed in the first maintenance release of NetWare 5. Some ways to work around this problem are: * Configure the Client as IPX Only when using NWIP. * Statically configure the NWIP information during setup. ---------------------------------------------------------------- 4.0 Printing ---------------------------------------------------------------- ---------------------------------------------------------------- 4.1 Printing to a Volume with Insufficient Space ---------------------------------------------------------------- When you print a large file to a volume with insufficient space, the Novell Client returns an error which might hang the computer. This occurs because the Novell Client cannot retry printing because the volume is out of disk space, and it cannot delete the print job because it thinks that important data will be lost. To resolve this problem, make sure that you have sufficient disk space before you start printing a large file. ---------------------------------------------------------------- 4.2 Do Not Configure a Local NPRINTER with Interrupts ---------------------------------------------------------------- You should not configure a local NPRINTER with interrupts. Use the default "polled mode" instead. ---------------------------------------------------------------- 4.3 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 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 an .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 is located. This file is located in the windows\inf directory, the windows directory being the directory 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 the workstation and then 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 you want. You might then be asked where the driver files are located. (If you have put the drivers and the .inf file 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 being the directory 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 go to download the driver because the driver will not be found. Make sure the files in the area you copy from are not read only. This usually will not be a problem if you follow the above directions. ---------------------------------------------------------------- 5.0 IPX/IP Gateway ---------------------------------------------------------------- ---------------------------------------------------------------- 5.1 The Novell IPX/IP Gateway is not Included with this Release ---------------------------------------------------------------- The Novell IPX/IP Gateway is not included with this release of Novell Client for Windows 95/98. It is scheduled to be released for Windows 95/98 soon after NetWare 5 is released. ---------------------------------------------------------------- 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 this Client. The HTML documentation is available on the Novell Client CD-ROM in the Novdoc directory. The search and print functionality are available on 32-bit operating systems such as Windows 95/98 and Windows NT. In addition to the HTML documentation, interface and end-user documentation can be found in the Client help. To access the help, open the setupnw.hlp file. For example, on a Windows 95/98 workstation, click Start > Run, and then enter c:\novell\client32\setupnw.hlp. ---------------------------------------------------------------- 7.0 Trademarks ---------------------------------------------------------------- ---------------------------------------------------------------- 7.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, NDS, NetWare/IP, Novell Client, and Open Data-Link Interface and ODI are trademarks of Novell, Inc. ---------------------------------------------------------------- 7.2 Third-Party Trademarks ---------------------------------------------------------------- 3Com is a registered trademark of 3Com Corporation. Compaq and Presario are registered trademarks of Compaq Computer Corporation Dell is a trademark of Dell Computer Corporation. Hewlett-Packard and Vectra are registered trademarks of Hewlett-Packard Company Microsoft, Windows, and Windows NT are registered trademarks of Microsoft Corporation. Network Driver Interface Specification and NDIS are trademarks of PC-Plus Communications LP. ---------------------------------------------------------------- 8.0 Disclaimer, Copyright, Export Notice, Patents ---------------------------------------------------------------- Novell, Inc., makes no representations or warranties with respect to any Novell 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 Novell 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. Copyright (C)1996-1998 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. This product may not be exported outside the U.S. or Canada without prior authorization from the U.S. Department of Commerce. U.S Patent Nos. 5,349,642; 5,594,863; 5,633,931; and 5,692,129. U.S. and International Patents Pending.