
 NetWare Lite 1.0  --  README file (09/12/91)
 --------------------------------------------
 ***************************************************************************
 ************ Print this file and save it for future reference. ************
 ***************************************************************************
      This file contains hints and suggested conventions for how NetWare
      Lite might be setup on a network and how it might be used. 



 Table of Contents
 -----------------
 1. Shared Resources
 2. Printing
 3. Network Applications
 4. Compatibility with the NetWare Shell
 5. SERVER optimization and functions
 6. Using CD-ROMs
 7. IPXODI
 8. Auxiliary NetWare Lite files
 9. Logging in after INSTALL
 10. Windows compatibility
 11. Documentation Errors (Errata)
 


 1. Shared Resources (Network Directories and Printers)
 ------------------------------------------------------

      Shared resources are those resources (Network Directories or Network
      Printers) that are shared with CLIENTs on a network.  We suggest that
      Network Directories and Printers be given descriptive names.  Good
      names for Network Directories might be: TURBOC, WORDPERFECT, GAMES,
      IBM_DOS_310 or PUBLIC.  Good names for Network Printers might be:
      LASERJET_II, EPSON_DOT.  Names that might not be good are CDRIVE,
      PRINTER1, PRINTER2.  These names provide no indication of what
      applications or what kind of printers are being made available.  You
      will notice that during NetWare Lite installation we create a CDRIVE
      Network Directory for you.  When you become familiar with the product
      this resource ought to be removed and one or more descriptive Network
      Directories created in its place.

 Assisting Floppy-based CLIENTs
      If there are workstations on the network that don't have hard disks
      then we suggest that NetWork Directories be set up to help those
      workstations.  A DOS shared Network Directory should be created so that
      workstations with no hard disks can load DOS commands from the network. 
      A Network Directory sharing IBM DOS version 3.10 (named IBM_DOS_310
      perhaps) would be useful for those CLIENTs with only floppy drives to
      get to their version of DOS.  In conjunction with this the DOS
      environment variable "comspec" should be set so as to allow the loading
      of DOS COMMAND.COM from across the network; for better performance. 
      For example, these lines could be included in an AUTOEXEC.BAT or
      STARTNET.BAT file:

           NET MAP F: IBM_DOS_310
           SET COMSPEC=F:\COMMAND.COM

      In addition, workstations that only have floppies can be assisted by
      creating a Network Directory where the NetWare Lite utility (NET.EXE,
      NET.OVL, NET.HLP and LITE$RUN.OVL) can be loaded from; instead of
      always loading them from the floppy.  We suggest that a Network
      Directory called NWLITE be created.  This directory should be a
      SERVER's C:\NWLITE  directory.  We also suggest that this Network
      Directory be given default rights of READ and not the default of ALL. 
      All floppy-only CLIENTs should map a drive to this resource and add the
      drive to their DOS path.  This will allow the loading of the NET
      utility from across the network; a much better solution than loading
      from floppy.  For example, these lines could be included in an
      AUTOEXEC.BAT or STARTNET.BAT file:

           NET MAP M: NWLITE
           PATH=M:.;%PATH%

      If you want to run the CLIENT from a floppy drive and have that
      diskette be the boot diskette, the following configuration is
      suggested.  Where ever NE2000.COM appears, replace it with the
      appropriate driver name you are using.  Also, L: and M: are simply used
      as examples; you may use any other valid driver letters.  We map drive
      M: to the Network Directory NWLITE as described above.  Similarly, L:
      is mapped to the Network Directory IBM_DOS_310 as described above.

      1)   Create a bootable diskette using the FORMAT A: /S command.

      2)   Copy the following NetWare Lite files to the diskette.
                 LSL.COM
                 NE2000.COM
                 IPXODI.COM
                 CLIENT.EXE
                 NET.EXE

      3)   Create an AUTOEXEC.BAT with the following lines added to it.
                 LSL
                 NE2000
                 IPXODI A
                 NET LOGIN
                 NET MAP L: IBM_DOS_310
                 NET MAP M: NWLITE
                 PATH=L:\;M:\;%PATH%
                 SET COMSPEC=L:\COMMAND.COM

      4)   Create an CONFIG.SYS with the following line added to it.
                 LASTDRIVE=M

      For those Network Directories that contain applications (executables)
      the drives used to map to these applications should be included in the
      DOS environment variable PATH.  For example, these lines could also be
      included in an AUTOEXEC.BAT or STARTNET.BAT file:

           NET MAP G: TURBOC
           NET MAP H: WORDPERFECT
           NET MAP I: GAMES
           SET PATH=G:\BIN;H:.;I:\TETRIS;%PATH%

 Make Shared Executables Read-Only
      Executable files that will be run by more than one user at a time need
      to be marked as read-only.  If they are not, then you may notice at
      times that you are temporarily denied access to a file you wish to run. 
      For example, you may get a message that access was denied or that the
      EXE file could not be run.  If this happens, mark the executable files
      read-only using the DOS ATTRIB command.  Type ATTRIB +R *.EXE in the
      directory where the executable files reside.  This example marks the
      *.EXE files read-only.  All shared .COMs, .BATs, and .OVLs should be
      marked as well.  The read-only attribute can be cleared using the same
      command replacing the +R with -R. (See DOS documentation for
      information on the ATTRIB command).

 Location Independence
      You will notice that our resources are location independent.  Suppose
      you create a Network Directory named ALL_APPS on a server named
      DEPT_SERVER.  Server DEPT_SERVER is a 8 MHz 286 machine with a 40 MB
      hard disk.  All CLIENTs map drives to ALL_APPS and use it every day. 
      Now suppose you buy a 50 MHz 486 machine with a 1 GB disk drive on it. 
      You want to move the Network Directory ALL_APPS to this new machine. 
      You install this new machine and call it HOT_SERVER.  You can then
      create a new Network Directory on this new server and call it ALL_APPS
      (same name as before).  You then copy the files from DEPT_SERVER to
      HOT_SERVER.  ALL_APPS can now be removed from DEPT_SERVER.  All your
      CLIENTs will now use ALL_APPS from HOT_SERVER and nothing need be
      changed from the CLIENT's perspective.  The CLIENTs don't need to know
      that the location of the Network Directory ALL_APPS has moved.  This
      same principle applies to Network Printers.



 2. Printing -- Conventions and Suggestions
 -----------

      Chances are that you bought this product to share one or more printers. 
      For this reason, give special attention to the following remarks.

 Local Network Printers
      Once a printer is assigned as a Network Printer, you should only access
      that printer through the network.  You may have a printer attached to
      your workstation that has been defined as a Network Printer.  In this
      case, you should capture a port when you wish to print to it.  If you
      print to it directly (not using capture), you may cause print job
      corruption.

 Characters Per Second and Print Buffers
      Network Printers are created in the NET menu utility in the "Supervise
      the Network" category.  When a printer is created, you can configure
      the performance of the printer relative to the DOS running on the same
      machine where the printer is attached.  This is done by modifying the
      "Chars per second" parameter in conjunction with the "Print buffer
      size" parameter of the server configuration.  The print buffer is an
      area in memory where characters are stored before being printed.  The
      larger the print buffer size, the less often the SERVER will need to go
      to disk to read more characters to print.  If the "Chars per second"
      value is high (relatively speaking) and the "Print buffer size" is
      large (relatively speaking) then the printer will be driven faster and
      the DOS running on that machine will be interrupted more often to send
      characters to the printer.  The converse is also true if the value of
      "Chars per second" is low and "Print buffer size" is small.  These
      values should also be tuned to the speed, or desired speed, of the
      printer.  If the printer is physically a "slow" printer then setting
      the "Chars per second" parameter to a high number will have no effect. 
      Additionally, if the "Chars per second" is set higher than the "Print
      buffer size" parameter then this will have little effect, as well.

 Setup Strings
      One of the options available on Network Printers is setup strings.  You
      can define up to ten setup strings for each Network Printer.  In short,
      a setup string is a series of characters that put the printer into a
      particular mode (i.e. landscape mode, large characters mode).  By
      default, the DEFAULT setup string is set to nothing.  The DEFAULT setup
      string should be set to a sequence of values which reset the printer. 
      Many printers use the string "1E 45" (<ESC>E) to reset the printer
      (check the documentation for your printer to find out what sequence
      resets the printer).  The manual that came with the printer should
      describe the values that place the printer into different modes.  Setup
      strings are always entered using hexadecimal codes.

      By defining more than one setup string for a Network Printer it is
      possible to submit jobs that will print in different printer modes. 
      Setup strings can be used as part of the "NET CAPTURE" command or in
      the "Print" category of the NET menu utility.  An example of its use
      with "NET CAPTURE" is provided below.

 Capture Settings
      CLIENTs can access Network Printers with the "NET CAPTURE" command. 
      There are several options available with this utility.  Special
      attention should be given to the options available with the "NET
      CAPTURE" command.  They are discussed in the manual, as well as in the
      on-line help in the NET menu utility and on the command-line when "NET
      CAPTURE HELP" is typed.  A sample command-line might look like this:

           NET CAPTURE LPT1 LASERJET B=N D=Y S=LANDSCAPE

      This means that all jobs sent to LPT1 of the local machine will be
      redirected to the Network Printer LASERJET.  It also means that for all
      print jobs sent to LPT1 (LASERJET), there should be NO banner printed
      and each job should start printing before the job has been completely
      submitted (direct printing).  Finally this job is printed using the
      LANDSCAPE setup string (created previously on printer LASERJET).  The
      LANDSCAPE setup string values are sent to the printer just previous to
      the data of each print job sent to LPT1.  The DEFAULT setup string
      values are sent to the printer after each print job is printed (thus
      resetting the printer for the next job sent to this printer). 

      From the NET menu utility it is also possible to submit a print job and
      have the job immediately go on hold.  When a print job is on hold it is
      placed on the queue but not printed.  It can be taken off hold (and
      thus printed) by selecting the job from the print job list and changing
      the flags of the job.

 Postscript printing
      Because of the nature of postscript printers, special care must be
      taken when sending print jobs.  You should make sure your capture has
      the following set:
           BANNER=No
           TABS=0
           FORMFEED=No
      You may also want to set the WAIT parameter to a value higher than 10
      seconds.  If your print job gets split to multiple jobs when printing
      to a postscript printer, you will want to increase the WAIT value. 
      Increase it until your print job comes out all in one job.

 Using WAIT=0
      The WAIT=0 should only be used if the application you are using will
      close the print job.  If the application does not close the print job,
      using WAIT=0 will keep the print job open until it is closed
      explicitly.  A print job on LPT1 can be closed manually from the DOS
      command-line by sending a formfeed or <Ctrl>-L, displayed ^L (press and
      hold the Ctrl key while pressing the L key, then release the L key and
      Ctrl key).  Type "ECHO ^L > LPT1".  This sends a form feed character to
      LPT1 and closes the job.  Generally using a WAIT value of 10 or so is
      adequate.  CAUTION: If you use WAIT=0 and DIRECT=Y you will hold the
      printer until the print job is explicitly closed.

 Capturing Ports
      The documentation incorrectly states that as a CLIENT, you can capture
      COM1 or COM2.  The COM1 and COM2 ports can only be used by a SERVER.  A
      Network Printer can be assigned to the COM1 or COM2 port.  CLIENTs can
      then capture LPT1, LPT2, or LPT3 to a Network Printer that has been
      created and assigned to COM1 or COM2.



 3. Network Applications
 -----------------------

 Installation
      Installing applications on NetWare Lite may be different than
      installing applications on NetWare.  NetWare is, as you know, a very
      popular LAN.  Many applications have NetWare specific installation
      options.  These installation options DO NOT apply to NetWare Lite
      networks.  NetWare Lite is a DOS peer-to-peer network.  If the
      application being installed has network specific installations then
      "Other networks.." or "DOS Peer to peer network" or the like, should be
      selected.  DO NOT select NetWare or Novell installation options.  See
      Appendix B in the documentation for more details.

      In general, some consideration should be given when installing
      applications.  If the application requires configuration information at
      the time it is installed, then consideration should be given to which
      CLIENTs (machines) will use the application.  For example, say
      application TESTAPP.EXE is being installed and it asks what kind of
      monitor will be used with this application.  Suppose that the machine
      you are sitting on has a VGA screen but no other machines on the
      network have VGA screens.  If you were to select VGA then when this
      application is run from across the network from an CGA screen, say, it
      may not function properly.  We have no specific guidelines on this
      subject, as a general solution may not be possible.  This is a general
      problem with configuration of applications on a network.



 4. Compatibility with the NetWare Shell
 ---------------------------------------

      If your site is currently using Novell NetWare and you are installing
      NetWare Lite on the same LAN, then there are some guidelines that
      should be followed in order for both to function properly.

      NetWare Lite functions on a single LAN segment.  In other words,
      NetWare Lite packets DO NOT cross Novell bridges (NetWare Lite packets
      do cross MAC layer bridges or repeaters, however.)  In a site that has
      existing NetWare, each NetWare Lite network will be constrained to a
      single LAN segment.

      If there are workstations that will load both the NetWare shell and
      NetWare Lite software we suggest the following load order:

      IPX                    (either the IPX you had or IPXODI that came with
                             NetWare Lite; either one but NOT both)

      DOS Share              (SHARE.EXE, if becoming a SERVER)

      NetWare Lite Server    (SERVER.EXE, if desired)

      NetWare Lite Client    (CLIENT.EXE, if desired)

      NetWare Shell          (NETx.COM)

      Once you have installed the CLIENT to a workstation that will also be
      running the NetWare Shell, you will need to modify your AUTOEXEC.BAT or
      appropriate batch file to load the files in the correct order.  Note:
      with LASTDRIVE set, the NetWare Shell will map the first drive past
      LASTDRIVE to the SYS:LOGIN directory of the NetWare server for you to
      login.  If LASTDRIVE is not set, DOS defaults it to E:, thus F: would
      be mapped to SYS:LOGIN.  Also, if you use the MAP *1:= command in your
      login script, *1 means the first drive past LASTDRIVE.  If you are
      dependant on certain drives being mapped with certain letters, the
      changing of LASTDRIVE may change which drive letters are mapped.  Be
      aware that all drive letters, A: - Z:, can be mapped to NetWare servers
      (NetWare Lite can only map A: - LASTDRIVE).

      See Network Applications in this README file for installing network
      applications.



 5. SERVER Optimization and Functions
 ------------------------------------

 Disk Caches
      NetWare Lite does not ship with a disk cache.  We have tested with
      several (read many) commercially available disk cache products and
      found them to be quite inexpensive while adding significant performance
      to the NetWare Lite SERVER software.  We suggest for higher performance
      of the NetWare Lite SERVER that a disk cache be acquired and installed
      on the SERVER machines.  Some cache tuning may be necessary for best
      results.

 Server Configuration
      For best performance we suggest that receive buffer and read buffer
      sizes be increased to what is supported by the network topology (i.e.
      ethernet, token ring) up to a maximum of 4096 bytes using a multiple of
      512 bytes.  In fact, if 4096 is selected then the SERVER will truncate
      the value to the maximum value supported by the topology.  This tuning
      allows CLIENTs to request more data from (or send more data to) the
      SERVER with each read (write) operation.  When more data is sent, fewer
      requests are necessary and better performance is obtained.  This
      enhancement does increase the size of the SERVER when it is resident in
      DOS.

      Depending on the "load" being placed on the server, it may be
      beneficial to increase the number of receive buffers and read buffers. 
      In general, we have found that 8-12 receive buffers is enough for even
      the most heavily loaded server.  Similarly, 5-10 read buffers is
      sufficient.  These values need not be more than one or two above the
      number of simultaneous connections (up to our suggested maximums of 8-
      12 receive buffers and 5-10 read buffers).

 Mapping vs. SUBSTing
      If your machine is a SERVER and you map to yourself, it is recommended
      that you SUBST to yourself instead of mapping to yourself.  SUBST is a
      DOS command that lets you assign a drive letter to a directory on
      another drive.  For example, if you usually map to yourself with G: to
      the Network Directory APPS, and if APPS is actually the C:\APPS
      directory, the NET MAP G: APPS could be replaced by SUBST G: C:\APPS. 
      To remove this substitution, you would type SUBST G: /D.  Using this
      substitution, rather than a mapping, will result in better performance
      for operations done on drive G:.

 Mapping Local Drive
      You can map drives that are local, for example A: or B:, and use them
      temporarily as network drives.  However as a general practice, it is
      not recommended.  If you run out of drive letters to map, increase
      LASTDRIVE in your CONFIG.SYS.

 Use of ASSIGN
      Do not use ASSIGN with NetWare Lite.  The DOS reference manual (3.3)
      recommends that you use SUBST instead of ASSIGN and explains how to do
      so.

 Remove a SERVER from your hard drive
      If you installed the SERVER on your hard drive and no longer want it
      there, you can remove it by doing the following:

           1) Boot your machine without loading the SERVER.

           2) Run the original INSTALL.EXE that came on a floppy.

           3) Select "Make this machine a SERVER".  When asked to select the
           network interface card, press ESC and exit the INSTALL utility. 
           The SERVER is now removed from your hard disk drive.

 Improving SERVER performance
      It has been found that fragmented file on the hard disk drive of a
      SERVER can adversely affect performance.  It is suggested that you
      periodically unfragment the files on the hard disk drive of each
      SERVER.  This can be done using any of a number of disk optimizing or
      disk compression tools available in the market place.  MAKE SURE THE
      SERVER IS NOT RUNNING WHEN THIS TYPE OF OPERATION IS DONE!!!

      NEVER run any low-level disk repair utilities on the hard disk drive of
      the SERVER while the SERVER is loaded.  This can cause corruption of
      data stored on the hard disk drive.  This includes CHKDSK /F, disk
      doctor utilities, and disk optimizing utilities.  Low-level utilities
      can only be run directly on the SERVER machine.  You cannot run them
      from CLIENTs that have a drive mapped to the SERVER.

 Renaming SERVERs and Reconnection
      Whenever a SERVER is renamed, you should reboot that SERVER as soon as
      possible and have the CLIENTs that were connected to that SERVER, re-
      login.  CLIENTs cannot reconnect to a SERVER that was renamed.

 Disabling the SERVER
      There is no way to remove the SERVER or CLIENT from memory once either
      is loaded.  The SERVER can be disabled once loaded.  Press CTRL-ALT-
      DEL, as if you were rebooting.  When the Reboot window comes up, press
      1 to disable the SERVER.  This simply turns the functionality of the
      SERVER off, it is not removed from memory.

 SHARE.EXE -- Status Report 5
      When loading the SERVER, you may get "Status Report 5", which talks
      about SHARE.EXE not being loaded when the SERVER.EXE was run. 
      SHARE.EXE is a program that comes with DOS 3.1 or above.  If you get
      Status Report 5, you do not have SHARE.EXE in your PATH.  Either add
      the appropriate directory to your PATH (where SHARE.EXE is located) or
      copy SHARE.EXE to the directory where NetWare Lite is installed.  SHARE
      should be loaded before the SERVER.  SHARE is the mechanism that allows
      files to be accessed simultaneously from multiple CLIENTs.  It is not
      required to be loaded for the SERVER to run, though strongly suggested.
      SHARE.EXE should be tuned for proper behavior.  You may need to
      increase the values for locks (/L) and files (/F) for SHARE if you run
      database applications, or if you have more than 4 users.  Configuration
      of SHARE.EXE is documented with your DOS manual.  The CLIENT does not
      need SHARE.EXE to be loaded.

 Workstation Time
      To keep time of CLIENT machines on the network synchronized we suggest
      that "NET TIME <server_name>" be placed in everyone's AUTOEXEC.BAT or
      STARTNET.BAT file.  <server_name> should be a machine that keeps
      "pretty good" time.  This becomes especially important if NetWare Lite
      is being used in a software development environment where MAKE.EXE is
      being used.  MAKE.EXE requires strict time synchronization.  If "NET
      TIME" is used then MAKE.EXE will function smoothly.  Further more, the
      time on all SERVERs can be synchronized by using the "Time
      Synchronization" option in the "Supervise the Network" menu.



 6. CD-ROM Support
 -----------------

      NetWare Lite does support CD-ROM drives.  You can use CD-ROM drives
      with the SERVER and/or CLIENT.  If you will be running the CLIENT on
      the same machine as the CD-ROM drive, you MUST load the CLIENT before
      loading the CD-ROM redirector (e.g. MSCDEX).  You may attach a CD-ROM
      to a SERVER workstation and create a Network Directory that point to
      the CD-ROM drive.  This way remote CLIENTs can access the CD-ROM.



 7. Loading IPXODI
 -----------------

      In the STARTNET.BAT file that is created for you, the line "IPXODI A"
      appears.  The parameter "A" tells IPXODI to only load IPX, this makes
      it so IPXODI takes up less memory.  If you have an application that
      needs SPX to run, remove the "A" from this line when loading IPXODI
      then SPX will also be loaded.  You can type "IPXODI ?" to see a list of
      all available options for IPXODI.



 8. Auxiliary NetWare Lite Files
 -------------------------------

      Included with NetWare Lite are four extra programs that are not
      documented.  These files are not needed for NetWare Lite to run, but
      add fun and functionality.  They are: DEDICATE.COM, DEMO.EXE,
      NETBIOS.EXE, and NLSNIPES.EXE.

      DEDICATE.COM -- DEDICATE is a little program that can be run on a
      SERVER to improve performance.  It is a useful program to be run on
      NetWare Lite machines that are acting as dedicated servers; or if a
      machine is a CLIENT/SERVER and the CLIENT is not going to be active for
      a while. To run DEDICATE, type DEDICATE when in the C:\NWLITE
      subdirectory on the machine running SERVER.EXE.

      DEMO.EXE -- DEMO is a networking demonstration program that shows how
      workstations can communicate using shared file access.  When run, a
      "worm" is shown moving around on the screens of the workstations
      running DEMO.EXE.  As the "worm" covers each screen, eventually the
      word "LITE" is shown.  To run DEMO, change to the same directory on the
      same SERVER on each machine that will be running DEMO.  With DEMO.EXE
      in your PATH, type DEMO and press ENTER on each workstation.  DEMO
      works best if run in a Left-to-Right fashion.  That is, starting on the
      left-most workstation, run DEMO.EXE and move right running DEMO on each
      machine.  The screens are "connected" starting left and moving right in
      the order which DEMO was started.  Once running, you can drive your
      "worm" using the arrow key.  DEMO will only support 9 workstations
      running simultaneously.

      NETBIOS.EXE -- This is the NETBIOS that is included with regular
      NetWare.  It can be loaded any time after IPXODI is loaded.  Some
      applications require the presence of NETBIOS.  For this reason NETBIOS
      is provided with NetWare Lite.  For more documentation on NETBIOS.EXE,
      contact the nearest Novell Authorized Reseller.

      NLSNIPES.EXE -- NLSNIPES is a game.  One to five users can play at a
      time.  Everyone that wants to play NLSNIPES must map a drive to the
      same Network directory on the same SERVER.  To run, type NLSNIPES.  You
      will then be asked for two initials, this uniquely identifies your
      "man" as you play.  The first person to run NLSNIPES is the "starter". 
      As people run NLSNIPES and enter their initials, they will see the
      initials of the other players that are entering the game.  Once the
      desired group is ready, the "starter" will press ENTER to begin.  Move
      your "man" through the maze killing snipes, generators, and other
      "men".  For instructions on how to move and shoot, type "NLSNIPES /H"
      at the command-line.



 9. Logging in after INSTALL
 ---------------------------

      The first time you login to a newly installed network there will be
      only one user defined on the network, SUPERVISOR.  To login, type NET
      LOGIN SUPERVISOR or type NET and enter SUPERVISOR when prompted for a
      username.

      If you are installing on a network where other SERVERs are already
      running, the user accounts defined on the network will also be defined
      on SERVERs you install.  You will need to consult with the
      administrator of the network to find out what user accounts are defined
      and how you may login.

      Note: The SUPERVISOR account on a newly installed network has no
      password.  For security reasons it is recommended that you set a
      password on the SUPERVISOR account soon after installation.  DO NOT
      FORGET THIS PASSWORD!



 10. Windows 3.0 Compatibility
 -----------------------------

      This section contains information about using NetWare Lite with Windows
      3.0.  Follow the suggestions outlined below to operate your Windows 3.0
      environment.

 Network vs. Local installation of Windows
      Install Windows locally, do not attempt to install it from a Network
      Directory.  Follow the regular installation procedures using Windows
      diskettes.  Windows INSTALL may indicate the presence of a "Microsoft
      Network (or 100% compatible)" network, change this selection to "No
      Network Installed".

 Before Entering Windows
      It is suggested that you set up your NetWare Lite environment before
      running Windows.  Such operations include: logging into the network,
      mapping drives, and capturing ports.
 
 Mapping Drives
      If a SERVER to which you have mapped a drive goes down, Windows will
      display a message indicating that the drive does not contain any files. 
      Any attempt to access that drive will fail.  Under regular DOS, this
      error is trapped and the CLIENT saves enough information to
      automatically restore the connection to that Network Directory when the
      downed SERVER returns to the network.  Windows prevents regular DOS
      from trapping this error.

      To restore connections to your mapped drive, exit Windows and re-issue
      the NET MAP command when the SERVER is back on the network.

 Printing
      Use the NET CAPTURE command described in your NetWare Lite User Guide
      to re-direct printing from your LPT1 or LPT2 ports to a network printer
      before you enter Windows.  Configure your printer in Windows to either
      the LPT1.OS2 or LPT2.OS2 ports depending on which port you captured
      before entering Windows.

      Workstations that are configured as both SERVER and CLIENT should use
      LPT1.OS2 or LPT2.OS2 to print from Windows.  (See the note on Local
      Network Printers above)

 NetWare Lite SEND messages
      NetWare Lite SEND messages will only appear when you open a DOS prompt
      or exit Windows.



 11. Documentation Errors (Errata)
 ---------------------------------

      Your manual may contain one or more of the following errors.

 Page 7 -- In the "Log in to NetWare Lite" section step 3, "NET LOGIN"
      should read "NET LOGIN SUPERVISOR".  See section 9 above.

 Pages 36 and 60 -- Incorrectly state that the supervisor privileges are not
      required.  That is not correct.  Supervisor privileges are required
      unless you are running on your own machine.

 Page 106 -- Incorrectly states that COM1 and COM2 can be captured using the
      NET CAPTURE command.  This is not true, only LPT1, LPT2, and LPT3 can
      be captured by a CLIENT.  NOTE: Serial printers are supported at the
      SERVER as Network Printers.

 Page 107 -- Is missing the "notify" capture setting.  You can specify the
      notify option using "N=Y" or "NOTIFY=Y".  If set, the SERVER will send
      you a message when the print job is done.

 Page 149 -- The discussion of network configuration files is not needed. 
      The NetWare Lite INSTALL utility generates the correct NET.CFG file
      from the options you select during installation.  After installation,
      you can edit the NET.CFG file using any standard ASCII text editor.



 WE HOPE YOU LIKE THIS PRODUCT!

