NetWare Client 32 for Windows 95

Frequently Asked Support Questions, (FAQs) for NetWare Client 32 for Windows 95

Note: For additional details on many of the FAQs and other issues, refer to the README.TXT and SETUP.HLP included with the Client 32 product.

Note: We have divided this FAQ into different sections based on the logical components of the 32-bit Client. New issues will first appear under the heading, "New since last update:."

New since last update:

Q: How can I Login to Multiple Trees from within the Login Script using the GUI Login?

A: Use the following syntax in your Login Script:

TREE TREENAME\.FULL.NDS.NAME

Client 32 Requester:

Q: Why do I get the following error on reboot after upgrading from VLM's to Client32 on Windows95? "NWDRV-3.00-20: There was a problem loading or executing the Netware Directory Services support libraries. All Netware Directory Services functions are disabled."

A: This error occurs when NETWARE.DRV can not find the correct support libraries or finds an incorrect version of the support libraries. To correct this issue make sure the support library DLL's listed below are in the Windows\system or Win95\system subdirectories. Also delete all other copies of these DLL's that exist on your hard drive. Following are the DLL's that shipping with the released Client 32 for Windows95.

NWCALLS.DLL 147,824 07-26-95

NWNET.DLL 225,280 07-12-95

NWLOCALE.DLL 43,344 01-22-96

NETWARE.DRV 157,872 01-26-96

This error can also be caused by having a trailing period in you name context set in the Novell Client32 properties page.

Q: Can the NetWare Client 32 for Windows 95 be used in a dual boot configuration for Windows 3.1?

A: The NetWare Client 32 for Windows 95 is written specifically for Windows 95 and is not compatible with Windows 3.1. In a dual boot configuration the NetWare Client 32 will only be loaded for Windows 95. Other Novell clients can be used for the DOS/Windows boot. In a dual boot configuration each operating system has its own CONFIG and AUTOEXEC files so loading VLMs on DOS and NetWare Client 32 on Windows 95 should be straightforward. However, care should be used when installing a Novell Client for DOS or Windows as all DOS session configuration files have the extension .DOS (CONFIG.DOS, AUTOEXEC.DOS) rather than .SYS or .BAT. This means that the install program will modify the Windows 95 configuration files which are named AUTOEXEC.BAT and CONFIG.SYS. Renaming the configuration files prior to installing and then renaming them back after the installation is recommended.

Q: I am having problems with database and mail programs when using Client 32. What can I do to troubleshoot the problem?

A: There have been reported cases of problems with some applications that do record locking. To verify whether the issue is with the Client, Go to Control Panel | Network. Select Client 32 and choose Properties. Now select Advanced settings and select Opportunistic Locking. Turn this parameter OFF (the default is ON) and restart the machine to verify if this is the issue.

Q: Does NetWare Client 32 for Windows 95 include support for TSA SMS?

A: The initial version of the client will not have TSA support in Windows 95. TSA support will be included in a future revision of the client.

Q: Does NetWare Client 32 for Windows 95 support running the client with a shared copy of Windows 95?

A: NetWare Client 32 for Windows 95 does not support running a shared copy of Windows from the network. This will be supported in a future revision of the client. However, NetWare Client 32 for DOS/Windows will contain support for running a shared copy of Windows 3.1 from the network.

Q: How do I adjust my frame type?

A: Frame types are set in the Network Control Panel. Frame information is stored in the IPX Protocol. Select IPX Protocol and click on the properties button. The frame type can be adjusted in the Advanced tab. By default, NetWare Client 32 will set a frame type of Auto-Detect with an Auto-Bind. Note: It is possible to have more than one IPX protocol loaded. Be sure to adjust the correct protocol.

Q: How does the Client32 for Windows 95 deal with file handles and how can they be increased?

A: Windows 95 uses the number of files indicated by the FILES= parameter in the CONFIG.SYS. The default and minimum required value is 60 files. The remaining maximum of 195 file handles are then available for use by Client32 (255 files is still a limitation for each individual PC). Thus to maximize the number of files available for Client32, the FILES= parameter should be left at the default value of 60.

Q: Why can I not see all files and directories on my 3.11 server?

A: The shortafx.nlm must be loaded on all 3.11 servers. Shortafx.nlm is shipped with the Client 32 and located in the admin directory or diskette. Os2opnfx.nlm should also be loaded on all 3.11 servers using the OS2.nam name space. Os2opnfx.nlm is also located in the admin directory or diskette. Refer to the Readme.txt for additional information on this subject.

Q: Does the Client 32 for Windows 95 provide both NetWare Directory Services support for NetWare 4 users as well as bindery support for NetWare 3.x users?

A: Yes, NetWare Client 32 for Windows 95 provides support for both NDS and bindery users.

Q: How do GroupWise Administrators configure users since the AD.EXE uses task swapping?

A: GroupWise AD.EXE program has a command line switch that disables it's task switcher usage. This switch will be required to run it successfully with Client 32.

Q: Does the Novell Client 32 support Long File Names on a NetWare server?

A: Yes, However we require the administrator to add the OS/2 name space to the NetWare volume. For more information on this topic, refer to the section in the README.TXT that is included with the client. It will detail which patches and commands are required to get this feature to work.

GUI Login Issues:

Q: Is there a way to disable the Novell Login when starting Windows 95?

A: There is no way to disable the Novell Login. Microsoft determines whether or not a network client (Novell, NT, etc.) is loaded upon startup of Windows 95. If a client is detected, Microsoft calls the primary network provider to login. After the user logs in to the primary network provider, Microsoft requires you to login to Windows 95 itself. Novell caches the login information so if the users Windows 95 name and password are the same as the networks, it will not display the Windows 95 login screen. If no network client is detected, the Windows 95 login is displayed to login to the workstation.

Q: I am trying to map insert a search drive on a 3.11 server in my login script and it is not working correctly. All the drives are being mapped to the root of the volume and I cannot see any directories beneath the root.

A: The problem on the 3.11 server is fixed by applying the shortafx.nlm included with the client. The shortafx.nlm is found in the \admin\patches\nw311 directory where the Client 32 was installed from.

Q: I am mapping a drive to f:\users\jdoe in the login script. When I login and try to access my jdoe directory using the Windows Explorer or any other GUI utility the drive seems to be map rooted.

A: This is the way that Windows 95 operates. A work-around to this issue would be to map root the directory. This would solve the problem of having to walk the directory tree to access the directory in the GUI utilities, but would present all the challenges associated with not being able to walk up the tree to get to directories above the mapped drives.

Q: The GUI login does not appear after installing the client. After confirming the standard "file server not found" issues, what other options do I have to troubleshoot the problem?

A: Edit the SYSTEM.INI file on the Windows 95 workstation and add the parameter found below in the [386Enh] section.

[386Enh]

NWEnableLogging=True

This will allow the Client to create a NIOS.LOG file in the C:\NOVELL\CLIENT32 directory which will give you more detailed information to help troubleshoot the problem.

Q: How do I execute external commands from within a login script?

A: Use the @ command instead of the # command. The difference between the two is that the @ command will spawn a process for the command to run but will continue with the login script. The # command will wait for the process to complete before going on.

Q: Is there any way to have other sounds or *.wav files play instead of fire phasers within a login script?

A: Phasers.wav ships with NetWare Client 32 and is played when the fire phasers command is issued in Login Script. Another *.wav file could be renamed phasers.wav if another *.wav file is desired every time. Another solution would be to put either:

fire filename.wav or

fire phasers filename.wav

in the login script. This will allow other *.wav files to be played instead of the phasers.wav during the login process.

Q: After installing NetWare Client 32 the splash screen displays but not a login screen. No error message is displayed. The Network Neighborhood is empty.

A: A file server could not be found. Make sure that the frame type conforms to your particular LAN. Also, make sure that the Novell NetWare Client 32 properties name the correct preferred server and preferred tree and that the Name context is correctly set. These adjustments are made from Control Panel|Network. Troubleshooting this issue is similar to getting "File Server not found" with VLMs.

Q: Can the GUI login make a bindery connection to a 3.x server if it is my preferred server? If so, is this option configurable?

A: Yes, enable the Advance login option under properties of NetWare Client 32. After a restart, select the Connection tab on the main property sheet. Make sure that the Server option is selected, followed by the bindery connection.

Q: Can LOGINW95.EXE be copied to, and executed from the server rather than the local workstation? Is this configurable during installation?

A: No, the GUI login is required to be executed from the local workstation.

Q: What do the drop down options in the advanced GUI login under the Script property sheet mean?

A: The GUI Login Advanced script option remembers the last five scripts and paths used for both user and profile scripts and stores those in the registry database.

Q: Why does the login results box not automatically close after completing the login script execution?

A: By default, the results screen should close. However, if there was an error that occurred, it will stay open so you can view the error that occurred.

Q: When capturing within the login script, why does the dos box that is opened not auto-close?

A: This is an issue with the way Windows 95 handles DOS boxes called from a GUI interface. To configure for close on exit, right click on the Dos icon (upper left hand corner) and select properties. Check the close on exit option and select apply.

Q: How can I prevent users from logging out of the tree within the network neighborhood?

A: Enable System policies. For now you can use the generic network options for system policies support. Note: Novell provides a template for Policy Editor (Client 32.ADM). This will allow you to select which specific Novell Client options a user can change or use on their desktop.

Q: In the Network Neighborhood, I do not understand the icon objects for NDS objects?

A: Novell is limited to the icons made available in the SHELL32.DLL. We are unable to provide snap-in resources for the Network Neighborhood or Explorer interfaces due to a limitation of the Microsoft's Network Provider specification.

Interoperability with other Novell Products:

Q: How do I get information and instructions to enable Win95 to connect to my NetWare Connect Server using "NRN: NetWare Connect" or "PPP:" that comes with Win95 Dial-Up?

A: NWCINF. EXE 01/05/96 contains the following readme text files that explain issues and patches needed to setup NetWare Connect. Files included in NWCNF.EXE are 95.TXT, IP.TXT, NWC201.TXT, NWC202.TXT, RNS.TXT, WIN95.TXT. NWCINF.EXE is available from NetWire in NWGENFIL Library 3. Note: We have seen problems with IPX/SPX using "PPP" and are looking into them.

Q: Why are Rconsole and other 16bit IPX/SPX applications unable to connect to or display all servers?

A: Rconsole and other 16bit IPX/SPX applications will send packets or communicate using the primary board. Client 32 can bind IPX to more than one frame type. By default Client 32 will Auto detect the IPX frame type to be used for the primary board. If this primary Board Frame type is not the one needed for Rconsole or other 16bit IPX/SPX applications problems may occur in finding or connecting to servers. These issues can be resolved clicking on the Network Icon in Control Panel and going to the "Novell NetWare 32-bit IPX Protocol Properties" and selecting "Advanced IPX ". Then use "Primary Logical Board" and change "Frame type:" to the correct one needed for your application. (ie. Ethernet_803.3 , Ethernet_802.2, Ethernet_II or Ethernet_snap)

Q: I am a developer, and would like to upgrade my applications to support a 32-bit version of NWIPXSPX.DLL. Will NetWare Client 32 for Windows 95 support a 32-bit IPX/SPX API Library?

A: NWSIPX.DLL is included with the Client 32, and is a 32-bit version of the NWIPXSPX.DLL file. Developers can use the SDK provided on-line with this client to gain information about how to write applications specifically to NWSIPX.DLL.

Q: Will there be a version of GUI Login that allows search mappings for DOS/Windows workstations?

A: When NetWare Client 32 for DOS/Windows ships, it will contain a GUI Login utility that allows search drive mappings and environment variables to be set from a login script in Windows 3.1.

Q: Will NetWare Client 32 for Windows 95 also work for NT workstations?

A: NetWare Client 32 for Windows 95 is specifically written to Windows 95. It will not function on Windows NT.

Q: How is NetWare/IP configured in Windows 95? Does it use DHCP or BootP for configuration?

A: NetWare/IP can be configured via either BootP or DHCP.

Q: Do I have to use the Microsoft stack with NetWare/IP or can I use another TCP/IP stack with NetWare/IP?

A: NetWare/IP in Windows 95 is supported over any TDI compliant TCP/IP stack, thus allowing TCP/IP stack independence.

Q: I am trying to use LANAlyzer for Windows, with Windows 95 and Client 32, but receive error messages. Will LANAlyzer work with Windows 95, and will it support both ODI and NDIS drivers?

A: The current version of LANAlyzer (v2.1) will not work with Client 32. DI.COM and APPLE.COM need to be loaded prior to Windows 95 loading. This version of LANAlyzer will work with VLMs and Windows 95.

A new version of LANAlyzer is in development, which will run with Client 32. It is currently in Beta test, and will be released shortly after Client 32 is released. It will function with Client 32 and a 32-bit ODI driver, a 16-bit ODI driver, or a NDIS 3.0 driver.

Q: Does NetWare Client 32 for Windows 95 support Personal NetWare, or NetWare Lite?

A: The first release of Client 32 does not support Personal NetWare, or NetWare Lite.

Q: Will there be a 32-bit version of NWAdmin available for Windows 95?

A: There is a 32-bit version of NWAdmin under development. This development is in parallel with the Client 32 effort. NWAdmin will be delivered separately, and after NetWare Client 32 for Windows 95. The current 16-bit version of NWAdmin will work with Client 32 for Windows 95.

Q: When will NetWare Client 32 for DOS/Windows be available?

A: NetWare Client 32 for DOS/Windows is currently in development. It will be made available in an Open Beta format in 2nd quarter 1996.

Lan Driver Issues:

Q: How do I switch from an NDIS to an ODI driver with Client32 for WIN95?

A: Do this by first adding the appropriate ODI driver under Network ---> Add ---> Adapter. Then, and only then, remove the NDIS driver from the Network panel interface list.

Q: Does NetWare Client 32 for Windows 95 support 100 Mbps ARCnet cards?

A: Currently, there is not a TSM (Topology Support Module) for ARCnet that will allow a 32-bit ARCnet driver to work with Client 32. However, the client can be configured with PC32MLID, which will allow the client to run with a 16-bit ARCnet driver.

Q: Will Client32 for WIN95 support a 32-bit ODI driver for Arcnet?

A: No.

Q: I am having driver-related problems (slow performance, errors, etc.) after installing Client32 for WIN95. What do I do?

A: Contact the manufacturer of the LAN board and request the latest driver whether it be the NDIS or ODI driver. If the driver is an ODI driver, request the latest 32-bit ODI server driver for 4.10 NetWare servers (e.g.-- NE2000.LAN); if that driver fails, switch to the latest 16-bit ODI driver for that adapter. Do this by highlighting the current adapter name under the "Network" icon and select "Properties", then mark "16-Bit ODI Driver".

Q: Can I use a Microsoft NDIS driver if a 32-bit ODI is not available for Windows 95?

A: Yes, Novell's Client 32 for Windows 95 can run over either a 32-bit ODI, 16-bit ODI or 32-bit NDIS drivers. These options are configurable in the Control Panel | Network window.

NAM Issues: (NetWare Application Manager)

Q: While attempting to setup and test NAM, I find I am unable to run NWADMIN after modifying the ini file. The following error occurs during the initialization of NWADMIN. Error: "APPSNAP.DLL version 4.00.1, does not correspond with the version the Netware Administrator requires (version 4.10.2). Install the correct version before restarting the Netware Administrator."

A: You have placed the APPSNAP.DLL in the wrong section of your nwadmin.ini. APPSNAP.DLL must be under the [Snapin Object DLLs] section. Additional information is available in readme.nal on the Admin diskette.

NIOS (NetWare I/O Subsystem):

Q: How do I determine which client NLMs are loaded?

A: Because NIOS is based on NetWare Server technology, you can drop out to a DOS box and type the command MODULES. This will display all the modules that are loaded on the client. This can be a useful tool for troubleshooting.

Q: How much memory is consumed by NIOS.VXD?

A: NIOS and the necessary Client 32 modules use approximately one megabyte of extended memory. If additional protocols or services are added, they will increase this requirement.

Q: What is the recommended memory for using Client 32 in a Windows 95 configuration?

A: 8 MB or greater is the preferred memory requirement. It is not supported to use Windows 95 networking with only four megabytes of RAM.

Printing Issues:

Q: How do I prevent the banner page and form feed when printing?

A: There are several locations from which the form feed and banner page can be set:

1- In the control panel, Novell NetWare Client32, Properties, under the default capture tab there are settings.

If the printer was setup to print applications from DOS:

2- In the capture settings - check using capture sh from a dos box

3- In the printer, properties, capture settings

If the printer was not set up to print from dos

2- In the printer, properties, Printer settings tab (capture settings tabs are ignored) there is a place to set the banner page and form feed option. Verify that the above settings are turned off. Also note that the way MS Windows 95 works that if you have more than one printer setup to service a queue, that Windows 95 will use the settings for the first printer that it finds to service that queue. That is the way windows 95 works, so make sure that you have the settings the same on all defined printers.

Q: When will an nprinter solution for Windows 95 and the NetWare Client 32 be available?

A: A GUI version of Nprinter that supports the NetWare Client 32 for Windows 95 will be available in the near future.

Q: Are there equivalent programs to RPRINTER.EXE and NPRINTER.EXE for Windows 95?

A: There is a GUI based NPRINTER utility in development for Windows 95, which will replace the current RPRINTER.EXE and NPRINTER.EXE utilities. This printer utility will be made available in beta format, separate from NetWare Client 32.

Q: How do I get HP's JetAdmin to work?

A: There are several issues that involve HP's JetAdmin.exe. First, If you install the JetAdmin as a service through the control panel...(Control Panel, Network, Add, Service, Hewlett-Packard, HP JetAdmin) you will get an error after logging in through the NetWare Client 32 GUI Login. The text error is on a blue background and reads "A fatal exception OE has occurred at (address) in VXD NWLINK(02) + (address). The current application will be terminated.

The second issue is related but the errors can be eliminated. If you specify the HP JetAdmin (NetWare support) from the Control Panel, Network, Add, Service, Hewlett-Packard, HP menu and make the following change in the c:\windows\inf\hpnetprn.inf file:

[JANW.ndi.reg]

HKR,Ndi\Compatability,RequireAll,,"NOVELL32"

All errors will be eliminated, but starting the JetAdmin through the Control Panel will result in the error "JetAdmin could not find any configuration printers on your network. Please be sure Networking is configured." even though there are JetDirect cards active on the network. Novell has determined the cause of the problem and referred the issue to HP.

To get JetAdmin to run in Windows 95 using the NetWare Client 32, run the version of JetAdmin that ships in the Novut1 and Novut2 files that HP ships (version A.01.11). This version of JetAdmin allows all printers to be seen and configured correctly.

Q: Why can't I see NDS print queues in the add printer wizard's browser?

A: There is a problem with the Microsoft SHELL32.DLL which limits this functionality for the provider. However, Microsoft has provided an updated file that includes this fix. This fix is available as SHELLUPD.EXE at:

ftp://ftp.microsoft.com/peropsys/Win_News/FreeSoftware/shellupd.exe

For more information on this issue, refer to the Client 32 README.TXT.

Provider Issues:

Q: Does this client include Auser level security,@ which is required for remote administration functions, like remote editing of registries?

A: No. This functionality is available when Windows 95 is configured with NCP file and print services as a server. Since NCP file and print services is not supported with Client 32, neither is user level security.

Q: Can I manage NetWare file access, rights, and trustees via the NetWare provider?

A: Graphical management of NetWare file access, rights, and trustees is available in the released version of Client 32 for Windows 95. This functionality can be managed via System Policies.

Q: Can I authenticate too, and access more than one NDS tree at a once?

A: Multiple Tree Authentication has been enabled in the released version of the Client.

Q: I have had a couple of problems using long file name support with the client. What can I do to correct these?

A: Follow the steps outlined in section 7.4 "Long Filename Support" of the README.TXT file that comes with the client software.

Q: In Windows 3.1, the client uses the NWUSER utility. What happened to this utility and its functionality?

A: NWUSER is a utility specific to Windows 3.1. All of the functionality of NWUSER, with the exception of the send command, is supplied through Novell's Provider extensions into Network Neighborhood and Explorer.

However, NWUSER is available to Windows 95 users. To enable this utility, create a NETWARE.INI file in the \WINDOWS directory. Add the following two lines in the NETWARE.INI file:

[restrict]

Win95AllowDRVUI=1

Note: Permanent Captures and Mappings set with NWUSER in Windows 95 will not be restored when Windows loads, since NWUSER saves this information in an INI file, and Windows 95 reads all the NetWare settings for Client 32 from the Registry. Use Novell's Windows 95 provider to set permanent drive mappings and captures.

Q: How do I configure the client to support either global or private drive mappings across DOS Boxes? When will this support be available?

A: By design, in Windows 95, mappings will be global across all DOS Boxes. NetWare Client 32 for DOS/Windows 3.1 will support private or global drive mappings.

Q: Is the SEND command supported under Windows 95 with the NetWare client software?

A: Novell's Provider for Windows 95 does not support the send command. However, NWUSER is available to Windows 95 users, which supports the SEND command. To enable this utility, create a NETWARE.INI file in the \WINDOWS directory. Add the following two lines in the NETWARE.INI file:

[restrict]

Win95AllowDRVUI=1

Note: Permanent Captures and Mappings set with NWUSER in Windows 95 will not be restored when Windows loads, since NWUSER saves this information in an INI file, and Windows 95 reads all the NetWare settings for Client 32 from the Registry. Use Novell's Windows 95 provider to set permanent drive mappings and captures.

Q: Winpopup works nicely. I like no icon. However, can it be shut off? Can a message be sent to other logged in users?

A: Winpopup is a Windows 95 utility, and is not supplied with Client 32. It is designed to work with the Microsoft client. Currently, it does not support sending messages to other NCP workstations, from a workstation with Client 32 loaded.

Q: Is there a way to disable the Novell Logo that is displayed when Client 32 loads?

A: Yes. Create a NETWARE.INI file in the \WINDOWS directory. Add the following two lines to the NETWARE.INI file.

[options]

DisableLogo=1

Q: What is the, "first network drive parameter"in the Control Panel | Novell NetWare Client 32 | Properties section used for?

A: The "first network drive parameter" functions differently with Client 32 for Windows 95 than it does in the DOS/Windows environment. The First Network Drive in the DOS/Windows environment is used to specify the drive letter to login from. Now it is used to specify what drives are available to be used as network drives. If your first network drive is set to F, and there was the following command in the login script:

map *1:=sys:public

Drive F would be mapped to sys:public.

The first network drive parameter does not map a drive to the server login directory, because login is being performed locally through loginw95.exe. Because of this, there will be no drive letter mapped to the first network drive unless the drive is mapped explicitly in a login script.

Q: How do you change your password without using SETPASS?

A: Select Control Panels, Passwords, Change Other Passwords, Novell NetWare. At this point you will be able to change your password. This also allows you to synchronize your password.

Q: How do I grant and view file system rights and information from within Windows 95.

A: NetWare Client 32 allows you to use the usual NetWare utilities (filer, rights, etc.) and has also built this functionality into the Windows Explorer. Right clicking on the directory or drive in Windows Explorer and choosing Properties, allows a user to see tabs labeled NetWare Folder, NetWare Rights, and if you are clicking on a disk, NetWare Volume Information.

The NetWare Folder contains information about the directory, i.e. name, type, location, size, DOS name, creation date/time and attributes. The NetWare Rights folder contains a list of trustees of the directory or volume and allows you to add and remove trustees and rights. The NetWare Volume Information folder shows the volume name and number, the server it resides on, the total space in KB, available space, total directory entries, and available entries.

Q: Why can't I see users in the Network Neighborhood ?

A: The NetWork Neighborhood flat browser is unable to display user objects. This is a limitation of the Microsoft interface.

Q: Does the NetWare Client 32 product still require a NET.CFG?

A: No. Novell has integrated with the Microsoft REGISTRY database. Changes made to the client property sheets are reflected as updated to the registry.

Setup Issues:

Q: How to I get the Dial-up Networking folder to show up with Windows 95 after configuring the Novell Client for the dial up adapter?

A: The dial-up networking client can be added by following these steps:

Select Start | Settings | Control Panel | Add/Remove Programs | Communications

The communications component needs to be selected. Now select Details. The Dial-Up Networking option should have a check mark. From here click OK to copy the files from the Win95 CD-ROM. When this process completes, you will be able to access the Dial-Up Networking folder found under My Computer. From here you will be able to finish configuring your dial-up connection

Q: What policy options does the Novell Client 32 for Windows 95 support?

A: The Novell Client works with the following: User Policies and System Policies. However, Group Policies, accessed from a NetWare Server are not supported in the initial release of the client.

Q: What happens if I re-install Windows 95 over an existing installation that contains the NetWare Client 32 for Windows 95.

A: A re-installation of Windows 95 over an existing one that contains NetWare Client 32 for Windows 95 will result in the client no longer working. The Novell splash screen will appear but no login window ever displays. The Network Control Panel will indicate that the Novell Client is still installed. This situation can be remedied by deleting everything in the Network Control Panel. Save the changes and then re-install the NetWare Client 32.

Q: Is there an uninstall utility available for the Client software?

A: There is currently no AUninstall@ utility for NetWare Client 32 for Windows 95. The, "Remove" option will prevent the client from loading.

Q: How can I get the NetWare Client 32 to integrate with MSBATCH.

A: There are special INF files for MSBATCH located in the INSTALL\ADMIN\BATCH directory of the NetWare Client 32 install for the full set (C3295N_B.EXE). The INF files are also located in the BATCH directory of disk 7 (labeled ADMIN) of the Client disk set. For additional information refer to the ONLINE HELP by selecting Start, Help, Novell NetWare Client 32, Installing, Option1: MSBATCH SETUP.

Q: How can I load a DOS TSR with WIN95 and Client32 after I have a connection to the network but before I execute LOGIN?

A: DOS TSR's that need to be loaded after a network connection is established, and must communicate with NetWare interfaces should be loaded in WINSTART.BAT to be globally accessible (from multiple DOS boxes and the System Virtual Machine). If this causes problems the TSR and application will have to be run from a single DOS box from within WIN95. If there are still problems, contact the TSR or application vendor.

Q: How do I increase the Environment size for DOS boxes?

A: You can increase the Environment size with the NetWare Client 32 by adding an environment pad. This is accomplished by adjusting the properties of the Novell NetWare Client 32. In the properties menu select Advanced Settings. Under Parameter groups select Environment Pad. The default is 64. This can be increased to as high as 32K (32,768 bytes). This setting only adds space to the existing environment. To make changes to the size of the startup environment for DOS edit the Command.com Properties. You can do this by opening a DOS box and then selecting the properties icon.

Q. Why are the Client 32 downloadable files so large (4 meg)? The Microsoft NDS client can be downloaded in a 400k file.

A. The entire Novell client is included in the downloadable file. Most of the Microsoft client is on the Windows 95 CD. You only have to download the updated files from Microsoft that allow you to use NDS.

Q: Can the Novell NetWare Client 32 installation program run from a directory with a long filename?

A: The Novell NetWare Client 32 Installation program does not support long filenames. This includes the use of spaces in the name of the directory. The directory that contains the Novell setup program, SETUP.EXE, and all parent directories needs to conform to the standard DOS 11 character (8.3) naming convention. Note: The 8.3 naming convention only applies to the installation program SETUP.EXE not the Novell NetWare Client 32 product.

Q: Will the Novell Client SETUP upgrade my existing Microsoft Client for NetWare to the NetWare Client 32?

A: Yes, the Novell SETUP program will upgrade your existing client configuration and apply those settings to the Client 32 setup. Refer to the README.TXT for more information on this topic.

Q: Can the NetWare Client 32 be configured to work with Windows 95 from a shared Windows environment?

A: NetWare Client 32 for Windows 95 v1.0 release will not. This will be considered for the v1.1 release of the product.

TCPIP Issues:

Q: How is TCP/IP managed in Windows 95? Does it use DHCP or BOOTP for configuration?

A: Currently, Client 32 uses the TCPIP.VxD file that ships with Windows 95. This version of TCP/IP uses DHCP for configuration setup. In addition, Client 32 can be used with any TDI compliant TCP/IP stack. Configuration via DHCP or BootP is TCP/IP stack dependant.

Q: Does NetWare Client 32 for Windows 95 include TCP/IP support?

A: The NetWare Client 32 release contains the NetWare/IP protocol only. This protocol does interoperate with the Microsoft TCP/IP stack. NetWare/IP replaces the IPX protocol which provides the transport in the native NetWare environment with the TCP/IP protocol. This is done by "wrapping" the IPX packet. If you need TCP/IP support install the Microsoft TCP/IP protocol. NetWare Client 32 is fully compatible with the Microsoft protocol. In fact, NetWare/IP requires that TCP/IP be installed, so it will only function if the Microsoft TCP/IP protocol is installed. NetWare