                       LAN WorkGroup v4.1
               LAN WorkGroup Documentation Updates
                           DOCUPDTE.TXT

Copyright (c) 1993 Novell, Inc.  All Rights Reserved.

THIS WORK IS SUBJECT TO U.S. AND INTERNATIONAL COPYRIGHT LAWS AND
TREATIES.  NO PART OF THIS WORK MAY BE USED, PRACTICED, PERFORMED,
COPIED, DISTRIBUTED, REVISED, MODIFIED, TRANSLATED, ABRIDGED,
CONDENSED, EXPANDED, COLLECTED, COMPILED, LINKED, RECAST,
TRANSFORMED, OR ADAPTED WITHOUT THE PRIOR WRITTEN CONSENT OF
NOVELL, INC.  ANY USE OR EXPLOITATION OF THIS WORK WITHOUT
AUTHORIZATION COULD SUBJECT THE PERPETRATOR TO CRIMINAL AND CIVIL
LIABILITY.


MANUAL SET:
~~~~~~~~~~

The LAN WorkGroup manual set consists of the following printed
documents:

     LAN WorkGroup Installation and Configuration Guide
     (Publication 100-001793-001)
     
     LAN WorkPlace for DOS User's Guide
     (Publication 100-000881-002)
     
     LAN WorkPlace for DOS Administrator's Guide
     (Publication 100-000882-002)
     
     LAN WorkGroup Troubleshooting Guide
     (Publication 100-001794-001)
     
     LAN WorkPlace Quick Reference
     (Publication 101-001076-003)

The user's guide and administrator's guide are also included with
the LAN WorkPlace for DOS software.  Some references in those
documents are not correct.  Specifically, references to the LAN
WorkGroup Configuration Guide should read LAN WorkGroup
Installation and Configuration Guide.

The LAN WorkGroup product also includes extensive online help.

===================================================================

DOCUMENTATION UPDATES:
~~~~~~~~~~~~~~~~~~~~~

The following paragraphs correct errors and provide new information
that became available after publication of the following LAN
WorkGroup v4.1 manuals.


LAN WorkGroup Installation and Configuration Guide:
**************************************************

The following paragraphs provide details about corrections and
additions to the LAN WorkGroup Installation and Configuration
Guide:


Installation
============

The installation program displays a list of available mounted
volumes for the shared \NET directory.  Select a volume from the
list by moving the highlight and then pressing <Enter>.

If the volume you want to use is not displayed, press <Alt-F10> to
exit from the installation program and mount the volume.  If the
volume is already mounted, verify that it has at least 8 MB of
available disk space.


LWGCON
======

Optional driver parameters for a link driver can be specified in
the Optional Driver Parameter form accessible from the Workstation
Type form.  You must enter the entire optional parameter including
the setting name in the option fields.

You can rename workstation, subnetwork, and workstation type entry
names by selecting (highlighting) the entry and pressing <F3>.

Refer to Appendix E of the LAN WorkPlace for DOS Administrator's
Guide for more information about subnetworks and IP addresses.


LAN WorkPlace for DOS User's Guide:
**********************************

The following paragraphs provide details about corrections and
additions to the LAN WorkPlace for DOS User's Guide.


Script Director
===============

The sample Script Director script on page 5-25 has the following
line:

  WAITFOR "ca_1> " 60

The preceding line waits for the "ca_1> " prompt, but if the prompt
does not exactly match the string between the quotes, including the
space after the prompt, the script waits 60 seconds for a space
character. The following line avoids the 60-second delay:

  WAITFOR "ca_1>" 60

In general, it is better to use unique substrings in your scripts.
For example, use "login:" rather than "login: " (with a space after
the colon).


LAN WorkPlace for DOS Administrator's Guide:
*******************************************

The following paragraphs provide details about corrections and
additions to the LAN WorkPlace for DOS Administrator's Guide.


BOOTPCHK Utility
================

The BOOTPCHK utility has two options not documented in the
reference summary on page B-5:  the -Tn option and the -H option.

The -Tn option is for timeout and the -H option is for help.

The syntax line should read as follows:

  BOOTPCHK  [-N{T|A|E}]  [-Pn]  [-Tn]  [-?|-H]

The -Tn option lets you set a timeout ranging from 1 second to a
maximum value of 60 seconds. By default, BOOTPCHK waits 2 seconds
to receive reply packets. If your network is complex, you may want
to increase the amount of time BOOTPCHK waits. For example, use the
following command to have BOOTPCHK wait for 5 seconds:

  BOOTPCHK -T5

The help option (-? or -H) displays usage information to the
screen.


BOOTPD and BOOTPFD Logging
--------------------------

The BOOTP logging feature is not described in Appendix B of the
administrator's guide.  The following features should be noted
about BOOTP logging:

     Logging transaction messages to a log file is on by default.
     The -Q (quiet) option turns logging off.

     File logging uses two files:  SYS:ETC\BOOTP.LOG and
     SYS:ETC\BOOTP.BAK.  These files hold up to 65 KB of log
     entries each.  When one log file fills up, the other file is
     used.  The file that is actively being written to is named
     BOOTP.LOG and the file that was previously being written to is
     renamed to BOOTP.BAK.  When the files are switched, the new
     current file is truncated to zero length.

     Both the BOOTP forwarder and the BOOTP server use the same log
     files.  (The BOOTPD and BOOTPFD NLMs cannot run simultaneously
     on the same server.)

     The server and forwarder open the file, write the log entry,
     and close the file.  This prevents the administrator from
     reading the file while the server is writing a log entry.
     
NOTE: If the administrator has the file open when the server or the
      forwarder attempts to write a log entry, that log entry is
      NOT written to the file.  However, once the file is again
      closed by the administrator, subsequent log entries are again
      written to the log file.


BOOTPFD.NLM
===========

The BOOTPFD NLM is not documented in Appendix B of the
administrator's guide.  BOOTPFD is a streamlined BOOTP server that
forwards requests for BOOTP services to a centralized system that
runs the main BOOTP server (BOOTPD).

The syntax is as follows:

  LOAD BOOTPFD  [-F<address>]  [-Q]  [-V]

The parameters are the same as for the BOOTP server (BOOTPD).  They
are as follows:

  -F <address>  Forward the BOOTP request to the BOOTP server at
                the address specified.  The address must be the IP
                address of the server in dotted notation.

  -Q            Turns logging off; runs the BOOTP server in quiet
                mode.

  -V            Displays resolved TCP/IP information on the server
                screen in verbose mode.

NOTE: For efficient operation and handling of IP address
      assignment, Novell recommends no more than one BOOTP server
      per subnet.


MVS Filenames
=============

The following information should be added to the MVS Filenames
description on page 4-38:

MVS filenames cannot begin with a number. For example, if you try
to use Rapid Filer or FTP to copy a file named 123.TXT from a DOS
workstation to an MVS host, the operation fails.


Resolver Configuration File Entries
===================================

The example DOMAIN entry on page 3-7 is incorrect. The example of
an entry with comments should read as follows:
     
     nameserver 129.47.8.1     ; COMPANY RESOLVER FILE

The term nameserver is a required keyword.


RFCNBIOS
========

On page B-19, the RFCNBIOS options (nb_adapter, nb_brdcast,
nb_sessions, nb_commands, and nb_domain) are set in the NET.CFG
file as described in Chapter 3, "Network Administration." These
options affect the command but are not part of the command line.


Script Director
===============

Script Director has a new section in the LWP.INI file (not
documented in Chapter 8, "Script Director Language") for starting
the application in one of three modes:

     Normal
     Minimized
     Maximized

Under the normal setting, Script Director displays the Script
Director panel and any windows opened by the script (for example,
the Status Window or the Trace Window).

Under the minimized setting, Script Director is iconized and any
script operations are run in the background.

Under the maximized setting, Script Director runs the same as under
the normal setting, but the display is enlarged (maximized).

The format of the [ScriptDirector] section of the LWP.INI file is
as follows:

  [ScriptDirector]
    Start={ Normal | Minimized | Maximized }

For example:

  [ScriptDirector]
    Start=Minimized

Any one of the values can be abbreviated to the first three letters
(that is, Nor, Min, and Max). The default setting is Start=Normal.

The following information should be added under the TELNET MODE
command description on page C-41:

#prevmode is set to -1 if the TELNET MODE fails.

The following information should be added under the TELNET SENDEOL
command description on page C-41:

TELNET SENDEOL gets the current mode setting if no parameter is
specified.

The following information should be changed under the EMULATE
command description on page C-49:

  #prevtype is -1 if the EMULATE command fails (not #prevpos).


UNPACKR Command
===============

A reference page for the UNPACK command is provided on Page A-77.
This command has been replaced by the UNPACKR command.  The syntax
of the UNPACKR command is as follows:

  UNPACKR  source  destination

Replace source with the name of the file on the diskette and
destination with the name for the expanded file. For example:

  F:\NET> UNPACKR A:\NET\BIN\PING.EX_ PING.EXE <Enter>

The above command unpacks the file to the current directory on the
current drive.  The PING.EXE file, for example, must be copied to
the <vol>:NET\BIN directory.  Specify the complete path as
necessary.


XPC Utility
===========

The following paragraphs provide XPC usage and configuration
information not covered in Chapter 5, "Configuring Terminal
Services," of the LAN WorkPlace for DOS Administrator's Guide.


Using the XPC Icon
------------------

If you click the XPC icon, XPC opens a DOS window and displays the
DOS prompt, but you must type the command XPC to run the utility.


Using Host Presenter with XPC
-----------------------------

You can use Host Presenter to log into a workstation that is
running XPC. Host Presenter includes a profile named XPC.PHP for
use with XPC. To use this profile, click the Load Profile button on
the Host Presenter Open Session menu and select profile XPC.PHP.
The default location for this profile is the server's \NET\PROFILE
directory.


Using TNVT220 with XPC
----------------------

When you use TNVT220 to log into a workstation running XPC, you
should turn off the status line display so that the entire screen
is available for the XPC display. To turn off the TNVT220 status
line, proceed as follows:

1.  Press <Alt-S> to display the TNVT220 Setup Directory.

2.  Press the numeric <Enter> to select the Display Setup menu.

3.  Select StatusLineOn.

4.  Press the numeric <Enter> to change the display to
    StatusLineOff.

5.  Press <Esc> twice to exit.


Using XPC with the QEMM 6.0 Memory Manager
------------------------------------------

If you enable the QEMM6.0 Stealth feature (ST:M or ST:F option),
XPC locks up when it is using expanded memory. When this QEMM
feature is enabled, start XPC using the -C command-line option to
prevent XPC from using expanded memory. Alternatively, you can
disable the QEMM Stealth feature by removing the ST:M or ST:F
command-line option from the QEMM statement in your CONFIG.SYS
file.


Using XPC with the EMM386 Memory Manager
----------------------------------------

Do not use the EMM386 m# option when you run XPC. The m# option
specifies the starting address of the page frame. XPC does not work
correctly if the m# option is specified and may lock up on some
workstations.

===================================================================

RELATED README FILES:
~~~~~~~~~~~~~~~~~~~~~

For additional information, see the following text files:

  LWGLWP.TXT (for information on running LAN WorkPlace and LAN
  WorkGroup on the same workstation)
  NFSV12B.TXT (for upgrade information on NetWare NFS v1.20B)
  NETCFG.TXT (for information about the NET.CFG file)
  README.TXT (for information on installation and configuration)
  SWUPDATE.TXT (for information on software updates)
     
All of these files are located on the first installation diskette
and copied to the <vol>:NET directory.  The README.TXT file is also
copied to the SYS:ETC\INSTALL directory as LWG.TXT.  If the
information in the printed manuals or in the text files does not
answer your questions, contact your Novell-authorized reseller for
assistance.

