INTRANETWARE CLIENT FOR DOS and WINDOWS 3.1x
ENGLISH-ONLY RELEASE
RELEASE NOTES
7/9/97
CONTENTS
1.0 Primary Documentation Is Help
2.0 Installation Issues
3.0 General Issues
4.0 International Issues
5.0 Trademarks
6.0 Copyright, Export Notice, Patents
1.0 Primary Documentation Is Help
The help files for IntranetWare Client for DOS and Windows
3.1x--containing information on installing, configuring,
using, understanding, and troubleshooting--are the primary
documentation. To see the Client help, click IntranetWare
Client Help in the IntranetWare Client program group. All the
Client help information is accessible from this file. The
IntranetWare Client help file (SETUP.HLP) can also be accessed
prior to installation in the
PRODUCTS/DOSWIN32/IBM_6/NLS/<language> directory.
2.0 Installation Issues
2.1 Installing from the IntranetWare Client CD-ROM
Complete the following steps to install the IntranetWare
Client on one workstation.
1. Insert the IntranetWare Client CD-ROM.
2. Do one of the following:
* From the File Menu in the Program Manager, click
Run, and then enter the path for the IntranetWare
Installation program (WINSETUP.EXE).
For example, if your CD-ROM drive is D:, enter the
following:
D:\WINSETUP.EXE
* From the File Mananger, click your CD-ROM drive,
and then double-click WINSETUP.EXE.
3. Click the language version you want to install.
4. Click Intranetware Components for Windows 3.x.
5. Click the software you want to install.
6. Click Yes to accept the Software License Agreement.
7. Do one of the following:
* If SETUP.INI has been edited for an unattended
installation or ACU, the setup process is
automatically completed. Reboot when prompted.
* If the Choose Optional Components dialog box is
displayed, select the components you require, and
then click Next.
8. Follow the on-screen instructions to complete the
setup.
Based on the optional components you have chosen, you
might have to set up a Location Profile. Follow the
on-screen instructions to complete this task if
necessary.
9. When Setup is complete, click Finish to restart the
computer.
10. (Conditional) If the Location Selection dialog box is
displayed when the workstation restarts, click a
location.
For more information on selecting locations and other
specific features of the IntranetWare Client, refer to
the IntranetWare Client online help.
11. Start Windows and log in.
2.2 Do Not Run DOS Install to Upgrade IntranetWare Client
Software on the Windows 3.1x Platform
Although the DOS install utility (INST_DOS.EXE) installs
the client software for Windows 3.1x and the VLM cleints,
it does not install some additional features included on
the Windows platform (including BorderManager
components). If you are upgrading a Windows 3.1x system,
you should run the WINSETUP.EXE install utility from the
root of the CD-ROM instead to make sure you receive all
new features.
2.3 Do Not Run DOS Install Utility to Reinstall the Client on
the Windows 3.1x Platform
If you have previously installed a Novell 32-bit client
for Windows 3.1x using the Windows-based utility
(SETUP.EXE), do not reinstall the client software using
the DOS-based utility (INST_DOS.EXE). The configuration
files for these two utilities are updated and maintained
differently, and configuration information from previous
Windows-based configurations will be lost. Instead, you
should run WINSETUP.EXE from the root of the CD-ROM.
2.4 Running the Setup over a Dial-up Connection Doesn't Reboot
Workstation
If the setup is run over a dial-up connection, the
workstation cannot reboot at completion while the dial-up
connection is still active. To resolve this, disconnect
the dialer and reboot manually when setup is completed.
2.5 NetWare/IP Auto-Connection Over Dial-Up Servers
In the LAN environment, NetWare/IP clients can be
automatically configured by Dynamic Host Configuration
Protocol (DHCP). This works only if your DHCP host can
be configured for NetWare/IP client configuration
records. In a Dial-Up environment, the NetWare/IP client
usually depends on a DHCP host located in the dial-up
server itself. Once again, this works only if the DHCP
host in the dial-up server can be configured for
NetWare/IP client configuration records. If you are
using a dial-up server that cannot be so configured, then
you must manually configure the client.
2.6 Incorrect IP Address Might Be Assigned If Two or More
Locations Are Configured to Use TCP/IP with DHCP
If two or more locations are configured to use TCP/IP
with DHCP on the same workstation and they exist on
different IP networks, the wrong IP address might be
assigned to a given location.
To avoid this problem turn off DHCP IP caching by
specifying the DHCPCACHEIP option under the PROTOCOL
TCPIP heading:
PROTOCOL TCPIP
DHCPCACHEIP = NO
2.7 NetWare/IP and the IP/IPX Gateway
The Novell IP Gateway can operate as an IPX/IP Gateway or
an IP/IP Gateway.
IPX/IP is appropriate when the client is attached to an
IPX network or to a network supporting both IPX and IP.
We recommend that NetWare/IP not be used when the client
is operating as an IPX/IP Gateway.
IP/IP Gateway is appropriate when the client is bound to
the IP Protocols. Normally, NetWare/IP should be used in
a configuration which supports user login and location of
IntranetWare servers with the gateway through NDS. If
the preferred gateway server is specified by IP address
and access control is disabled for the server, then
NetWare/IP is not required when using the gateway. In an
IP/IP Gateway configuration, NetWare/IP is required for
access to other IntranetWare servers on the LAN.
2.8 Dial-in Connections via NWIP Might Fail on Second or
Subsequent Connections
If you experience problems connecting with NWIP via
remote access through a dial-in connection on the second
or subsequent connections, do one of the following:
* Restart your workstation so that the required
connection will be the first connection.
* Create a location profile that uses IPX protocols
over the dial-in connection.
For more information on creating a location
profile, see "Creating a New Location Profile" in
IntranetWare Client Help.
2.9 Backup Files Created by SETUP.EXE
SETUP.EXE creates backups of both AUTOEXEC.BAT and
CONFIG.SYS files such as AUTOEXEC.000 or CONFIG.000.
Subsequent installations then create additional backup
files such as AUTOEXEC.001 or CONFIG.001, AUTOEXEC.002 or
CONFIG.002, and so forth.
2.10 SPX Parameters Are Not Properly Carried over from the VLM
Client.
If a workstation with the VLM client had SPX parameters
set in the NET.CFG file, those parameters are not in
effect after installing the IntranetWare Client. The
reason is that the section under which the SPX parameters
reside has changed from PROTOCOL SPX to PROTOCOL IPX. To
have the SPX parameters work with the IntranetWare
Client, move them under the PROTOCOL IPX section.
2.11 INST_DOS Asks for DISK 1 and Then Hangs the Workstation
When running the DOS install for the IntranetWare Client
for DOS and Windows 3.1x (INST_DOS.EXE), the error
"Insert the NetWare Client 32 for DOS/Windows 3.1x Disk 1
into drive <drive letter>: or press <Alt><F10> to exit
Install" occurs. To resolve this, map root the drive and
run INST_DOS.EXE again.
2.12 Editing the STARTNET.BAT and NET.CFG Files with More Than
One Location Profile
If you have more than one location profile, most
modifications to the the NET.CFG file and STARTNET.BAT
file must be made using the Location Manager.
1. From the IntranetWare Client Program Group,
double-click Client Control Panel.
2. Double-click Locations.
3. Click a Locations Profile in the Locations scroll box.
4. Click Advanced.
5. Do one of the following:
* To edit the NET.CFG file, click Edit NET.CFG.
* To edit the STARTNET.BAT file, click Edit
STARTNET.BAT.
6. Edit the file.
7. Save your changes and exit the editor.
8. Restart your computer to implement the changes.
NOTE: If your files use upper ASCII or extended ASCII
characters, you might want to use an editor other than
Notepad, which uses only the Windows code page.
2.13 Running Setup from the GUI Login
If you are running Setup from the GUI Login, do not use
the pound sign (#) in the login script because it causes
the workstation to hang if the client version is already
up to date.
For example: #SETUP
Instead, use the at (@) sign
For example: @SETUP
For more detailed information on running Setup from a
login script, refer to the IntranetWare Client for DOS
and Windows 3.1x Supervisor Guide in Dynatext or HTML
format.
2.14 TCP/IP Not Installed by Default Even When Workstation
Currently Has TCP/IP Loaded
During the Windows 3.1x install, users are asked if they
want to access the Internet or use an application that
requires TCPIP. The default is NO even if TCP/IP is
currently installed on the workstation. If TCP/IP is to
be installed, users must either select YES or install
NetWare IP (or another option that requires TCPIP).
2.15 SLOT Parameter Not Inserted during Setup.
Most 32-bit drivers support the SLOT parameter used when
loading on a Novell server. This parameter is not
required when loading on a client workstation and will
not be inserted during Setup. If you have a driver that
requires this parameter, you must manually add the line
to your STARTNET.BAT file.
2.16 IBM Thinkpad 755 CD Prompted to Enter the Interrupt for
the LAN Adapter
After installing IntranetWare Client for DOS and Windows
3.1x on an IBM Thinkpad 755 CD with Windows 3.1, IBM DOS
v.7.0, and a 32-bit 3Com 3C589.LAN driver, and then
restarting the workstation, the user is prompted to enter
the interrupt (IRQ) for the LAN adapter. This occurs
because the 32-bit 3Com 3C589.LAN driver cannot load and
the workstation cannot find a file server.
To resolve this, complete the following steps:
1. In the CONFIG.SYS file, add the following two lines
to Enable PC (PCMCIA) card services and run 3COM
3C589MGR.EXE before loading 3C589.LAN:
DEVICEHIGH=C:\THINKPAD\IBMDSS01.SYS /D
DEVICEHIGH=C:\THINKPAD\IBMDOSCS.SYS
2. In the STARTNET.BAT or AUTOEXEC.BAT file, add the
following line:
3C589MGR.EXE
3. Edit the STARTNET.BAT file and add the slot number
of the card.
For example: slot=2
3.0 General Issues
3.1 Get Current Directory Fails on Directories with Only DOS
Name Space
Directories on volumes that have ONLY the DOS name space
cannot have a combined path length greater than 64
characters. If the directory path has more than 64
characters, Get Current Directory fails and regresses
the path until it finds a directory with a path length of
64 characters or less. This is not an issue for volumes
that have the long name space.
3.2 NDSManager v1.06 Hangs Workstation When Using the Create
Alias Feature
NDSManager v1.06 might hang the client workstation if
Create Alias is used to move a partition. To resolve
this problem, upgrade to the latest version of NDSManager
(v1.24) included in Support Pack 3.0.
3.3 Printing to a Volume with Insufficient Space
When you print a large file to a volume with insufficient
space, the IntranetWare Client gives an error which might
hang the computer. This occurs because the IntranetWare
Client cannot retry printing because the volume is out of
the disk space and it cannot delete the print job because
it thinks that important data will be lost. To resolve
this problem, make sure that you have sufficient disk
space before you start printing a large file.
4.0 International Issues
This CD-ROM is an English-only version of the IntranetWare
Client. The IntranetWare Client software and help files, as
well as DynaText documentation files, will be translated into
Portuguese, French, Italian, German, and Spanish for the
international release of the IntranetWare Client CD-ROM.
5.0 Trademarks
5.1 Novell Trademarks
Novell and NetWare are registered trademarks of Novell,
Inc. in the United States and other countries.
IntranetWare Client, Internetwork Packet Exchange and
IPX, NetWare/IP, IntranetWare Client, Sequenced Packet
Exchange, and Virtual Loadable Module and VLM are
trademarks of Novell, Inc.
5.2 Third-Party Trademarks
3Com is a registered trademark of 3Com Corporation.
DynaText is a registered trademark of Electronic Book
Technologies, Inc. IBM is a registered trademark and
ThinkPad is a trademark of International Business
Machines Corporation. Windows is a registered trademark
of Microsoft Corporation.
6.0 Disclaimer, Copyright, Export Notice, Patents
Novell, Inc., makes no representations or warranties with
respect to any software, and specifically disclaims any
express or implied warranties of merchantability, title, or
fitness for a particular purpose. Distribution of any Novell
software is forbidden without the express written consent of
Novell, Inc. Further, Novell reserves the right to discontinue
distribution of any Novell 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.
Copyright (C)1993-1994, 1995-1997 Novell, Inc. All rights
reserved.
This product may not be exported outside the U.S. or Canada
without prior authorization from the U.S. Department of
Commerce.
U.S. Patent Nos. 5,157,663; 5,349,642; and 5,455,932. U.S.
Patent Application No. 5,572,528. U.S. and International
Patents Pending.
