CONTENTS OF README FILE for LANSight Support v3.01 (5/3/93)

1)   WHAT'S NEW IN LANSIGHT SUPPORT 3.01

2a)  INSTALLATION--COPYING FILES TO THE NETWORK
 b)              --SETTING UP THE SERVER
 c)              --SETTING UP A WINDOWS VIEWING STATION
 d)              --SETTING UP TARGET STATIONS
 e)              --LOADING THE TSRS 
 f)              --SETTING UP LANSELECT (OPTIONAL)

3)   KNOWN LANSIGHT PROBLEMS 


===============================================================
1) WHAT'S NEW IN LANSIGHT SUPPORT 3.01
===============================================================
* Improved user interface
  -- Graphical screens for network diagnostics
  -- Network view filters (you can customize your view of
     the network)
  -- Improved button bar
  -- Scalable windows
  -- Improved ease of use, better look and feel
* Support for Dynamic Data links
* Support for NetPorts
* Ability to load TSRs from login scripts by using LOGIN.COM
* Automatic configuration of workstations during login with
  WKSTACFG.EXE


===============================================================
2a)  INSTALLATION--COPYING FILES TO THE NETWORK
===============================================================
LANSight Support can only be installed from floppy disks (5.25"
or 3.5") and must be installed to a network drive. The
installation will not allow you to install LANSight to a local
drive.

1) Insert Disk 1 in the drive and type a:INSTALL or b:INSTALL.

2) When prompted, select the network drive on which you wish to
   install and run LANSight.

3) When prompted, specify a directory in which to install
   LANSight (LANSIGHT by default). If the directory does not
   exist it will be created for you.

4) When the installation is done copying files it will
   serialize your server. This will take anywhere from a few
   seconds for a small LAN to a few minutes for a medium-sized
   LAN. In some cases where there is a very large network with
   multiple WANs connected over long distances the
   serialization can take a couple of hours (the current record
   is 4 hours).

5) When the serialization is done you can store the LANSight
   disks in a safe location and continue to the next step.


===============================================================
2b)  INSTALLATION--SETTING UP THE SERVER
===============================================================

1) Go to the LANSIGHT directory and run SITEADMN.EXE to set the
   default server security. As soon as you select "Server
   Default Security" a default security template will be
   created for you on that server. You may use these defaults
   or modify these defaults at any time.

   NOTE:  Failure to set the default server security could
          result in an error when you try communicating
          with a workstation using LANSight Support.

2) If you want to use LANSight to remotely control a server you
   must manually copy USER.VAP or USER.NLM from the LANSIGHT
   directory to the SYS:\SYSTEM directory. If you are using a
   NetWare 3.x server you can type LOAD USER and add USER to
   the AUTOEXEC.NCF file. If you are using NetWare 2.x you must
   bring down the server and bring it back up in order for
   USER.VAP to be loaded.


===============================================================
2c)  INSTALLATION--SETTING UP A WINDOWS VIEWING STATION
===============================================================

1) If you want to run the Windows version of LANSight
   (WSIGHT.EXE) you need to configure your computer
   appropriately. This is easily done by entering Windows and
   running SETUP.EXE from the LANSIGHT directory. Follow the
   instructions to update files and drivers as needed. At the
   end of the setup you will have a LANSight Support program
   group with three icons--LANSight, Chat, and File Transfer.

   NOTE: After running the LANSight for Windows Setup you must
         restart Windows before LANSight will work (you do not
         need to reboot).

If you have trouble restarting Windows, it is probably because
of a duplicate line "device=*vpicd" in the [386 Enh] section of
your SYSTEM.INI file. It will be on the first line. Remove that
line and restart Windows.

   NOTE: Make sure that your Windows installation has been
         set up for NetWare. If you are using Windows v3.0,
         also make sure you are using the latest drivers
         available off CompuServe.

You can run the DOS version of LANSight by running SIGHT.EXE,
or you can run the Windows version by running WSIGHT.EXE. Make
sure your current or working directory is the directory where
you just installed LANSight (LANSIGHT by default). You cannot
yet communicate with user workstations until you have
configured the workstations appropriately (as described in the
next section).


===============================================================
2d)  INSTALLATION--SETTING UP TARGET WORKSTATIONS
===============================================================
If you wish to chat with, view, or transfer files with target
stations you must first run a one-time configuration for each
workstation. This process can be partially automated by using
the utility WKSTACFG.EXE, which is included with LANSight
v3.01. The following paragraphs outline this process:

Good morning Mr. Phelps.

Your mission, should you decide to accept it, is to configure
all nodes on your network that run Windows to be compatible
with this version of LANSight Support.

Your arsenal will include something new from our labs,
WKSTACFG.EXE. Don't be fooled by its harmless appearance. It is
very powerful and, if implemented correctly, can force even the
most uncooperative network user into full compliance.

WKSTACFG will perform the following checks and upgrades:

1. Searches the local drives (C:,D:,E:) for Windows
   installations and if found:

      a. Looks for the old LANSight IMOUSE drivers and deletes
         them and modifies the SYSTEM.INI file to reflect the
         change in mouse drivers.

      b. Checks the SYSTEM.INI file for NetWare drivers and
         prints a message if this copy of Windows is not
         configured for use with NetWare.

      c. Updates the following files if they are older than the
         ones in the directory that WKSTACFG was run from.

                VUSER.386
                NOTIFY.DRV
                WLANSEL.EXE
                NWIPXSPX.DLL
                VIPX.386

       THESE FILES MUST BE IN THE SAME DIRECTORY AS
       WKSTACFG.EXE! USER.COM SHOULD ALSO BE THERE IF YOU
       CHOOSE THE /Overwrite OPTION.

       d. Adds "device=vuser.386" line to the [386 Enh] section
          of the SYSTEM.INI file.

       e. Backs up .INI files before making any changes to them
          (*.bak).

       f. Adds WLANSEL.EXE to the run= line in the WIN.INI
          file. If it was already there, it is modified to make
          sure that the one that is run is the one that was
          copied to the Windows\System directory.

2. If the /Network switch is specified, WKSTACFG will check
   only the network search drives for a version of Windows. If
   a network version of Windows is found then the same
   modifications described in #1 (a to f) above will be made
   to the network version of Windows.

3. If the /Overwrite switch is used, all older copies of
   USER.COM found on the local drives will be overwritten with
   the new version.

4. When run with the /Log= switch, WKSTACFG can insure that
   each node only configures once. The file that is created in
   the specified directory can be used with Desktop Access as
   an alias (.STA) file that uses full (long) names instead of
   login names. The file must be renamed to have the .STA
   extension. It would be best to copy the file to another
   directory so that users are not modifying the run-only-once
   log.

5. If the /Prompt switch is specified, the user will be
   prompted and given an opportunity to decline configuration.
   If he declines, this action is also logged in a separate
   file so that he won't continue to be prompted every time he
   logs in (assuming WKSTACFG is being run from a login
   script).

As usual, if you or any of your System Administration team is
caught or captured, the secretary will disavow any knowledge of
your actions....

A typical login script might include a section such as one of
the following examples which configures the desired target
workstations:.


EXAMPLE 1
---------

IF MEMBER OF "MY_GROUP" THEN
  #FS2\SYS:\LOGIN\SIGHT\WKSTACFG /P /V /L=FS2\SYS:\LOGIN
    REM  THIS ASSUMES THE PROPER FILES (#1c) ARE IN LOGIN\SIGHT 
    REM  AND USERS HAVE READ AND FILESCAN [RF] RIGHTS

    REM  /P = PROMPT USERS (USERS MAY DECLINE CONFIGURING)

    REM  /V = VERBOSE MODE (SHOW USERS WHAT'S HAPPENING)

    REM  /L = PUT LOG FILES IN SPECIFIED DIRECTORY AND RUN
    REM       WKSTACFG ONLY ONCE PER MACHINE
    REM  USERS ALSO NEED READ AND WRITE [RW] RIGHTS IN THE
    REM  DIRECTORY USED FOR THE LOG FILES. THE LOG FILES ARE
    REM  NAMED CFG_YES.LOG AND CFG_NO.LOG
END


EXAMPLE 2
---------

FS2\SYS:\LOGIN\SIGHT\WKSTACFG /L=FS2\SYS:\LOGIN\TEMP
  REM  NO IF...THEN STATEMENT = CONFIGURE ALL USERS

  REM  USERS NEED [RF] RIGHTS IN LOGIN\SIGHT DIRECTORY 
  REM  AND THE PROPER FILES NEED TO BE THERE, i.e. #1c
 
  REM  NO /P = DON'T ASK USERS IF THEY WANT TO CONFIGURE

  REM  NO /V = DON'T SHOW DETAILS TO USERS

  REM  /L = PUT LOG FILES IN SPECIFIED DIRECTORY AND RUN
            WKSTACFG ONLY ONCE PER MACHINE
  REM  USERS ALSO NEED READ AND WRITE [RW] RIGHTS IN THE
  REM  DIRECTORY USED FOR THE LOG FILES. THE LOG FILES ARE
  REM  NAMED CFG_YES.LOG AND CFG_NO.LOG


You may manually configure a workstation by going to the
computer and running WKSTACFG from the LANSight directory. This
is useful if you want to try out LANSight on one or two
machines before configuring the rest of your machines.


===============================================================
2e)  CONFIGURATION--LOADING THE TSRS
===============================================================
LANSight requires target stations to load USER.COM, which is a
6k TSR. If you want to chat or transfer files with a user in
DOS then the user also needs to have LANSEL.EXE (a 5k TSR)
loaded. USER and LANSEL may not be loaded in upper memory.

USER COMMAND OPTIONS
          USER [-?] [-remove] [-nomouse] [-oldega] [-snow]

where:

 remove       removes USER.COM from workstation memory
 nomouse      disables mouse support
 oldega       avoids reading EGA registers
 snow         avoids snow on CGA displays

LANSEL COMMAND OPTIONS:
          LANSEL [/L=path] [/T=path] [/H=hot-keys] [/R] [/M]
          [/S] [/E]

where:
 /L=path      the full path name of the directory where the
              LANMENU.DAT file is stored;
 /T=path      the full path name of the directory in which
              LANSelect stores temporary files;
 /H=hot-keys  the names of the hot keys that run LANSelect.
              Enter the first letter of each key name: for
              example, CAL for <Ctrl>-<Alt>-<L>;
 /R           removes LANSelect from workstation memory;
 /M           disables use of expanded memory at the 
              workstation;
 /S           shows the current status of LANSelect;
 /E           displays the last error LANSelect encountered;

LANSelect version 1.90 offers several additional switches for
use with unusual video adapters or modes. They are:

  foreign - For VGA monitors on which soft character fonts
            (usually foreign character sets) are destroyed when
            LANSelect pops up.

  model30 - For kaleidoscope color problem that is usually
            experienced on Model 30's and 50's on token ring or
            arcnet networks with non-IBM network cards.
            This switch tells LANSelect to use an intermediate
            buffer for saving and restoring video memory. It is
            slower than the default method.

  nobeep  - Another switch that has been included in the latest
            release of the product is one that will disable the
            "BEEP" that occurs each time the hot keys are
            Pressed. This switch must be used when loading
            LANSelect, it will not work if LANSelect is already
            resident.

  noecb   - Use this switch when you are unable to communicate
            with a workstation that is on the other side of a
            bridge and you are using Novell's ODI drivers. This
            switch will not try to avoid IPX Event Control
            Blocks when swapping out memory.  Therefore, load
            any TSRs, such as USER, that open IPX sockets
            before loading LANSelect.

  noshift - This switch is used to disable the "no-fail" hot
            key combination <ctl>+<alt>+<l_shift>+<r_shift>.
            This is a hot key combination That was included
            because it was not easily masked out by other
            applications (other combinations can be easily
            masked out). This switch must be used to load
            LANSelect, it will not work if LANSelect is already
            loaded.

  oddherc - If your Hercules adapter type screen goes blank
            when you exit from the popped up LANSelect, try
            this switch.

  oldega  - If your EGA screen goes blank when you exit
            LANSelect, try this switch.

  oldvga  - For VGA monitors that flip out after hitting the
            hot key.  Their old BIOS doesn't properly support
            int 10h function 1ch.

  win     - For use with Microsoft Windows on Hercules graphics
            cards. This switch will tell LANSelect to assume
            Windows is loaded if it finds that the Hercules
            card is in graphics mode, but the BIOS data does
            not indicate that it is.  It will work on Hercules
            and true compatibles.

  win30   - for use in Enhanced Windows (v3.0 only) to allow
            proper printing. Users using Microsoft Windows 3.1
            should not have to use this switch.

To use any of the above switches, simply put the word on the
command line when loading LANSelect or changing LANSelect parameters. LANSelect will display a response to each of the switches.


The easiest way to load the TSRs is from the system login
script. This should only be done when using a login
supplement such as Intel's Login Supplement, LOGIN.COM.
Otherwise, if you try loading a TSR from a login script, the
computer's free memory will be severely fragmented.

LOGIN.COM should be copied to the same directories where you
have LOGIN.EXE. Then you can modify your system login script
to load the needed TSRs.

OK4TSRS.EXE is a program included with LANSight which is used
for checking available memory. When combined with LOGIN.COM it
will help make sure TSRs are loaded properly when run from a 
login script.

The following example shows a typical section in a system login
script.

EXAMPLE
-------

  REM The following lines check to see if there is memory
  REM to load TSRs (i.e. LOGIN.COM was run)
#FS2\SYS:LOGIN\LANDESK.101\OK4TSRS>NUL

IF "%ERROR_LEVEL"="0" THEN
    REM Load a 6K TSR required for LANSight
  #FS2\SYS:\LOGIN\SIGHT\USER
    REM Load a 5K TSR used for Chat and File Transfer
  #FS2\SYS:\LOGIN\SIGHT\LANSEL /t=FS2\SYS:\LOGIN\TEMP

ELSE
    WRITE " "
    WRITE "OK4TSRS.EXE did not find space to load TSRs."
    WRITE "Make sure LOGIN.COM is in the same directory as
          LOGIN.EXE."
    WRITE "TSRs Not Loaded!"
    PAUSE
END


You can use LOGIN.COM and OK4TSRS to load other TSRs as well.
Or, if you prefer, you can exit to a batch file and load the
TSRs. The main advantage of loading TSRs from the system login
script is that the system administrator can control which TSRs
are loaded during login, but users still get to use their
 personal login scripts. An exit statement in the system login
script prevents personal login scripts from running, and an
exit statement in a personal login script can be modified
without the administrator's knowledge. LOGIN.COM is offered as
one possible solution for this dilemma.


===============================================================
2f)  CONFIGURATION--SETTING UP LANSELECT (OPTIONAL)
===============================================================
This section describes the procedure for installing and
configuring LANSelect.  If you do not have LANSpool or
LANSelect, follow the instructions found in the first section
of this file (SECTION 1). If you have LANSpool, follow the
instructions found in the second section of this file (SECTION 2). If you have the full version of LANSelect, refer to the
LANSelect documentation for instructions on adding the LANSight
program to your LANSelect menu.

GENERAL INFORMATION
-------------------
Here's how to make LANSelect work in Enhanced and Standard
Windows:
1)      At installation time, place LANMENU.PIF and WLANSEL.EXE
       in the WIN subdirectory (where win.com is located).

2)      Place "WLANSEL.EXE" on the "run= " line in the WIN.INI
        file.

3)      Every time you boot up, load LANSEL.EXE as usual,
        before entering Windows. This way it is available for
        pop up while not in Windows. It is also necessary for
        WLANSEL to work properly with some applications.

4)      If you want to pop up LANSelect, you must use 
        SHIFT-SHIFT-CTRL-ALT while in Windows. Features of
        Sight that require LANSelect will work normally.

----------------------------------------------------
SECTION 1 (If you do not have LANSpool or LANSelect)
----------------------------------------------------
This section describes the procedure for installing and
configuring the partial version of LANSelect that comes with
LANSight. Follow these instructions if you want to install
LANSelect and do not already have a full version of LANSelect
or the partial version that comes with LANSpool. If you have
LANSpool, refer to the second section of this file.

DIRECTORY FOR LANSELECT TEMPORARY FILES
---------------------------------------
When you select a utility from the LANSelect menu, LANSelect
swaps the currently-running application with the selected
utility in expanded memory.

If there is no expanded memory, LANSelect writes temporary
files on disk to store the swapped application. These
temporary filenames begin with SEL followed by a series of
letters, and have the extension .TMP.

Before installing LANSelect, you should first tell LANSelect
where you want to store LANSelect's temporary files. If you
don't specify the full path name for temporary files, LANSelect
writes temporary files to the directory from which it was run.

There are three ways to specify the directory for temporary
filenames:
 1 - set the environmental parameter TEMP in a login script or
     from the DOS prompt;
 2 - specify the full path name as an argument to the LANSEL
     command;
 3 - use the temporary path option on the LANSelect
     Administrator menu.

The first two methods, described below, ensure that the TEMP
parameter will be set consistently for each user at login time.
The third method uses a special program (SPLADMN.EXE) described
in the "SPECIFYING THE DIRECTORY FOR TEMPORARY FILES" section
 of this file.

USING THE SET TEMP PARAMETER
----------------------------
You can set the environmental parameter TEMP in a user's login
script, in the system login script, or from the DOS prompt.

To set the TEMP parameter in a login script, insert this line
in the login script, using NetWare's SYSCON utility:

          DOS SET TEMP=path

where: path is the full path name of the directory in which
LANSelect will store its temporary files.  An example of a full
path name is:

          FS1/SYS:USER\username\subdirectory

where: username is the login username for the user's home area
or personal subdirectory; and subdirectory is the name of the
subdirectory that will store LANSelect's temporary files.

To set the environmental parameter TEMP within the DOS
environment, enter the following statement at the DOS prompt:

          SET TEMP=path  <Enter>

where: path is the full path name of the directory in which
LANSelect will store its temporary files.

Setting the TEMP environmental parameter in a batch procedure
(.BAT file) ensures that this parameter will be set
automatically each time the user boots up the workstation.
Remember, you can execute a batch procedure using the EXIT statement in a login script as follows:

          EXIT "filename.BAT"

where: filename is the name of the batch file that includes the
SET TEMP parameter setting.  If you have already created a
batch file to load the USER program, you can insert the SET
TEMP command in that batch file.

USING THE LANSEL COMMAND
------------------------
Another way to set up a temporary file path is to run LANSelect
at the user's workstation using the LANSEL command with the /T
option. The LANSEL command statement can be included in the user's boot-up procedure:

          LANSEL /T=path

where: path is the full path name of subdirectory in which
LANSelect will store temporary files.  For example:

          SYS:USER\@USERNAME

Note: The literal @USERNAME is a LANSelect variable that
      represents a login username. You can use it in the LANSEL
      command statement to indicate any user's home area or
      personal directory. When the user boots up the
      workstation, LANSelect automatically uses the user's home
      area as the subdirectory for LANSelect's temporary files.

CONFIGURING LANSELECT:
----------------------
The partial version of LANSelect that comes with LANSight comes
pre configured to run the SIGHT program with the
<Ctrl>-<Alt>-<V> hot key sequence. To select a different hot
key sequence for the SIGHT program, you must run the
LANSelect Administration program (SPLADMN.EXE). This program
also enables you to:

  - designate particular user groups who may use the SIGHT hot
    key sequence
  - specify the directory that LANSelect will use to store its
    temporary files

The LANSelect Administration program includes additional
functions that are not relevant for environments where LANSpool
version 2.0 or higher is not installed. These functions appear
in the LANSelect Administration menus but they are inoperative.

To run the LANSelect Administration program, follow these
steps:

 1.  Run the LANSelect Administration program from the network
     volume and directory where LANSight programs reside, using
     the SPLADMN command. For example:

       F:\>MAP G:=FS1/SYS:LANSIGHT
       F:\>G:
       G:\LANSIGHT>SPLADMN <Enter>

     The LANSight Administrator screen is displayed.

 2.  In the window at the top of the screen, the Menu File Name
     shows the current full path name for the LANMENU.DAT file.
     This file stores the LANSelect database for your LANSelect
     menu entries. LANSight comes with a pre configured copy of
     this file, so press <Enter>.

SPECIFYING A HOT KEY SEQUENCE
To reset the hot key sequence that invokes the SIGHT program,
follow these steps:

 1.  Select the Edit Menu Entries option in the Available
     Options window and press <Enter>. The LANSelect Menu
     Entries window opens. This version of LANSelect contains
     just one entry, SIGHT.

 2.  With the SIGHT option highlighted, press <Enter>. The next
     screen shows the parameters of the SIGHT.EXE program.

 3.  Highlight the Dedicated Hot Key field and press <Enter>
    twice. The LANSelect Administration program will replace
    the V with an empty box. You can then enter a new letter as
    the third character in the hot key sequence. Note that you
    cannot change the <Ctrl> and <Alt> components of the hot
    key sequence.

DESIGNATING USER GROUPS
To limit the SIGHT hot key sequence to particular user groups,
follow these steps:

 1.  In the User Group parameter, type N if you want all
     network users to use the SIGHT program. Type Y if you want
     to restrict the SIGHT program to specific users or user
     groups. The User Group window opens. Initially, this
     window is empty. Press <Ins> to display the user groups
     already defined in your network. Select up to five user
     groups that will be allowed to pop up the SIGHT program
     with the designated hot key sequence, and press <Enter>
     (Press <F5> to mark multiple groups). The SIGHT hot-key
     sequence is now available to those users included in the
     selected user group(s).

     To restrict SIGHT program usage to selected viewers, you
     can create a special user group using the NetWare SYSCON
     utility. You can then specify this user group in the user
     group window. Refer to the NetWare Supervisor's Reference
     for instructions on how to set up a user group with
     SYSCON.

After specifying the appropriate user groups, press <Esc> to
return to the Configure options window.

SPECIFYING THE DIRECTORY FOR TEMPORARY FILES
--------------------------------------------
You can use the LANSelect Administration program to specify the
temporary directory where LANSelect will store programs that it
swaps out of memory. Note, however, that there are two other
methods to specify this directory without using the LANSelect
Administration program. Please see the sections "USING THE SET
TEMP PARAMETER" and "USING THE LANSEL COMMAND" above for a
description of these two other methods.

If you decide to specify the temporary file directory through
the LANSelect Administration program, follow these steps:

 1.  Highlight Configure on the LANSelect Administration main
     menu, and press <Enter>. The Configure options window
     appears.

 2.  Place the selection bar on the Temporary Path option and
     press <Enter>. The Temporary File Path window opens at the
     bottom of the screen. The first time you use the LANSelect
     Administration program, this window is empty. If you leave
     this window blank, you must set the environmental
     parameter TEMP, as explained above.

 3.  Type in the full path name of the subdirectory in which
     you want LANSelect to store its temporary files. For
     example:

          SYS:USER\@USERNAME

     Note: The literal @USERNAME is a LANSelect variable that
           represents a login username. You can use it to
           indicate any user's home area or personal directory.
           LANSelect will automatically use the user's home
           area as the subdirectory for LANSelect's temporary
           files.

 4.  Press <Esc> to save your entry and return to the Configure
     options window.


IMPORTANT:
If your LANSelect version is before 1.30, delete the
LANMENU.DAT file and recreate it by running the SPLADMN program
(for runtime versions of LANSelect) or the SELADMN program (for
the complete version of LANSELECT).

If you have a large menu defined and have version 1.1 of
LANSelect, you may want to use the convert.exe program to
update your LANMENU.DAT file--it asks for a source file, and
creates a destination file of the proper version.

--------------------------------
Section 2 (If you have LANSpool)
--------------------------------

This section of this file describes the procedure for
installing and configuring a partial version of LANSelect if
you have LANSpool version 2.0 or higher on the same file
server. The procedures described in this section will enable
you to configure a LANSelect menu that includes SIGHT,
LANPRINT, STATUS, and PCONSOLE as menu choices.

NOTE: You do not need to follow this procedure if you do not
      want the ability to pop up the SIGHT program.

INSTALLING A PARTIAL VERSION OF LANSELECT
------------------------------------------
Although you have a partial version of LANSelect in your
LANSpool directory, you must replace it with the LANSelect
version that comes with LANSight. Then you must delete the
LANSelect files in the LANSight directory to ensure that there
is only one version of LANSelect on the file server.  If there
are two versions of LANSelect on your file server, you will
experience unpredictable results.

Follow these steps to install the partial version of LANSelect:

  1.  Login to the file server where LANSight and LANSpool are
      installed. You should log in as either SUPERVISOR or a
      user with supervisor equivalence.

  2.  Go to the LANSight directory. 

  3.  The partial version of LANSelect that comes on the
      LANSight system disk consists of the following nine
      files:

	    LANMENU.BIN
	    LANMENU.DAT
	    LANMENU.EXE
	    LANMENU.OVL
	    LANMENU.PIF
	    LANSEL.EXE
	    LANSEL.HLP
	    SPLADMN.EXE
	    SPLADMN.HLP

      Copy these files from your LANSight directory to your
      LANSpool directory.

  4.  Delete these same files from the LANSight directory.

  5.  Go to the LANSpool directory and run the LANSelect
      Administration program, as described in the next section.

CONFIGURING THE LANSELECT MENU
------------------------------
To configure the LANSelect menu to include LANSight and
LANSpool programs, run the LANSelect Administration program
(SPLADMN). Follow these steps:

  1.  Run the LANSelect Administration program by typing
      SPLADMN. For example:

      G:\LANSPOOL>SPLADMN <Enter>

      The LANSelect Administrator screen is displayed.

  2.  In the window at the top of the screen, the Menu File
      Name shows the current full path name for the LANMENU.DAT
      file. This file stores the LANSelect database for your
      LANSelect menu entries. If the path name is correct,
      press <Enter>. If it is incorrect, use the <Backspace>
      key to erase it, type the correct path and filename, and
      press <Enter>.

      If the file does not already exist, you are prompted to
      create it.
      Select Yes and press <Enter> to create a new file. The
      File Name window disappears and the Available Options
      window opens.

  3.  To configure the LANSelect menu for LANSight and
      LANSpool, select the Edit Menu Entries option in the
      Available Options window, and press <Enter>.
      
      The LANSelect Menu Entries window opens. Initially, this
      window shows one option: SIGHT.EXE. This option is
      already configured as a choice on the LANSelect menu.

  4.  Now you will include the menu choices currently available
      with LANSpool version 2.0 installation. If you previously
      configured the LANSelect menu with LANSpool version 2.0
      options, you must configure the menu again when adding
      LANSight.
 
      To see which programs you can include in the menu, press
      <Insert>. The Available Programs window opens.

  5.  Notice that the programs provided with LANSpool version
      2.0 are available with your LANSight package. Highlight
      each program you want to appear as a LANSelect menu
      choice, and press <Enter> (press <F5> to mark multiple
      programs). After you press <Enter>, the Available 
      Programs window closes and the program(s) you highlight
      move to the LANSelect Menu Entries window.
 
  6.  To remove any one of these programs from the LANSelect
      menu, highlight the program to be removed and press
      <Del>. You are prompted to verify the deletion. Select
      Yes or No in response to the prompt. If you press Yes,
      press <Ins> to open the Available Programs window. The
      entries you deleted will appear in this window. 

  7.  Highlight the SIGHT program option in the LANSelect Menu
      Entries window, and press <Enter>.  A new window opens 
      showing the parameters of the SIGHT.EXE program for the
      LANSelect menu.

  8.  The Program Title is already entered. This title will
      appear on the LANSelect menu. You can change it by simply
      typing in a new name. However, you cannot change the
      Executable File Name.

  9.  To change the hot key sequence, highlight the Dedicated
      Hot Key and press <Enter> twice. The LANSelect
      Administration program will replace the V with an empty
      box. You can then enter a new letter as the third
      character in the hot key sequence. Note that you cannot
      change the <Ctrl> and <Alt> components of the hot key
      sequence.

 10.  In the User Group parameter, type N to enable all network
      users to use the SIGHT program.

      Type Y if you want to restrict the SIGHT program to
      specific users or user groups.  When the User Group
      window opens the first time, it will be empty. Press
      <Ins> to display the user groups already defined in your
      network. Select up to five user groups that will use the
      SIGHT program, and press <Enter> (Press <F5> to mark
      multiple groups). The SIGHT program is now available to
      those users included in the selected user group(s).

      The SIGHT program will appear as a selection on the
      LANSelect menu only to those users included in the groups
      you specify on this screen.

      To restrict SIGHT program usage to selected viewers, you
      can create a special user group using the NetWare SYSCON
      utility. You can then specify this user group in the user
      group window. Refer to the NetWare Supervisor's Reference
      for instructions on how to set up a user group with
      SYSCON.

      After specifying the appropriate user groups, press
      <Esc>.

 11.  To edit a new menu option or to return to the main menu,
      press <Esc>. Then you are prompted to:

          Save Changes?

      Highlight Yes and press <Enter>.  The LANSelect
      Administration main menu returns.

 12.  To configure the program parameters for the other
      programs, repeat steps 3-11 for each program, as
      explained above. You can specify the Program Title,
      Dedicated Hot Keys, and User Groups for these programs.

THE CONFIGURE OPTION
--------------------
Next, you will select the Configure option in the Available
Options window on the LANSelect Administration main menu to set
up the LANSelect menu hot-keys, screen colors, temporary file
path, and the size and location of the LANSelect menu. Follow
these instructions:

  1.  Highlight Configure on the LANSight Administrator main
      menu, and press <Enter>.

  2.  To create the hot keys that users will press to display
      the LANSelect menu at their workstation, highlight the
      Hot Key option and press <Enter>. LANSelect uses a
      combination of three hot keys. The first two are already
      defined: <Ctrl> and <Alt>. Select a third key that does
      not execute another function in combination with <Ctrl>
      and <Alt> in your network.  The default hot keys are
      displayed in the window: <Ctrl>-<Alt>-<L>. Press the
      three key(s) simultaneously to create the LANSelect menu
      hot-key combination.

  3.  When you are finished, press <Esc> to save the changes.
      The Configure menu returns.

  4.  Next, place the selection bar on Screen Colors and press
      <Enter>. The left window displays color choices. The
      window in the center shows the default settings for the
      foreground and background colors. The right window
      displays the current settings for the LANSelect menu, the
      selection bar and the text that appears within the
      selection bar. The default colors for the menu are a blue
      background with a white foreground and yellow borders.

      To change the display colors, highlight the screen
      component you want to change, and type the new color
      number over the existing one. For example, to change the
      foreground text color from white to yellow, move to the
      Text field where the number 15 is displayed, and type 14
      over it. Then press <Enter>. The change is shown in the
      right menu so you can see how it looks. Repeat this
      process for all other screen components.

  5.  Press <Esc> once you are satisfied with the changes. You
      are prompted to save your changes: 

          Save changes?

      To save the color changes you made, highlight Yes and
      press <Enter>. LANSelect returns the Configure options
      menu.

SETTING THE TEMPORARY PATH OPTION
---------------------------------
You use the Configure option to specify the path name of the
subdirectory that LANSelect will use to write temporary files
when swapping an application. Temporary files are used only
when LANSelect does not find enough expanded memory at the
user's workstation.  These temporary filenames begin with SEL
followed by a series of letters, and have the extension .TMP. 
To set the temporary file path name, follow these instructions:

  1.  Highlight Configure on the LANSight Administrator main
      menu, and press <Enter>. The Configure options window
      appears.

  2.  Place the selection bar on the Temporary Path option and
      press <Enter>. The Temporary File Path window opens at
      the bottom of the screen. The first time you use the
      LANSelect Administration program, this window is empty.
      If you leave it empty, you must set the environmental
      parameter TEMP, as explained in "USING THE SET TEMP
      PARAMETER" or "USING THE LANSEL COMMAND" below.

  3.  Type in the full path name of the subdirectory in which
      you want LANSelect to store its temporary files. For
      example:

          SYS:USER\@USERNAME

      Note: The literal @USERNAME is a LANSelect variable that
            represents a login username. You can use it to
            indicate any user's home area or personal
            directory. LANSelect will automatically use the
            user's home area as the subdirectory for
            LANSelect's temporary files.

  4.  Press <Esc> to save your entry and return to the
      Configure options window.

USING THE SET TEMP PARAMETER
----------------------------
You can set the environmental parameter TEMP in a user's login
script, in the system login script, or from the DOS prompt.

To set the TEMP parameter in a login script, insert this line
in the login script using NetWare's SYSCON utility:

          DOS SET TEMP=path

where: path is the full path name of the directory in which
LANSelect will store its temporary files.  An example of a full
path name is:

          FS1/SYS:USER\username\subdirectory

where: username is the login username for the user's home area
or personal subdirectory; and subdirectory is the name of the
subdirectory that will store LANSelect's temporary files.

To set the environmental parameter TEMP within the DOS
environment, enter the following statement at the DOS prompt:

          SET TEMP=path  <Enter>

where: path is the full path name of the directory in which
LANSelect will store its temporary files.

Setting the TEMP environmental parameter in a batch procedure
(.BAT file) ensures that this parameter will be set
automatically each time the user boots up the workstation.
Remember, you can execute a batch procedure using the EXIT
statement in a login script as follows:

          EXIT "filename.BAT"

where: filename is the name of the batch file that includes the
SET TEMP parameter setting.  If you have already created a
batch file to load the USER program, you can insert the SET
TEMP command in that batch file.

USING THE LANSEL COMMAND
------------------------
Another way to set up a temporary file path is to run LANSelect
at the user's workstation using the LANSEL command with the /T
option. (Before users can run this program, you must configure
LANSelect for the network using the LANSight Administration
program. Instructions are provided later in this file.) The
LANSEL command statement can be included in the user's boot-up
procedure:

          LANSEL /T=path

where: path is the full path name of subdirectory in which
LANSelect will store temporary files.  For example:

          SYS:USER\@USERNAME

     Note: The literal @USERNAME is a LANSelect variable that
           represents a login username. You can use it in the
           LANSEL command statement to indicate any user's home
           area or personal directory. When the user boots up
           the workstation, LANSelect automatically uses the
           user's home area as the subdirectory for LANSelect's
           temporary files.

MENU SIZE AND LOCATION
----------------------
To specify the size and location of the LANSelect menu, follow
these instructions:

  1.  Highlight Configure on the LANSight Administrator menu,
      and press <Enter>.

  2.  Select the Window Size/Location option. The four corners
      of the LANSelect menu appear on the screen. These corners
      indicate the position of the menu as it will appear on
      the user's screen.

  3.  To move the window to a new location on the screen, press
      the left, right, up, or down arrow key.  Pressing the
      left arrow will move the four corners one position left,
      pressing the right arrow moves it to the right, pressing
      the up arrow moves it up, and pressing the down arrow 
      moves it down.

  4.  The menu can be made narrower, wider, shorter, or longer
      by pressing <Shift> and an arrow key. To make the menu
      narrower, hold down a <Shift> key and press the left
      arrow key.  When you press these keys, the corners move
      closer together,  alternating between the left and right
      corners. To make the menu wider, hold down a <Shift> key
      and press the right arrow key. When you press these keys,
      the corners move farther apart, alternating between the
      left and right corners.  To make the menu longer, hold
      down a <Shift> key and press the down arrow key. When you
      press these keys, the corners move farther apart,
      alternating between the top and the bottom corners. To
      make the menu shorter, hold down a <Shift> key and press
      the up arrow key. When you press these keys, the corners
      move closer together, alternating between the top and the
      bottom corners.

  5.  When you are satisfied with the size and location of the
      LANSelect menu, press <Esc> to save the changes.

EXITING FROM THE LANSELECT ADMINISTRATION PROGRAM
-------------------------------------------------
To exit from the LANSelect Administration program and return to
the network prompt, press <Esc> from the main menu and press
<Enter>. You are prompted to:

          Exit  SPLADMN?

Highlight Yes to exit.  The network prompt returns.

For more information on LANSelect refer to the documentation
included with LANSight.


===============================================================
3)  KNOWN LANSIGHT PROBLEMS (5/3/93)
===============================================================

1.  You cannot view any screen in Super VGA mode or higher
    resolution. LANSight can only view standard VGA mode users
    (640x480, 16 colors) and other modes with lower resolution
    (such as EGA).

2.  Some machines with on-board VGA boards, such as the Compaq
    DeskPro 20e, will show colors on the viewer workstation
    which are different than those appearing on the host
    workstation.

3.  Going into accelerated mode causes the user or host machine
    to send out ten times the number of packets.  This will
    cause some older and slower machines to actually work
    slower than they would in non-accelerated mode.

4.  The application box for VIEWER.EXE cannot be closed by
    double-clicking the system box in the upper-left-hand
    corner or by choosing "CLOSE" in that box.  It can only be
    closed by pressing SHIFT-ESC.  This is because VIEWER.EXE
    is a DOS application running from within Windows and only
    the proper LANSight sequence to close the window will
    ensure system integrity.

5.  Some information screens, such as the Interrupt Vector
    Table, may not appear correctly when the viewer is in EGA
    mode.

6.  VIEWER.PIF is configured to initialize the screen in a
    full-screen window.  A full-screen window avoids video mode
    conflicts. You cannot, for instance, view a VGA graphics
    screen from a Super VGA non-full-screen window without
     Windows giving you an error message.

7.  It is extremely important that you only have one version of
    LANSight located on your network. You may experience
    unpredictable results when mixing multiple versions of any
    of the LANSight files.  If you currently have a version of
    LANSight, you should be sure that only the most current
    version is located on any NetWare or DOS search path.

8.  When running a Novell Access Server, you may dial into your
    network and use the SIGHT program without any adverse
    effects.  However, the USER program should NOT BE LOADED on
    any of the virtual machines in the NACS. This means that
    these "virtual stations" cannot be viewed or controlled
    using LANSight.

9.  When sighting users who are running Lotus 3.x, you should
    only use the BIOS keyboard mode.  Lotus runs in 386
    protected mode and will hang if you try to use the
    interrupt driven keyboard method.

10. The screen blank program (SCR_BLK.COM) lets the viewer
    blank out the screen of the workstation being viewed. To
    use the screen blanker, type: SCR_BLK from the DOS prompt
    at the remote workstation. To restore the screen as it
    appeared before running SCR_BLK, type: SCR_BLK
    again.
    Note: The SCR_BLK.COM program will not work for any user
          from the DOS prompt. The viewer, can run it only from
          within LANSight while viewing a workstation. This is
          not a problem, but is often misunderstood.

11. A number of problems are associated with viewing
    workstations that load an IPX version earlier than version
    2.15, or Version 3.0 shells earlier than Revision D. These
    problems are due to bugs with these versions of the IPX 
    drivers.

12. WLANSEL.EXE is a Microsoft Windows-only program that allows
    LANSelect to pop up in Windows. It does not require LANSEL
    to be loaded from DOS. When you run WKSTACFG the line RUN=
    is modified to run WLANSEL upon startup.

    There is no way to hide the WLANSEL icon, nor is there a
    way to keep users from closing WLANSEL. IF WLANSEL is not
    loaded and you sight a machine then you will not have mouse
    control. However, you can use the RUN command to load
    WLANSEL and gain mouse control.

13. If you are using Windows 3.0 with LANSight there are two
    files that are included with the LANSight Support 3.01
    package that should be manually moved into your Windows 3.0
    directory, WINHELP.EXE and WINHELP.HLP, if you do not
    choose to do it automatically in the LANSight for Windows
    installation program.

    These files are the help program Microsoft includes with
    Windows 3.1 and must be available in order to use the help
    files included with LANSight Support 3.01. They are
    compatible with Windows 3.0.

14. Using a Microsoft mouse driver 6.24 or older may not allow
    the viewer to control the user's mouse. Use a newer version
    of MOUSE.COM or MOUSE.SYS. Also, versions prior to 8.2 have
    been known to cause flickering on the Viewer side.

15. In Lotus versions 2.2 and greater, you will need to change
    your keyboard stuffing (found in LANSight Configuration
    Menu) to BIOS mode. Lotus incorporates keyboard handling
    that makes our interrupt mode unusable.

16. LANSight for Windows will not run in standard mode unless
    you load the TSR TBMI.COM (for Windows 3.0) or TBMI2.COM
   (for Windows 3.1) before going into Windows. These programs
   enable IPX-aware task switching from Standard mode and are
   supplied by Novell.

17. Mouse control will probably not work unless you have done
    the following:
       - load a mouse driver on the target station
       - load a mouse driver on the viewer station
       - load USER on the target station
       - Load WLANSEL at the target station when running
         Windows
       - Set Keyboard Stuffing to Interrupt-Driven (if that
         doesn't work then try BIOS)
       - Turn on Quick Mouse Display (if viewing EGA/VGA)
