README. Control Lab, Version 1.3, December 1995
===============================================

** This file should be read by your Computer or Network Manager **

Control Lab, version 1.3 requires a PC with at least:

a) 530KB of free conventional memory
b) 2.6MB free Hard Disk space
c) 1MB of extended memory
d) a 386SX 16MHz MS-DOS compatible PC
e) a Microsoft Mouse Driver 6.24 or a 100% compatible mouse driver
f) DOS 3.3
g) EGA display
h) an available serial port
i) If you run Control Lab under Microsoft Windows you need at least
   a 386DX 33MHz CPU.

Control Lab, version 1.3 has been tested in six networking
environments where all clients tested were running one of
the following software packages:

a) Microsoft LAN Manager 2.2
b) MicroSoft LAN Manager/X 1.8
c) Research Machines LAN Manager 2.0
d) Digital Pathworks 4.1
e) Microsoft Windows for Workgroups 3.11
f) Novell 3.12, and Novell 4.1

Microsoft LAN Manager, MicroSoft LAN Manager/X, Research Machines
LAN Manager, Digital Pathworks, Microsoft Windows for Workgroups
and Novell are registered trademarks.

Areas of special interest:

1) How to Share Printers in a Network.

In order to share multiple printers in a network, Control Lab
has the ability to keep its own printer setup file named ctrlab.cfg.
This setup file must be placed at a writeable area on a shared disk.
Therefore you must add a line (see below) to your autoexec.bat on
all the PCs where you want to run Control Lab.

Example:

set CTRLABCFG=G:\client

Please note that this example requires that G:\client exists.
Then Control Lab will place the CTRLAB.cfg file in that directory.
We recommend that you specify a directory name that reflects the
name of the actual PC. For example, you could add 'set CTRLABCFG=G:\client1'
on the first PC and 'set CTRLABCFG=G:\client2' on the second
PC and so forth.

2) How to Handle PREFERENCES in a Network.

If you add the above line to your autoexec.bat, Control Lab will
place the CTRLAB.prf file in the above directory. In this way
you will get your own private setup of the PREFERENCES in Control Lab. 

If you use the environment variable CTRLABCFG you must delete the files
ctrlab.cfg and ctrlab.prf from the directory where ctrlab is installed.

3) How to Handle Disk Access and Disk Usage.

Temporary structures:

Control Lab uses the TEMP environment variable to place a file
that is used for storing temporary structures. If the power to
your computer for any reason is cut off, this temporary file
will remain on your disk until you delete it. You will probably
not notice that the file is there because Control Lab will
start working with a new temporary file the next time it is
booted. However, it is a good idea to delete the file manually
because it takes up disk space. The TEMP environment is usually
set uplike this:

SET TEMP=G:\temp 

If you need to delete the file it should be done when nobody is
using Control Lab on the network.

MS LAN Manager/X Environments:

In some networks you will have to change the mode of the files
that are installed in the Control Lab directory into read-only.
For example, in an MS LAN Manager/X networking environments
where the server is a UNIX machine.