NETWARE DOS/WINDOWS 

               WORKSTATION UPDATE





                May 1990 Edition

                  Revision 1.0

      For NetWare DOS Client Version 3.01 









              Novell, Incorporated
               122 East 1700 South
                  P.O. Box 5900
             Provo, Utah  84606  USA

    þ   Copyright 1990 Novell, Inc.  All rights
    reserved.  No part of this publication may be
    reproduced, photocopied, stored on a retrieval
    system, or transmitted without the express prior
    written consent of the publisher.


          Novell Part # 100-000821-001Disclaimer

Novell, Inc. makes no representations or warranties with respect to the contents or use of
this manual, and specifically disclaims any express or implied warranties of merchantability
or fitness for any particular purpose.  Further, Novell, Inc. reserves the right to revise this
publication and to make changes to its content, at any time, without obligation to notify
any person or entity of such revisions or changes.

Further, Novell, Inc. makes no representations or warranties with respect to any NetWare
software, and specifically disclaims any express or implied warranties of merchantability or
fitness for any particular purpose.  Further, Novell, Inc. reserves the right to make changes
to any and all parts of NetWare software, at any time, without obligation to notify any
person or entity of such changes.


FCC warning

Computing devices and peripherals manufactured by Novell generate, use, and can radiate
radio frequency energy, and if not installed and used in accordance with the instructions in
this manual, may cause interference to radio communications.  Such equipment has been
tested and found to comply with the limits for a Class A computing device pursuant to
Subpart J of Part 15 of FCC Rules, which are designed to provide reasonable protection
against radio interference when operated in a commercial environment.  Operation of this
equipment in a residential area is likely to cause interference, in which case the user---at his
own expense---will be required to take whatever measures are necessary to correct the
interference.

Some components may not have been manufactured by Novell, Inc.  If not, Novell has
been advised by the manufacturer of the component that the component has been tested
and complies with the Class A computing device limits as described above.


Trademarks

Novell, Inc., has made every effort to supply trademark information about company names,
products, and services mentioned in this book.  Trademarks indicated below were derived
from various sources.

IBM is a registered trademark of International Business Machines Corporation.
Internetwork Packet Exchange (IPX) is a trademark of Novell, Inc.
Microsoft is a registered trademark of MicrosoftCorporation.
NetWare and Novell are registered trademarks of Novell, Inc.
Windows is a trademark of Microsoft Corporation.
þ Copyright 1990 Novell, Inc.  All rights reserved.  No part of this
publication may be reproduced, photocopied, stored on a retrieval system, or
transmitted without the express prior written consent of the publisher.

Novell, Incorporated
122 East 1700 South
Provo, Utah  84606  USA

NetWare DOS/Windows Workstation
Update

The NetWare DOS Client software allows a DOS
workstation to communicate with a NetWare file
server and other workstations.

This version of the NetWare DOS shell is compatible
with NetWare v2.1x and above.  

This booklet provides instructions on how to install a
new version of the DOS shell on your workstations
along with a brief description of each of the new
features supported.

Installation                              3

New Features

   Microsoftþ Windowsþ v3.0 Support      11

   Modified NetWare utilities            15

   Preferred server and other
   shell configuration parameters        17

   Extended Memory Support               21

   Expanded Memory Support               23

   DOS client parameters                 25
Your NetWare DOS/Windows Workstation Update kit                 2
includes three 3.5" high-density (HD) diskettes and
three 5.25" HD diskettes containing the following
files:

   IPX.OBJ  
   NETx.COM 
   XMSNETx.EXE
   EMSNETx.EXE
   NETBIOS.EXE
   SHGEN.EXE
   NetWare utilities (modified for fake root)

The diskettes also contain files necessary for running
the SHGEN utility.

IPX.COM contains the IPX/SPX protocol that is
linked to a LAN driver and manages communications
among the network stations.  Use the new IPX.OBJ
file with the simplified SHGEN program to generate
the IPX.COM file.  

The shell file redirects messages from the
workstation to the file server.  The shell can be one
of the following:

þ  NETx.COM for all workstations using
   conventional memory

þ  EMSNETx.EXE for workstations with expanded
   memory

þ  XMSNETx.EXE for workstations with extended
   memory 

The x in the shell file name refers to the DOS
version that runs on your workstations.  

The NetWare utilities included in this kit have been
modified to support fake roots.  Some applications
including Microsoft Windows require fake roots in
order to function properly.
Installation                                                   3

We assume you are updating shell files on existing
machines and have already installed the appropriate
network boards in your workstations.    

If you will be using the extended or expanded
memory shell, you need to install the appropriate
memory boards and software.  The extended and
expanded memory shells are not intended for use on
a machine running non-dedicated NetWare.

If you are using extended memory, install a third-
party memory manager such as HIMEM.SYS.  If you
are using expanded memory, load an EMS-
compatible driver.

The SHGEN.EXE program generates the IPX.COM
file.  Workstations running the SHGEN.EXE
program must meet the following minimum
requirements:

þ  640KB of memory

þ  DOS 3.0 or above

þ  High-capacity diskette drive

You can run SHGEN from the workstation's hard
disk, a network drive, or a diskette to generate
IPX.COM.  However, if you are generating IPX.COM
for several workstation configurations, we recommend
you use the hard disk or the network drive methods. 


        Use the hard disk or the network drive method if
        you are generating IPX.COM for diskless
        workstations.


Run SHGEN                                                      4

1.  Use the new SHGEN.EXE utility.

If you are running SHGEN from your hard disk or
network drive, copy the files from the DOS
WORKSTATION diskette included in this kit into
the SHGEN-1 directory on your hard disk.

If you are running SHGEN from a floppy diskette,
insert the DOS WORKSTATION diskette into drive
A.

2.  Change to the drive containing SHGEN.EXE.
 
3.  Type SHGEN. 

   SHGEN  <Enter>

A menu similar to the following appears:

                Selected LAN Driver       
                LAN Driver Options        

        Select LAN driver from list         
        Load into list from LAN_DRV ??? DISK



4.  Select an option from the "LAN Driver Options" menu.

  For       Choose        Complete                        

  Common    "Select LAN      Select a LAN driver to match 
  NetWare   driver from      the network board.           
  boards    list"                                         

  Boards    "Load into    1. Insert the LAN_DRV ???       
  not on    list from        diskette into drive A.       
  SHGEN     LAN_DRV ???   2. Select a LAN driver to match 
  list      disk"            the network board.           

                                                               5
Note:  If a driver on your LAN_DRV ??? diskette is the
same as one of the drivers already listed in SHGEN,
you may get a message asking if you want to replace
"Driver 1" with "Driver 2."

The six-digit code found in parentheses at the end of
the Driver title represents the year, month, and day
the driver was updated.  


  If Driver 2 is...     Select 

  Newer than Driver 1   Yes    

  Older than Driver 1   No     




5.  Select the LAN driver configuration option for the network
    board.

Choose the same configuration option for the
workstation files that you set on the network board. 
See your network board installation supplement for
more information.


Note:  The option screen may read "Self Configured."  If it
does, IPX.COM will automatically adapt to the
settings on your network board.


Record the LAN driver configuration for the
IPX.COM file that you have generated.


6.  Select "Yes" to save your selections.


  If selections are     Select 

  Correct               Yes    

  Incorrect             No    


Create the master workstation diskette                         6

The master workstation diskette is a copy of the files
to boot one type of workstation.  You will copy these
files to individual workstation boot diskettes.  

1.  Copy the workstation files to the master workstation diskette.

Depending on the method you used, the workstation
files are located in


  Method                 Location          

  Diskette               DOS WORKSTATION   
                         Diskette         

  Hard disk/network      SHGEN-1 directory 


1a.  If you haven't already, create system diskettes by
formatting them using the /s parameter.  


Note:  Format these diskettes using the correct version of
DOS registered for each workstation on the network.


1b.  If you received software with your network board
(the DXMAID program for Token-Ring network
boards, for example), see the installation supplement
for steps to configure or install this software.

1c.  Depending on your workstation configuration, copy
the following workstation files to the master
workstation diskette:


  Configuration            Files needed     

  Expanded memory          IPX.COM          
  (LIM 4.0 EMS             EMSNETx.EXE      
  compatible)             (+ EMS driver)   

  Extended memory          IPX.COM          
  (XMS 2.0 compatible)     XMSNETx.EXE      
                           (+ XMS memory    
                              manager)       

  Workstations using       IPX.COM           
  conventional memory      NETx.COM         

The x in NETx.COM refers to the DOS version that
runs on your workstations.  
                                                                7
1d.  Copy other executable files for customizing the boot
procedure and operating system. 
 

  If                   Copy                   

  Workstations use     NETBIOS.EXE 
  NETBIOS              INT2F.COM

  Workstations are     ROUTE.COM1              
  on a Token-Ring      TOKEN.COM              
  network with         TRN.COM                
  IBM routers                                 

  Workstations use     those files to         
  additional           the master             
  software to boot     workstation diskette   


1e.  If your workstation needs a configuration change to
make some network applications perform better,
create a SHELL.CFG file using any DOS text editor
(optional).  

For information and options, see the Shell
Configuration File options in your NetWare manual
set.  Additional options, including the preferred
server option, are also documented on page 17 of
this booklet.

1f.  Create any additional boot files for the master
workstation diskette using a DOS text editor
(optional).

þ  AUTOEXEC.BAT 

þ  CONFIG.SYS 

Copy the EMS-compatible driver (for expanded
memory) or the XMS memory manager (for extended
memory) to the CONFIG.SYS file.  

1g.  Label the master workstation diskette.

Label the master workstation diskette with a name,
such as "Master Workstation NE2000," and list the
LAN driver and configuration option on the label.
2.  Run ECONFIG (optional).                                     8

You must run ECONFIG if your workstation is
attached to an Ethernet cable that uses an Ethernet
frame format other than the 802.3 standard.  For
example,

þ  Your NetWare configuration shares the same
   Ethernet cabling with other systems (such as
   VAX);

þ  You use an Ethernet II topology.

For instructions on running ECONFIG, see the
documentation in your NetWare manual set.


Create the workstation boot diskette


1.  Copy the master workstation diskette files to each workstation
    boot diskette.


   If booting from             Then                       

   Floppy                      Copy files to formatted     
                               boot diskette (/s)          

   Hard disk                   Copy files to root directory
                               (C:\)                       

   Remote Boot image files     Copy files to formatted     
   on the file server          boot diskette (/s)          


2.  Personalize the user's boot diskette with executable files, and
    update AUTOEXEC.BAT (optional).

If the owner of the boot diskette wants any other
commands executed or programs loaded during the
boot process, add those files to the boot diskette and
make appropriate changes to the AUTOEXEC.BAT
file.
3.  Label the workstation boot diskette (optional).            9

Label boot diskettes with the workstation's name and
owner, the LAN driver, the configuration option, and
the custom boot files included.  This information
helps prevent the boot diskette from getting lost.

4.  Record the boot file information.

Keep a copy of the boot file information for
troubleshooting purposes.

5.  Repeat Steps 1 through 4 for each workstation.

6.  Run DOSGEN (optional).

Documentation for creating the Remote Boot image
file on the file server for diskless workstations is in
your NetWare manual set.


Boot the workstation and log in to the file server

If your AUTOEXEC.BAT file does not contain any
network commands, type

   IPX  <Enter>

   [EMS/XMS]NETx  <Enter>

   F:  <Enter>

   LOGIN SUPERVISOR  <Enter>               
Copy NetWare utilities on to the file server                  10

The NetWare utilities provided with this update kit
have been modified to support fake roots.  These
utilities are necessary to run certain applications
such as Microsoft Windows.

If you have NetWare 386 or NetWare 286, copy the
following utilities and their corresponding help files
from the UTILITIES-1 and UTILITIES-2  diskettes
to SYS:PUBLIC and SYS:LOGIN.
   
SYS:PUBLIC      CAPTURE.EXE
                FILER.EXE
                FLAG.EXE
                FLAGDIR.EXE
                GRANT.EXE                  
                LOGIN.EXE
                MAKEUSER.EXE
                MAP.EXE
                NCOPY.EXE
                NDIR.EXE
                NPRINT.EXE
                PRINTDEF.EXE
                REMOVE.EXE
                REVOKE.EXE
                RIGHTS.EXE
                SESSION.EXE
                TLIST.EXE

SYS:LOGIN       LOGIN.EXE

In addition, if you have NetWare 286, copy the
BINDFIX utility from the UTILITIES-1 diskette into
the SYS:SYSTEM directory.

SYS:SYSTEM      BINDFIX.EXE                


        Do not copy the BINDFIX utility if you have
        NetWare 386.



New Features                                                  11

The following pages explain the new features
supported in this version of the DOS client software.


Microsoft Windows v3.0 Support

Install Microsoft Windows v3.0 using the instructions
that came with the Windows package.


Note:  Windows will be properly configured to the network
if the shell is generated and loaded first.  


Windows v3.0 builds the NETWARE.INI file.
The NETWARE.INI file tells the NetWare driver
what commands are available under the Network
icon in the Windows Control Panel.  

The default commands are Attach, Detach, Disable
Broadcast Messages, and Enable Broadcast Messages. 

Instructions for modifying the NETWARE.INI file
can be found in the next section.
                         
NETWARE.HLP file contains help information to be
used in the Windows help system.


Modifying the NETWARE.INI file

The NETWARE.INI file can be modified using any
text editor.  It may be easier to use the Notepad
application since it is included with the Windows
package.                                                      12
Any application, command, or utility that runs under
Windows can be added to the NETWARE.INI file.  

The file header must not be changed.  It must
appear before the command lines.  Below is an
example of a modified NETWARE.INI file.

   [MSW30-Utils]

   Attach A File Server=<Attach
   Detach A File Server=<Detach
   Disable Broadcast Messages=<No Messages
   Enable Broadcast Messages=<Messages
   A Game of Dots=REVERSI.EXE
   Show Your Timepiece=CLOCK

The first four commands are default commands as
indicated by the less than sign (<) preceding the
command.

There are several rules for modifying the
NETWARE.INI file:

þ  The command line includes the title of the
   command that will appear in the Network
   Utilities dialogue when the Network icon is
   opened.  To the right of the command title an
   equals sign (=) and the name of the executable
   file for the appropriate program or command.  

þ  The total length of all the titles cannot exceed
   512 characters.

þ  The total number of characters after the "=" for
   each command line cannot exceed 128.


NetWare Utilities support

Windows support provided by Novell is intended to
support the use of the Windows environment and
Windows-based applications on a NetWare network. 
Because Windows takes control of the system, any
utilities not specifically written for the Windows
environment may not function correctly.  
Therefore, when using the NetWare utilities provided          13
with the operating system, be aware that they may
not function properly under Windows.  For best
results, create a PIF file for the utility that you
would like to use, and run the utility as a PIF.


Creating a PIF file

To create a PIF file, complete the following steps.

1. Copy the NETWARE.PIF file from the
   UTILITIES-1 diskette to the Windows directory. 
   This file is a sample file you can use to create
   your PIF files.

2. Execute the PIF editor from the Program
   Manager window.

3. Open the NETWARE.PIF file.

4. Change the program filename to the name of the
   utility you want to create a PIF file for.  For
   example, if you wanted to create a PIF file for
   the CAPTURE command, type CAPTURE.EXE.

5. Save the file using the NetWare utility name
   with a PIF extension.  For example, for the
   CAPTURE command, type CAPTURE.PIF when
   prompted for the new filename in the Save As
   window.

6. Exit the NETWARE.PIF file without saving
   changes so you do not overwrite the sample file.

You can repeat these steps for each NetWare utility
you want to create a PIF file for.

To run the NetWare utility, run the PIF file from
the File Run menu.
Login and the Windows environment                             14


        Do not use LOGIN or LOGOUT while in the
        Windows environment.  Log in before you start
        Windows and log out after you exit Windows.


If you do not want to manually log in before you
start Windows each time you boot your machine, you
can edit and use the AUTOEXEC.BAT file included
in this kit.  

The AUTOEXEC.BAT file contains the following
commands:

   IPX
   NET3
   F:LOGIN <servername/username>
   WIN  
   LOGOUT

You can modify these commands according to your
environment.  

If you want users to be able to edit their login
scripts from within the Windows environment, you
may want to map a drive to their mail directory.  To
map a drive to each user's mail directory, include
the following line in the system login script:

MAP F:=SYS:MAIL\%user_id

Once a drive is mapped to the appropriate directory,
a user can use Notepad to modify the login script.  

If a drive mapping is not used, users will need to
know their user IDs to select the proper mail
subdirectory.

Modified NetWare utilities                                    15

The NetWare utilities provided with this update kit
have been modified to support fake roots.  Fake
roots are necessary to run some applications, such as
Microsoft Windows.  

You must also use these utilities to use the SHOW
DOTS parameter explained in the next section.    


        The functionality of the NetWare utilities is limited
        in the Windows environment.  Do not use LOGIN or
        LOGOUT while in the Windows environment.  Log
        in before you start Windows and log out after you
        exit Windows.


The fake roots feature has been added to simulate
the DOS SUBST command.  Fake roots effectively
set the root of a given drive to a directory
designated by the user instead of to the volume.

Some applications require files to be read from and
written to the root directory.  If, in setting up your
directory structure, you have restricted users' rights
at the volume level, you must create a fake root
directory that the application can recognize.   

You can create this fake root directory by mapping a
fake root drive to a directory where the user has
rights.  Use the MAP command included in this kit
to map a drive to a fake root directory.

For example, suppose you have set up your directory
structure as follows:

SYS: PUBLIC
     SYSTEM
     LOGIN
     MAIL
     HOME  ANDY
           PAM
           TIM

User PAM wants to run an application that requires            16
access to a root directory.  You have given user Pam
all rights to her home directory.  In addition, you
have mapped drive F to SYS:HOME\PAM.  

You do not want to give user PAM rights to the SYS
volume, so you map a fake root drive to her home
directory by typing

   MAP ROOT F:=HOME\PAM <Enter>

If you are using the default file server and volume,
you don't need to include the file server and volume
name in the command.  To map to a file server
other than your default, include the servername and
volume in the command.

When you type MAP, you see a double space and
backslash after PAM, indicating that the root
directory for drive F is now PAM:

   F:=servername\SYS:HOME\PAM  \

User PAM will now be able to use the application in
question because she has rights to a directory the
application recognizes as a root directory.  

To change the root directory back to the volume
level, type

   MAP F:=SYS:\HOME\PAM

When you type MAP, you see a double space and
slash after SYS: indicating that the root directory for
drive F has been returned to the SYS volume.

   F:=servername\SYS:  \HOME\PAM

You can create a different fake root directory for
each drive mapping.  


Preferred server and other shell configuration parameters     17

The NetWare shell is responsible for many routines
and processes in a network workstation.  Shell
parameters can be changed to modify the way the
shell interacts with those routines and processes.  To
change the shell's reactions, modify the parameters
found in the SHELL.CFG file.  

The preferred server parameter allows you to
indicate which server you would like the shell to
attach to. 

The shell configuration parameters are documented
in your NetWare manual set.  In addition to the
existing shell configuration parameters, the following
parameters can now be used:


Parameter         Maximum  Minimum  Default 
     
All Servers       On       Off      Off
Entry Stack Size  40       5        10
Max Cur Dir Length255      64       64
Max Path Length   255      64       255
Preferred Server  None     None     None
Set Station Time  On       Off      On
Show Dots         On       Off      Off
Special Upper CaseOn       Off      Off

ALL SERVERS                                                   18

Determines whether the "End of Task" is sent to all
connected servers or only those servers interacting
with the task.  When turned on, it will send "End of
Task" to all connected servers.  When turned off, it
will send "End of Task" only to those servers the
task has interacted with.

Default:  ALL SERVERS = OFF


ENTRY STACK SIZE

Sets the number of times you can reenter the
NetWare Expanded Memory shell.  If you reenter the
shell from a program that is already in expanded
memory, you run the risk of hanging the machine. 
The maximum is 40.

Default:  ENTRY STACK SIZE = 10


MAX CUR DIR LENGTH

DOS defines the "Get Current Directory" call to
return 64 bytes of path.  In the past, the shell has
allowed 128 bytes to be returned.  To provide
compatibility both ways, this parameter is now
configurable.  The numeric range is from 64 to 255. 
Some applications including Windows may have
problems with path names greater than 64
characters.

Default:  MAX CUR DIR LENGTH = 64


MAX PATH LENGTH

DOS defines a valid ASCII string as 128 bytes, but
that may be insufficient for some network paths. 
This parameter can be changed to allow users to
have paths from 64 to 255 characters.  Some
applications including Windows may have problems
with path names greater than 64 characters.  This
path does not include file or server names.

Default:  MAX PATH LENGTH = 255
PREFERRED SERVER                                               19

Allows the user to specify a preferred server
connection.  When you specify a preferred server,
PREFERRED SERVER = servername, the shell
attempts to establish its first connection to the
server specified rather than just the first server that
responds.

The shell also polls up to five different server
connections before returning the message "Server has
no available slots."  If the shell was unable to
establish a connection with the server specified, it
will attempt to make a connection to one of the
other five servers.

The preferred server parameter does not affect how a
diskless workstation attaches to a file server from
the boot ROM.  

Default:  No preferred server 


SET STATION TIME

Allows user to turn off the updating of the
workstation's time when the shell loads.  With this
option on, the shell will synchronize the
workstation's time with that of the server it attaches
to. 

Default:  SET STATION TIME = ON


SHOW DOTS

Since the NetWare file server does not have
directory entries for "." and ".." as DOS does, the
shell must emulate these entries on
FindFirstMatching and FindNextMatching DOS calls. 

Some applications including Windows use these
entries to allow a mouse to select these entries and
change directories.  Set SHOW DOTS to "ON" if you
plan to such applications. 

Default:  SHOW DOTS = OFF
SPECIAL UPPERCASE                                              20

Determines how the shell translates ASCII
characters above 127 into uppercase characters. 
With this option off, no translation is performed on
these characters.  With this option on, the shell
makes a request of the resident DOS to do the
translation.

Default:  SPECIAL UPPERCASE = OFF

Extended Memory Support                                       21

Extended memory refers to memory above the 1MB
range.  Up to 15MB of extended memory are
addressable.  

The NetWare Extended Memory shell moves most of
the shell out of conventional DOS memory and puts
it in extended memory.  This frees up 34KB of
conventional memory.  6KB of the extended memory
shell must remain in conventional memory to handle
interrupts and some data.   

The extended memory shell requires the support of
an XMS (Extended Memory Specification) v2.0
memory manager (or compatible) such as Microsoft's
HIMEM.SYS.  The memory manager makes the first
64KB (beginning at the 1MB address) of extended
memory directly available to DOS-based applications.














To install the NetWare Extended Memory shell,                 22
complete the following steps:

1. Install a third-party extended memory manager.  
    
2. Copy the NetWare Extended Memory shell,
   XMSNETx.EXE, to the workstation boot disk.

3. Include the filename XMSNETx.EXE in the
   AUTOEXEC.BAT file (x represents the version of
   DOS you are using).

Because the Extended Memory Shell operates in
extended memory, larger applications can run in the
conventional memory space.  This approach is faster
than disk swapping and overlays.  

The NetWare Extended Memory shell works with all
versions of NetWare v2.1x and above.   

All the shell configuration (SHELL.CFG) parameters
work with the NetWare Extended Memory shell.  


        XMSNETx.EXE can be used only with DOS 3.0 and
        above.  The current VDISK.SYS from IBM is not
        compatible with HIMEM.SYS, so do not use the
        extended memory shell with VDISK.SYS.  Do not
        use the extended memory shell on a machine
        running non-dedicated NetWare. 


This shell requires a high degree of IBM
compatibility.  Depending on the brand of IBM
compatible you are using, you may experience
keyboard sluggishness or other hardware problems.

Expanded Memory Support                                       23

Expanded memory refers to memory in addition to
the 640KB limit of conventional memory.  An
expanded memory manager swaps memory that
exists above the 1MB range into a window, or
memory page, below the 1MB range.  This allows
DOS applications to access up to 32MB of expanded
memory.  

The NetWare Expanded Memory shell moves most of
the shell out of conventional DOS memory and puts
it in expanded memory.  This frees up 33KB of
memory.  The remaining 7KB of the shell must
remain in conventional memory to handle interrupts
and some data.  

The NetWare Expanded Memory shell was written to
the specifications of LIM/EMS (Lotus/Intel/Microsoft
Expanded Memory Specification) v4.0 memory
manager.


Expanded memory manufacturers provide Expanded                24
Memory Specification (EMS)-compatible driver
programs.  You must load an EMS-compatible driver
before loading the NetWare Expanded Memory shell.

To install the NetWare Expanded Memory shell,
complete the following steps:

1. Load third-party EMS-compatible driver.

2. Copy the EMSNETx.EXE file to the workstation
   boot diskette. 

3. Include the filename EMSNETx.EXE in the
   AUTOEXEC.BAT file.

Because the Expanded Memory Shell operates in
expanded memory, larger applications can run in the
conventional memory space.  This approach is faster
than disk swapping and overlays.  

The NetWare Expanded Memory shell works with
NetWare v2.1 and above.

All the shell configuration (SHELL.CFG) parameters
work with the NetWare Expanded Memory shell.  


        EMSNETx.EXE can only be used with DOS 3.0 and
        above.  The expanded memory shell is not designed
        to work on a machine running non-dedicated
        NetWare.
DOS client parameters                                         25

The DOS client software now contains command line
parameters that allow you to unload or modify
configuration.  Each of the DOS client parameters
are described below.

IPX

Use the IPX options to 

þ  View information about the version of IPX.COM
   installed on your workstation;

þ  View the available hardware configuration
   options for your workstation;  

þ  Change the configuration option number for the
   network driver.

New parameters

   IPX [I] | [D] | [Ox]

Use the [I] option to view Information about a
specific IPX.COM file.  This option shows how IPX
would be configured if you loaded that IPX file.

Use the [D] option to Display the available hardware
configuration options for the network board.  The þDþ
option places an asterisk (*) by the current option.


Note:  Typing "IPX I" at the command line will not load
IPX.


Use the [Ox] option to change the configuration
Option number for the network driver without
having to use DCONFIG or rerun SHGEN.  

This option will override the configuration option
currently in memory.  It does not permanently
modify the IPX program.  To permanently modify the
hardware configuration option in IPX, use the
DCONFIG utility.
For example, suppose you have NE1000 boards in                 26
two workstations.  The network board in workstation
A is set to option 5.  The network board in
workstation B is set to option 0.  

If you have an IPX file that has been configured to
run with an NE1000 board, you can use the option
parameter to change the option as it is loaded. 

To allow IPX to use option 5 on workstation A, type

   IPX O5  <Enter>

To allow IPX to use option 0 in workstation B, type

   IPX O0  <Enter>


NetBIOS

Use the NetBIOS command line parameters to 

þ  View the NetWare NetBIOS version information; 

þ  View whether NetBIOS has been loaded; 

þ  View which interrupts are currently in use;  

þ  Unload NetBIOS.


New parameters

   NETBIOS [I] | [U]


Use the [I] option to view version information,
whether NetBIOS has been loaded, and the
interrupts it is using.


Note:  Typing "NetBIOS I" at the command line will not
load NetBIOS.

When you execute NetBIOS I, you see a screen                  27
similar to the following.

Novell Network BIOS Emulator v3.01 Rev A
(C) Copyright 1990 Novell, Inc.  All rights reserved.
Novell NetBIOS interface (interrupt 5Ch) loaded.
Novell NetBIOS alternate interface (interrupt 2Ah)
loaded.

Use the [U] option to unload NetBIOS.  Using this
option frees up the memory used by NetBIOS,
restores the interrupts that NetBIOS was using, and
cancels all NetBIOS activity for that workstation.

When you execute NetBIOS U, you see a screen
similar to the following.

Restored interrupt 2Ah handler successfully.
Restored interrupt 5Ch handler successfully.
Restored interrupt 2Fh handler successfully.
NetBIOS unloaded from memory successfully.


Note:  The unload option will unload only NetBIOS v3.01.
It will not successfully unload previous NetBIOS
emulator versions.  You cannot unload NetBIOS if
other TSR programs have been loaded after
NetBIOS.



[EMS,XMS]NETx

Use the [EMS,XMS]NETx parameters to view the
version of the NetWare shell, unload the shell, or
specify a preferred server.  


New parameters

   [EMS,XMS]NETx [I] | [U] | [PS = server name]

Use the [I] option to view the version of the
NetWare shell.
When you execute this option, you see a screen                28
similar to the following.

NetWare V3.01 rev.A - Workstation shell for PC DOS V3.x
(C) Copyright 1983, 1988 Novell, Inc.  All rights
reserved.

Use the [U] option to unload the NetWare shell.

When you execute NET3 U, you see a screen similar
to the following.

You are being logged out of all servers . . .
Memory for resident shell has been released.
The NetWare shell has been unloaded.


Note:  The unload option will unload only the v3.01 shell
files. It will not successfully unload previous
versions.  You cannot unload the shell files if other
TSR programs have been loaded after the shell files.


Use the [PS] option to set the server you will attach
to.  With this parameter set, the shell polls up to
five servers for the first available connection; then it
attaches to the server specified in the parameter.  

The command line parameters override the
configuration file parameters.