NETWARE CLIENT 32 FOR DOS AND WINDOWS 3.1x RELEASE NOTES 08/22/96 CONTENTS 1.0 Welcome 2.0 Installation and Support 3.0 ODI LAN Driver 4.0 Software Compatibility 5.0 Hardware Compatibility 6.0 Memory Management 7.0 International Issues 8.0 Trademarks 9.0 Disclaimer 1.0 Welcome NetWare Client 32 for DOS and Windows 3.1x is a 32-bit Client that enables DOS and Windows 3.1x computers to access NetWare network services. For more information about Client 32, see the online help file (SETUP.HLP) in one of the following places: * Before running setup: For Diskette: DISK1WIN subdirectory of \NLS\ENGLISH For CD-ROM: NLS\ENGLISH * After running setup: Double-click the "Client 32 Help" icon or run SETUP.HLP from the \NOVELL\CLIENT32\NLS\ENGLISH directory on your local drive. 2.0 Installation and Support 2.1 Setting Up Client 32 You can install Client 32 from DOS or Windows. Prerequisites * To install NetWare Client 32 for DOS and Windows 3.1x, you must have a computer with one of the following operating systems installed: * Novell DOS 7 * MS-DOS 5.x or 6.x * Windows 3.1x * Windows for Workgroups 3.11 * The Setup programs require 500 KB of memory to run. After Setup, Client 32 requires very little conventional memory (less than 5 KB). * Make sure that the computer has a LAN board installed and that a cable connects the LAN board to the network. * Make sure you do not have 40 program groups in Program Manager. This is the maximum number of groups Program Manager can contain. The DOS-based Setup program does not check for a maximum number, so if you run Setup from DOS with 40 program groups, Windows might fail to start. If you have 40 program groups, delete one of the groups or rename a group to "NetWare Tools" (NW.GRP in PROGMAN.INI) before installing Client 32. 2.1.1 Upgrading NetWare Client 32 Software Using Floppy Diskettes If NetWare Client 32 already exists on your workstation and you are upgrading the NetWare Client 32 software from floppy disk, you should first rename the ODI LAN drivers on the workstation or remove the NetWare Client 32 software completely. The floppy disk Setup (from Windows or DOS) does not replace the ODI LAN driver the computer uses if it is already on the computer. Also, if you are using Novell's 32-bit ODI LAN driver, SETUP might mis-match the driver's message file by installing a new message file while leaving the old driver on the computer. The 32-bit Novell ODI LAN drivers are CNE1500T, CNE2, CNE2_32, CNE2000, CNE2100, CNE3200, and CNTR2000. To Set Up Client 32 1. Insert the Client 32 diskette or CD or change to the network drive where the Client 32 files are located. 2. Run the Setup program by doing one of the following: * To install from DOS, enter the drive and "INSTALL" at the DOS prompt (not a DOS box in Windows). For example: D:INSTALL * To install from Windows, choose File | Run in File Manager. Enter the drive and "SETUP.EXE." For example: A:SETUP.EXE Then choose "OK." 3. Follow the instructions on the screen. In Windows, you can choose the Help button or press F1 for online help in any screen. The DOS program displays help at the bottom of the screen. Note: If you want to install support for peer-to-peer networking in Windows for Workgroups 3.11, you should install a 16-bit ODI LAN driver during Setup. For information on configuring Windows for Workgroups peer-to-peer networking, see section 4.4, "Windows for Workgroups 3.11." 2.1.2 Installing LAN Drivers Because of the diskette space limitations, the following drivers listed below are not available on the LAN driver diskettes for both 32-bit drivers and 16-bit drivers. If you are installing NetWare Client 32 for DOS and Windows 3.1x from diskettes and require a driver listed below, complete the following procedures: Prerequistists - NetWare Client 32 for DOS and Windows 3.1x installation diskettes created from the NetWare 4.11 CD-ROM. - A workstation with a CD-ROM and 3 1/2 inch diskette drive. 1) Ensure that enough free disk space exists on one of the NetWare Client 32 for DOS and Windows LAN driver diskette. You can delete some of the existing drivers to free up disk space. 2) Determine if any of the drivers provided in the following list are required for your installation. 3) For 16-bit drivers, copy the drivers (.COM and .INS) from PRODUCTS\DOSWIN32\IBM_6\LANDRV16 to the 16-bit driver diskette in the floppy drive. For example, A:\landrv16. or For 32-bit drivers, copy the drivers (.LAN and .LDI) from PRODUCTS\DOSWIN32\IBM_6\LANDRV32 to the 32-bit driver diskette in the floppy drive. For example, A:\LANDRV32. NOTE: These instruction apply to diskette installations only. The full set of certified drivers are available from a network or CD-ROM installation. The following is a list of files that are exist on the CD-ROM but were not included on the diskettes: 32-bit LAN drivers Cabletron E22N4X.LAN (E2219 (E10, PnP ISA)) Madge MADGEODI.LAN (SMART token-ring (TR, EISA, PCI)) CMDGODI.LAN (SMART token-ring (TR, EISA, PCI)) Intel E100S.LAN (PRO/100 SMART (E10/100, PCI)) SysKonnect SKFENW.LAN (SK-NET FDDI-FE, UE (FDDI, EISA)) SKFINW.LAN (SK-NET FDDI-FI, UI (FDDI, ISA)) SKFMNW.LAN (SK-NET FDDI-FM, UM (FDDI, MCA)) KTI PNPSRV.LAN (ET16P (E10, ISA)) DEC DE43X.COM (DE434/5 (E10, ISA)) EWRK3.LAN (DE204/5 (E10, ISA)) DE450.LAN (DE450-CA, TA (E10, PCI)) DE500.LAN (DE500 (E10/100, PCI)) Olicom A/S OCE2XODI.LAN (OC-2175 (E10, ISA) OCE4XODI.LAN (OC-2183(E10, PCI)) 16-bit COM drivers Novell Drivers NE1000.COM NE1500T.COM NE2.COM NE2000.COM NE2100.COM NE2_32.COM NE3200.COM NTR2000.COM ODINSUP.COM ROUTE.COM Accton PCIMLID.COM (EN2216 (E, PCMCIA)) AMD PCNTNW.COM (PCNET-PCI II (E10, ISA) D-Link DE22X.COM (220PCT (E, ISA)) DLKPCI.COM (DFE-500TX (E10/100, PCI)) DEC DE43X.COM (DE434/5 (E10, ISA)) Intel E100BODI.COM (EPRO/100B (E10/100, PCI)) EPROODI.COM (EPRO/10 ISA(E10, ISA) Kingston KTC20.COM (KNE20T/BT (E10, ISA)) KTC2000.COM (KNE2000TLC/2021LC (E10, ISA)) Madge MADGEODI.COM (SMART token-ring (TR, EISA, PCI)) Cabletron E22ODI.COM (E2219 (E10, PnP ISA)) 2.2 Automatic Client Upgrade You can upgrade computers that already use NetWare Client software by implementing the Automatic Client Upgrade (ACU). See the SETUP.HLP Windows online help file and the ACU.TXT file (in the ADMIN\NLS\ENGLISH directory) for more information. Note: If you use ACU to upgrade computers that are already running Client 32, use the /C option to specify the path to the NET.CFG file. 2.2.1 Setting Up the Automatic Client Update Utility The CD-ROM directory path for Automatic Client Update (ACU) information referenced in the NetWare Client 32 for DOS and Windows 3.1x setup utility is incorrect. The path statement should read as follows: PROJECTS\ADM32\L4\DOS_ACU\NLS\language 2.2.2 Copying Automatic Client Update Files to the Server The following file should be copied to the SYS:PUBLIC directory for setting up the Automatic Client Update (ACU) on a server: NWDETECT.EXE NWLOG.EXE NWSTAMP.EXE REBOOT.COM These files should then be placed in the SYS:PUBLIC\NLS\ directory for each language. ACU.TXT NWDETECT.MSG NWLOG.MSG NWSTAMP.MSG 2.2.3 Setting Up the Automatic Client Update (ACU) to Flush SMARTDRV Cache If you are using SMARTDRV included with Window 3.1x and you use automatic client update (ACU) to set up NetWare Client 32 for DOS and Windows 3.1x software, add a command to the login script to flush the Smart Drive cache before rebooting the computer. The following example shows a portion of a login script that uses drive I: as the network install directory for NetWare Client 32 for DOS and Windows 3.1x software: #I:INSTALL IF ERROR LEVEL = "0" THEN #I:NWSTAMP Novell_Inc_client32 4.1.0 #I:NWLOG /F I:\LOG\UPDATE.LOG /M "Upgrade Successful %LOGIN_NAME %NETWORK_ADDRESS:%P_STATION" ; The next line flushes the Smart Drive cache #C:\WINDOWS\SMARTDRV /C #I:REBOOT END If you do not flush the cache, the NetWare Client 32 for DOS and Windows 3.1x setup utility might replace a computer's AUTOEXEC.BAT file with a zero-byte file. If this does occur, you can restore the computer's original AUTOEXEC.BAT file by renaming the AUTOEXEC.OLD file to AUTOEXEC.BAT. 2.3 Additional Setup for 16-bit DOS ODI LAN Drivers Some 16-bit DOS ODI LAN drivers might require manual setup by editing the STARTNET.BAT file. You also might need to edit the computer's TCP/IP and LAN WorkPlace configuration in the NET.CFG file. If you install 16-bit ODI LAN drivers or if you use LAN WorkPlace, you should check these files in the computer's \NOVELL\CLIENT32 after setting up Client 32. 2.4 Technical Support Technical support for NetWare Client 32 for DOS and Windows 3.1x is the same as for other NetWare products. Novell and its partners will provide full technical support, including technical assistance, enhancements, and fixes. See the "Support" topic in the Reference section of the online help file (SETUP.HLP) for information on reaching technical support. 3.0 ODI LAN Driver 3.1 32-bit ODI LAN Drivers 32-bit ODI LAN drivers do not refer to the NET.CFG file for configuration parameters. You must use command line parameters to specify settings for 32-bit ODI LAN drivers. This is a sample STARTNET.BAT file created by Setup: SET NWLANGUAGE=ENGLISH NIOS.EXE LOAD LSLC32.NLM LOAD CMSM.NLM LOAD ETHERTSM.NLM LOAD CNE2000.LAN INT=5 PORT=300 FRAME=ETHERNET_802.2 LOAD CNE2000.LAN INT=5 PORT=300 FRAME=ETHERNET_II LOAD IPX.NLM LOAD CLIENT32.NLM Note that other modules (such as CLIENT32.NLM) do refer to the NET.CFG file for configuration information. Do not delete NET.CFG. 3.2 Token-Ring Source Routing If you want to use token-ring source routing, you must load ROUTE.COM when using the 16-bit DOS ODI token-ring LAN driver or SROUTE.NLM when using 32-bit ODI token-ring LAN drivers. For more information, see "Source Routing" in the online help file (SETUP.HLP). You can also view command line help from DOS by typing "?" with the SROUTE or ROUTE command. For example: LOAD SROUTE ? Prerequisites: * Load source routing (ROUTE.NLM) on a NetWare server * Install Client 32 on the computer Setting Up Source Routing 1. Modify the STARTNET.BAT file in a text editor by adding a line to load the appropriate source routing driver from the Client 32 working directory. Load SROUTE.NLM after loading the ODI LAN drive but before loading IPX.NLM. For example: * If the computer loads 32-bit ODI LAN drivers, add a line to load SROUTE.NLM and any options for the driver. For example: . . . LOAD NTR2000.LAN LOAD SROUTE.NLM LOAD IPX.NLM LOAD CLIENT32.NLM . . . * If the computer loads 16-bit ODI LAN drivers, add a line to load ROUTE.COM and any options for the driver. For example: . . . NTR2000.COM LOAD LSLC32.NLM LOAD PC32MLID.LAN ROUTE.COM LOAD IPX.NLM LOAD CLIENT32.NLM . . . 2. Save your changes and exit the text editor. 3. Restart the computer. 3.3 Using TCP/IP with Token-Ring Source Routing If you experience problems using TCP/IP on a token-ring network, add "DEF" to the command line of the source routing driver that TCP/IP uses. This parameter configures the source-routing driver to send packets that have destinations not in the driver's routing table as all-routes broadcast. Without this parameter, the packet is sent as a single-route broadcast. Single-route broadcast IP packets sometimes do not reach their destination in source-routing environments. To add the "DEF" parameter to the SROUTE.NLM driver used by TCP/IP, modify the driver's load line in the STARTNET.BAT file. For example: LOAD SROUTE BOARD=1 DEF LOAD TCPIP For more information, see "Source Routing" in the online help file (SETUP.HLP). 3.4 Using 16-bit Protocol Stacks with Client 32 16-bit protocol stacks require a shim called PDOSMLID.NLM to communicate with the 32-bit ODI modules. You load this module by loading the topology-specific counterpart, PDOS[eth | tok | fddi].COM. These modules load PDOSMLID.NLM automatically. Load the shim and the 16-bit protocols after loading LSL.COM in STARTNET.BAT. For example: NIOS.EXE LOAD LSLC32.NLM LOAD CMSM.NLM LOAD [ether | token | fddi]TSM.NLM LOAD <32-bit LAN driver> LSL.COM N16ODI.COM NESL.COM PDOS[eth | tok | fddi].COM <16-bit ODI protocol stack> Note: If you are using 16-bit NDIS compliant stacks, you must load ODINSUP.COM and then the 16-bit NDIS stack. 3.5 Using Automated IP-Addressing If you use DHCP, BOOTP, or RARP for dynamic IP-addressing, install TCP/IP support but do not enter any TCP/IP addresses during Setup. You also must complete the following procedure after installing Client 32: 1. Open the computer's NET.CFG file in the Client 32 working directory. You can use any ASCII text editor to open and edit this file. 2. Under the Protocol TCPIP section, add or edit the IF_CONFIGURATION line to indicate the type of addressing automation your network uses. For example: Protocol TCPIP IF_CONFIGURATION BOOTP NOTE: DHCP and RARP are also valid values in place of BOOTP. 3. Delete the following lines, if they exist, from the Protocol TCPIP section: IP_ADDRESS IP_ROUTER IP_NETMASK 4. Save your changes to the NET.CFG file and close the text editor. 5. (Conditional) For Ethernet networks, TCP/IP must have only one frame type choice. TCP/IP uses only ETHERNET_II or ETHERNET_SNAP frame type for communication. Make sure that you do not have both ETHERNET_II and ETHERNET_SNAP frame types loaded in addition to ETHERNET_802.2 and/or ETHERNET_802.3. 5a. Open STARTNET.BAT in a text editor. 5b. Search for "ETHERNET_II" and "ETHERNET_SNAP." For example, "ETHERNET_II" might appear on a line similar to the following: LOAD C:\NOVELL\CLIENT32\CNE2000.LAN INT=5 PORT=300 FRAME=ETHERNET_II 5c. If both frame types load from the STARTNET.BAT file, comment out one of the lines. Check with your network supervisor to see which frame type to use. 5d. Save your changes to the STARTNET.BAT file and close the editor. 6. Restart the computer. 3.6 Using NetWare/IP NetWare Client 32 for DOS and Windows 3.1x does not support NetWare/IP over the Microsoft TCP/IP stack in Windows for Workgroups. 4.0 Software Compatibility 4.1 GroupWise for DOS To run GroupWise for DOS, disable the DOS task-switching support by using the /da command line switch. NetWare Client 32 for DOS and Windows 3.1x does not support task-switchers. 4.2 VLM Modules Not Supported The NetWare DOS Requester (VLM software) is not qualified to run over the IPX and SPX protocol stacks for the NetWare Client 32 for DOS and Windows 3.1x. The NetWare DOS Requester packet burst mode does not work over these protocol stacks. 4.3 Semi-Private DOS Box Sessions Not Supported All drive mappings are global when you use Client 32. This means MAP.EXE commands made in DOS boxes in Windows affect the drive mappings in all other DOS boxes and Windows applications. Installing Client 32 disables the Global option in User Tools (NETWARE.DRV). If you have applications that require separate drive mappings in each DOS session, you should use the VLM client. Semi-private DOS mappings are not possible in Windows 95, so CLIENT32.NLM (used on both Windows 3.1x and Windows 95) could not support this functionality on both platforms. 4.4 Windows for Workgroups 3.11 Client 32 supports peer-to-peer networking in Windows for Workgroups 3.11. To set up support for peer-to-peer networking, install Client 32 on the Windows for Workgroups computer. Make sure to choose a 16-bit ODI LAN driver as the driver type. Complete the following procedure from Windows: 1. Install Client 32. Note: During Setup, choose a 16-bit ODI LAN driver card for your network board. You should avoid using 32-bit ODI LAN drivers if you plan to use Windows For Workgroups peer-to-peer networking. 2. Install Windows For Workgroups Peer-to-Peer Networking. 2a. Double-click the "Network Setup" icon in the "Network" Program Manager group. 2b. Choose "Networks." 2c. Choose "Install Microsoft Windows Network." 2d. Choose "Other" to install Windows support for an additional network, and then choose "Novell NetWare (Workstation Shell 4.0 and above)" in the drop-down box. 2e. Choose "OK." 2f. (Optional) Click the "Sharing" button and specify if you want to share drives or printers connected to the computer. Then click "OK." 2g. Choose "Drivers." 2h. Select the proper LAN driver for the computer's network board. 2i. Choose "Setup." 2j. Select "ODI driver" from the "Driver Type" drop-down list. 2k. Choose "OK." 2l. Add or remove protocols, as needed. You can use the following protocols with Client 32: * IPX/SPX Compatible Transport * IPX/SPX Compatible Transport with NetBIOS * Microsoft NetBEUI 2m. (Conditional) If you have more than one protocol loaded, select the protocol you want to use as the default and choose "Set as Default Protocol." 2n. Choose "Close" to close the "Network Drivers" dialog box. 2o. Choose "OK." 2p. Choose "No" when prompted to copy over files that are already on the computer. 2q. Choose "Continue" to return to Windows without restarting the computer. 3. Edit the AUTOEXEC.BAT and NET.CFG files to load ODIHLP.EXE after LSLC32.NLM. 3a. From the Program Manager "File" menu, choose "Run." Type "SYSEDIT" and choose "OK." 3b. In the "AUTOEXEC.BAT" window, select the line that loads ODIHLP.EXE (Microsoft's NDIS-to-ODI mapper). From the "Edit" menu, choose "Cut." 3c. From the Program Manager "File" menu, choose "Run." Then type "NOTEPAD" and the path to the STARTNET.BAT file. For example: NOTEPAD C:\NOVELL\CLIENT32\STARTNET.BAT 3d. Click "OK." 3e. In the STARTNET.BAT file, paste the ODIHLP.EXE line above the line that loads PC32MLID.LAN. The STARTNET.BAT file should look similar to the following example: SET NWLANGUAGE=English C:\NOVELL\CLIENT32\NIOS.EXE C:\NOVELL\CLIENT32\LSL.COM C:\NOVELL\CLIENT32\N16ODI.COM C:\NOVELL\CLIENT32\NESL.COM C:\NOVELL\CLIENT32\NE2000.COM LOAD C:\NOVELL\CLIENT32\LSLC32.NLM C:\WFWG\ODIHLP.EXE LOAD C:\NOVELL\CLIENT32\PC32MLID.LAN LOAD C:\NOVELL\CLIENT32\IPX.NLM LOAD C:\NOVELL\CLIENT32\CLIENT32.NLM 3f. Save your changes and close SYSEDIT and NOTEPAD. 4. Restart the computer. NOTES: * If this procedure is not followed, an error 1536 or error 58 will occur during startup of Windows and you will not be able to reference NetWare bindery servers or Directory trees in File Manager or other utilities. * If you change settings in Network Setup or reinstall, Windows places ODIHLP back in the AUTOEXEC.BAT, so ensure that ODIHLP.EXE is being loaded in the proper place. * Any Windows for Workgroups supported combination of IPX/SPX emulation, NetBIOS, and NetBEUI can be used with this configuration. * ODIHLP.EXE maps from NDIS to the 16-bit ODI interface and supports only 16-bit ODI LAN drivers in this configuration. * Refer to the April 1995 NetWare Application Notes for more information on this configuration. 4.4 Named Pipes The Named Pipes terminate-and-stay-resident (TSR) program (DOSNP.EXE) works under DOS and Windows 3.1 only. Windows for Workgroups 3.11 and Windows 95 do not support Named Pipes. 4.5 CD-ROM Drivers MSCDEX.EXE must be loaded before NetWare Client 32 for DOS and Windows 3.1x. If you have a CD-ROM drive and are experiencing problems with the NetWare Client, ensure that the statement to load MSCDEX.EXE comes before the call to STARTNET.BAT in your AUTOEXEC.BAT file. 4.6 Opportunistic Locking Not Available in This Release The Opportunistic Locking feature is disabled in this release of Client 32. Client 32 ignores settings for opportunistic locking in the NET.CFG file. 4.7 Setting the Preferred Tree In NetWare User Tools NetWare Client 32 for DOS and Windows 3.1x allows users to log in to multiple Directory trees and access resources simultaneously. There are applications, that do not support multiple tree access such as GroupWise and the 16-bit version of NetWare Administrator. Applications that are not multi-tree aware, require the correct Directory context to complete some tasks. To set the preferred Directory tree or preferred server in NetWare User Tools, you should complete the following procedures: a. Switch to the "NetWare Connections" screen. b. Identify the Directory tree icon that is marked with and asterisk '*' at the left of the name. c. If it is the incorrect tree context, you can select the preferred tree and then press while double-clicking the tree icon. The asterisk '*' should have moved to the new context. 4.8 Using the Lease Renewal Feature in DHCP 2.0 In the Lease Renewal feature in DHCP 2.0, lease renewal packets are dropped under a heavy load if many workstations request lease renewal packets at the same time. This causes the workstation to hang or exit windows when it receive a lease renewal packet from a DHCP server. The default renewal time is three days. If the lease renewal window is dropped below one day, the potential for this problem to occur increases. You should leave the lease renewal window set at the default. This is a known problem and a patch is available on the Novell Support Connection web site at http://support.novell.com. 5.0 Hardware Compatibility 5.1 Removing PC Cards from Laptop Computers You should power-off laptops when you remove a PC card or when you remove the computer from the docking station. Because Windows 3.1x does not support plug-and-play, Client 32 cannot detect changes in the hardware. 5.2 AST Ascentia 900N Laptop If you have an AST Ascentia 900N laptop computer running 386 Max, see section 6.4, "386 Max 7.x and 8.0." 5.3 Using the 3Com 3C592 and 3C597 EISA Adapters The 3Com 3C592 or 3C597 EISA adapters require the following procedures to successfully install or upgrade them with any other PCI adapters in the same NetWare Client 32 for DOS and Windows 3.1x workstation. Follow these procedures to resolve a conflict with slot numbers created while installing the 3Com EISA adapter after a PCI adapter. a. New NetWare Client 32 for DOS and Windows 3.1x 1. Install NetWare Client 32 with only the EISA adapter(s) present. 2. Reboot the workstation. 3. With the workstation turned off, add your PCI adapters. 4. Start the workstation and load all LAN drivers. 5. All adapters and drivers should load successfully. b. Existing NetWare Client 32 for DOS and Windows 3.1x Workstation or Upgrading an Existing Workstation 1. Delete or comment out all LAN driver load command line information in the AUTOEXEC.BAT file. 2. Unload Client 32 software. 3. Change to the directory on the local drive where Client 32 software is located. 4. Delete the NBIHW.CFG file (if it exists). 5. Turn off the system, then restart the workstation with only the EISA adapters installed. 6. Once the workstation is running and the EISA LAN drivers have loaded correctly, restart the workstation. 7. With the workstation turned off, install your PCI adapters. 8. Restart the workstation and load all adapters or drivers. 9. All adapters should load successfully. 6.0 Memory Management 6.1 Unloading NetWare Client 32 NetWare Client 32 for DOS and Windows 3.1x NLM software can be removed from memory by using the UNLOAD command. For example, to unload the CLIENT32 NLM, type UNLOAD CLIENT32 Note: This will remove your current connections to a NetWare server. 6.2 HIMEM.SYS A HIMEM.SYS 2.3 driver error in Novell DOS 7 requires you to load DOS into the HMA area if you are running the NetWare Client 32 for DOS and Windows 3.1x on a COMPAQ machine. Add the following line to your CONFIG.SYS file: DOS=HIGH,UMB You can also disable the HIMEM.SYS driver and load the EMM386.EXE file included with Novell DOS 7 instead. 6.3 EMM386 * The EMM386.EXE memory manager distributed with MS-DOS 5.0 has a bug that causes programs like NIOS.EXE and SMARTDRV.EXE to hang during a soft reboot (Ctrl+Alt+Del). You should upgrade to a more recent version of EMM386.EXE. Version 4.44 (dated 3/10/92 and distributed with Windows 3.10) as well as versions distributed with MS-DOS 6.x do not have this problem. * If you load EMM386.EXE without the NOEMS option, then you must use the ALTBOOT option. If you don't use this option, the workstation hangs when rebooting using the Ctrl+Alt+Delete command. * COMPAQ 386 users that have machines with BIOS dates prior to 1990 and that are using MS-DOS EMM386.EXE memory manager might experience a hang during a soft reboot when NIOS is loaded. You can avoid the problem by updating the BIOS or by using a memory manager other than EMM386. * COMPAQ laptops sometimes hang if MEMAKER has not configured the computer to run EMM386.EXE. If you are running EMM386.EXE on a COMPAQ laptop, you should run MEMAKER to avoid this problem. * NIOS.EXE can cause some Pentium computers to hang if they are running a version of EMM386.EXE earlier than 4.49 (5/31/94--distributed with MS-DOS v6.22) and an older AMI BIOS. Upgrade to version of EMM386.EXE later than 4.49 to avoid this problem. If possible, you should also upgrade the BIOS. 6.4 386 Max 7.x and 8.0 Some NIOS functions currently do not work correctly on AST Ascentia 900N laptops with 386 Max 7.x and 8.0. You should use 386Max 6.x, QEMM, HIMEM.SYS, or HIMEM.SYS with EMM386.EXE instead. 7.0 International Issues 7.1 Text-Mode Utilities After installation, users of localized platforms in Korea, Japan, China, and Taiwan need to set SHORT MACHINE TYPE to the correct name. See the documentation accompanying your Novell NetWare server. If text mode popup and shutdown border characters are incorrect, use the following information in the NET.CFG file to set the border character values: NIOS LINE DRAW CHARS = "++++|-" If there is not a NIOS section, create one. Future installation programs will set these values automatically. 7.2 Windows Codepages Supported If your system uses a codepage that is not yet supported, copy the following files from the Client 32 CD-ROM's ENGLISH folder to both the \NOVELL\NLS and \WINDOWS\NLS folders: UNI_000.001 UNI_.001 000_UNI.001 _UNI.001 These Unicode mapping tables will restrict object naming to ASCII characters 0x20 through 0x7E (except 0x5C) for old applications that use NETWARE.DRV. The following characters are the ASCII characters that can be used: Backspace Tab Line-Feed Carriage-Return Space ! " # $ % & ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? @ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z [ ] ^ _ ` a b c d e f g h I j k l m n o p q r s t u v w x y z { | } ~ 8.0 Trademarks 8.1 Novell Trademarks Client 32 is a trademark of Novell, Inc. GroupWise is a trademark of Novell, Inc. Internetwork Packet Exchange and IPX are trademarks of Novell, Inc. IPX/SPX is a trademark of Novell, Inc. LAN WorkPlace is a registered trademark of Novell, Inc. in the United States and other countries. NE2000 is a trademark of Novell, Inc. NetWare is a registered trademark of Novell, Inc. in the United States and other countries. NetWare Application Notes is a registered trademark of Novell, Inc. NetWare Client is a trademark of Novell, Inc. NetWare DOS Requester is a trademark of Novell, Inc. NetWare/IP is a trademark of Novell, Inc. NetWare Loadable Module and NLM are trademarks of Novell, Inc. Novell is a registered trademark of Novell, Inc. in the United States and other countries. Novell DOS is a trademark of Novell, Inc. Open Data-Link Interface and ODI are trademarks of Novell, Inc. Sequenced Packet Exchange and SPX are trademarks of Novell, Inc. Virtual Loadable Module and VLM are trademarks of Novell, Inc. 8.2 Third-Party Trademarks AST is a registered trademark of AST Research, Inc. COMPAQ is a registered trademark of Compaq Computer Corporation. Microsoft is a registered trademark of Microsoft Corporation. MS-DOS is a registered trademark of Microsoft Corporation. Network Drive Interface Specification and NDIS are trademarks of PC-PlusCommunications LP. Windows is a registered trademark of Microsoft Corporation. Windows 95 is a registered trademark of Microsoft Corporation. 9.0 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.