Following is a sample scenario using NetWare Connectivity:
The user has the LAN Manager workstation software running whenever
the computer is on, and starts NetWare Connectivity only to access
a file or printer on the NetWare network. (If the workstation also
runs the Windows operating system, the user should start NetWare
Connectivity before starting the Windows operating system.)
The user starts NetWare with the nwload
command. This command saves the current MS-DOS configuration, then
starts the NetWare workstation software. The IPX.COM command starts
the IPX protocol.
When NetWare Connectivity is running (and with the LAN Manager
workstation still running), the user can access resources on Windows
NT computers, LAN Manager servers and NetWare servers.
If the workstation has the Windows operating system, the user
can use it to connect to directories and printers on both types
of servers. If the workstation does not have the Windows operating
system, the user uses LAN Manager commands to communicate with Windows
NT computers and LAN Manager servers, and NetWare commands to communicate
with NetWare servers. When the user types a command, LAN Manager
processes the command if it is a Windows NT or LAN Manager command,
and NetWare processes the command if it is a NetWare command, as
shown in the following figure.
When finished with NetWare resources, the user can type nwunload
to stop NetWare and unload it from memory. The nwunload
command also restores the MS-DOS configuration that was saved when
NetWare started. The nwunload command cannot
be used when the Windows operating system is running on the workstation--the
user must stop the Windows operating system temporarily before unloading
NetWare.
When the user uses the nwload and nwunload
commands to run NetWare, the memory required by NetWare is used
only when NetWare is actually running. When NetWare is not running,
that memory is free to be used by applications.
A user of a workstation with NetWare Connectivity can bypass
nwload and nwunload
and can run IPX.COM and the NetWare shell directly. However, in
this case the NetWare software cannot be unloaded from memory until
the workstation is rebooted.
You may prefer this method if the workstation has enough memory
for running both LAN Manager and NetWare Connectivity constantly
and if you want the user to always be able to access Windows NT,
LAN Manager, and NetWare servers. This also lets experienced NetWare
users start NetWare with the same commands they always have used
on NetWare-only workstations.
Alternatively, the user can run the NetWare Connectivity software
without also running the LAN Manager workstation software.
Files Used by NetWare Connectivity |
 |
A workstation running LAN Manager with NetWare Connectivity
is a complete LAN Manager workstation; it has all the files typically
found on a LAN Manager workstation. It also has additional files
specific to NetWare Connectivity, including the following:
NETx.COM, NETX.COM or NETX.EXE
The NWLOAD.BAT and NWUNLOAD.BAT files are copied from the
distribution disks to the workstation's hard disk when
you install NetWare Connectivity.
The IPX.COM file is generated during the installation of NetWare
Connectivity, using files both from the LAN Manager distribution
disks and from your Novell NetWare distribution disks. When installing
NetWare Connectivity on several workstations, you may choose to
generate the IPX.COM file only on the first workstation, and then
copy it to your installation disks. This eliminates the step of
generating IPX.COM during each subsequent installation.
The NETx.COM, NETX.COM or NETX.EXE file comes from the NetWare
distribution disks and is copied to the hard disk when you install
NetWare Connectivity.
Printable version
