(c) 1993 IntraLink Corp.

This file is intended to provide suggestions made by users on optimizing
LanScan.  If you have an idea that you feel is helpful, please leave us a
CompuServe message.


Network Scanner (SCAN.EXE)
--------------------------
o Some XT's and 286/386/486 with little memory had problems
  running SCAN.EXE for extended periods of time.  A new
  switch has been added so that SCAN.EXE will restart itself
  every hour.  To do this, edit SC.BAT and add -R to the SCAN.EXE
  line.

          Example

                  SYS:SCAN\SCAN.EXE SYS:SCAN\ -R

  NOTE: The -R should have a Space before it.


o In the Log Files Scan, include the System Login Script
  SYS:PUBLIC\NET$LOG.DAT  and flag it to alert you if the
  file changes size.  This is helpful if you have more than
  one Lan person and they modify this file without telling you
  (i.e.  you will be alerted if they modify it).
  Submitted by Juliette Correa/IntraLink

o If you are using RPRINTER:
  For those queues pointing to RPRINTER defined printers, create
  an unattended batch job which uses SEND to send a message to
  the user who normally resides at the PC where the printer
  is attached to.  If the Queue times out, chances are the RPRINTER
  TSR may have been locked up.  For this queue definition in MANAGE.EXE/
  Print Queues to Scan, have that queue run the unattended batch job.
  This way, the you can automatically ask the user to reboot the PC or
  take whatever action may be necessary.
  Submitted by John Campbell

o For those of you that run SCAN.EXE all night long and maybe even run
  unattended batch jobs, you may want to have it page you at some point
  to show you that the program is still running.  There are several ways
  to do this.  The first way is run PA.BAT and schedule a page for you
  at a certain time.  The other ways is to create an Unattended Batch
  Job which calls the PAGE.EXE program.  You must know the order number
  if your pager in the Pagers\Users to alert table.  Let's say it was the
  third entry.  Do have it page the third entry to call 55-1212, you would
  create an Unattended Batch Job that would include the following command:

                PAGE 3 5551212

  You would also instruct this job as to when to run.
  Submitted by Tim Echeverria/IntraLink


o Distributed Processing

  In many cases, SCAN.EXE can be setup as a pseudo-distributed processing
  environment.  If there a tasks that you would like to start from a
  workstation but not run there, you can set up the tasks as Unattended
  Batch Jobs.  Instead of telling the job WHEN to run, fill in the
  File to start... field with a file name on the network.  The idea is
  to somehow have the workstation create the file when the time comes
  to run the task.  SCAN.EXE will see that the file has been created
  and start the task.  REMEMBER, when defining the commands for the
  batch job, make sure that the last command in the batch job
  deletes the file!

  Submitted by Sam Gridley/Hyatt Hotels



Node Scanner (LANSCAN.EXE)
--------------------------

  Some users are reporting a "Low Memory" message when LANSCAN.EXE runs.
  Several factors can cause this such as TSR's loaded at the workstation
  prior to LANSCAN.EXE running.  However, one solution is to move the
  LanScan commands that are in the System Login Script to a batch file
  and have the System Login Script exit to the batch file.  This frees
  up the memory taken up by the System Login Script before LANSCAN.EXE
  is run.
  Submitted by Bob McNeil/McNeil Consulting



Manager (MANAGE.EXE)
--------------------






