2.10 Novell NetWare Windows version 3.1 includes updated versions of several Novell NetWare files that are required to run with Windows 3.1. If you are running Novell NetWare, Windows Setup will copy the following files to the SYSTEM subdirectory of your Windows directory (or the shared network directory if you set up a shared copy of Windows by using setup /n). NETX.COM (version 3.26) IPX.OBJ (version 3.10) TBMI2.COM (version 2.1) IPXODI.COM (version 1.20) LSL.COM (version 1.21) Before running Windows you may need to do the following: . Replace your current NetWare shell with the NETX.COM provided (if your current NetWare shell is older than the version provided). Windows 3.1 requires that the NetWare shell components on your workstation (such as NET5.COM) be version 3.01 or higher. You can use these shell components even if your servers are running older versions of NetWare (as early as NetWare 2.10). Your current shell may have one of the following names: NET3.COM XMSNET3.EXE EMSNET3.EXE NET4.COM XMSNET4.EXE EMSNET4.EXE NET5.COM XMSNET5.EXE EMSNET5.EXE NETX.COM XMSNETX.EXE EMSNETX.EXE NETX.COM will run on MS-DOS versions 3.1 or higher. The EMS and XMS versions of the shell are available from your Novell dealer and the Microsoft Windows Driver Library (WDL). For information about ordering the WDL, see Getting Started with Microsoft Windows. Note: The EMS NetWare shells (EMSNETX.EXE, etc.) are not supported when Windows is running in 386 enhanced mode. . If you are running Novell IPXODI.COM and LSL.COM, you need to upgrade these to versions 1.20 or higher. Use the files provided with Windows and copy them from the SYSTEM subdirectory of your Windows directory (or your shared network directory) to the directory where your existing versions are located. . To run Windows in standard mode, load the TBMI2.COM memory-resident utility when running Windows. Novell recommends that you create a batch file that will load this utility, start Windows, and then unload the utility when you quit Windows. The batch file could be named RUNWIN.BAT and look like this: TBMI2 WIN TBMI2 /U TBMI2 enables you to safely run applications that use the NetWare IPX and SPX functions in standard mode Windows or the MS-DOS 5.0 task switcher. . If you are running Novell IPX.COM, you need to have your system administrator build you a new version using the IPX.OBJ provided with Windows. In addition: . If you enable 32-bit disk access and you are running the XMS shell rather than one of the standard NetWare shells (NETX.COM, etc.), you can further improve performance by setting the OverlappedIO entry in the [386Enh] section of your SYSTEM.INI file to on. . Do not try to log in, log out, attach, or detach a Novell server from MS- DOS Prompt within Windows. You should log in before starting Windows, and attach or detach servers by using File Manager or the Printers option in Control Panel. . If you experience problems starting applications while running Windows or Windows applications from a file server, make sure you are not running the MS-DOS SHARE utility. Current versions of the NetWare shell are not fully compatible with SHARE. . If you have a Western Digital Ethercard Plus and have problems accessing drives by using the MAP ROOT command, contact Western Digital for an updated driver. . By default, NetWare gives you access to only 40 files at a time. When you are running applications with Windows, you can exceed this limit rather quickly. If so, you might see unexpected error messages. To increase the file access limit, add the following line to your SHELL.CFG file: file handles = 60 You should also add the following to your CONFIG.SYS file: files = 60 . If you get unusable output when printing to a NetWare server (such as incorrect fonts, garbled text, invalid page breaks, or blank lines), you may need to edit your print-job configuration. Try using the NetWare PRINTCON utility to set the Auto Endcap and Enable Timeout options to No. . When running Windows in 386 enhanced mode, swapping to a drive on a NetWare 286 server might make starting Windows take up to a minute. See Chapter 14, "Optimizing Windows," in the Microsoft Windows User's Guide for information about controlling the location of your swap file. . A NetWare file server does not include the directory entries dot (.) and double dot (..) as MS-DOS does. However, the NetWare shell (version 3.01 or higher) can emulate these entries when applications attempt to list the files in a directory. If you have problems listing files or deleting directories, turning on the Show Dots feature will help. Add the following line to your SHELL.CFG file: show dots = on Turning on Show Dots will cause problems with earlier versions of some 286-based NetWare utilities, such as BINDFIX.EXE and MAKEUSER.EXE. Make sure you upgrade these utilities if you upgrade your NetWare shell. For more information, contact your Novell dealer. . Redirected drives can look different in Windows than they did without Windows. For example, a device mapped as FileServerName/Volume:Directory will appear in Windows as FileServerName/Volume:\, showing the root of the file server's shared volume, rather than the subdirectory you expected. You can correct this with the MAP ROOT entry explained in the following information. . In some cases, Windows applications may change the default directory on a drive. This might cause problems if, for example, your path includes the current directory on a network drive (that is, your path includes a drive letter without a specific directory, such as z: instead of z:\system). You can prevent this problem by using MAP.EXE and LOGIN.EXE versions 3.0 and later to set up fake roots, or by choosing the MAP ROOT function when mapping a connection in File Manager. This feature simulates the MS-DOS subst command, which sets the root of a given drive to a directory designated by the user instead of to the true root of the volume. For example, suppose you normally mapped drive F to the HOME\TERRI directory on the SERVER\SYS volume, and then included F: in your path. You would do this by including the following command in your AUTOEXEC.BAT file or by typing the command before starting Windows: map f:=count\sys:home\terri The default directory on drive F would then be HOME\TERRI. To prevent Windows from changing this, you would replace the command above with the one shown below: map root f:=count\sys:home\terri This command would make the directory HOME\TERRI appear to be the root drive F. . If you are running Windows in 386 enhanced mode, you can adjust the way Windows handles your network drive mappings by using the Network option in Control Panel. Normally, when you quit Windows, all of your drive mappings are restored to the way they were before you started Windows, and all changes you made inside Windows are lost. If you clear the Restore Drives option, the mappings you made inside Windows will remain when you quit Windows. Typically, each instance of MS-DOS Prompt you start from Windows has its own set of drive mappings. Changes you make in one instance do not affect another. If you set the NWShareHandles option, drive mappings will instead be global, and changes made in one instance of MS-DOS Prompt will affect all other applications. If you are running a NetWare 286 server, setting NWShareHandles increases the number of workstations that can be connected to the server before the server runs out of available connections. See the Help available in the Network dialog box in Control Panel for more information on these options. . When setting up Windows for use with Novell NetWare, the following entry is added to the [windows] section of your WIN.INI file: load=nwpopup.exe This automatically starts the NetWare pop-up utility, which displays your incoming broadcast messages. . If you are running Novell NetBIOS, you may need to specify TimerCriticalSection=10000 in the [386Enh] section of the SYSTEM.INI file. . If you have applications or files that use extended characters (ASCII characters above 128) and you have problems viewing or using them, try adding the following line to your SHELL.CFG file: special uppercase = on . When connecting or disconnecting network resources from File Manager, Print Manager, or Control Panel, pay attention to the state of the Permanent check box. If this option is checked when you make a connection, the connection is automatically made each time you restart Windows. To stop reconnecting, disconnect with the Permanent option checked. If the option is not checked when you disconnect, the connection is removed for the current Windows session, but is reconnected when you restart Windows. .