Novell Client for Windows NT Release Notes 4/10/98 These notes describe new features and some issues that have not been resolved for this release of the Novell* Client* for Windows** NT** software. Most of these issues will be resolved in future releases. This release supports Intel**-based Windows NT Workstation 4.0 workstations. To install Novell Client for Windows NT, you must have access to the Windows NT 4.0 CD or be able to access Windows NT installation files over the network. ----------------------------------------------------------------------- ----------------------------------------------------------------------- Contents ----------------------------------------------------------------------- 1.0 Client Installation 2.0 NetWare/IP Issues 3.0 Login and Shutdown 4.0 Drive Mappings 5.0 Profile Storage 6.0 RAS Issues 7.0 File Manager Toolbar 8.0 How Customers Can Get Support 9.0 Unlocking a Locked Workstation 10.0 Print Issues 11.0 Driver Issues 12.0 Software Compatibility 13.0 Win2NCS Compatibility Issues 14.0 Miscellaneous 15.0 Trademarks, Copyright, Disclaimer, and Patents ----------------------------------------------------------------------- 1.0 Client Installation ----------------------------------------------------------------------- No installation issues at this time. ----------------------------------------------------------------------- 2.0 NetWare/IP Issues ----------------------------------------------------------------------- ----------------------------------------------------------------------- 2.1 NetWare/IP: DHCP vs. Custom Configuration ----------------------------------------------------------------------- If DHCP is not enabled, the only way to get NetWare*/IP* to run is to use the custom configuration option. To use this option, there must be a specified NetWare/IP domain or DSS server; otherwise, NetWare/IP will not load. ----------------------------------------------------------------------- 2.2 NetWare/IP Performance on Windows NT 4.0 Multiprocessor Workstations ----------------------------------------------------------------------- In the past, NetWare/IP has not performed well on Windows NT 4.0 multiprocessor workstations. This problem has been fixed in the Microsoft** Service Pack 2 for Windows NT 4.0. ----------------------------------------------------------------------- 2.3 NetWare/IP Multiboard Support ----------------------------------------------------------------------- NetWare/IP does not support multiple network boards. NetWare/IP will work over RAS alone or on the LAN alone. It does not work when someone tries to use a board other than the one currently being used. ----------------------------------------------------------------------- 2.4 NetWare/IP Auto-Connection over Dial-Up Servers ----------------------------------------------------------------------- In the LAN environment, NetWare/IP clients can be automatically configured by DHCP. This works only if your DHCP host can be configured for NetWare/IP client configuration records. In a dial-up environment, the NetWare/IP client usually depends on a DHCP host located in the dial-up server itself. Again, this works only if the DHCP host in the dial-up server can be configured for NetWare/IP client configuration records. If you are using a dial-up server that cannot be so configured, then you must manually configure the client. ----------------------------------------------------------------------- 2.5 NetWare/IP and the IP/IPX Gateway ----------------------------------------------------------------------- NetWare/IP requires a TCP/IP protocol stack on the client and an IP connection to the network. Although NetWare/IP coexists with the IP/IPX* Gateway, NetWare/IP cannot be run over the gateway. This is because the gateway does not supply an IP connection to the network for low-level services such as NetWare/IP. For example, if you want to run a NetWare/IP client over a dial-up connection, you must enable IP for that connection. ----------------------------------------------------------------------- 3.0 Login and Shutdown ----------------------------------------------------------------------- ----------------------------------------------------------------------- 3.1 Login Utilities ----------------------------------------------------------------------- The NetWare 3* login utility does not work with this client. Also, we recommend that you don't use the NetWare command line login utility either. Use the Novell Client Login to log in to the network. There are several ways to initiate a Novell Client Login once you have already logged in to NetWare or the local workstation: 1. Click Start > Programs > NetWare (Common) > NetWare Login. 2. In Network Neighborhood, double-click the server or tree you want to log in to, and the NetWare Login automatically loads. 3. In Network Neighborhood, right-click on the desired tree or server and choose either Authenticate or Login. 4. Run loginw32.exe from the DOS command prompt. ----------------------------------------------------------------------- 3.2 Logout Utility ----------------------------------------------------------------------- The logout.exe command is also not recommended for use. If you use this command, you should use it with a server name specified (for example: LOGOUT ). If you want to log in to new NetWare services while logging out of or clearing your current connections, use the NetWare Client Login (use any of the methods described in section 3.1 above to start the login) and click the Clear Current Connections check box. If you want to log out of both the Windows NT workstation and NetWare, press Ctrl+Alt+Del and click the Logout button. Alternatively, another way to log out of a specific server is to right-click Network Neighborhood, click NetWare Connections, select the server or tree, and then click Detach. ----------------------------------------------------------------------- 3.3 CAPTURE Execution in a Login Script ----------------------------------------------------------------------- If you use a login script that contains an external CAPTURE command using capture.exe, the screen might go blank with a blinking cursor in the upper-lefthand corner. Eventually, the capture executes and everything returns to normal. This happens if Windows NT is set to "full screen" when the CAPTURE command is executed from the login script. Although things are working correctly, a slow server performing the capture with a blank screen makes it appear as though it is not working. Follow these steps: 1. Click My Computer > Control Panel > MS-DOS Console. 2. In the Console Windows Properties dialog box, make sure the Options tab is selected. 3. From the Display Options group, click Window. ----------------------------------------------------------------------- 3.4 NetWareAutoAdminLogon ----------------------------------------------------------------------- This feature allows the system to automatically log on a user each time the system boots or the user logs off. Availability of this feature is controlled by registry key values. To use this feature, you must first log in to the workstation as the desired AutoLogon user, using the location profile and login script settings that you want used during an AutoLogon. If you do not use the settings you want used during an AutoLogon, the default location profile will override many of the AutoLogon settings. These key values have value types of REG_SZ. These values must be entered in the following path: \HKEY_LOCAL_MACHINE\Software\Novell\NWGINA\LoginScreen The following values need to be added: Value: NetWareAutoAdminLogon Value data: "1" enables AutoLogon; "0" disables it Value: DefaultNetWarePassword Value data: Value: DefaultNetWareUserName Value data: Value: DefaultNDSTree Value data: Value: DefaultNDSContext Value data: Value: DefaultNDSServer Value data: Value: DefaultBinderyServer Value data: Note: AutoAdminLogon must also be enabled for the NT system. This is done by setting registry key values in the Winlogon ini key, which is found at \HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon The following NT values also need to be set: Value: AutoAdminLogon Value data: "1" enables AutoLogon; "0" disables it Value: DefaultPassword Value data: Value: DefaultDomainName Value data: Value: DefaultUserName Value data: ----------------------------------------------------------------------- 3.5 AutoAdminLogon and Changing Passwords in NetWare Login ----------------------------------------------------------------------- If AutoAdminLogon is enabled, be careful when running the NetWare Login utility from the icon in the NetWare (Common) group. When run as a standalone from the icon, the NetWare Login utility does not recognize that the workstation is running AutoAdminLogon. If your primary connection's password expires when running NetWare Login from the icon, you will be given the chance to synchronize all NetWare and NT passwords. Make sure you do not synchronize the NT password, because NetWare Login does not update the Registry setting for AutoAdminLogon. ----------------------------------------------------------------------- 3.6 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\winnt\i386\libs32\mfc42.dll Copy the DLL to the following directory on your workstation: c:\winnt\system32 ----------------------------------------------------------------------- 3.7 Login script command SET_TIME ON/OFF behaves differently on NT ----------------------------------------------------------------------- Novell Client for Windows NT Properties > Advanced Settings contains a "Set Workstation Time" property. When this setting is On, the workstation time is always synchronized with the network during GINA Login. The Login script SET_TIME command has no effect on time synchronization. This is due to the time being synchronized before the script command is processed. When the setting is Off, the "SET_TIME ON" script command will have an effect when scripts are run and the workstation time will be synchronized with the network. ----------------------------------------------------------------------- 4.0 Drive Mappings ----------------------------------------------------------------------- ----------------------------------------------------------------------- 4.1 Map.exe ----------------------------------------------------------------------- The map.exe utility might function improperly if the computer's DOS environment size is small. If you encounter problems while running map.exe, increase the DOS environment size by adding or editing the "SHELL=" line in the winnt\system32\config.nt file. For example: SHELL=%SYSTEMROOT%\SYSTEM32\COMMAND.COM /E:2048 Map.exe was not designed as a Windows NT executable and, therefore, does not recognize drives mapped to NT servers as network drives. Consequently, MAP will not list NT network drives. The Windows NT NET USE command can be used to correctly connect and list network drives for both NetWare and NT servers. ----------------------------------------------------------------------- 4.2 Drive Mappings ----------------------------------------------------------------------- All drive mappings made using the NetWare Login are root mapped. Programs cannot access directories above the directory that the drive is mapped to. ----------------------------------------------------------------------- 4.3 Turning Off Map Root ----------------------------------------------------------------------- This release includes a feature that allows you to turn off map root from a login script by doing the following: 1. Right-click My Computer. 2. Click Properties > Environment. 3. Enter MAPROOTOFF (all one word) as a variable. Note: Because this is an environment variable, you could also put SET MAPROOTOFF="1" as the first line in the login script. This would globally force all NT workstations using the login script to not map root drives. 4. Set the value of the MAPROOTOFF variable to 1. 5. Click Select. This feature only affects MAP commands performed in a login script. Once Windows NT has been started, NT allows you only to map to the root. ----------------------------------------------------------------------- 4.4 Errors When Reconnecting Permanent Drive Mappings to Servers in Different Directory Trees ----------------------------------------------------------------------- In Windows NT 4.0, users might encounter an error when restoring permanent drive mappings to NetWare servers which are in different Directory trees. These mappings will be authenticated through NDS. The user might get an "Invalid Password" prompt when restoring these drives. This is not because the password is invalid, but because the client does not have a valid context for the secondary tree. If this problem is encountered, enter the default context for all Directory trees on the Client tab of the Novell Client Configuration page. This is accessed by right-clicking Network Neighborhood, and then clicking Properties > Services > Novell Client for Windows NT > Properties. ----------------------------------------------------------------------- 4.5 Permanent Connections ----------------------------------------------------------------------- If you have a permanent drive mapping that conflicts with a drive mapping made in your login script, a dialog box appears indicating that an error occurred while reconnecting the drive and that the local device name is already in use. One of the options in this dialog box has some confusing results. If you check Do Not Try to Restore the Connection in the Future and then click Yes or OK, the drive mapping made from your login script is removed. If you do not check this check box, the drive mapping from your login script is preserved. This is a bug in Windows NT itself. By default, Windows NT removes any mappings on that drive letter without checking to see if the existing mapping is the same path as the permanent connection. ----------------------------------------------------------------------- 5.0 Profile Storage ----------------------------------------------------------------------- ----------------------------------------------------------------------- 5.1 Using the Same Profile for Multiple Users ----------------------------------------------------------------------- When storing your profile through an NDS login, you can use a File System Pointer. This allows multiple users to use the same profile, provided they all use the same path as the file system pointer. ----------------------------------------------------------------------- 5.2 Long Filenames ----------------------------------------------------------------------- When storing your profile from a Windows NT 4.0 workstation on a NetWare server, that server volume must support long filenames. In versions of NetWare earlier than NetWare 4.11, the OS/2** name space was required for long filename support. In NetWare 5* and NetWare 4.1x, the long.nam name space is required. Have your network supervisor install the os2.nam or long.nam name space on the server. ----------------------------------------------------------------------- 6.0 RAS Issues ----------------------------------------------------------------------- ----------------------------------------------------------------------- 6.1 NetWare/IP ----------------------------------------------------------------------- NetWare/IP works with RAS in a Windows NT 4.0 environment only. ----------------------------------------------------------------------- 6.2 Multiboard Support ----------------------------------------------------------------------- RAS supports multiple boards. This means that both a RAS connection and a LAN connection can exist simultaneously. However, the user cannot see all of the possible servers in Network Neighborhood at once. To see the servers supported by the second board: 1. Right-click Network Neighborhood. 2. Click NetWare Connections. 3. From the resource list, select the server you connected to with RAS. 4. Click Set Current > OK. ----------------------------------------------------------------------- 6.3 Supporting a Large Number of Remote Access Users ----------------------------------------------------------------------- If you support a large number of RAS users in your network and you experience problems with users not being able to log in because of insufficient NetWare connections, try setting the Watchdog Configuration parameters so that connections time out quickly when RAS connections abnormally terminate. ---------------------------------------------------------------------- 7.0 File Manager Toolbar ----------------------------------------------------------------------- ----------------------------------------------------------------------- 7.1 Upgrading from NT 3.51 to NT 4.0 ----------------------------------------------------------------------- When upgrading from Windows NT 3.51 to Windows NT 4.0, the NetWare buttons and menu in File Manager are removed. This is because these same functions are available elsewhere in the NT 4.0 interface and the File Manager versions of these applets are not enabled for multitree support. The new locations for these functions are as follows: Send Message Right-click a server in Network Neighborhood and then click Send Message. Change Context Right-click a tree in Network Neighborhood and then click Change Context. Change Passwords Press Ctrl+Alt+Del and then click Change Password. Login To run the NetWare Login standalone, click Start > NetWare > Login. ----------------------------------------------------------------------- 8.0 How Customers Can Get Support ----------------------------------------------------------------------- We strongly encourage customers to first seek support through Novell Support Connection* J electronic services or Novell partners. Novell provides fee-based support 24 hours a day, 7 days a week, to organizations that want direct access to Novell support professionals. ----------------------------------------------------------------------- 8.1 Novell Support Connection J ----------------------------------------------------------------------- The Novell Support Connection gives you access to Novell and its partners for technical support through the Novell Support Connection Web site, the Novell Support Connection CD, Novell partners, and Premium Service*. ----------------------------------------------------------------------- 8.2 Contact Information ----------------------------------------------------------------------- You can contact Novell Support at any of the locations listed below. Internet http://support.novell.com (Americas) http://support.novell.de (Europe, Middle East and Africa) http://support.novell.com.au (Asia Pacific) gopher://gopher.novell.com (Americas) gopher://gopher.novell.de (Europe, Middle East and Africa) gopher://gopher.novell.com.au (Asia Pacific) ftp://ftp.novell.com (anonymous) (Americas) ftp://ftp.novell.de (anonymous) (Europe, Middle East and Africa) ftp://ftp.novell.com.au (anonymous) (Asia Pacific) CompuServe** Go NETWIRE Telephone 1-800-828-3362 / 801-228-5370 (PartnerNet* K) 1-800-858-4000 / 801-861-4000 (Americas) 49-211-5632-0 (Europe, Middle East and Africa) 61-2-9925-3133 (Asia Pacific) 1-800-321-3256 / 801-228-9906 (Hearing-impaired using TDD) 1-800-377-4136 / 303-297-2725 (CD subscription) See the Novell Support Connection Web site for a list of support telephone numbers. ----------------------------------------------------------------------- 9.0 Unlocking a Locked Workstation ----------------------------------------------------------------------- When the administrator unlocks a workstation, the logged-in user's applications are terminated and the user is logged out, thereby freeing the workstation to be used by any user who subsequently logs in. Access to the logged-in user's desktop is not allowed. Only the user who is logged in to the workstation can unlock the workstation and access the user's desktop. ----------------------------------------------------------------------- 10.0 Print Issues ----------------------------------------------------------------------- ----------------------------------------------------------------------- 10.1 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 an .inf file or driver is located. If you are setting up drivers for an NT package while running Windows 95, 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.inf 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 a Windows 95 package 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 is installed. The easiest thing to do is to copy all of the .cab files from the win95 directory of your Windows 95 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 package on Windows 95, you will not be asked for the .inf files. However, you must still point the install to where the drivers are located, usually the installation CD for Windows NT or Windows 95. ----------------------------------------------------------------------- 10.2 Printing DBCS Characters from DOS ----------------------------------------------------------------------- Under Windows NT, the default command window is a 32-bit process. In order to use the existing DOS printer driver for DOS-intrinsic commands, a 16-bit command window must be used. This allows DOS-intrinsic commands such as COPY, TYPE, etc., to use the print driver. The following instructions explain how to set up NT to support this. These instructions also set up the NT system to support the printer driver for DOS applications. 1. Edit the autoexec.nt file, found in the %SystemRoot%\system32 directory, and add the DOS printer driver for your specific printer. Add the printer driver after the %SystemRoot%\system32\vlmsup.exe line. Make sure you copy the printer driver to the path you specify in the autoexec.nt file. 2. Copy the \system32\config.nt file to another name such as config.prt. 3. Edit the new config file and add the DOSONLY command to the file. 4. Continue the setup process using the instructions for your specific version of Windows NT: 4a. Create a shortcut to the command.com program, found in the \system32 directory. 4b. Right-click the shortcut icon and then click Properties. 4c. On the Program property page, click Windows NT and enter the paths for the config and autoexec files that you created in Steps 1 and 2. 4d. Double-click the shortcut icon and a DOS window opens. Only DOS applications can be run from this window, but anything that is printed will be rendered by the printer driver you installed. Any commands intrinsic to DOS must be executed from this window in order to be rendered by the print driver. DOS applications can be executed by any method. ----------------------------------------------------------------------- 11.0 Driver Issues ----------------------------------------------------------------------- ----------------------------------------------------------------------- 11.1 Network Board Driver Issues ----------------------------------------------------------------------- There have been some problems found in the drivers for the following network boards (adapter cards): --Intel EtherExpress** 100 (drivers dated earlier than May 7, 1996) --HP** J2573A ISA (drivers dated earlier than April 10, 1996) --HP J2577A EISA (drivers dated earlier than April 10, 1996) For a driver that will work with one of these boards, contact the board manufacturer. ----------------------------------------------------------------------- 11.2 Older ODI Drivers ----------------------------------------------------------------------- This release of the NT Client does not update or install ODI* drivers. If an ODI driver is already in place, it will not be changed. You can only install a new--or update an existing--NDIS** driver. ----------------------------------------------------------------------- 11.3 Improper NIC Specified in Unattend.txt ----------------------------------------------------------------------- If a network interface card (NIC) is not properly specified in the Unattend.txt file, the installation fails with a blue screen. This occurs because Windows NT attempts to run the network software even though there is no card installed. ----------------------------------------------------------------------- 12.0 Software Compatibility ----------------------------------------------------------------------- ----------------------------------------------------------------------- 12.1 Microsoft SMB Client Support over IPX ----------------------------------------------------------------------- The Novell Client for Windows NT coexists with the Microsoft SMB Client over IPX networks. The Microsoft SMB Client utilizes NetBIOS when communicating over IPX, which increases the utilization of your network. If you choose, you can prevent the Microsoft SMB Client from communicating over NetBIOS by modifying your workstation configuration. Unbind the workstation and server from NWLink NetBIOS in the Network Properties page. ----------------------------------------------------------------------- 12.2 Envoy for Windows ----------------------------------------------------------------------- Currently, Envoy* for Windows (both version 1.0 and 1.0a) opens and allows you to view documents, but as soon as you try to exit the application, it hangs and requires you to reboot. If you experience this problem, go to the Novell Services Support area on the World Wide Web (http://support.novell.com/) and search for the file evynt.exe. When you run this self-extracting executable file, it produces two files--one .exe file and one .dll file. Copy these files to your Envoy directory. ----------------------------------------------------------------------- 12.3 Microsoft File and Print Services ----------------------------------------------------------------------- The Novell Client for Windows NT software does not work with Microsoft's File and Print Services for NetWare (FPNW). This is because FPNW advertises itself as a NetWare 3.12 server but does not emulate a 3.12 server. It more closely emulates a NetWare 2.2 server. When the client attaches, it attempts to use features that are available on 3.12 servers. Since FPNW does not support these features, the client is unable to use FPNW. ----------------------------------------------------------------------- 12.4 NVER ----------------------------------------------------------------------- The NVER command does not work with Windows NT. Attempting to use this command hangs the command window. ----------------------------------------------------------------------- 12.5 Attachmate Irma ----------------------------------------------------------------------- Attachmate** Irma v3.02 does not work with the Novell Client for Windows NT at this time. Attachmate recommends that customers use the 32-bit version of this application under Windows NT. ----------------------------------------------------------------------- 12.6 RCONSOLE and the Japanese Version of Windows NT ----------------------------------------------------------------------- Rconsole.exe currently does not work on NEC PC98 systems using the Japanese version of Windows NT. ----------------------------------------------------------------------- 12.7 Novell's 3270 LAN Workstation v1.2x (WSLANWIN.EXE) ----------------------------------------------------------------------- Novell cannot support this application on the v4.0 NT Client. This application cannot handle SPX* Sends that complete in true asynchronous fashion. If the SPX Sends are made synchronous, then the application works fine. Unfortunately, this would cause a negative impact on the API. Some customers have been successful in getting v2.21 to run. Novell no longer owns the rights to this application. It is now property of Attachmate. ----------------------------------------------------------------------- 12.8 VIPX and VLMSUP Commands in Autoexec.nt ----------------------------------------------------------------------- When you run SETUPNW /A /ACU, SETUPNW places the VIPX and VLMSUP commands at the end of your autoexec.nt file. This is normally not a problem. However, if you load a DOS TSR such as BREQUEST for Btrieve** applications, they require that VIPX and VLMSUP be loaded first. To fix this problem, edit the autoexec.nt file so that these commands are before the command to load the TSR. ----------------------------------------------------------------------- 12.9 Files Marked Execute-only Do Not Execute ----------------------------------------------------------------------- Only Win32 files can be marked Execute-only and work, due to a problem with the way 16-bit subsystems process executables. Microsoft is aware of the problem, but will not fix it because it breaches security in that subsystem. There is no workaround. ----------------------------------------------------------------------- 12.10 DiscView Software for a DISCPORT CD-Tower by Microtest ----------------------------------------------------------------------- When you attempt to access one of these CDs, the current process might crash. This is apparently a bug in the Microtest software. When using this software and a NetWare 4.1 or later server, the client might crash. To resolve this problem, the Microtest software needs to be updated on the server. ----------------------------------------------------------------------- 12.11 Microsoft Word 7 ----------------------------------------------------------------------- If you remove any NetWare volume while using Word 7, a Dr. Watson error occurs. Do not remove any volumes while using Word 7. Novell is discussing these problems with Microsoft in the hopes of solving them for future releases. ----------------------------------------------------------------------- 12.12 SFLOGIN ----------------------------------------------------------------------- SFLOGIN 32 v2.01 and all prior releases are incompatible with this client. For more information see the Netoria web site at http://www.netoria.com. If an incompatible SFLOGIN version is detected during installation, then it will be disabled to avoid serious workstation problems. ----------------------------------------------------------------------- 12.13 Quarterdeck CleanSweep 3.0 ----------------------------------------------------------------------- Quarterdeck CleanSweep will pagefault the NT Workstation when initializing the QDFSDRV.SYS if the Workstation Manager service is enabled. This issue is being reported to Quarterdeck. ----------------------------------------------------------------------- 12.14 Additional Software Incompatibilities ----------------------------------------------------------------------- When a new product is released, it is inevitable that software incompatibilities will be found. As Novell becomes aware of these problems, more information will be posted on the Novell Support Connect Web site. Refer to Novell Support Connect for possible workarounds to new problems and to the problems listed in these release notes. ----------------------------------------------------------------------- 13.0 Win2NCS Compatibility Issues ----------------------------------------------------------------------- ----------------------------------------------------------------------- 13.1 Win2NCS and pcANYWHERE 7.5 for Windows NT ----------------------------------------------------------------------- When using Win2NCS and pcANYWHERE** 7.5 to set up a host session on a network client, the workstation displays the message "Modem Intialization Error." This problem appears to be a timing issue between Win2NCS and pcANYWHERE 7.5 for NT. The problem is currently being addressed by both companies and will be resolved in a future release. ----------------------------------------------------------------------- 13.2 ReachOut 7.0 for Windows NT Does Not Reliably Switch COM Ports Assigned to Win2NCS ----------------------------------------------------------------------- When using Win2NCS and ReachOut** 7.0, ReachOut 7.0 for NT does not reliably switch COM ports on an existing ReachOut configuration for those COM ports assigned to Win2NCS. ----------------------------------------------------------------------- 13.3 Windows NT Experiences System Faults after Using ReachOut 7.0 for Windows NT and Win2NCS ----------------------------------------------------------------------- System faults (blue screens) have been noted in NT after using ReachOut 7.0 and Win2NCS on NT. These problems are currently being addressed by both companies and will be resolved in a future release. ----------------------------------------------------------------------- 14.0 Miscellaneous ----------------------------------------------------------------------- ----------------------------------------------------------------------- 14.1 Password Restrictions ----------------------------------------------------------------------- It is best if administrators configure NT workstations to not use any of the Microsoft password restrictions available in User Manager. Novell Client for Windows NT works best if password authentication is left up to NetWare. ----------------------------------------------------------------------- 14.2 NPRINTER ----------------------------------------------------------------------- NPRINTER is not supported in this release. If you need to use NPRINTER, email an enhancement request to enhclient@novell.com. Make sure to include your company name and impact of this problem. ----------------------------------------------------------------------- 14.3 Using LAN Adapter and Dial-up Adapter Together ----------------------------------------------------------------------- If you configure the client with LAN Adapter and Dial-up Adapter together in NETWORKING, TCP/IP will not function properly. This occurs in both Windows 95 and Windows NT 4.0 Workstation. To resolve this issue, do one of the following: --Remove LAN Adapter. --Keep the LAN Adapter, remove Dial-up Networking, and install Novell's Mobile Dialer released in NIAS 4.1 or support 3rd Party PPP Dialer. ----------------------------------------------------------------------- 14.4 Using the Novell Client v4.2 for Windows NT (English) on Korean and Chinese versions of Windows NT ----------------------------------------------------------------------- Under Chinese Simplified, Chinese Traditional, Korean, and Japanese versions of Microsoft Windows NT, the initial login will not correctly display Asian DBCS characters. The second and subsequent login dialogs will display Asian DBCS characters correctly. After starting Windows NT, Click Start > Shut Down > Close All Programs and Login As a Different User. The problem is corrected in the Novell Client v4.1 for Windows NT localized versions of Korean, Chinese Simplified and Chinese Traditional. These versions are available on www.novell.com. For information about enhancements in this release, refer to the list of differences between this release and the previous release at the beginning of this Readme. ----------------------------------------------------------------------- 15.0 Copyright, Patents, Disclaimer, and Trademarks ----------------------------------------------------------------------- ----------------------------------------------------------------------- 15.1 Copyright, Patents, and Disclaimer ----------------------------------------------------------------------- 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. U.S. Patent Nos. 5,349,642; 5,594,863; 5,633,931; and 5,692,129. U.S. and International Patents Pending. 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. ----------------------------------------------------------------------- 15.1 Novell Trademarks ----------------------------------------------------------------------- (* Novell trademark.) Envoy is a registered trademark of Novell, Inc. in the United States and other countries. Internet Packet Exchange and IPX are trademarks of Novell, Inc. IPX/SPX is a trademark of Novell, Inc. LANalyzer is a registered trademark of Novell, Inc. in the United States and other countries. NDS is a trademark of Novell, Inc. NE2000 is a trademark of Novell, Inc. NetWare is a registered trademark of Novell, Inc. in the United States and other countries. NetWare 3 is a trademark of Novell, Inc. NetWare 4 is a trademark of Novell, Inc. NetWare 5 is a trademark of Novell, Inc. NetWare/IP is a trademark of Novell, Inc. NetWire is a registered service mark of Novell, Inc. in the United States and other countries. Novell is a registered trademark of Novell, Inc. in the United States and other countries. Novell Client is a trademark of Novell, Inc. Novell Support Connection is a trademark of Novell, Inc. Open Data-Link Interface and ODI are trademarks of Novell, Inc. Packet Burst is a trademark of Novell, Inc. PartnerNet is a trademark and a service mark of Novell, Inc. Premium Service is a service mark of Novell, Inc. Sequenced Packet Exchange and SPX are trademarks of Novell, Inc. ----------------------------------------------------------------------- 15.2 Third-Party Trademarks ----------------------------------------------------------------------- (** Third-party trademark.) Attachmate is a registered trademark of Attachmate Corporation. Btrieve is a registered trademark of Pervasive Software, inc. CompuServe is a registered trademark of CompuServe Incorporated. EtherExpress is a trademark of Intel Corporation. Hewlett Packard and HP are registered trademarks of Hewlett- Packard Company. Intel is a registered trademark of Intel Corporation. Microsoft and MS are registered trademarks of Microsoft Corporation. Network Driver Interface Specification and NDIS are trademarks of PC-Plus Communications LP. pcANYWHERE is a registered trademark of Symantec Corporation ReachOut is a registered trademark of Stac, Inc. OS/2 is a registered trademark of International Business Machines Corporation. Windows is a registered trademark of Microsoft Corporation. Windows NT is a registered trademark of Microsoft Corporation.