NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: NT Client for Alpha DOCUMENT ID: TID013903 DOCUMENT REVISION: A DATE: 03NOV93 ALERT STATUS: Yellow INFORMATION TYPE: Symptom Solution README FOR: NWNTA.EXE NOVELL PRODUCT and VERSION: NetWare Client for Microsoft Windows NT ABSTRACT: This file contains a prerelease version of the NetWare Client for MS Windows NT and is not recommended for use in a production environment. Includes several significant improvements to earlier releases. Functional updates will be posted on CompuServe periodically. 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴 DISCLAIMER Novell, Inc. makes no representations or warranties with respect to any NetWare software, and specifically disclaims any express or implied warranties of merchantability, title, or fitness for a particular purpose. Distribution of any NetWare software is forbidden without the express written consent of Novell, Inc. Further, Novell reserves the right to discontinue distribution of any NetWare software. Novell is not responsible for lost profits or revenue, loss of use of the software, loss of data, costs of re-creating lost data, the cost of any substitute equipment or program, or claims by any party other than you. Novell strongly recommends a backup be made before any software is installed. Technical support for this software may be provided at the discretion of Novell. 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴 SYMPTOM A released version of NetWare Client for MS Windows NT not available. SOLUTION Thank you for your interest in the NetWare Client for MS Windows NT. This contains a prerelease version of the client. This release was posted on November 3, 1993. Novell has provided this prerelease, in response to your requests, to help you in your planning and development for integrating MS Windows NT into your NetWare network. It is Novell's policy to recommend that you do not use this, or any prerelease software, in a production environment. Please remember that by downloading the prerelease you are bound bythe terms of the following legal terms. You may without charge reproduce, distribute and use copies of the software for its intended purposes, namely to test and evaluate the software, provided you do the following: 1. Do not make any statements about the software to the public (except in the NOVDEV and NDSG forums on CompuServe or on the NTCLIENT internet list servers); 2. Do not duplicate the software for any entity other than the legal entity you represent; 3. Do not distribute or authorize use of the software by any entity other than the legal entity you represent; 4. Do not receive any direct payment, commercial benefit, or other consideration for the reproduction, distribution or use of the software; 5. Do not change or omit any proprietary rights notice appearing on or in the software, 6. Do not reverse compile, reverse engineer or attempt any method of discovering the source code of the software, and; 7. Do not benchmark the software. The rights granted above are personal rights and not transferrable. THE SOFTWARE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, TITLE OR NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE. TO THE EXTENT YOU USE THE SOFTWARE, YOU DO SO AT YOUR OWN RISK. IN NO EVENT WILL NOVELL BE LIABLE TO YOU FOR ANY DAMAGES ARISING OUT OF YOUR USE OF OR INABILITY TO USE THE SOFTWARE. This release was refreshed on November 3, 1993 Self-Extracting File Name: NWNTA.EXE Revision: A Files Included Size Date Time \ NWNTA.TXT (This File) IPXAPI.DL_ 4255 10-29-93 3:26p NETWARE.DL_ 19983 10-29-93 3:24p NOVELL.CP_ 9749 10-29-93 3:25p NWAPI32.DL_ 26313 10-29-93 3:24p NWCM.DL_ 5212 10-29-93 3:25p NWEVENTS.DL_ 3258 10-29-93 3:26p NWFS.SY_ 149898 11-03-93 2:32p NWMSG.DL_ 2429 10-29-93 3:25p NWSETUP.DL_ 12504 10-29-93 3:25p NWSPOOL.DL_ 21502 10-29-93 3:24p NWSUBS.INF 52894 10-28-93 11:12a NWV1_0.DL_ 5989 10-29-93 3:25p OEMNADNA.INF 101961 11-01-93 4:14p OEMNADNB.INF 31783 11-01-93 4:14p OEMNADNC.INF 28708 11-01-93 4:14p OEMNADNG.INF 33565 10-28-93 11:31a OEMNADOD.INF 34386 10-20-93 3:11p OEMSETUP.INF 67451 10-29-93 2:37p PSAPI32.DL_ 11591 10-29-93 3:26p RESMGR.SY_ 27174 10-29-93 3:23p SPX2API.DL_ 9652 10-29-93 3:25p TEMPLATE.FAX 434 01-19-93 1:56p WCAP.EX_ 27931 10-27-93 11:09a WSHNW.DL_ 3429 10-29-93 3:25p This information explains how to set up the NetWare Client for the commercial release of Microsoft MS Windows NT (builds 511 and 528). It contains the following sections: Novell's support for MS Windows NT What You're Getting Before You Install Installing the NetWare Client for MS Windows NT Configuring the Client Accessing NetWare Services Other Network Adapters Reporting Problems ---------------------------------- Novell's Support for MS Windows NT ---------------------------------- Novell is committed to supporting MS Windows NT as a client in the NetWare network environment. Novell has been working with Microsoft to develop Windows NT client software since before MS Windows NT was released. Since Novell released their first prealpha client, they have received a number of useful comments and problem reports from early MS Windows NT users. In addition to the need for more ODI drivers (this release supports approximately 65 boards), one of the most common requests was to provide support for both ODI and NDIS drivers for IPX and non-IPX protocols. Novell has responded to this user request by adding it into this pre-release client. Novell is continuing to add features and improve the performance of the NetWare client for MS Windows NT. After the initial release of the product, now scheduled for early 1994, we will continue to add the features you need so that you can fully utilize MS Windows NT as a NetWare client. ------------------- What You're Getting ------------------- ************************************************************ * Note: This pre-release software allows users of * * Microsoft MS Windows NT to have a first look at how the * * NetWare Client works transparently with MS Windows NT. * * However, as Novell and Microsoft continue product * * development for the NetWare Client and the MS Windows * * NT OS, respectively, interfaces and functionality may be * * added or changed. * ************************************************************ Installing this version of the prerelease NetWare Client for MS Windows NT provides you with the following new features: 1. NWLINK support Allows you to choose between NDIS or ODI LAN drivers. Now you can use IPX over NDIS LAN drivers. The Novell client will now communicate over NWLINK, which is the MS Windows implementation of the IPX protocol stack. If you want to use IPX over ODI you will still use Novell's IPX protocol stack. With the client using NWLINK, IPX applications can share use of a LAN card with your non-IPX applications in the NDIS environment. If you want NDIS protocol stacks to share a card with ODI protocol stacks in the ODI environment, you can do so by using ODINSUP support. 2. Support for Intel, MIPS, and DEC Alpha hardware This prerelease version of the Novell Client for MS Windows NT is available for the MIPS and DEC Alpha hardware platforms, as well as for Intel machines. You must download the correct version for your hardware. 3. ODI drivers for approximately 65 LAN boards supporting ISA, EISA, and MCA architectures. Manufacturers include 3COM, AMD, Ansel, DEC, HP, IBM, Intel, Microdyne, Novell/Eagle, Proteon, SMC, Wearnes, and Western Digital. 4. Improved Multiple frame types support Setting the frame type is easier now; it can be changed without entering the REGEDT32.EXE program. Instructions are included in this text file. 5. Frame type auto-detect This client will auto-detect the frame type being used on the network. Because this is a function of ODI, it is available only if you choose "Novell IPX/SPXII" as your protocol and an ODI LAN driver. You can select "Auto-detect"for your frame type or choose a specific frame type. If a file server is not found on your selected frame type, the client will search the other frame types for a NetWare server and automatically switch. 6. Redirect LPT ports with WCAP.EXE While previous versions only allowed you to print directly to a NetWare print queue, this release includes WCAP.EXE, which allows you to also redirect an LPT port from the command line. This utility also allows you to drag-and-drop print jobs to the queue captured to the LPT1 port. 7. Improved preferred server support Now you can set the preferred server without using REGEDT32.EXE. Simple instructions are included in this text file. 8. Much more stable than earlier versions This client has had many changes and bug fixes that will greatly improve reliability. Ongoing features included in earlier versions of the pre-release client: 1. NetWare file service connectivity Allows connection to NetWare 2.1x, 2.2x, 3.x and 4.x file servers. (4.x Directory Services support is still under development. Prerelease supports only bindery emulation on 4.x servers.) 2. NetWare print service connectivity Allows print redirection to NetWare print queues. 3. Single LAN card solution NDIS protocol connectivity over high-performance ODI LAN drivers using the supplied ODINSUP support. 4. Mutual login support Username and password from MS Windows NT machine login may be used to authenticate to a NetWare server. 5. MS Windows NT Provider support Novell modules allow a user to access the native MS Windows NT provider and communicate with NetWare services. 6. High performance NetWare 4.0 (rev F) server LAN drivers run unmodified under MS Windows NT on Intel platforms. 7. IPX and SPXII ODI protocol stacks 8. Integrated installation and configuration Uses the MS Windows NT "Network Settings Control Panel" installation interface. 9. Unlimited number of concurrent connections 10. Permanent drives and printer connections 11. FAT file system supported on NetWare file servers 12. Transport independent Enables communication to future NetWare servers running on protocols other than IPX. 13. Uses MS Windows NT integrated cache manager 14. Supports protocol look-ahead This feature, unique to ODI, allows IPX to operate faster at the transport layer. 15. Control Panel applet for connection information 16. Auto-reconnect support Note: This version of the NetWare Client does not include support for DOS applications which use NetWare APIs, such as SYSCON, MAP, FILER, etc. This support will be added in future versions. NETWORK INTERFACE CARDS SUPPORTED ================================= Novell currently has ODI drivers for the following network cards: ISA/EISA: --------- ODI 3Com EtherLink II (DIX) ODI 3Com EtherLink II (BNC) ODI 3Com EtherLink II/16 (DIX) ODI 3Com EtherLink II/16 (BNC) ODI 3Com EtherLink III ODI 3Com EtherLink III TP ODI AMD AM2100 ODI AMD AM1500T ODI Ansel M1500 All-In-One-Networking ODI Ansel M2100 All-In-One-Networking ODI Microdyne EXOS 105 ODI HP J2405 ODI IBM Token Ring ODI Novell NE1000 ODI Novell NE2000 ODI Novell NE2000PLUS (I/O Mode) ODI Novell NE2000PLUS (Shared RAM Mode) ODI Novell NE2100 ODI Novell NE1500T ODI Novell NTR2000 ODI Proteon p1391 RapiDriver ODI Proteon p1392 RapiDriver ODI Pure Data PDI8023 ODI Pure Data PDI8023T ODI Pure Data PDI8023-16 ODI Pure Data PDI8023T-16 ODI Pure Data PDI8023PLUS-16 ODI Pure Data PDI8023TPLUS-16 ODI SMC (WD) 8003EP ODI SMC (WD) 8003WC ODI SMC Elite 8013EWC ODI SMC Elite 8013WC ODI SMC Elite 8013EPC ODI SMC Elite 8013EW ODI SMC Elite 8013EP ODI SMC Elite 8013W ODI SMC Elite Ultra 8216 ODI SMC Elite Ultra 8216C ODI SMC Elite Ultra 8216T ODI Wearnes 2110T ODI Wearnes 2107C ODI WD 8003E ODI WD 8003EBT ODI WD 8003WT ODI WD 8003W ODI WD 8003EB ODI WD 8013EBT Micro Channel Architecture: --------------------------- ODI 3Com EtherLink 16 MC ODI 3Com EtherLink 16 MC TP ODI 3Com EtherLink III MC ODI 3Com EtherLink III MC TP ODI IBM Token Ring MC ODI Novell NE2 MC ODI Novell NE2_32 MC ODI Proteon p1892 RapiDriver Token-Ring MC ODI Pure Data PDuC8023-16 MC ODI SMC (WD) 8003E/A MC ODI SMC (WD) 8003W/A MC ODI SMC 8013EP/A MC ODI SMC 8013WP/A MC EISA: ----- ODI 3Com EtherLink III EISA ODI 3Com EtherLink III EISA TP ODI DEC FDDIcontroller/EISA ODI Novell NE3200 EISA ODI Novell NF32000 FDDI EISA ODI Proteon p199X RapiDriver Token-Ring EISA ODI INTEL EtherExpress32 EISA ODI Microdyne EXOS235T EISA OTHER: ------ ODI Support for NDIS Protocols Adapter (ODINSUP) The ODINSUP support module provides support for using both ODI protocol stacks and NDIS protocol stacks with one network card. Novell will continue to update the list of supported network cards as others are added in the future. ------------------ Before You Install ------------------ Install the commercial release of MS Windows NT (Build 511 or 528) on your system. If you take the "EXPRESS" option in MS Windows NT Setup, and if you have a network interface card in your machine BEFORE you begin to install MS Windows NT, setup will sense the card and the NT networking components will be installed. If you choose the "CUSTOM" option, be sure to select the "Set Up Network" option in the GUI portion of Setup. These instructions assume you have installed the MS Windows Networking services. To utilize the mutual login feature and maximize ease of use, we suggest you make your username and password for your MS Windows NT machine the same as your login name for NetWare servers. You can use the "User Manager" located in the "Administrative Tools" group to add a new user on your MS Windows NT system or from a DOS machine use the DOS SYSCON, or you can use NETADMIN utility to change your NetWare account. ----------------------------------------------- Installing the NetWare Client for MS Windows NT ----------------------------------------------- ************************************************************ * Attention: MIPS and ALPHA users: * * * * Because there are currently no ODI LAN drivers available * * for these platforms, you must use the NWLINK protocol for* * the present. You will not be prompted to choose between * * Microsoft NWLINK and Novell IPX/SPXII. * * * * Also, you need not complete any steps relating to * * removing NDIS LAN drivers or installing ODI LAN drivers. * * Simply "Add Software" and your installation is completed.* ************************************************************ NOTE: If you already have a previous version of the NetWare client running, you must remove it. Complete the following steps: (Do NOT use the "Update" button in the "Network Settings" panel) a. Access the MS Windows NT network installation dialog. This is accomplished by selecting "Control Panel", then "Network." b. Remove any ODI adapters and ODINSUP, if loaded. Select the ODI adapters (including ODINSUP) listed in the "Installed Adapter Cards" box, and select "Remove." Approve the confirmation. c. Next, remove the NetWare software. In the "Installed Network software" box, select "NetWare Workstation," then select the "Remove" button. Approve the confirmation, then choose "OK." d. REBOOT your workstation. e. Continue with the following steps: 1. Log on to your NT system as Administrator (or an administrator 'equivalent'). If you deinstalled an earlier version of the NetWare client, you will receive a message similar to the following: MESSAGE SERVICE CONTROL MANAGER - At least one service or driver failed during system startup. Choose "OK." 2. From the Program Manager's "Main" window, choose "Control Panel." From there, choose "Network." You should see the following items already listed in the "Installed Network Software" listbox: Computer Browser NetBEUI Protocol NetBIOS Interface RPC Name Service Provider Server Workstation You should see the name of your network interface card listed in the "Installed Adapter Cards" box. If you deinstalled an earlier version of the NetWare Client, you will not see any Adapters listed. 3. From the "Network Settings" dialog, choose "Add Software." 4. Scroll down the list box to " Requires disk from manufacturer," select it, and then choose "Continue." You will be prompted for a disk in Drive A:. 5. Insert the Netware Client for MS Windows NT "Install" diskette into drive A: and choose "OK." 6. "NetWare Services for MS Windows NT" is displayed. Choose "OK." Setup copies NetWare files to their appropriate directories and adds them to the installed software list. 7. The "NetWare Client Installation dialog box will appear. Choose the IPX protocol you wish to use. Choose "OK." If you choose the default "Novell IPX/SPXII", you will be using the Novell-developed IPX/SPX protocol stacks. If you choose "Microsoft NWLink," you will be using the Microsoft developed IPX/SPX protocol stacks. Novell recommends you choose "Novell IPX/SPXII" unless you need to use an NDIS driver. Remember that you can use ODINSUP to allow NDIS protocols to run with an ODI driver. *** WARNING: *** Once chosen, the "Microsoft NWLINK" option cannot be removed due to a problem with MS Windows NT. 8. After reading the instructions presented, choose "OK." You are returned to the "Network Settings" dialog. 9. If you have only one adapter installed in the machine and you did not deinstall an earlier version of the NetWare Client before starting step 1, do the following; otherwise, skip this step: With the name of your adapter highlighted in the "Installed Adapter Cards" box, choose "Remove". When the confirmation box is presented, choose "Yes." 10. If you chose "Novell IPX/SPXII" in step 7, you must select an ODI LAN driver. Go to step 11. If you chose "Microsoft NWLink" in step 7, you have already selected an NDIS LAN driver. Go to step 20. 11. Choose "Add Adapter." 12. From the list box, select the ODI driver you want to run and choose "Continue." NOTE: The ODI LAN drivers all begin with "ODI." 13. Enter the path to your NetWare for MS Windows NT distribution files (usually A:\) and choose "Continue." 14. If prompted, set the options for your network card; then choose "OK." 15. In the "IPX Frame Type" dialog, choose the Frame type for your network from the listbox. Then, choose "OK." 16. After reading the installation complete message, choose "OK." You will see the selected ODI driver in the "Installed Adapter Cards" list. 17. If you are using a single network card and need both NetWare and MS Windows NT networking services continue with step 18. Novell recommends that, if you have installed MS Windows NT networking services, you install ODINSUP whether or not you plan to use the MS Windows NT networking services, so that the MS Windows NT networking services have a transport to bind to. Otherwise, you will receive a warning when you start MS Windows NT. If you have a separate card for each networking service, go to step 20. 18. From the "Network Settings" dialog, choose "Add Adapter." 19. From the list box select "ODI Support for NDIS Protocols Adapter (ODINSUP)" and choose "Continue." Note that the LAN drivers are listed in alphabetical order. "ODI Support for NDIS Protocols Adapter (ODINSUP)" now appears in the"Installed Adapter Cards" list. Any preinstalled MS Windows NT networking software will now bind to this adapter. 20. From the "Network Settings" dialog, select "Bindings" to view the NetWare driver bindings. After clearing the "Network Bindings" dialog, choose "OK," or simply choose "OK." 21. In the next "Network Settings" dialog box, you are prompted to restart your system. You must restart for NetWare Services to become active. (Be sure to remove the NetWare diskette from the diskette drive before rebooting.) ---------------------- Configuring the Client ---------------------- You may need to modify your client configuration for optimal performance. These modifications include the following: - Setting the preferred server - Defining frame types - Setting the Retry Count - Setting the Session Count Setting the Preferred Server ============================ Setting the preferred server can make establishing network routes more efficient. 1. From the "Main" group, select "Control Panel". Then, select the "NetWare" icon. 2. Choose on "Configure." 3. In the "Network Settings" dialog box, highlight "NetWare Workstaton" in the "Installed Network Software" listbox. Choose "Configure" or double-click on "NetWare Workstation." 4. In the "NetWare Workstation Setup" dialog box, select from the listbox the server you want to connect to at boot time. Choose "OK." Choose "OK" to exit the "NetWork Settings" dialog. Then, choose "Close" to exit the "Novell NetWare" dialog. You must restart the machine in order for the preferred server option to take effect. Defining frame types (available only with Novell IPX/SPXII) =========================================================== To change to another frame type, do the following: 1. From the "Main" group, select "Control Panel". Then, select the "NetWare" icon. 2. Choose "Configure." 3. In the "Network Settings" dialog box, highlight "NetWare IPX/SPXII Transport" in the "Installed Network Software" listbox. Choose "Configure" or double-click on "NetWare IPX/SPXII Transport." 4. In the "NetWare IPX Bind" dialog box, choose "OK." In the "IPX Frame Type" dialog box, select from the listbox the frame type you wish to use. Choose "OK." Choose "OK" to exit the "NetWork Settings" dialog. Then, choose "Close" to exit the "Novell NetWare" dialog. You must restart the machine in order for the frame type option to take effect. Setting the Retry Count: ======================== The Retry Count is the number of times the NetWare Client will try to connect to a NetWare file server before failing. To change the Retry Count from its default of 12: 1. Start the REGEDT32 program. To do this, from the "Program Manager" "File" menu, choose "Run." At the command line, type "REGEDT32" and choose "OK." 2. Select options in the following order: HKEY_LOCAL_MACHINE on Local Machine SYSTEM CurrentControlSet Services NetWareWorkstation Parameters 3. From the "Parameters" sub-key, create a VALUE called "Retry Count" using the data type "REG_DWORD". Choose "OK." 4. In the "DWORD Editor" panel, enter the value you wish to use for a Retry Count in the "Data" field. Select "Decimal" in the "Radix" box. Choose "OK." Exit the REGEDT32 program. Setting the Session Count ========================= The Session Count is the number of SPX sessions the NetWare Client will support. SPX sessions are used by applications such as SQL Server and printing. Failure to connect to a NetWare file server would not indicate a need to change the Session Count. To change the Session Count from its default of 10: 1. Start the REGEDT32 program. To do this, from the "Program Manager" "File" menu, choose "Run." At the command line, type "REGEDT32" and choose "OK." 2. Select options in the following order: HKEY_LOCAL_MACHINE on Local Machine SYSTEM CurrentControlSet Services IpxSpxII Parameters 3. Select the "SessionCount" parameter from the list of parameters displayed. 4. In the "DWORD Editor" panel, enter the value you wish to use for a Retry Count in the "Data" field. Choose "OK." Exit the REGEDT32 program. -------------------------- Accessing NetWare Services -------------------------- NetWare Services are available through Control Panel, Print Manager, File Manager, and the command line. Control Panel: The NetWare icon in the Control Panel lists your connections, username, and connection ID. Network connections can be added by selecting "NetWare" from the "Control Panel," selecting any entry in the "Current Attachments" box, and pressing the "Insert" key. Select the desired server from the listbox, type in Username and Password, then choose "Login." To delete a network connection, simply select the connection and press the "Delete" key. That connection will be logged out. Print Manager: To print to a NetWare queue, choose "Print Manager" from the "Main" window. Then from the "Printer" menu, choose "Connect to Printer." Browse the NetWare servers for the queue to which you wish to print. File Manager: From the "File Manager" menu bar, choose "Disk," "Connect Network Drive," or "Disconnect Network Drive" to manage NetWare connections. Remember, to specify network resources you must use UNC formatting conventions (\\SERVER\VOLUME\DIRECTORY\DIRECTORY). Command Line: To redirect an local LPT port to a NetWare print queue, execute the WCAP.EXE command line program. From the "NetWare Capture Utility" panel, highlight the LPT port you wish to redirect. Then, select the desired NetWare queue from the "Available Queues" drop box. To deselect an assigned NetWare queue, select "none" from the "Available Queues" drop box. Help is not currently available. If you minimize the WCAP.EXE application, you can drag-and-drop a file onto the icon and it will print on the printer you have captured to the LPT1 port. Note that at this time print jobs are listed in Print Manager as "LPT Port Redirection." ---------------------- Other Network Adapters ---------------------- Novell has included a selection of the MS Windows NT drivers that are currently available for NetWare with this client kit. Novell realizes, however, that the driver you need to use your network adapter with MS Windows NT may not be available at this time. If the driver you need is not in this kit, contact the manufacturer and encourage them to upgrade their NetWare ODI driver to support MS Windows NT. NetWare ODI 32-bit drivers written to the revision F (3.1) specification support MS Windows NT as a client. ------------------ Reporting Problems ------------------ It is Novell's policy to support only commercially available products through our technical support service. Please do not call the Novell Technical Support telephone line with questions or problem reports regarding this software. Instead, Novell has created special sections within Novell's NOVDEV and NDSG forums to allow you to get support from other prerelease users and to gather your feedback on this prerelease. The NOVDEV section is section 17 (for registered developers) and the NDSG section is section 14. Internet users can subscribe to a private list server by emailing the REQUEST.TXT file available on FTP.NOVELL.COM in the NETWIRE\NOVFILES\CLIENT.KIT\WINNT directory. The Novell development team will monitor these forums so that fixes can be made available for the issues you help to identify. Novell's NT development team will not be monitoring other Novell forums for your questions and comments so please confine your comments to the identified forums. If you prefer, you can communicate your problems or suggestions through FAX. Complete the TEMPLATE.FAX file and return it to FAX: 801-429-5200 Attention: NetWare Client for MS Windows NT, Development ************************************************************ * DISCLAIMER * * * * Novell, Inc. makes no representations or warranties with * * respect to any NetWare software, and specifically * * disclaims any express or implied warranties of * * merchantability, title, or fitness for a particular * * purpose. * * * * Distribution of any NetWare software is forbidden without * * the express written consent of Novell, Inc. Further, * * Novell reserves the right to discontinue distribution of * * any NetWare software. * * * * Novell is not responsible for lost profits or revenue, * * loss of use of the software, loss of data, costs of * * recreating lost data, the cost of any substitute equipment* * or program, or claims by any party other than you. Novell* * strongly recommends a backup be made before any software * * is installed. Technical support for this software may be * * provided at the discretion of Novell. * ************************************************************* �