-------------------------------
RELEASE NOTES FOR LANSight V4.0
-------------------------------

This file contains information about LANSight that was 
not availible in time to be included in the manuals or 
in the online help.

The following topics are discussed in this file.

**  UPDATING NETWARE WINDOWS DRIVERS

1.  WHAT'S NEW IN LANSight V4.0
2.  KNOWN LANSight PROBLEMS 
    2.1  Video mode related problems
    2.2  Mouse & keyboard control problems
    2.3  USER TSR conflict with NetSatFax
    2.4  Network driver version dependencies
    2.5  Problems with Netware VLMs
    2.6  Miscellaneous problems
3.  SETTING UP LANSight
    3.1  Setting up the server
    3.2  Loading the TSRs
    3.3  Setting up LANSELECT (optional)
4.  CONTROLLING WORKSTATIONS THAT USE PREVIOUS VERSIONS OF USER.COM

**  UPDATING NETWARE WINDOWS DRIVERS
------------------------------------
The Windows network driver VIPX.386 installed by WKSTACFG.EXE may
not be compatible with some older versions of IPX.COM. Furthermore,
the demands of LANSight may exceed the capabilities of IPX.COM.
You are encouraged to replace IPX.COM with the latest IPXODI drivers.

1.  WHAT'S NEW IN LANSight V4.0
-------------------------------
The following features have been added to LANSight since V3.1.

* New Windows viewer that allows remote control of stations in
  high resolution modes (svga modes)
* New quick search function in network view
* New switches with USER.COM
  -- loadhigh - load user into high memory
  -- permission - force user permission to be on
  -- fixed - disable user remove capability

2.  KNOWN LANSight PROBLEMS (10/27/93)
--------------------------------------------
2.1.  Video mode related problems
---------------------------------
1.  You cannot view any screen in Super VGA mode or higher
    resolution unless the workstation is running Windows.
    LANSight can only view standard VGA mode users (640x480,
    16 colors) and other modes with lower resolution (such
    as EGA) while the user is in DOS.

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.  Some information screens, such as the Interrupt Vector
    Table, may not appear correctly when the viewer is in EGA
    mode.

4.  If you are using ATI's video driver, you need to disable Crystal
    Font for LANSight to work accurately.

5.  For some video cards, when you switch between video modes, you might
    get the message "Unable to set timer" when you try to remote control
    the station when it is running Windows.  You need to exit Windows 
    and reboot your machine and try it again.

6.  For some video cards, when it is in 256 color mode and it is being
    viewed by a 16 color device, some colors might show up differently.  
    To get better color translation, you need to create a file name 
    WUSER.INI in your Windows directory and put in this line 
    "Fix16ColorBitmaps=ON".

IN GENERAL:

If you are having color problems while viewing a machine in SVGA mode, try
switching to Standard VGA mode.  If your problems go away when you are in VGA
mode, you need to make sure that you have the latest drivers for your video
card.

2.2 Mouse & keyboard control problems
-------------------------------------
1. 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 WUSER 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)

2. WUSER.EXE is a Microsoft Windows-only program that allows
   you to control a workstation running in Windows using the
   quick viewing technology. When you run WKSTACFG, WUSER is added 
   to Windows' Startup group.

   IF WUSER is not loaded and you sight a machine in Windows
   then you will not have mouse control and you will not be able
   to view a machine in SVGA mode.  However, you can use 
   the RUN command to load WUSER and gain mouse control.

3. 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.

4. 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.

5. If you are using BIOS as your keyboard stuffing method while viewing
   a server, CTRL-ESC will not work.  Change your keyboard stuffing mode
   to Interrupt Driven, and all the hot keys will work.

6. If you are viewing a NetFrame, you need to set your keyboard stuffing 
   to BIOS mode.


2.3.  User TSR conflict with NetSatFax
--------------------------------------
1.  There is a conflict in loading USER.COM TSR and the TSRs for 
    NetSatFax.  You need to load the TSRs in the following order:
    (1) FAXNODE
    (2) USER.COM
    (3) FAXPOP


2.4. Network driver dependencies
--------------------------------
1.  WKSTACFG copies VIPX.386 version 1.15 dated 5/11/93 to your Windows/System
    directory.  The VIPX.386 comes from Novell and it solves a deadlock problem
    when you enter a DOS box within Windows.  

    Novell officially ceased maintenance on the dedicated IPX driver (IPX.OBJ)
    version 3.10 dated 11/21/91.  The last version of VIPX supports IPXODI.COM
    only.  It is strongly recommended that you update your dedicated IPX driver
    with IPXODI.COM when using versions of VIPX later than 1.10.


2.5.  Problems with Netware VLMs
---------------------------------------
1.  Print Capture information is not available for workstations running 
    Netware VLMs.
 
2.  LANSEL is fully compatible with Intel's LANSpool FAX.  However, LANSpool
    does not work with NetWare VLMs.  

2.6.  Miscellaneous problems
----------------------------
1.  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.

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

3.  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.


3.  SETTING UP LANSight
-----------------------------
3.1.  Installation--setting up the server
-----------------------------------------
If you want to use LANSight to remotely control a 
server you must manually copy USER.VAP or USER.NLM from 
the LOGIN\LANDESK 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.

3.2.  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 may be loaded in upper memory but LANSEL may not.

USER command options:
USER [-?] [-remove] [-nomouse] [-oldega] [-snow] [-loadhigh] [-stealth]
     [-permission] [-fixed]

where:

remove       removes USER.COM from workstation memory
nomouse      disables mouse support
oldega       avoids reading EGA registers
snow         avoids snow on CGA displays
loadhigh     loads user in upper memory
stealth      loads without showing the copyright banner
permission   access allowed with user permission only
fixed        forces USER.COM to be non-removable

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

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.

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. If you run the install for LANDesk Manager 1.5, the
TSRs will be added to your system login script automatically.

3.3.  Configuration--setting up LANSELECT (optional)
----------------------------------------------------
This section describes the procedure for installing and
configuring LANSelect.  

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

 2.  Add "WUSER.EXE" to Windows' Startup group.

 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
     WUSER 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.

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 two 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;

The two methods, described below, ensure that the TEMP
parameter will be set consistently for each user at login time.


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.


4. CONTROLLING WORKSTATIONS THAT USE PREVIOUS VERSIONS OF USER.COM
------------------------------------------------------------------
Care has been taken to ensure basic compatibility with previous versions
of LANSight or Desktop Access.  LANSight v4.0 can control
workstations that run version 3.01 or later of USER.COM.  If you would
like to control a workstation that uses a previous version of USER.COM,
please configure LANSight using the Tools | Control Options | 
3.01 Control Parameters dialog in LANSight.  This dialog is the
equivalent of the Tools | Control Options | Control Parameters dialog
in LANSight 3.01. For more information about this dialog please see your
LANSight Support v3.01 User's Guide.

