----------------------------------- Novell IntranetWare Client for Windows NT Release Notes 2/14/97 These notes describe issues that have not been resolved for this release of the Novell* IntranetWare* Client* for Windows** NT** software. Most of these issues will be resolved in future releases. This release supports the following: Intel**-based Windows NT Workstation 3.51 workstations, with Service Pack 4 installed Intel-based Windows NT Workstation 4.0 workstations To install IntranetWare Client for Windows NT, you must have access to the Windows NT 3.51 or 4.0 CD, or be able to access Windows NT installation files over the network. * Novell trademark. ** Third-party trademark. For more information, see Trademarks. ----------------------------------- Contents 1.0 Workstation Manager Issues 2.0 Login and Shutdown 3.0 Drive Mappings 4.0 Profile Storage 5.0 Installing NWADMNNT and NAL 6.0 NWADMNNT 7.0 NAL 8.0 DSMigrate Issues 9.0 NetWare/IP issues 10.0 Documentation Issues 11.0 RAS Issues 12.0 File Manager Toolbar 13.0 Features Not Included in This Release 14.0 Customer Support 15.0 Unlocking a Locked Workstation 16.0 Printing DBCS Characters from DOS 17.0 Driver Issues 18.0 Software Compatibility 19.0 Miscellaneous 20.0 Trademarks ----------------------------------- 1.0 Workstation Manager Issues 1.1 Installing over a Previous Version of Workstation Manager The filenames of two key Workstation Manager administration DLLs used by NWAdmin NT (NWADMNNT.EXE) have changed. If you used an earlier version of Workstation Manager, including the initial Closed Beta release, you need to delete these two DLLs and reinstall the Workstation Manager administration tool. These DLLs are located on the server that you are running NWAdmin NT from, at the paths shown below: SYS:PUBLIC\WINNT\NWCSNPNT.DLL SYS:PUBLIC\WINNT\NLS\language\NWCRES32.DLL If you do not delete these files, it is likely that some members of your organization will be using the older version of Workstation Manager without your knowledge. There is no easy way to tell if the older version is being used. 1.2 Error Message Says a DLL Cannot Be Found If, when you run the Novell* NWAdmin NT (NWADMNNT.EXE) utility, you get a message saying that either NWCSNPNT.DLL or NWCRES32.DLL cannot be found, it means that your system is trying to load the older, Closed Beta release of Workstation Manager after you deleted the old DLLs (as discussed in 1.1, above). To correct this problem, install the newer version of Workstation Manager, using the ADMSETUP.EXE program. 1.3 Workstation Manager Object Association Precedence Workstation Manager will check for Workstation Manager associations in the order of user, group, container. If a user is associated to multiple groups and each group is associated to a different NT Configuration object, there is no way to guarantee which NT Configuration object will be used. 1.4 Location of Workstation Manager Help File The Workstation Manager Help file, NTWSMGR.HLP, is installed to the WINNT\SYSTEM32\NLS\language directory on the workstation. Locate that Help file for more information about Workstation Manager. This information can also be accessed from the main Help file. 1.5 Storing Workstation Manager Snap-In Information in NDS Instead of the Registry Normally NWADMIN stores its list of snap-ins in the user's hive of the registry. This causes the following problem: If the user moves to a different computer, or if the user is deleted and re-created, it is necessary to re-add the snap-in information to the registry. This is especially a problem with Workstation Manager when using volatile users that get created every time a user logs on. NWADMIN provides a workaround so that the registry information can be stored in the User object in NDS. The information can be stored in NDS by running NWADMNNT with the /N switch. There is a page in the User object called NetWare Registry Editor that stores this information, which can be edited and configured for any snap-ins beyond the default. To configure NWADMNNT with Workstation Manager, follow these steps: 1. Run ADMSETUP to install the Workstation Manager and NWADMNNT pieces on the server. 2. Run NWADMNNT /N. This will store the default registry settings in the user's NetWare Registry Editor page. 1.6 Workstation Manager Not Activated If Workstation Manager has not been activated on a workstation, Novell IntranetWare* Client* for Windows** NT** was not installed using the SETUPNW /W or SETUPNW /U option. You can activate Workstation Manager without reinstalling the client by enabling Workstation Manager on the Novell Workstation Manager property page in the Novell IntranetWare Client Services Configuration dialog box, accessible from the Network control panel. When Workstation Manager is activated, you will need to add at least one tree to the Trusted Trees list on the property page. The Trusted Trees list contains the names of the Novell Directory trees that Workstation Manager searches to find NT Configuration objects. 1.7 NT Configuration object does not work properly An enhancement in the current release forces the Volatile User option to ON when IntranetWare credentials are not used. If the NT Configuration object was created with a previous version of Workstation Manager, the Novell Directory Services* (NDS*) software cannot recognize this change until the user opens the object in NW Admin. As soon as the user clicks the NT Configuration object to open it, the object is updated in NDS and the information that appears when the window opens is the correct information. * Novell trademark. ** Third-party trademark. For more information, see Trademarks. ----------------------------------- 2.0 Login and Shutdown 2.1 Login Utilities The NetWare* 3* login utility does not work with this client. Also, Novell recommends that you don't use the IntranetWare* command line login utility either. Use the IntranetWare Login to log in to the network. There are three ways to initiate an IntranetWare Login, once you have already logged in to IntranetWare or the local workstation: 1. Run LOGINWNT /A from the DOS command prompt. 2. Select the IntranetWare Login icon from the IntranetWare Common Group. 3. Select the IntranetWare Login icon from the Toolbar of File Manager (NT 3.51 only). or Double-click the server or tree you want to log in to, and the IntranetWare Login automatically loads (NT 4.0 only). 2.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 servername). If you want to log out or clear your current connections, use the IntranetWare Login (use any of the methods described in section 2.1 above to start the IntranetWare Login) and click the Clear Current Connection button, or log out using Ctrl+Alt+Del before proceeding with the login. Alternatively, another method to log out of a specific server is by right-clicking Network Neighborhood, choosing IntranetWare Connections, highlighting the server or tree, and choosing Detach. 2.3 LOGIN.DAT File Problems If the Login Results window was open when the client was updated, you must reboot before running IntranetWare Login or an error message about an outdated LOGIN.DAT file will appear. This message will not appear after rebooting. 2.4 Close Any NT Services Dialog Box Close any open NT Services dialog box before you try logging in to your NT workstation. If the box is not closed before you log in, the workstation might appear to hang, because the message is not being moved to the user desktop. 2.5 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. To correct the problem in Windows NT 3.51, follow these steps: 1. Start the PIF editor (PIFEDIT.EXE). 2. Open DEFAULT.PIF. 3. Change the Display Usage setting from Full Screen to Windowed. In Windows NT 4.0, follow these steps: 1. Choose My Computer. 2. Choose Control Panel. 3. Choose MS-DOS Console. 4. In the Console Windows Properties dialog box, make sure the General Settings tab is selected. 5. Under the Display Options group, choose Window. 2.6 Capturing Bindery Queues in the Login Script under Windows NT 3.51 If LPT ports are captured to bindery queues in the login script when using NT 3.51, the current context pointer will be set to the root of the tree. 2.7 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. These key values have value types of REG_SZ. These values must be entered in the following path: \HKEY_LOCAL_MACHINE\Software\Novell\NWGINA\Login Screen 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: 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\Current Version\Winlogon AutoAdminLogon should be set to "1," the DefaultDomainName should be the name of the domain the user account is in, and DefaultUserName and DefaultPassword should be the same as their equivalent NetWare key values. 2.8 AutoAdminLogon and Changing Passwords in IntranetWare Login If AutoAdminLogon is enabled, be careful when running the IntranetWare Login utility from the icon in the IntranetWare (Common) group. When run as a standalone from the icon, the IntranetWare Login utility does not recognize that the workstation is running AutoAdminLogon. If your primary connection's password expires when running IntranetWare Login from the icon, you will be given the chance to synchronize all IntranetWare and NT passwords. Make sure you do not synchronize the NT password, because IntranetWare Login does not update the Registry setting for AutoAdminLogon. 2.9 Specifying Country Name in NDS Context If you need to specify a Country, State, or Locality object in the NDS* context, you need to enter a typeful context, such as OU=Sales.O=Company.C=US If you enter a typeless context (for example, Sales.Company.US), the context will fail. This is true only when your context includes a Country, State, or Locality object. If your context does not include a country, you can use a typeless context without any problems. * Novell trademark. ** Third-party trademark. For more information, see Trademarks. ----------------------------------- 3.0 Drive Mappings 3.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 IntranetWare and NT servers. 3.2 Drive Mappings All drive mappings made using the IntranetWare Login are root mapped. Programs cannot access directories above the directory that the drive is mapped to. We are Beta testing a feature in this release that, if approved, will allow users to override the map root default. 3.3 Turning Off Map Root (Test Feature) This release includes a beta feature that is available for testing. This feature allows you turn off map root from a login script. To turn off map root: 1. Right-click My Computer. 2. Choose Properties. 3. Choose the Environment tab. 4. Enter MAPROOTOFF (all one word) as a variable. Note: Because this is an environment variable, you could also put the line: SET MAPROOTOFF=1 as the first line in the login script. This would globally force all NT workstations using the login script not to map root drives. 5. Set the value of the MAPROOTOFF variable to 1. 6. Choose Select. This feature only works from a login script. Once Windows NT has been started, NT only allows you to map to the root. 3.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 IntranetWare* servers which are in different Directory trees. In the 3.51 version of the client, which is not multitree-enabled, such mappings were made in Bindery mode. In the 4.0 client, which is multitree-enabled, 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 IntranetWare Client Services Configuration page. This is accessed by right-clicking Network Neighborhood, selecting Properties, selecting the Services tab, selecting Novell IntranetWare Client Services, and then pressing the Properties button. 3.5 Permanent Connections If you have a permanent drive mapping that conflicts with a drive mapping made in your login script, you are presented with a dialog box telling you 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 press the Yes or OK button, 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 will be 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. * Novell trademark. ** Third-party trademark. For more information, see Trademarks. ----------------------------------- 4.0 Profile Storage 4.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. This also works with IntranetWare*, NetWare* 3*, and NetWare 4* bindery connections. 4.2 Long Filenames When storing your profile from a Windows** NT** 4.0 workstation, your home directory 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 IntranetWare and NetWare 4.11, the LONG.NAM name space is required. Have your network supervisor install the OS2.NAM or LONG.NAM name space on the server. * Novell trademark. ** Third-party trademark. For more information, see Trademarks. ----------------------------------- 5.0 Installing NWADMNNT and NAL This release of IntranetWare* Client* for Windows** NT** includes an updated version of NetWare* Administrator, called NetWare Administrator NT (NWADMNNT). It also includes the Novell Application Launcher* (NAL). Note: To install NetWare Administrator NT, you must have NDS rights to create objects on the Directory tree and rights to create files on the SYS:\PUBLIC directory of the server where you are installing NetWare Administrator NT. To install NWADMNNT and NAL for use with Windows NT 1. Locate the ADMSETUP.EXE icon on the IntranetWare Client for Windows NT CD. 2. Double-click ADMSETUP.EXE. 3. Choose Yes to accept the Novell Terms and Conditions. If you choose No, you will not be able to install the administration utilities. 4. Choose Continue after reading the Administrator Utility title screen. If you choose Cancel, you will not be able to complete the installation. 5. Choose the utilities you want to install by checking the check boxes next to the utilities' names. There are three choices, Novell Application Launcher, NetWare Administrator, and Workstation Manager Administration Module. 6. Choose a server from the To Server list. 7. Choose OK. A progress screen appears. The progress screen has two progress bars. The top bar shows which application is being installed. The bottom bar shows the percentage of files that have been installed. When the files are installed, the Installation Complete dialog box appears. 8. Choose Run NWAdmin to start NetWare Administrator. OR Choose OK to exit the installer without starting NetWare Administrator. * Novell trademark. ** Third-party trademark. For more information, see Trademarks. ----------------------------------- 6.0 NWADMNNT 6.1 Using NWAdmin NT The 32-bit NetWare* Administrator for Windows** NT** (NWADMNNT) utility that ships with the IntranetWare Client* for Windows NT was built to work with IntranetWare. The 16-bit NetWare Administrator that ships with NetWare 4.1 (NWAdmin) will also work with the IntranetWare Client for Windows NT. Running the 32-bit NWADMNNT utility on NetWare 4.1 will result in the following conflicts: 1. The Template object is designed for the NetWare 4.11 NDS* schema. It will not work on a NetWare 4.1 directory. There will be a Create Template button on the toolbar, but it gives an error message when clicked. 2. Snap-ins created for older versions of NetWare Administrator will not run with the new version. 3. The DS Migrate and File Migrate snap-ins are designed to work with NetWare 4.11. They will not work with a server earlier than NetWare 4.11, but will work with this client on a NetWare 4.11 server. Note: Although the 16-bit version of NetWare Administrator will work with IntranetWare Client for Windows NT, it cannot take advantage of the NWAdmin snap-in for administrating Workstation Manager objects * Novell trademark. ** Third-party trademark. For more information, see Trademarks. ----------------------------------- 7.0 NAL The Novell* Application Launcher* (NAL) utility version 1.1 is included with this release. Read the READNAL.TXT file in the I386\NAL\NLS\language directory for installation instructions. * Novell trademark. ** Third-party trademark. For more information, see Trademarks. ----------------------------------- 8.0 DSMigrate Issues 8.1 DSMIGRAT.INI File Before using DSMigrate after installing a new version, delete the DSMIGRAT.INI file. This file contains information that might not apply to the new installation. You can find the file at: SYS:\SYSTEM\DSMIGRAT\DSMIGRAT.INI 8.2 Before Running DSMigrate Before running DSMigrate from the Tools menu of NWAdmin, run it from My Computer or the File Manager. You must have a drive mapping to run DSMigrate. DSMIGRAT.EXE is located in the SYS:\SYSTEM\DSMIGRAT directory of your IntranetWare server. Once DSMigrate is run, the WIN.INI file in your local Windows NT directory will have entries added to it that point to the location where you loaded DSMigrate from. From then on, as long as you have the same drive mapping, you can run DSMigrate from NWAdmin. ----------------------------------- 9.0 NetWare/IP Issues 9.1 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 the custom configuration option, there must be a specified NetWare/IP domain or DSS server; otherwise, NetWare/IP will not load. 9.2 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. 9.3 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. 9.4 Installing TCP/IP and NetWare/IP at the Same Time (Windows NT 3.51 Only) If you install TCP/IP and NetWare/IP at the same time and use the Custom Configuration option on TCP/IP, open the NetWare/IP property page after closing the NetWare/IP install, but before restarting the workstation. This ensures that NetWare/IP works properly. 9.5 NetWare/IP and NT Server NetWare/IP is not supported on NT Server. * Novell trademark. ** Third-party trademark. For more information, see Trademarks. ----------------------------------- 10.0 Documentation 10.1 About the Documentation All documentation for Novell* IntranetWare* Client* for Windows** NT** software is supplied in Microsoft** help files. The help file in the SETUPNW.EXE utility contains very basic installation instructions. Network supervisors should install Novell IntranetWare Client for Windows NT using those instructions once. When the client software is installed, the installer also installs the complete help files. Those help files provide more detailed information about installation options. 10.2 Errata: Installing DSMigrate and NDS Manager Instructions in NW Admin NT The NW Admin NT instructions for installing DS Migrate and NDS Manager are incorrect. To install DS Migrate and NDS Manager for Windows NT, follow the instructions under "Installing Administration Utilities" in the Novell IntranetWare Client for Windows NT help. * Novell trademark. ** Third-party trademark. For more information, see Trademarks. ----------------------------------- 11.0 RAS Issues 11.1 NetWare/IP NetWare*/IP* works with RAS in a Windows** NT** 4.0 environment only. NetWare/IP will not work with RAS under Windows NT 3.51. 11.2 Login The first time you log in, log in to the workstation only. Otherwise, you will receive an error message saying that there is no network present. After establishing a RAS connection, use the IntranetWare Login utility to log in to IntranetWare. 11.3 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 on Network Neighborhood. 2. Choose IntranetWare Connections. 3. From the resource list, choose the server you connected to with RAS. 4. Choose Set Current. 5. Choose OK. 11.4 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. * Novell trademark. ** Third-party trademark. For more information, see Trademarks. ----------------------------------- 12.0 File Manager Toolbar 12.1 NetWare Menu and Buttons in File Manager The Novell* IntranetWare* Client* for Windows** NT** version 3.51 install currently extends the File Manager toolbar with four IntranetWare-specific buttons: Change Context Login Change Passwords Send Message If you have previously modified the File Manager toolbar, additional client buttons might not show up. To enable these buttons: 1. From the Options menu, choose Customize Toolbar. 2. On the Customize Toolbar dialog box, click the Reset button. This changes the toolbar back to the default, but the Client buttons will show up. Alternatively, you can manually insert the new buttons using the Customize Toolbar feature. Also, depending on the resolution of the monitor, the client buttons might not be visible unless you remove some other buttons. Note: This does not apply to Windows NT 4.0. The Novell IntranetWare Client for Windows NT provides this functionality elsewhere in Windows NT 4.0. 12.2 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. Choose Send Message. Change Context Right-click a tree in Network Neighborhood. Choose Change Context. Change Passwords Right-click Network Neighborhood and choose Change Password. (Or press Ctrl+Alt+Del and choose Change Password.) Login To run the IntranetWare Login standalone, choose the Start menu, choose the NetWare folder, and then choose Login. * Novell trademark. ** Third-party trademark. For more information, see Trademarks. ----------------------------------- 13.0 Features Not Included in This Release 13.1 Group Policies The IntranetWare Client for Windows NT 4.0 currently does not support group policies. Novell is working on providing this support. 13.2 Private DOS Support The IntranetWare Client for Windows NT does not support private DOS. ----------------------------------- 14.0 How Customers Can Get Beta Support Novell* strongly encourages 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. 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*. 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. * Novell trademark. ** Third-party trademark. For more information, see Trademarks. ----------------------------------- 15.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. * Novell trademark. ** Third-party trademark. For more information, see Trademarks. ----------------------------------- 16.0 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: NT 4.0 a. Create a shortcut to the COMMAND.COM program, found in the \system32 directory. b. Right-click the shortcut Icon and select Properties. c. On the Program property page, choose the Windows NT button and enter the paths for the CONFIG and AUTOEXEC files that you created in Steps 1 and 2. d. Double-click the shortcut and a DOS window will be opened. 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. NT 3.51 a. In the Program Manager, open the Main program group and launch the PIF Editor. b. In the PIF Editor, choose New from the File menu to create a new PIF file. c. Fill in the following fields: Program Filename: \system32\command.com Window Title: DOS Only (This field is optional) Startup Directory: \system32 (This field is optional) d. Set any of the other fields as needed or desired. Choose the Windows NT button and enter the paths for the config, and autoexec files that you created in Steps 1 and 2. e. Save the PIF file as something like DOSPRT.PIF. f. Exit the PIF Editor. g. Create a program Item in one of your Program Manager groups that points to the PIF file just created. h. Double-click on the program item created in Step 11 to open a DOS box. Only DOS applications can be run from this box, 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. * Novell trademark. ** Third-party trademark. For more information, see Trademarks. ----------------------------------- 17.0 Driver Issues 17.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. 17.2 Older ODI Drivers This release of the NT Client does not update the following list of ODI* drivers. Name Date Time DEFEA.LAN 11/07/94 7:51p ES3210.LAN 6/01/94 4:00p EWRK3.LAN 6/14/94 5:46p HP3AT16P.LAN 6/24/94 12:38p ILANPCI.LAN 2/07/95 8:24a NI6510.LAN 3/06/95 9:24a OC32T164.LAN 7/04/94 3:03a OCTOK162.LAN 2/09/95 3:17a SMC8000.LAN 9/08/94 3:16p SMC8100.LAN 9/21/94 2:05p SMC8232.LAN 8/31/94 1:10p SMC8332.LAN 10/04/94 1:08p SMC9232.LAN 2/15/95 1:03p TCE32ESH.LAN 9/23/94 11:59a TCE32MCH.LAN 9/23/94 11:59a SKFDDIFM.LAN 9/15/94 11:48a SKFDDIFE.LAN 9/15/94 11:30a If one of the above drivers was installed before updating the Novell* NT Client, the driver will remain installed but will not be updated. If at a later time the driver needs to be updated or removed, removing the Novell NT Client will remove the driver (from the network control panel, selecting the driver and selecting remove will not remove the driver). The Novell NT Client can then be reinstalled. After the client has been installed, the desired driver can be added. If an updated driver to one of the above listed drivers is needed, contact the LAN adapter manufacturer for their latest driver. 17.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. * Novell trademark. ** Third-party trademark. For more information, see Trademarks. ----------------------------------- 18.0 Software Compatibility 18.1 Microsoft SMB Client Support over IPX The Novell* IntranetWare* Client* for NT now 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 as follows: If you have the NT 3.51 workstation, unbind the workstation and server from NWLink NetBIOS in the Control Panel's Network Settings. If you have the NT 4.0 workstation, unbind the workstation and server from NWLink NetBIOS in the Network Properties page. 18.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. 18.3 Microsoft File and Print Services The Novell IntranetWare Client for Windows NT software does not work with Microsoft's File and Print Services for NetWare for Windows NT (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. 18.4 NVER The NVER command does not work with Windows NT. Attempting to use this command hangs the command window. 18.5 Attachmate Irma Attachmate Irma v3.02 does not work with the Novell IntranetWare Client for Windows NT at this time. Attachmate recommends that customers use the 32-bit version of this application under Windows NT. 18.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. 18.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. 18.8 BREQUEST and multiple server connections BREQUEST.EXE hangs when trying to communicate with more than three servers. This problem has been traced to a defect in the BREQUEST application. 18.9 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 VIPS 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. 18.10 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. 18.11 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. 18.12 Microsoft Word 7 Two problems have been noted in Microsoft Word 7. First, you must map the drives that contain files you want to edit in Word 7. You cannot locate files on unmapped drives, even if you are logged in to the Directory tree where that drive is located. Second, if you remove any IntranetWare 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. 18.13 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. * Novell trademark. ** Third-party trademark. For more information, see Trademarks. ----------------------------------- 19.0 Miscellaneous 19.1 Some UNATTEND.TXT Settings Not Set during First-Time Install No matter how you set them in the UNATTEND.TXT file, GINA sets the Run Scripts, Display Login Results, and Close Script Results Automatically parameters to ON during a first-time install. After the first installation, run SETUPNW /U with the same parameters and they will be set correctly. 19.2 Empty CD Drive with Windows NT 3.51 If you have a CD drive and there's no CD in it, when you run a 16-bit program a message appears telling you to insert a CD. Either insert a CD or click Ignore. To prevent the error from appearing, open the AUTOEXEC.NT file and comment-out the line that loads MSCDEXNT.EXE. This is a problem with Windows** NT** 3.51 and does not exist under Windows NT 4.0. 19.3 Windows 95** GUI on Windows NT 3.51 Novell* IntranetWare* Client* for Windows NT does not support Windows 95 GUI running on Windows NT 3.51. 19.4 Internal Network Number Novell does not support the use of the internal network number on the NWLink stack in this release. Using an internal network number generates errors and prevents a network connection from taking place. 19.5 Password Restrictions It is best if administrators configure NT workstations to not use any of the Microsoft** password restrictions available in User Manager, The Novell IntranetWare Client for Windows NT works best if password authentication is left up to IntranetWare. 19.6 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. 19.7 Browsing Trees in the "Map Network Drive" Dialog Box in NT 4.0 Microsoft's Map Network Drive dialog box with the browser window (available by right-clicking on Network Neighborhood and choosing Map Network Drive) has a bug that prevents you from browsing any Directory trees to which you are not authenticated. When you double-click on a tree to which you are not authenticated, you receive a message telling you "The parameter is incorrect." As a workaround, browse trees to which you are not authenticated in Network Neighborhood and map drives by right-clicking on the volume object and choosing Map Network Drive. 19.8 Changed Objects Do Not Appear in NDS Because of the way NDS* works, there is a delay before changed objects appear with the new changes. If you make a change to the object but do not see the changes in NDS, wait several seconds and try again. * Novell trademark. ** Third-party trademark. For more information, see Trademarks. ----------------------------------- 20.0 Trademarks Novell Trademarks Envoy is a trademark of Novell, Inc. IntranetWare is a trademark of Novell, Inc. IntranetWare Client is a trademark of Novell, Inc. Internetwork Packet Exchange and IPX are trademarks 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 Client is a trademark of Novell, Inc. NetWare/IP is a trademark of Novell, Inc. Novell is a registered trademark of Novell, Inc. in the United States and other countries. Novell Application Launcher is a trademark of Novell, Inc. Novell Directory Services and NDS are trademarks of Novell, Inc. Novell Support Connection is a trademark of Novell, Inc. Open Data-Link Interface and ODI are trademarks 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. Third-Party Trademarks 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 is a registered trademark of Microsoft Corporation. OS/2 is a registered trademark of International Business Machines Corporation. Windows is a registered trademark of Microsoft Corporation. Windows 95 is a trademark of Microsoft Corporation. Windows NT is a registered trademark of Microsoft Corporation.