NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: IntranetWare Client for Windows NT (diskette) README FOR: NTENU_D2.EXE NOVELL PRODUCTS and VERSIONS: IntranetWare Client 4.0 for Windows NT ABSTRACT: Novell has updated the IntranetWare Client for Windows NT in preparation for the upcoming Novell Workstation Manager Open Beta and to include a few fixes for the client. This client supports both Windows NT v3.51 and v4.0. This file contains the images necessary to make a diskette install of the IntranetWare Client for Windows NT. NTENU_D2.EXE replaces NTENU_D1.EXE ----------------------------------------------------------------- DISCLAIMER THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION. HOWEVER, THE INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY. NOVELL MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION. ----------------------------------------------------------------- ISSUE: Novell has updated the IntranetWare Client for Windows NT in preparation for the upcoming Novell Workstation Manager Open Beta and to include a few fixes for the client. NTENU_D2.EXE replaces NTENU_D1.EXE To determine which NT Client is installed use the date listed in the title of the Gina Login (IE Login Screen). The title and date for NTENU_D2.EXE is "Novell NetWare Client Services v4.0 (961120)" The title and date for NTENU_D1.EXE is "Novell NetWare Client Services v4.0 (961104)" The issues resolved in NTENU_D2.EXE are listed below: 1) A very infrequent blue screen while running Internet browsers (either Microsoft's or Netscape's.) 2) Problem seen while copying files to a NetWare 3.11 server using token ring with Packet Burst disabled. 3) Problem with Extended ASCII characters not being recognized by the NetWare Graphical Login. 4) All available NT Domains will now be listed in the "from" pull down field in the Windows NT tab on the NetWare Graphical Login. 5) Dragging and dropping items from the NT desktop to a shortcut icon of a Network printer on the NT desktop caused a blue screen. 6) Dos Capture utility did not work if users did not have local NT admin rights. 7) A very infrequent Auto-reconnect problem. 8) After removing the NT client, the Network Neighborhood was no longer browsable. 9) Time sync did not change to the correct time zone. Novell IntranetWare Client for Windows NT Release Notes 11/20/96 These notes describe issues that have not been resolved for the release of Novell* IntranetWare* Client* for Windows** NT**. Most of these issues will be resolved in future releases. This release supports the following: * Windows NT 3.51 * Windows NT 4.0 To install NetWare 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. Contents 1.0 New Issues 2.0 Login and Shutdown 3.0 Software Compatibility 4.0 Profile Storage 5.0 Installing NWADMNNT and NAL 6.0 NWADMNNT 7.0 NAL 8.0 NetWare/IP issues 9.0 RAS Issues 10.0 Documentation Issues 11.0 File Manager Toolbar 12.0 Features Not Included in This Release 13.0 Customer Support 14.0 Unlocking a Locked Workstation 15.0 Miscellaneous 16.0 Trademarks * Novell trademark. ** Third-party trademark. For more information, see Trademarks. 1.0 New Issues 1.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 1.2 Errors when Reconnecting Permanent Drive Mappings to Servers in Different NDS Trees. In Windows NT 4.0, users might encounter an error when restoring permanent drive mappings to NetWare* 4* servers which are in different NDS trees. In the 3.51 version of the client, which is not multi-tree enabled, such mappings were made in Bindery mode. In the 4.0 client, which is multi-tree 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 NDS trees on the Client tab of the Novell NetWare Client Services Configuration page. This is accessed by right-clicking on Network Neighborhood, selecting Properties, selecting the Services tab, selecting Novell NetWare Client Services, and then pressing the Properties button. 1.3 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. * Novell trademark. ** Third-party trademark. For more information, see Trademarks. 2.0 Login and Shutdown 2.1 LOGIN.DAT File Problems If the login results window was open when the client was updated, you must reboot before running GUI login or or an error message about an outdated login.dat file will appear. This message will not appear after rebooting. 2.2 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.3 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 keys must be entered in the following path: \HKEY_LOCAL_MACHINE\Software\Novell\NWGINA\Login Screen The following keys and values need to be added: Key: NetWareAutoAdminLogon Value: "1" enables AutoLogon; "0" disables it Key: DefaultNetWarePassword Value: Key:DefaultNetWareUserName Value: 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.4 CAPTURE Execution in a Login Script If you use a login script with a CAPTURE command in it, the screen might go blank with a blinking cursor in the upper left-hand corner. Eventually, the capture executes and things return 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 Options tab is selected. 5.Under the Display Options group, choose Window. 3.0 Software Compatibility 3.1 Drive Mappings All drive mappings made using GUI Login are root mapped. Programs cannot access directories above the directory the drive is mapped to. 3.2 Login Utilities The NetWare* 3* login utility does not work with this client. Novell also recommends that you don't use the NetWare 4* login utility either. Use the GUI login to log in to the network. There are 3 ways to initiate a GUI Login, once you have already logged in to NetWare or the Local Workstation. 1.Run loginwnt /a from the DOS command prompt. 2.Select the GUI Login icon from the NetWare Common Group. 3.Select the GUI Login icon from the Toolbar of File Manager (NT 3.51 only). or Double-click on the server or tree you want to log in to and the GUI Login automatically loads (NT 4.0). 3.3 Logout Utility The logout.exe command is also not recommended for use. If you use the logout command, you should use it with a servername specified (e.g. LOGOUT servername). If you want to clear your current connections, use the GUI Login (use any of the methods described in secion 3.2 "Login Utilities" to start GUI Login) and select the Clear Current Connection button, or log out using Ctrl-Alt-Del before proceeding with the login. 3.4 Microsoft SMB Client Support over IPX The Novell* NetWare* 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. 3.5 Envoy for Windows Currently, Envoy* for Windows (both version 1.0 and 1.0a) will open and allow 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 ENVOYNT.EXE. When you run this self-extracting executable file, it will produce two files--one .EXE file and one .DLL file. Copy these files to your Envoy directory. 3.6 Microsoft File and Print Services The Novell NetWare Client for Windows NT 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. * Novell trademark. ** Third-party trademark. For more information, see Trademarks. 4.0 Profile Storage 4.1 "Profile Not Present" Error Message The first time you select Store your desktop profile on the network, an error message from WinLogon warns that the profile is not present or is possibly corrupt. This is because the profile has not been saved to the network yet. This message will not appear on subsequent logins. 4.2 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 NetWare 3 and NetWare 4 bindery connections. 4.3 Long Filenames When storing your profile from a Windows NT 4.0 workstation, your home directory must support long filenames. In versions of NetWare prior to NetWare 4.11, the OS/2** name space was required for long filename support. In 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. 4.4 Mandatory Profile This version of Novell NetWare Client for Windows NT supports mandatory profiles in Windows NT 4.0 only. Mandatory profiles are not supported at this time in Windows NT 3.51. * Novell trademark. ** Third-party trademark. For more information, see Trademarks. 5.0 Installing NWADMNNT and NAL This release of NetWare* Client* for Windows** NT** includes an updated version of NetWare Administrator, called NetWare Administrator NT (NWADMNNT). It also includes the NetWare Application Launcher* (NAL). To install NWADMNNT and NAL for use with Windows NT: 1.Locate the ADMSETUP.EXE icon on the NetWare Client for Windows NT. 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 box next to the utility's name. There are two choices, NetWare Application Launcher and NetWare Administrator. 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 NW Admin 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 The 32-bit NetWare* Administrator for Windows** NT** (NWADMNNT) utility that ships with the NetWare Client* for Windows NT was built to work with NetWare 4.11. The 16-bit NetWare Administrator that ships with NetWare 4.1 will also work with the NetWare Client for Windows NT. Running the 32-bit NWADMNNT utility on NetWare 4.1 will result in the following conflicts: *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 pressed. *Snap-ins created for older versions of NetWare Administrator will not run with the new version. *The DS Migrate and File Migrate snap-ins are designed to work with NetWare 4.11. They will not work with a server prior to NetWare 4.11, but will work with this client on a NetWare 4.11 server. In order to use the DS Migrate and File Migrate snap-ins, you must add two String Values to the following key in the registry. To do this, follow these steps: 1.Close NetWare Administrator. 2.Run REGEDIT (in the WINNT subdirectory). 3.Click on the following keys, in order, to expand the registry. HKEY_CURRENT_USER / Software / NetWare / Parameters / NetWare Administrator / Snapin Object DLLs WINNT If any of the keys don't exist, create them by following this example: the NetWare Administrator parameter exists in the Parameters section, but the Snapin Object DLLs WINNT parameter doesn't exist within the NetWare Administrator section. 1.Highlight the NetWare Administrator section. 2.Right click. 3.Choose New Key from the popup menu. 4. Enter the following: Snapin Object DLLs WINNT 5. Choose Snapin Object DLLs WINNT to expand that section. 6.Follow the steps under "String Values") String Values 1> name: DSMGSNNT.DLL value: "DSMGSNNT.DLL" 2> name: MIGSNPNT.DLL value: "MIGSNPNT.DLL" 7.With the Snapin Object DLLs WINNT section highlighted, right click on that option. 8.Choose New. 9.Choose String Value. 10.Enter the name listed in 1> above. 11.Right click on that String name. 12.Choose Modify. 13.Enter the value listed in 1> above. 14.Repeat for 2> above. 15.Close RegEdit before trying to run NetWare Administrator. * Novell trademark. ** Third-party trademark. For more information, see Trademarks. 7.0 NAL The NetWare* Application Launcher* (NAL) utility version 1.1 is included with this release. Read the README.NAL file in the I386\NAL\NLS\ENGLISH directory for installation instructions. * Novell trademark. ** Third-party trademark. For more information, see Trademarks. 8.0 NetWare/IP Issues 8.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. * Novell trademark. ** Third-party trademark. For more information, see Trademarks. 9.0 RAS Issues Note: Full Remote Access Services (RAS) support is available in this release. 9.1 Installation To install RAS: 1.Open the Control Panel. 2.Choose Network. 3. Select the Add Software option in the network settings. 4.Choose Remote Access Services. 5. Answer the questions for the components that are needed. This will set up a group for the Remote Access Services. 6.In the Novell* NetWare* Client* Services configuration, either specify the preferred server and tree where you want to initially log in, or specify under the Login tab the options you want to change upon login. 9.2 Execution After logging in to the workstation, choose the Remote Access icon from the Remote Access Services group. Specify the phone number for the RAS server and then choose Dial. After a connection has been established, log in and run the login script. Do this by going to the NetWare (Common) group and selecting NetWare GUI Login. Then select Login to run the login script and log in to the tree or server. 9.3 NetWare/IP NetWare/IP* will only work with RAS in a Windows NT 4.0 environment. NetWare/IP will not work with RAS under Windows NT 3.51. 9.4 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. 9.5 Multi-board support RAS does not support multiple boards. * Novell trademark. ** Third-party trademark. For more information, see Trademarks. 10.0 Documentation 10.1 Documentation All documentation for Novell* NetWare* Client* for Windows** NT** is supplied in Microsoft** Help files. The Help file in the SETUPNW.EXE utility contains very basic installation instructions. Network supervisors should install Novell NetWare Client for Windows NT using those instructions once. When you install the client software, the installer also installs the complete help files. Those help files provide more detailed information about installation options. * Novell trademark. ** Third-party trademark. For more information, see Trademarks. 11.0 File Manager Toolbar 11.1 NetWare Menu and Buttons in File Manager The Novell* NetWare* Client* for Windows** NT** version 3.51 install currently extends the File Manager toolbar with four NetWare-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 on 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. Note: This does not apply to Windows NT 4.0. The Novell NetWare Client for Windows NT provides this functionality elsewhere in Windows NT 4.0. 11.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 will be 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 multi-tree support. The new locations for these functions are as follows: * Send Message Right-click on a server in Network Neighborhood. Choose Send Message. * Change Context Right-click on a tree in Network Neighborhood. Choose Change Context. * Change Passwords Right-click on Network Neighborhood and choose Change Password. (Or press Ctrl+Alt+Delete and choose Change Password.) * Login To run the GUI Login standalone, choose the Start menu, choose the NetWare folder, and then choose Login. * Novell trademark. ** Third-party trademark. For more information, see Trademarks. 12.0 Features Not Included in This Release The following features and functionality are not included in this release: * Remote Dial-in over NWIP will not work with this release * Private DOS support is not supported by the Novell* NetWare* Client* for Windows** NT** software. * Novell trademark. ** Third-party trademark. For more information, see Trademarks. 13.0 How Customers Can Get Novell Support Novell* Technical Services*, in order to better support our customers, has implemented electronic support through the Novell Support Connect Web Site. This is the same World Wide Web (WWW) site that you go to get patches and fixes for all Novell released products. To get to the Novell Support Connect Web Site: 1.Go to the following address on the WWW: http://support.novell.com/home/pubbeta/winnt 2.Choose File Updates. 3.(Conditional) If you are outside the United States, select your region in the Worldwide Sites scrolldown menu at the bottom of the page. 4. Choose Product Support. 5.Choose Client for Windows NT. The following options are available on this Web page: *File Updates -- Enables you to download the latest version of the Client *FAQ -- Enables you to view the current issues for this product *Problem Reporter -- Enables you to submit any issues you are seeing for this client. To use the Problem Reporter: 1.Choose Problem Reporter from the Web page. A form appears. This form contains a series of questions that will help Novell Support professionals understand the problem you are reporting. 2.Complete all fields in the form. 3.Choose Continue. Another Web page appears. 4.Scroll down the Product Module list to find the product module that best describes your issue. For example, if you are having trouble printing from Novell NetWare Client for Windows NT 4.0, you would choose Printing - CLNT40. 5.Choose Continue to go to the next page. 6. Complete all fields on this page. This information helps the Support professional reproduce your issue. 7.Choose Submit to Novell. (Note: Novell will not respond to your issues directly, but they will be addressed in the FAQ.) * Novell trademark. ** Third-party trademark. For more information, see Trademarks. 14.0 Unlocking a Locked Workstation If the user who locked the workstation logged in to NetWare during the initial logon, then only that user or a user with Administrator rights on NetWare (within the NDS context of the user who locked the workstation) can unlock the workstation. A Windows NT administrator can only unlock a locked workstation if the user who locked the workstation logged in using the Workstation Login Only option. When the administrator unlocks a workstation, the workstation immediately logs out and reboots. 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. 15.0 Miscellaneous 15.1 NVER The NVER command does not work with Windows** NT**. Attempting to use this command will hang the command window. 15.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 DOS 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. 15.3 Windows 95 GUI on Windows NT 3.51 Novell* NetWare* Client* for Windows NT does not support Windows 95* GUI running on Windows NT 3.51. 5.4 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. 5.5 WIN2NCS The WIN2NCS software, which uses the NASI interface to connect the Windows NT workstation to a modem pool on the network, is scheduled to be available for electronic download around the same time that Novell NetWare Client for Windows NT ships. WIN2NCS will not be shipped as a part of the client. The WIN2NCS software on NT will provide the same functionality currently available in Windows and Windows 95. 15.6 Specifying Country Name in NDS Context If you need to specify a Country object in the NDS context, you need to enter a typed context, such as: OU=Sales.O=Company.C=US If you enter a typeless name (for example, Sales.Company.US), the context will fail. This is only true when your context includes a Country 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. 16.0 Trademarks Novell Trademarks Envoy is a trademark of Novell, Inc. IPX 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 Application Launcher 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 Directory Services and NDS are trademarks of Novell, Inc. Novell Technical Services is a service mark of Novell, Inc. Third-Party Trademarks 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 trademark of Microsoft Corporation. Self-Extracting File Name: ntenu_d2.exe Files Included Size Date Time ..\ NTENU_D2.TXT (This file) MAKEDISK.BAT 212 7-15-96 11:25:00 pm NWC_1 2 9-4-96 6:27:02 pm NWC_10 2 9-4-96 6:27:06 pm NWC_11 2 9-4-96 6:27:12 pm NWC_12 2 9-4-96 6:27:16 pm NWC_13 2 9-4-96 6:27:22 pm NWC_14 2 9-4-96 6:27:28 pm NWC_15 2 9-4-96 6:27:32 pm NWC_16 2 9-4-96 6:27:38 pm NWC_17 2 9-4-96 6:27:42 pm NWC_18 2 9-4-96 6:27:48 pm NWC_19 2 9-4-96 6:27:54 pm NWC_2 2 9-4-96 6:27:58 pm NWC_20 2 9-4-96 6:28:02 pm NWC_21 2 9-4-96 6:28:06 pm NWC_22 2 9-4-96 6:28:16 pm NWC_23 2 9-4-96 6:28:22 pm NWC_24 2 9-4-96 6:28:26 pm NWC_3 2 9-4-96 6:28:30 pm NWC_4 2 9-4-96 6:28:34 pm NWC_5 2 9-4-96 6:28:40 pm NWC_6 2 9-4-96 6:28:44 pm NWC_7 2 9-4-96 6:28:50 pm NWC_8 2 9-4-96 6:28:56 pm NWC_9 2 9-4-96 6:29:02 pm REV.A 54885 11-27-96 12:08:36 am ..\IMAGE\ NT1_ENU.350 1474979 11-27-96 12:09:18 am NT2_ENU.350 1474979 11-27-96 12:09:26 am NT3.350 1474979 11-27-96 12:09:32 am NT4.350 1474979 11-27-96 12:09:40 am NT5.350 1474979 11-27-96 12:09:48 am NT6.350 1474979 11-27-96 12:09:52 am NTAENU_1.350 1474979 11-27-96 12:10:00 am NTAENU_3.350 1474979 11-27-96 12:10:16 am NTAENU_4.350 1474979 11-27-96 12:10:26 am NTA_2.350 1474979 11-27-96 12:10:08 am NTA_5.350 1474979 11-27-96 12:10:38 am NTA_6.350 1474979 11-27-96 12:10:46 am NTA_7.350 1474979 11-27-96 12:10:52 am NWMKDISK.EXE 52944 5-16-95 10:19:40 pm NWMKDISK.MSG 2835 11-3-94 10:48:22 pm NWMKDISK.SCR 258 10-26-96 6:19:44 pm Installation Instructions: Extract ntenu_d2.exe in a temporary directory. This will create a directory structure that contains the images needed to create the installation diskettes. From the root of the temporary directory, type MAKEDISK and follow the prompts to make the installation diskettes (You will need 12 disks). To install the Client, put the first disk created (NetWare NT Client Disk 1) into the floppy drive and run SETUPNW.EXE from that drive. (Detailed instructions on how to install the IntranetWare Client for Windows NT are found in the README.HLP file. ----------------------------------------------------------------- Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information. -----------------------------------------------------------------