You need to choose between the two ways a user can start NetWare
Connectivity:
The user can use the nwload
command to start NetWare Connectivity, and then use nwunload
to unload it when finished using it.
Choose this method if you want the user to be able to unload
NetWare when not using it, so that NetWare occupies memory only
while being used. If you choose this method, tell the user to load
and unload NetWare with nwload and nwunload. Make sure the user
knows that the Windows operating system must not be running when
they issue the nwload or nwunload
command. If you want, you can add nwload to the AUTOEXEC.BAT file
to have NetWare start when the computer starts.
If the net start workstation command
appears in AUTOEXEC.BAT, add the nwload command
after it. If a command in AUTOEXEC.BAT starts the Windows operating
system, add the nwload command before it.
If you need to add nwload to AUTOEXEC.BAT,
but it is not the last command in the file, use call
nwload instead. The call command
ensures that the rest of AUTOEXEC.BAT will run after nwload
runs. For more information, see your MS-DOS manual(s).
The user can start IPX.COM and NETx.COM, NETX.COM,
or NETX.EXE directly, as on a NetWare-only workstation.
Choose this method if the workstation has enough memory to
run both LAN Manager and NetWare all the time, and the
user will want both running all the time. This method also lets
experienced NetWare users start NetWare using the commands they
are accustomed to.
You can put the ipx and netx
commands into the workstation's AUTOEXEC.BAT file. If the
net start workstation command appears in
AUTOEXEC.BAT, add the ipx and netx
commands after it. If a command in AUTOEXEC.BAT starts the Windows
operating system, add the ipx and netx
commands before it.
Note that NetWare cannot be started with either method while
the Windows operating system is running. To start NetWare, the user
must first exit the Windows operating system.
The information about NetWare Connectivity in the LAN Manager
user documentation for MS-DOS assumes that nwload
and nwunload will be used. If this is not
the case, explain to the users how to start and stop NetWare Connectivity.
The following sections give more information about each way
of starting NetWare Connectivity.
Using NWLOAD to Run NetWare Connectivity |
 |
The nwload command starts the NWLOAD.BAT
file, which starts the NDIS-compliant version of IPX.COM, and the
NetWare shell (the netx program), and logs
the user into a NetWare server using NetWare's login
utility.
If the user wants NetWare Connectivity to start when the workstation
starts, you can add nwload to the end of
the workstation's AUTOEXEC.BAT file. If the net
start workstation command appears in AUTOEXEC.BAT, make
sure that the nwload command appears after
it. If a command in AUTOEXEC.BAT starts the Windows operating system,
add the nwload command before it.
If you need to add nwload to AUTOEXEC.BAT, but it is not the
last command in the file, use call nwload
instead. The call command ensures that the
rest of AUTOEXEC.BAT will run after nwload
runs. For more information, see your MS-DOS manual(s).
If necessary, a workstation user could also start NetWare
on the workstation without LAN Manager running by typing
either nwload or the combination of the ipx
and netx commands.
Using NETX.COM and NETX.EXE
NETX.COM and NETX.EXE are versions of the NetWare shell that
run on any version of MS-DOS. A NetWare workstation can run NETX.COM
or NETX.EXE instead of NET3.COM, NET4.COM, or NET5.COM. NetWare
Connectivity supports the use of NETX.COM and NETX.EXE.
If you want to use NETX.COM or NETX.EXE on a workstation and
have the user use the nwload and nwunload
commands to start and stop NetWare Connectivity, you need to modify
the NWLOAD.BAT and NWUNLOAD.BAT batch files.
Edit the NWLOAD.BAT file to remove rem from these two lines,
near the top of the file:
Edit the NWUNLOAD.BAT file to remove rem from these
two lines:
rem netx /u
rem goto IPXREL |
After you make these changes, the nwload
and nwunload commands will use NETX.COM or
NETX.EXE.
Using IPX and NETX Commands to Run NetWare Connectivity |
|
If the user will not need to unload NetWare Connectivity,
you can have the user start NetWare Connectivity in the same way
as a NetWare-only workstation, using the ipx
and netx commands. Or you can put these commands
in the AUTOEXEC.BAT file so that they will be run automatically
when the workstation starts. Add them toward the end of AUTOEXEC.BAT
but before commands that start the Windows operating system.
You can also load the IPXNDIS.DOS device driver in the CONFIG.SYS
file, then type ipx
to run the IPX protocol. This method of running IPX is not demand
loaded and occupies more memory.
You and the user should know an important difference between
starting NetWare on a NetWare Connectivity workstation and on a
NetWare-only workstation. The default network drive the NetWare
Connectivity user uses to log in to a NetWare server will probably
be different from that used on a NetWare-only workstation. With
a NetWare-only workstation, the login drive is usually the F drive.
With NetWare Connectivity, the drive will be the drive letter following
the drive letter set as the lastdrive in
the CONFIG.SYS file. The default (set when you install NetWare Connectivity)
for lastdrive is p;
in this case, the login drive must be the Q drive.
If you change lastdrive, use the appropriate
login drive instead of the Q drive. For more information about lastdrive,
see "Setting the LASTDRIVE Option," later in this
chapter.
If you put the login command in the
AUTOEXEC.BAT file, be sure to specify the correct drive letter.
If the user will type the login command,
be sure he or she knows which drive letter to use.
Using the Fixpath Utility |
|
NetWare Connectivity includes a fixpath
utility to ensure that a workstation's search path remains
correct when both LAN Manager and NetWare are loaded. A
problem occurs with the search path when NetWare is started on the
workstation and the NetWare login script creates search- drive connections
to NetWare servers, using commands such as the following:
This command not only creates the connection, but it also
alters the user's MS-DOS search path. Elements already
in the search path, such as the LANMAN.DOS\NETPROG directory,
may be deleted from the path.
The fixpath utility runs after the user logs on to a NetWare
server and has the login script run. The fixpath utility automatically
restores the path that was present before NetWare was started.
If you use the nwload utility to start NetWare, fixpath will
run automatically. However, if your LAN Manager directory
is not C:\LANMAN.DOS, you must first edit the NWLOAD.BAT
file (located in the NETPROG subdirectory of your LAN Manager
directory). Near the bottom of NWLOAD.BAT is the following line:
c:\lanman.dos\netprog\fixpath.exe |
Edit this line so that it shows the actual location of your
LAN Manager directory. For example, if your LAN Manager
directory is D:\NETWORK, edit this line so that it reads:
d:\network\netprog\fixpath.exe |
If you don't use nwload, you can still run fixpath
yourself after starting ipx and netx. To run fixpath yourself, type
its full path. For example, if your LAN Manager directory
is C:\LANMAN, type the following to run fixpath:
c:\lanman\netprog\fixpath |
Setting the LASTDRIVE Option |
|
On a workstation running both LAN Manager and NetWare
Connectivity, the two systems share the drive letters available
to be assigned to network directories. The letters up to and including
the letter specified as lastdrive in the
CONFIG.SYS file can be used for LAN Manager directories;
the letters following the lastdrive letter
can be used for NetWare directories.
|
| |
|
 | NOTE: If the workstation runs the Microsoft Windows
operating system, there is an exception to the drive letter restriction.
While using the Windows File Manager to make network connections,
the user can assign any drive letter (whether it is before or after
lastdrive) to NetWare directories, but will
be restricted to drive letters up to and including lastdrive
for LAN Manager directories. |
|
| |
|
When NetWare Connectivity is installed, it sets the lastdrive
entry in CONFIG.SYS to p. This provides about the same number of
drive letters for LAN Manager as for NetWare.
If a workstation user will need to connect to more than ten
LAN Manager or NetWare directories simultaneously, you
might want to change lastdrive. If the user
will connect to many LAN Manager directories, set lastdrive
to a letter closer to Z. If the user will connect to many NetWare
directories, choose a letter closer to A.
If you change lastdrive, and if the
user uses the nwload command to start NetWare
Connectivity, you must also edit the NWLOAD.BAT file. This is because
the NetWare login command in NWLOAD.BAT must
use the drive letter immediately following the drive letter set
as lastdrive.
The line you must edit looks like this:
Change it so that it uses the drive letter immediately following
the letter set as lastdrive. For example,
if you change lastdrive to u,
edit the NWLOAD.BAT line like this:
Also, if you change lastdrive on a
workstation that does not run the Windows operating system, be sure
to tell the user.
Printable version
