NETWARE CLIENT 32 FOR DOS AND WINDOWS 3.x
OPEN BETA NOTES
11/01/95
CONTENTS
1.0 Welcome
2.0 Installation
3.0 Documentation
4.0 LAN Driver Compatibility
5.0 Software Compatibility
6.0 Memory Management
7.0 Trademarks
8.0 Disclaimer
1.0 Welcome
Welcome to the NetWare Client 32 for DOS and Windows 3.1x beta 1.
We are excited about this product and appreciate your support in
testing this early software release. Please e-mail any comments or
suggestions to BETACLIENT@NOVELL.COM. Overview of NetWare Client 32
for DOS and Windows 3.1x NetWare Client 32 for DOS and Windows 3.1x
provides access to network services provided by NetWare servers. Many
of the components that will be in the NetWare Client 32 for DOS and
Windows 3.1x product are in this beta-level software. Other components
are still being developed.
2.0 Installation
To install from DOS, run the DOS installation program INSTALL.EXE.
Future releases will include a Windows 3.x based SETUP.EXE. Install
can set up a computer to run DOS and Windows components.
2.1 DOS C-Worthy Installation
On computers with limited conventional memory, the DOS C-Worthy
install program may run out of memory after repetitive actions or
while scrolling. The computer may report a EMM386 error. This is a
limitation of the beta 1 software that will be corrected in a future
release. If your computer runs out of conventional memory while
installing Client 32, reboot your computer and free some
conventional memory. Run INSTALL.EXE again, avoiding unnecessary
keystrokes.
2.2 DOS C-Worthy User Interface
The user interface is still under construction. The following
interface issues will be resolved for the next beta release.
* Inconsistent actions with F10, Enter and Escape keys.
* Messages boxes with truncated text.
2.3 Installing NetWare Client 32 from a Network Directory
If you want to install NetWare Client 32 from the network, you
should create an installation directory and copy the contents of the
disk directories into the installation directory. Installing NetWare
Client 32 from a single directory is faster than installing from the
disk image directory structure and Setup does not prompt the user to
insert disks.
To create an 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. For example, type the following commands at a DOS prompt
to copy files to the INSTALL directory:
XCOPY WSC32_01\*.* INSTALL /S /E
XCOPY WSC32_02\*.* INSTALL /S /E
XCOPY WSC32_03\*.* INSTALL /S /E
XCOPY WSC32_04\*.* INSTALL /S /E
XCOPY ADMIN\*.* INSTALL /S /E
XCOPY LANDRV\*.* INSTALL /S /E
NOTE: Some files are duplicated in different diskette directories.
When XCOPY prompts you to overwrite files, type "A" to overwrite all
duplicate files.
3. Run INSTALL.EXE from a DOS prompt.
Note: If you have problems installing a third-party LAN driver, choose
a known LAN driver during installation (such as NE2000) and edit
STARTNET.BAT after installation completes to load the driver you
want to use. Some 16-bit LAN drivers require manual setup by editing
the STARTNET.BAT. You also may need to edit the computer's TCP/IP
and LAN Workplace configuration. These are limitations of the Beta 1
DOS C-Worthy installation and do not reflect limitations of the
final product.
3.0 Documentation
Documentation is available in a Windows help file called SETUP.HLP.
There is no .TXT version of this file.
4.0 LAN Driver compatibility
4.1 32-bit Drivers.
NetWare Client 32 for DOS and Windows 3.1x supports third-party
32-bit drivers. In addition, client computers can run NetWare server
LAN drivers such as NE2000.LAN.
Use command-line parameters to specify settings for 32-bit LAN
drivers. The 32-bit drivers do not refer to the NET.CFG file for any
settings. For example, to set the IRQ to 5 for an NE2000 LAN driver,
use the following command:
LOAD NE2000 INT=5
The IRQ parameter in the NET.CFG file is ignored.
4.2 16-bit ODI LAN Drivers
If your computer hangs while using a 16-bit ODI LAN driver, copy
N16ODI.COM from the WSC32_02\NIOS directory to the NOVELL\CLIENT32
directory and load it from the computer's STARTNET.BAT file (located
in the NOVELL\CLIENT32 directory). The following is a sample
STARTNET.BAT file that loads N16ODI.COM:
SET NWLANGUAGE=english
NIOS.EXE
LSL.COM
N16ODI
NE2000
LOAD LSLC32.NLM
LOAD PC3MLID.LAN
LOAD IPX.NLM
LOAD CLIENT32.NLM
Note: Because NIOS.EXE cannot be unloaded from memory, TSRs loaded
before NIOS.EXE can be removed only by rebooting the computer.
5.0 Software Compatibility
5.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.
5.2 VLMs 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's packet
burst mode does not work over these IPX and SPX protocol stacks.
5.3 Upgrading From Client 32 Alpha Releases
The graphical login utility (LOGINW31.EXE) may display an illegal
instruction error on computers that have an Alpha release
installed. If your computer reports this error, search for all
instances of the LOGIN.DAT file and delete all instances that are
not in the Novell\Client32\Nls\English directory.
To remove extra LOGIN.DAT files:
1) At an MS-DOS prompt change to the C: drive.
2) Change to the root directory by typing CD \.
3) Search for the file by typing DIR LOGIN.DAT /S.
4) Remove all instances of the file except the one in Novell\Client32
\Nls\English by typing DEL path\LOGIN.DAT.
5.4 NetBIOS
The NetBIOS terminate-and-stay-resident (TSR) program (NETBIOS.EXE)
works under DOS and Windows only, not under Windows 95.
5.5 Named Pipes
The Named Pipes terminate-and-stay-resident (TSR) program
DOSNP.EXE) works under DOS and Windows only, not under Windows 95.
5.6 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.
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 <Enter>
Note: This will remove your current connections to a NetWare server.
6.2 HIMIEM.SYS
Due to a bug in the HIMEM.SYS (v2.3) driver in Novell DOS 7, you
must load DOS into the HMA area if 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 MS Windows 3.10) as well as versions distributed with MS DOS
6.x do not have this problem.
COMPAQ 386 users that have machines with BIOS dates prior to 1990
and that are using MS-DOS EMM386.EXE memory manager may experience a
hang during a soft reboot when NIOS is loaded. The only workarounds
at this time are to update the BIOS or to not use EMM386.
7.0 Trademarks
7.1 Novell Trademarks
GroupWise is a trademark of Novell, Inc.
Internetwork Packet Exchange and IPX are trademarks of Novell, Inc.
NetWare is a registered trademark of Novell, Inc. in the United States
and other countries.
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.
NetWare Requester is a trademark is a trademark of Novell, Inc.
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.
7.2 Third-Party Trademarks
COMPAQ is a registered trademark of Compaq Computer Corporation.
Microsoft and MS are registered trademarks of Microsoft Corporation.
MS-DOS is a registered trademark of Microsoft Corporation.
Windows is a registered trademark of Microsoft Corporation.
8.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.
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.