NETWARE CLIENT 32 FOR WINDOWS 95 OPEN BETA NOTES 10/23/95 CONTENTS 1.0 Welcome 2.0 Installation Basics and Help 3.0 Creating a Network Installation Directory 4.0 Installation Issues 5.0 Graphical (GUI) Login Issues 6.0 NetWare Application Manager 7.0 Requester Issues 8.0 Printing Issues 9.0 ODI and NDIS Support Issues 10.0 NetWare 3 Compatibility Issues 11.0 NetWare 2.2 Compatibility Issues 12.0 SNMP Issues 13.0 General Issues 14.0 International Issues 15.0 Documentation Issues 16.0 Future Plans 17.0 Trademarks 18.0 Disclaimer 1.0 Welcome Welcome to the NetWare Client 32 for Windows 95 beta test. We are excited about this product and appreciate your support in testing this early software release. 1.1 Open Beta Support While Novell is supporting beta customers already enrolled in the NetWare Client 32 Beta program, Novell will not provide technical support for new Open Beta customers. However, customers may submit enhancement requests to ENHCLIENT@NOVELL.COM and other feedback to CLIENT32BETA@NOVELL.COM during the Open Beta phase of development. Answers to FAQs will be posted to CompuServe and the WWW. 1.2 Final Release Support Technical support for the final release of NetWare Client 32 for Windows 95 will be the same as for all other NetWare products. Novell and its partners will provide full technical support, including technical assistance, enhancements and fixes. 2.0 Installation Basics and Help For information on installing NetWare Client 32 for Windows 95 at the same time you install Windows 95, see "Option 1: Installing Using a Server-Based Windows 95 Install" in the "Installing" section of the SETUP.HLP file. To open the SETUP.HLP file, click "Start" then "Run" and browse for the SETUP.HLP file in the NetWare Client 32 file set and click "OK" to execute the help. TIP: For better responsiveness, copy the SETUP.HLP and SETUP.CNT files to the NetWare Client 32 for Windows 95 folder (typically, C:\NOVELL\CLIENT32). If the \NOVELL\CLIENT32 folder does not exist, create it. 3.0 Creating a Network Installation Directory PREREQUISITES: These instructions assume that the NetWare Client 32 for Windows 95 self-extracting files have been copied to a single directory and expanded into a structure that can be used to create diskettes. The installation can be done from either the diskettes or from a network installation directory. For ease of installation and performance, we recommend that you create an installation directory on the network or on your local drive. To create a network installation directory: 1. Create a directory called INSTALL in the same directory from which the self-extracting files were executed. 2. Copy the contents of each diskette directory to the INSTALL directory using the XCOPY command. For example: XCOPY SETUP\*.* INSTALL /S /E XCOPY DISK2\*.* INSTALL /S /E XCOPY DISK3\*.* INSTALL /S /E XCOPY DISK4\*.* INSTALL /S /E XCOPY ADMIN\*.* INSTALL /S /E XCOPY LANDRV\*.* INSTALL /S /E XCOPY UNICODE\*.* INSTALL /S /E NOTE: Several files exist on more than one diskette. During the XCOPY process, the DOS message "Overwrite (Yes/No/All)?" is displayed. Type "Y" to overwrite the specific file listed in the message or type "A" to overwrite any and all duplicate files. 3. To install the client from this INSTALL directory, run SETUP.EXE from a Windows 95 workstation. NOTES For a network install, always use the INSTALL directory. The SETUP directory is used for diskette creation. 4.0 Installation Issues 4.1 Upgrading from the VLM Client If you are upgrading from the VLM NetWare client or if you don't have any network client software installed, you need to have the Windows 95 CD-ROM or diskettes or the Windows 95 cabinet (CAB) files available when you install NetWare Client 32 for Windows 95. 4.2 Upgrading from the NETX Client If you are upgrading from the NETX NetWare client, edit your CONFIG.SYS file and remove the LASTDRIVE statement or change it to LASTDRIVE=Z. 4.3 Upgrading from the Microsoft Clients to NetWare Client 32 for Windows 95 If Microsoft's Client for Microsoft Networks and Client for NetWare Networks are currently installed on your Windows 95 workstation and you are upgrading to NetWare Client 32 for Windows 95, you might need to configure for "Preferred server," "Preferred tree," "Name context," and "First network drive." To set the above properties: 1. In the "Network" control panel, click "Novell NetWare Client 32." 2. Click "Properties." 3. In the "Login" tab, enter the values you want for "Preferred server," "Preferred tree," "Name context," and "First network drive." 4.4 Alpha Testers If you were an alpha tester and have NetWare Client 32 for Windows 95 installed on your workstation, remove ODINSUP and your adapter from the "Network" control panel before setting up NetWare Client 32 for Windows 95 to get the latest ODI LAN driver for your network adapter. When you remove ODINSUP and your adapter from the "Network" control panel, the client is also removed. All the properties are preserved, however, so you don't have to redo the "Preferred server," "Preferred tree," "Name context," and any other properties you might have set. 4.5 File and Printer Sharing for Microsoft Networks If a copy of NetWare Client 32 for Windows 95 that is older than the Open Beta software is installed on your workstation, and "File and printer sharing for Microsoft Networks" is also installed, do the following: 1. Remove "File and printer sharing for Microsoft Networks" from the "Network" control panel. 2. Install NetWare Client 32 for Windows 95. 3. Reinstall "File and printer sharing for Microsoft Networks." 4.6 TCP/IP Configuration Settings NetWare Client 32 for Windows 95 does not include its own TCP/IP protocol stack. Therefore, any existing TCP/IP parameters are not moved from the NET.CFG file to the registry. 4.7 Building Driver Information Database Message You might see this message four or five times during installation. This is normal. The installation program does not display this message, but depending on installation procedures, it has Windows 95 rebuild the driver information database to ensure that the driver index is correct. 4.8 "Network" Control Panel It's been observed that a lot of changes in succession on the "Network" control panel without clicking "OK" tends to result in registry corruption. We recommend that you click "OK" between changes. 5.0 Graphical (GUI) Login Issues 5.1 Advanced Screen Available There is an advanced screen available for the graphical login utility. There is a property on the "Login" tab of "Novell NetWare Client 32 Properties" to control whether the advanced or simple login screen is displayed. 5.2 MS-DOS Prompt If the login script being used contains a #command (such as #CAPTURE), you might have to manually close the associated MS-DOS Prompt window. To have the MS-DOS Prompt window close automatically, do the following: 1. Click the icon in the upper-left corner of the MS-DOS Prompt window. 2. Click "Properties." 3. Click "Close on exit," which is on the "Program" tab. The box next to "Close on exit" should now have a checkmark in it. 4. Click "OK." The fix for this will be in a future update of this Beta product. 5.3 Removing Old LOGIN.DAT Files If the graphical login (LOGINW95.EXE) is displaying an illegal instruction error, check for LOGIN.DAT files outside the \Novell\Client32\Nls\English folder. To search for LOGIN.DAT files, at an MS-DOS Prompt enter: C: CD \ DIR LOGIN.DAT /S Remove all instances of the file except the one in \Novell\Client32\Nls\English. NOTE This only applies to users who have installed an Alpha or Beta 1 release of NetWare Client 32 for Windows 95. 5.4 Additional Login Parameters The "Additional login parameters" field on the Login tab is not functional and will be removed in the future. 6.0 NetWare Application Manager The NetWare Application Manager allows users to run applications that were previously configured by a network supervisor, and whose setup information is stored as an Application object in the NetWare Directory tree. For more information about NetWare Application Manager, see the README.NAL file in the NAL directory of the ADMIN disk. 7.0 Requester Issues 7.1 Do Not Cancel "Network Status" Messages NetWare Client 32 might display a "Network Status" message on networks that are experiencing abnormal delays. It is recommended that you not cancel this message. The client is retrying the operation in the background. If you click "Cancel," there is a possibility that your workstation will hang. If you wait, the client closes the "Network Status" message when it gets a response from the server. 7.2 Global Drive Mappings All drives (including search drives) are viewed globally with the client. That means that anytime a drive is mapped anywhere in Windows (for example, File Manager, MS-DOS Prompt, or Windows Explorer), the drive is accessible and visible in every other part of Windows. Locations or directory paths are private to each area. Whenever a drive is changed to a different directory, the directory change affects only that specific instance of the drive. For example, if the drive is changed to the PUBLIC directory at an MS-DOS Prompt, no other MS-DOS Prompt or Windows application (such as File Manager) displays this change. If a drive is mapped to a location on a volume, the following things happen in the case of a nonrooted drive: * The drive is mapped to the volume level on the server. * The drive is then changed to the directory specified. This means that all areas of Windows see the drive as new, but every location sees the drive mapped to the volume level except the MS-DOS Prompt or Windows application where the drive was originally mapped. If a drive is mapped using the map root syntax of the MAP utility, the following occurs: * The drive is mapped to the location (volume:directory) specified. In this case, all locations of Windows see the drive as mapped to the same directory. 7.3 Running Out of Server Disk Space NetWare Client 32 for Windows 95 behaves differently than previous NetWare clients with respect to running out of server disk space. The difference is that NetWare Client 32 for Windows 95 caches file write data in memory and then actually writes this data out later. This makes an application think that its writes completed successfully, but in the case of running out of disk space, the following happens: 1. An application writes file data and receives a success return code. 2. The file data resides in cache until a background process writes the data to the server across the network. 3. The server returns an OUT_OF_DISK_SPACE error code to the client. 4. The client pops up a critical error box with the following message: "Out of disk space writing file to server ." "Try deleting some files before continuing." "Warning: You will lose data if you hit 'Cancel'." 5. If the user clicks "Retry" after deleting some files to make room, the file is written to disk. If the user clicks "Cancel," that file's write data is lost but the application might still indicate that the file was saved successfully, potentially confusing the user. This behavior can be disabled by turning off the caching of write data. To do so, change the value of "Cache Writes" to "off." For more information, see the Cache Writes topic in the NWCFG95.HLP help file. NOTE When users exceed their volume space limit (as specified in their volume space restrictions), they should delete some files and click "Retry" the same as if the server ran out of disk space. 7.4 Long Filename Support 7.4.1 Long Filename Support on NetWare 4.1 To enable long filename support on NetWare 4.1: 1. Copy PM410.NLM and NSWILDFX.NLM from the Patches\Nw410 directory on the Admin diskette to the SYS:\SYSTEM directory on the server. 2. Load the OS/2 name space. At the server console prompt, enter LOAD OS2.NAM 3. Load the patches. At the server console prompt, enter LOAD PM410 LOAD NSWILDFX 4. Add the OS/2 name space to the server volumes. At the server console prompt, enter ADD NAME SPACE OS2 TO VOLUME 5. Add the load commands for the OS/2 name space to the STARTUP.NCF file and the patches to the AUTOEXEC.NCF file. 7.4.2 Long Filename Support on NetWare 3.11 To enable long filename support on NetWare 3.11: 1. Copy PATCHMAN.NLM, SHORTAFX.NLM, and OS2OPNFX.NLM from the Patches\Nw311 directory on the Admin diskette to the SYS:\SYSTEM directory on the server. 2. Load the OS/2 name space. At the server console prompt, enter LOAD OS2.NAM 3. Load the patches. At the server console prompt, enter LOAD PATCHMAN LOAD SHORTAFX LOAD OS2OPNFX 4. Add the OS/2 name space to the server volumes. At the server console prompt, enter ADD NAME SPACE OS2 TO VOLUME 5. Add the load commands for the OS/2 name space to the STARTUP.NCF file and the patches to the AUTOEXEC.NCF file. NOTES PM410.NLM and PATCHMAN.NLM are the server patch managers. The OS/2 name space provides long filename support at the server. You won't be able to delete a long filename using wildcards if the mask is longer than 8.3. For example, ERASE ThisIsALong*.TXT won't work, but ERASE This*.TXT works (and includes ThisIsALong*.TXT). 7.5 Borland C++ Under Windows 95 Under Windows 95, the Borland C++ make utility version 4.5 does not work correctly when the Borland executable files are located on a network search drive. For example: map ins s1:=server/sys:tools/bc45/bin The make utility is building an invalid path for the other Borland utilities called in the makefile. The workaround is to map the search drive as a root, similar to the following example: map ins r s1:=server/sys:tools/bc45/bin 7.6 NLM Programs After Windows 95 is loaded, loading and unloading NLM programs is not supported. 8.0 Printing Issues 8.1 NPRINTER Workstations cannot run the NetWare 4 NPRINTER or NetWare 3 RPRINTER terminate-and-stay-resident (TSR) programs under Windows 95. A 32-bit NPRINTER.EXE will be available in the future. 8.2 Windows 95 Applications Do Not Use Captured Printer Ports A capture redirects the output from an LPT device to a network printer. Under Windows 95, GUI applications do not send data to an LPT device. Instead, they send the data directly to a Windows 95 printer device, which points to a network printer. If you do a capture at an MS-DOS prompt, any writes to LPT1 are directed to the network printer specified in the capture, as long as you are at the MS-DOS prompt. However, any flags set up under a DOS capture cannot be translated into the GUI world. There's no way to associate a Windows 95 printer device with an LPT port. Here's an example of the problem. You have a printer device under Windows 95 called HP_PRINTER, which is set to print to NETWORK_HP_PRINTER. The flags for HP_PRINTER are set up such that there is no banner or form feed. At an MS-DOS prompt, you now do two captures (LPT1 and LPT2) to NETWORK_HP_PRINTER. The first capture specifies a banner and a form feed. The second capture specifies a banner and no form feed. Now you attempt to print a document in the GUI environment to HP_PRINTER. How can the provider associate one of the captured LPTs with HP_PRINTER? Which LPT capture information should it associate with HP_PRINTER? In summary: * A capture has meaning only when printing to an LPT port. * Captures are global. If you do a capture at an MS-DOS prompt, the capture exists under GUI; if you do a capture in the GUI world, it exists for MS-DOS prompts. However, the settings that are used when printing from a GUI application to a Windows 95 printer device are not the same as the settings in the capture. 8.3 NDS Print Queues NDS print queues are displayed in the Network Neighborhood and the Windows Explorer. To add a printer for an NDS print queue, find the print queue using the Network Neighborhood or the Windows Explorer. Then, double-click the print queue icon and use the "Add Printer Wizard." The problem occurs if you go through "My Computer," "Printers," and "Add Printer" to get to the "Add Printer Wizard." In this case, no NDS print queues are displayed in the "Browse for Printer" window. The fix for this is available as SHELLUPD.EXE at these Internet sites: http://www.microsoft.com/windows/software/shellupd.htm ftp://ftp.microsoft.com/peropsys/Win_News/FreeSoftware/shellupd.exe SHELLUPD.EXE updates the SHELL32.DLL in the Windows System folder. 9.0 ODI and NDIS Support Issues 9.1 Updating LAN Drivers If you have newer versions of third-party ODI LAN drivers than those that ship with this Open Beta of NetWare Client 32 for Windows 95, it is possible to update them by copying the .LAN or .COM file to the NOVELL\CLIENT32 folder for 32-bit .LAN drivers or the NOVELL\NWCLIENT folder for 16-bit .COM drivers. 9.2 Third-Party ODI .INF Files If you want to use an ODI LAN driver for your network adapter, do the following before running SETUP.EXE: 1. Edit the NWSETUP.INI file. NWSETUP.INI is in the Install directory of the NetWare Client 32 for Windows 95 file set. For diskettes, it is on the Setup disk. 2. Uncomment the .INF file for the ODI LAN driver that you want. The .INF files are listed in the [INF Files] section of the NWSETUP.INI file. The .INF files for third-party LAN drivers are named ODIxxx.INF (for example, ODI3COMT.INF), where xxx is the manufacturer of the network adapter. To uncomment a .INF file, delete the semicolon (;) in front of it. If you want to use NDIS drivers, comment out the corresponding .INF file in the NWSETUP.INI file. 9.3 Alpha Third-Party ODI .INF Files If you have installed the alpha versions of NetWare Client 32 for Windows 95, you might need to delete the third-party ODI .INF files from the Windows INF directory (typically, C:\WINDOWS\INF). 1. Open an MS-DOS Prompt and change to the Windows INF directory. 2. Create a backup directory (for example, INFBKUP). 3. Copy all of the ODI .INF files to the backup directory. 4. Delete the ODI .INF files from the \WINDOWS\INF directory. 5. Restore the ODINSUP.INF file from the INF backup directory. For example: CD C:\WINDOWS\INF MD INFBKUP COPY ODI*.INF INFBKUP DEL ODI*.INF COPY INFBKUP\ODINSUP.INF 9.4 List of LAN Drivers A list of ODI LAN drivers that are shipped with NetWare Client 32 for WIndows 95 is included in the SETUP.HLP file. Additional LAN drivers will be added as they are developed and tested. 9.5 Do Not Remove "Novell ODINSUP" Do not remove any instances of "Novell ODINSUP" from the "Network" control panel unless you know which one belongs to which ODI adapter. There is a one-to-one mapping. You cannot just remove any of them. "Novell ODINSUP" is automatically removed when the adapter is removed, but not until after the "Network" control panel is closed. Also, removing "Novell ODINSUP" removes NetWare Client 32 for Windows 95 if there is only one adapter in use. 9.6 16-bit ODI Driver Limitations The following issues are apparent only if there are multiple adapters using 16-bit drivers in the machine. There are no known problems having two adapters using 32-bit drivers or with one adapter using a 32-bit driver and the other using a 16-bit driver. The problems occur when both adapters are set to use 16-bit drivers at the same time. 9.6.1 If two or more adapters are set to use 16-bit DOS ODI drivers and later one of the drivers is switched to be a 32-bit ODI driver, the Windows 95 installation process (which is utilized by the driver .INF files) removes the LSL.COM and NESL.COM files from the AUTOEXEC.BAT file. This leaves the remaining 16-bit DOS ODI driver without LSL.COM and NESL.COM in the AUTOEXEC.BAT file. The removal occurs because there is no usage count associate with the LSL.COM or NESL.COM files. To correct this problem, edit the AUTOEXEC.BAT file and add lines for LSL.COM and NESL.COM. Add these lines before the 16-bit driver. 9.6.2 If there are two or more adapters of the same type that specify the same 16-bit DOS ODI driver, the Windows 95 installation process adds the driver to the AUTOEXEC.BAT file only once. To correct this problem, edit the AUTOEXEC.BAT file and copy the driver statement so that each adapter has a driver loaded for it by the AUTOEXEC.BAT file. 9.6.3 If there are two or more adapters of the same type and both are using 16-bit DOS ODI drivers, switching one adapter to use a 32-bit ODI driver or removing the driver altogether removes the one instance of the 16-bit driver from the AUTOEXEC.BAT file. The adapter left using the 16-bit driver is not in the AUTOEXEC.BAT file. To correct this problem, edit the AUTOEXEC.BAT file and add the driver statement. 9.6.4 If there are two or more adapters of the same type and both are using 16-bit DOS ODI drivers, changing the first adapter to use the second adapter’s configuration, and then changing the second adapter’s configuration to a nonconflicting configuration, removes the first driver from the NET.CFG file (which used to be the second driver’s old configuration) if the second driver is processed first during the install process. If the first driver is processed first, then both drivers are removed from the NET.CFG file. This condition occurs because when updating the NET.CFG file, the process tries to remove an adapter’s old configuration and then add the new configuration. If the old configuration matches a different driver’s current configuration, the configuration is removed. There is no easy way to know that the configuration belongs to a different adapter. 9.7 Limitations When There is More Than One Driver Available for a Network Board The following problems generally occur when a driver choice for an adapter is between ODI and NDIS, but they also occur if there are two ODI drivers or two NDIS drivers that can be used on the same adapter. The term "same adapter" refers to adapters that have the same Plug and Play ID. The adapters might be manufactured by different venders, but if they are compatible, they will have the same Plug and Play ID. 9.7.1 Installing a Hardware-detectable Adapter, Such as an EISA Adapter The Windows 95 hardware detection routine installs all network software when it detects a new adapter in the system. An adapter is new if there is no information about it in the registry. (Either the adapter was in the system but the existing driver was removed, or an adapter was put in the machine and powered on). When the adapter is detected, the first driver in the list of drivers is installed. If the desired driver for that adapter is further down in the list, the first driver found is still installed. 9.7.2 Switching Back and Forth Between the 16- and 32-bit ODI Drivers If the driver for the selected adapter has a Plug and Play ID in an .INF file that appears before the .INF file containing the selected driver in the driver index list, the install and remove sections in the selected driver’s .INF file are not executed by the Windows 95 install process. Without the install and remove sections executing, the AUTOEXEC.BAT file is not maintained correctly and the driver files are not copied. If either of the two previous problems manifests itself, rename the .INF file that is not desired, so that the information from the desired .INF is always used. To find the .INF file to rename, search each .INF file for the one that the system is currently using, which is the .INF file that matches the LAN driver's provider, manufacturer, and device ID. 9.8 NetWare Server Drivers NetWare server drivers written to the NetWare 3 driver specification cannot be used on a workstation that is running NetWare Client 32 for Windows 95. 9.9 Source Routing The source route NLM program is designed to work with ODI drivers. NDIS LAN drivers are not supported by the source route NLM program. NDIS drivers support source routing through the NDIS protocol stack. 10.0 NetWare 3 Compatibility Issues For information about long filename support, see "7.5.2 Long Filename Support on NetWare 3.11." 11.0 NetWare 2.2 Compatibility Issues There are known issues using Briefcase, Windows Explorer, and Network Neighborhood. These issues will be resolved in the future. Basic login and utilities are supported. 12.0 SNMP Issues Currently, printers, modems, and tape drives are not shown in the Host Resources MIB Device Table. 13.0 General Issues 13.1 Refresh NWPOPUP.EXE If receipt of a network message gives you a TEXT MODE "NetWare critical error" message and your system appears to be hung, do the following: 1. If you are unable to regain control of the system, reboot. 2. Copy NWPOPUP.EX_ from DISK 2 to the Windows 95 system directory. 3. Press ctrl-alt-del and end the NWPOPUP.EXE task. 4. Delete the old NWPOPUP.EXE from your Windows 95 system directory. 5. Expand the new NWPOPUP.EXE (that is,. EXPAND NWPOPUP.EX_ NWPOPUP.EXE). 6. To activate this new version, shutdown and restart your computer. 13.2 GroupWise Client for DOS To run the GroupWise Client for DOS, use the /da command line switch, which disables the DOS task- switching API support. NetWare Client 32 for Windows 95 does not support task switchers. 13.3 Task Switching Is Not Supported NetWare Client 32 for Windows 95 does not support task-switching features of programs. For example, the task-switching features of the GroupWise Client for DOS and the MS-DOS Shell (DOSSHELL.EXE) are not supported. 13.4 Data Files Held Open Login script data files and Application object icon data files might be held open if accessed by the graphical (GUI) login or the NetWare Application Launcher for Windows 95. The problem might manifest itself through access denied messages or by changes not being saved. To get around this, have all users that have accessed these data files from Windows 95 log out. 13.5 Winsock for SPX and IPX The WINSOCK.DLL file that supports SPX/IPX connectivity is not shipped with this Open Beta of NetWare Client 32 for Windows 95. If you want to use Winsock for SPX and IPX, copy the WINSOCK.DLL file from the NetWare Client 32 for DOS and Windows 3.1x release. The WINSOCK.DLL file will be included with NetWare Client 32 for Windows 95 in our next Beta release. 13.6 NDOS Command Shell For users of Symantec's The Norton Utilities' NDOS command shell, NetWare Client 32 for Windows 95 is compatible only with NDOS versions distributed with The Norton Utilities v7.00 and later. 14.0 International Issues 14.1 Unicode Tables Not Found On some international versions of Windows 95, you might see the following message during startup. NWDRV-3.00.30: Initialization of the Unicode tables failed Country id = XXX and code page = YYY All NetWare Directory Services functions are disabled. To work around this problem, add a code page override in your WIN.INI file. Use the [NetWare] section in your WIN.INI file to set the NWCodepage override value. If the [NetWare] section does not already exist, create it. You can edit the WIN.INI file using SYSEDIT or NOTEPAD. After you make this change, restart your system for the change to take effect. Also, be sure that the iCountry= setting in the [intl] section of the WIN.INI file is correct for your locale. For example, on a traditional Chinese system in Taiwan, you might need to have the following sections in the WIN.INI file: [NetWare] NWCodepage=950 [intl] iCountry=88 The following are example country code and code page values. Country Code Code Country Page 81 Japan 932 82 Korea 949 86 China 936 88 Taiwan 950 If you find this problem in other countries, please let us know by sending Internet E-mail to client32beta@novell.com. This problem will be corrected in future updates of this Beta product. 14.2 Unicode Tables for Text-mode Utilities If you have difficulties running NetWare text-mode utilities (such as FILER, PCONSOLE, NETADMIN, and so forth) at a Windows 95 MS-DOS Prompt, copy the Unicode mapping tables to the following directories: SYS:LOGIN\NLS SYS:PUBLIC\NLS SYS:SYSTEM\NLS For example, for running a traditional Chinese system in Taiwan attached to a Novell NetWare 4.1 server, you could do the following: MAP T:=SYS: CD C:\WINDOWS\NLS COPY *.088 T:\LOGIN\NLS COPY *.088 T:\PUBLIC\NLS COPY *.088 T:\SYSTEM\NLS NOTES You must have the appropriate trustee rights in order to copy the files. NetWare 2 and NetWare 3 servers do not use Unicode files. Therefore, this procedure is not applicable. 14.3 Text-mode Utilities Might Not Display Correctly Text-mode utilities (such as FILER, PCONSOLE, NETADMIN, and so forth) might not display correctly for Korea, China, and Taiwan. The overlay files that are needed to correct this problem will be provided in the future. 14.4 People's Republic of China The Unicode mapping files for PRC, country code 86, are not available in this Open Beta. If you are using PRC Windows 95, please send E-mail directly to Novell at client32beta@novell.com for information on receiving these files. 14.5 Other International Issues If you have any other difficulties, please report the problem by sending Internet E-mail to client32beta@novell.com. Preface your message with "Attention: Novell International Development." 15.0 Documentation Issues The documentation is not complete. We're working on comprehensive information about NetWare Client 32 for Windows 95. Comments and suggestions are welcome. 16.0 Future Plans 16.1 Planned Beta 2 Updates 16.1.1 Automatic Client Upgrade (ACU) ACU will allow a network supervisor to centrally locate the NetWare Client 32 for Windows 95 code on a file server. At login time, the workstation can be updated with the client code the network supervisor has placed on the server. This includes the ability to update to NetWare Client 32 for Windows 95 from the NETX, the VLM, or the Microsoft NetWare client. 16.1.2 RAS Support RAS support will allow remote dial-in to a RAS server using a local modem, ISDN card, or X.25. Services available to a typical network user are available by using a RAS connection. 16.1.3 System Policies Complete management of NetWare Client 32 for Windows 95 using System Policy Editor (POLEDIT) and system policies will be available. A template containing client properties that can be specified using the NetWare Client 32 property sheets will be made available for use with POLEDIT. 16.1.4 Browser for Graphical Login Users will be able to browse the network for a server or tree at login time. 16.1.5 Multiple Tree Support Will allow the ability to authenticate to and browse multiple NetWare Directory Services (NDS) trees and their resources. 16.1.6 Complete Documentation Complete documentation for NetWare Client 32 for Windows 95. It will include complete online help in native Windows 95 format and quick-reference information in hard copy. 16.2 Planned for Future Releases 16.2.1 Network Copy of Windows 95 NetWare Client 32 for Windows 95 does not support running a shared copy of Windows 95 off the network. 16.2.2 Remote Program Load (RPL) NetWare Client 32 for Windows 95 does not support Remote Program Load (RPL). These capabilities are planned for a later release after NetWare Client 32 for Windows 95 v1.0. If you currently need to run a shared copy of Windows 95 off the network or if you need RPL support, you should use NetWare Client for DOS and MS Windows. 16.2.3 Personal NetWare Support NetWare Client 32 for Windows 95 does not support Personal NetWare. (The install program comments out any calls to SERVER.EXE or STARTNET.BAT in the AUTOEXEC.BAT file.) 16.2.4 Private Drive Mappings All drive mappings are global. Private DOS box support is not available. Private DOS box support will be in a future release. See also "7.2 Global Drive Mappings." 16.3 No Support Planned No support is planned for Windows 95's file and print sharing for NetWare Networks (emulated NCP file and print services). However, NetWare Client 32 for Windows 95 does support file and printer sharing for Microsoft Networks (peer services) using the [Microsoft] Client for Microsoft Networks, which uses the SMB file- sharing protocol. 17.0 Trademarks 17.1 Novell Trademarks Novell and NetWare are registered trademarks of Novell, Inc. in the United States and other countries. GroupWise, NetWare 3, NetWare 4, NetWare Client, NetWare Core Protocol and NCP, NetWare Directory Services and NDS, NetWare Loadable Module and NLM, Open Data-Link Interface and ODI, Personal NetWare, and Virtual Loadable Module and VLM are trademarks of Novell, Inc. 17.2 Third-Party Trademarks Borland is a registered trademark of Borland International, Inc. CompuServe is a registered trademark of CompuServe Incorporated. Microsoft, MS, MS-DOS, and Windows are registered trademarks of Microsoft Corporation. HP is a registered trademark of Hewlett-Packard Company. OS/2 is a registered trademark of International Business Machines Corporation. Symantec and The Norton Utilities are registered trademarks of Symantec Corporation. Unicode is a registered trademark of Transoft Ltd. 18.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.