OS/2 Shareware BBS: 8 Other/08-Other.zip/lcf103.zip/ReadMe.INF

OS/2 Help File | 1994-01-09 | 33KB | 506 lines

ΓòÉΓòÉΓòÉ 1. Copyright/Contacting ForeFront ΓòÉΓòÉΓòÉ

(C) Copyright 1993 ForeFront Software Inc.  All rights reserved.

ForeFront Software Inc.
2202 2 Ave. N.W.
Calgary, Alberta
T2N 0G9

Phone:      [phone]

Fax:        [phone]

CompuServe: 73110,722

LCF is supported on CompuServe in section 1 of the OS2 Vendor A forum (GO
OS2AVEN).

Please title any notes left in that section with the keyword LCF.  Also address
them to the above CompuServe id to assure that they are easily found by the LCF
support team.

The LCF is also supported by phone or fax at the above numbers.


ΓòÉΓòÉΓòÉ 2. Quick LCF Overview ΓòÉΓòÉΓòÉ

If you are new to the LCF, here is a quick overview of how the facility is
installed and used:

Installing the Code Server
Creating a Seed Diskette
Setting up the reference system
Taking an image of the reference system
Creating the Scripts and Model Configuration Files
Distributing the Image


ΓòÉΓòÉΓòÉ 2.1. Installing the Code Server ΓòÉΓòÉΓòÉ

The LCF code server is installed on a machine from the LCF distribution
diskette.  This is done by using the INSTALL.CMD command file found in the root
of the diskette.  Read the rest of this README.INF before proceeding with this.

Actions 1 to 5 and 7 on the INSTALL menu need to be performed before the
facility can be used.  Action 4 loads some of your OS/2 licensed material and
action 5 is used to load you LAN support software.  Actions 4 and 5 may be
performed for both OS/2 2.0 and 2.1 if required.  When performing action 7 you
will need to contact ForeFront Software to obtain your authorization key for
the trial.

The code server can be started after these actions have been performed.


ΓòÉΓòÉΓòÉ 2.2. Creating a Seed Diskette ΓòÉΓòÉΓòÉ

A seed diskette is created to allow OS/2 to be booted from floppies.  This is
one of many ways by which locked OS/2 files are avoided.  It will be used when
running the Installation Verification Procedure (IVP).


ΓòÉΓòÉΓòÉ 2.3. Setting up the Reference System ΓòÉΓòÉΓòÉ

A reference system is set up.  This is an OS/2 system with any services and
applications you want installed on your target machines.  It is this system
which will be replicated.


ΓòÉΓòÉΓòÉ 2.4. Taking an Image of the Reference System ΓòÉΓòÉΓòÉ

LCF is started on the reference system from the seed diskette created earlier
and the TAKEIVP.SCR script is run.  This script takes an image of a specified
partition of the reference machine and uploads it to the code server.


ΓòÉΓòÉΓòÉ 2.5. Creating the Scripts and Model Configuration files ΓòÉΓòÉΓòÉ

Next a script and corresponding model configuration files are created for use
in installing the image.

The IVP attemps to skip this task by providing a generalized script and model
configuration files (mcf's) to handle differences in network adapters, channel
types and other hardware factors between your reference system and the target
systems.  This is not always 100% successful, if the IVP script and mcf's do
not produce the correct results you may have to modify them for your
environment!

When creating your own scripts, you usually use the IVP script and mcf's as a
model.


ΓòÉΓòÉΓòÉ 2.6. Distributing the Image ΓòÉΓòÉΓòÉ

Target machines are booted with the seed diskette and the INSTIVP.SCR script is
run to install the image.

In real LCF use, it is not always necessary to run the LCF client from seed
diskettes.  The client program can be started by running the Boot Strap program
from some other partition, or the LCF Agent can be used to start it.  Also, one
can image individual packages -- as opposed to whole partitions.  What is
imaged and how it is installed and reconfigured is all controlled by the LCF
script commands which run at the client (on the reference system when imaging,
at the target when installing).


ΓòÉΓòÉΓòÉ 3. Note on the Trial Version ΓòÉΓòÉΓòÉ

The trial expires 30 days after it has been authorized.  You authorize it by
calling ForeFront Software to obtain a trial key which is entered during action
7 of the installation process.

Once the first part of the LCF Installation (which is described in this file)
is completed, you should carefully review the legal agreement which accompanies
this trial.  This information can be found in the section entitled "LCF Legal
Information" in the LCFDOC.INF book.  The first part of the installation will
install this book in the LCF folder on your OS/2 desktop.

When you have completed the trial you need only obtain a new authorization key
from ForeFront Software to convert your LCF to production.  Any work you
perform in tailoring the trial to your environment is thus preserved.  When
obtaining the new authorization key you may chose to license up to 32
concurrent accesses for each code server and you can select the code server
name at that time (this name is OS2BENCH in the trial).

If you forget when your trial expires, you can look at the date contained in
the \LCF\BIN\SERVER\OS2BENCH.AUT file.  This file contains the authorization
data for the LCF and cannot be directly changed without obtaining a new
authorization key.  After authorizing the LCF it is a good idea to backup this
file.


ΓòÉΓòÉΓòÉ 4. LCF First Time Installation ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 4.1. Overview of the Installation ΓòÉΓòÉΓòÉ

The procedure contained in this section describes how to install this release
of the LCF for the first time.  If a previous release or level of the LCF has
already been installed on the PC then you can simply upgrade it by following
the procedure outlined in the LCF Upgrade section of this book.

The REXX installation command file provided on the diskette(s) received from
ForeFront Software will set up a code server on a workstation.  It will also
create a directory structure which will be used for storing packages, scripts
and other LCF data.

The section which follows will guide you through the installation of the code
server.  After you have completed the installation instructions in this file,
you will be directed to proceed with the instructions contained in the
"Continuing the LCF Installation" section of the LCFDOC.INF book which will
have been placed in the LCF folder on the code server.

The LCFDOC.INF book also contains instructions on installing some of the LCF's
optional features such as Name Resolution Services, the LCF Agent and Mini-OS/2
systems.  These optional installations options should be performed only after
you have successfully run the Installation Verification Procedure (IVP).


ΓòÉΓòÉΓòÉ 4.2. Program Requirements ΓòÉΓòÉΓòÉ

The following tables should be consulted in selecting workstations for use as
LCF code servers and used to determine which workstations are eligible for LCF
services.


ΓòÉΓòÉΓòÉ 4.2.1. Hardware Requirements ΓòÉΓòÉΓòÉ

LCF Code Server

 Minimum  8 MB of main memory.

 8 MB of hard disk space (when fully installed) plus an amount equal
 to the size of the images being stored.  Images are not compressed.

LCF Client (Target Workstation)

 Requirements dictated by software being installed.

 OS/2 2.x install requires 6 MB

LCF Agent

 500K hard disk space.


ΓòÉΓòÉΓòÉ 4.2.2. Software Requirements ΓòÉΓòÉΓòÉ

LCF Code Server
  OS/2 2.x with REXX support installed.

LCF Client
  OS/2 2.x

LCF Agent
  OS/2 2.x


ΓòÉΓòÉΓòÉ 4.2.3. Networking Requirements ΓòÉΓòÉΓòÉ

All Components

  NetBIOS (available with LAN Requester, Extended Services,
      NetWare Requester, etc.)


ΓòÉΓòÉΓòÉ 4.3. Installation (Part 1) ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 4.3.1. Server Machine Selection ΓòÉΓòÉΓòÉ

The previous Program Requirements section should be consulted for selecting a
workstation for use as the LCF code server.

The most important requirement for a code server is that the hard disk is large
enough to hold the packages.  LCF packages are not compressed.  The package
occupies the same amount of storage at the code server as it does on its source
system.  The LCF Server and Client programs are light users of CPU, memory and
the LAN.  The LCF process is often constrained by its access to the hard disk
at both the server and client.  Therefore, a fast code server hard disk can
make a significant speed difference.


ΓòÉΓòÉΓòÉ 4.3.2. HPFS vs. FAT Issues ΓòÉΓòÉΓòÉ

If the code server is to store images taken from an HPFS drive, the drive on
which the server is installed should be using the HPFS file system.  OS/2
images taken from a FAT drive can be stored at the code server on an HPFS drive
and later installed on a FAT drive without problems.  The reverse however,
where an HPFS image is stored on a FAT drive is not always possible.


ΓòÉΓòÉΓòÉ 4.3.3. Installing the Code Server and non-LCF Licensed Material ΓòÉΓòÉΓòÉ

The installation process copies all the necessary files from the ForeFront
distribution diskette(s) to a specified directory on the code server.  However,
some of the files required by the LCF are not on the LCF distribution media,
but rather are files provided by IBM's or other vendor's distribution media.
The installation command file extracts these files -- the licensed material
from their respective distribution diskettes.  Therefore, in this step of LCF
Installation you will require:

o The LCF Install diskette(s).

o The OS/2 Distribution diskettes.

o Your LAN software's distribution diskettes. (required for LS 2.0 and LS 3.0,
  but not required for NetWare)

The LCF provides an installation command file, INSTALL.CMD to install the LCF.
The INSTALL.CMD file is restartable, so LCF components may be re-installed or
configured at any time.

The first part of LCF code server installation involves copying and
decompressing the LCF distribution files.  This is done as follows:

 1. Insert the LCF Install diskette in the diskette drive and issue a change
    drive command to that drive.

 2. Enter the following to run the INSTALL.CMD file:

      INSTALL

 3. Select action 2, "Unload LCF product from the distribution diskette".

 4. When prompted, enter the correct drive to install the LCF on.

 5. Select the version and type of NetBIOS that you will use with the LCF.  If
    you select NetWare's NetBIOS simulator then you should review the "LCF and
    NetWare" section of the LCFDOC.INF book before you start the LCF code
    server.  This book will be available in the LCF folder as soon as this
    action and the next (action 3) have been completed.

Next create an LCF folder on the Code Server's desktop.  This folder will
contain icons to access the LCFSERV program, as well as the on-line
documentation.  To do this:

 1. Run INSTALL.CMD (see the previous steps 1-2)

 2. Select action 3, "Set up LCF folder and icons on Desktop"

Some special files from the OS/2 licensed materials must now be loaded into the
new directory structure at the code server.  INSTALL.CMD will require your OS/2
distribution media to extract these files.  This extraction of files from OS/2
and LAN distribution diskettes should not be confused with taking an image of
an OS/2 system.  The OS/2 and LAN files are required in creating seed diskettes
and the MINIOS2 system, described later in the second part of the installation
process.  They are not sufficient by themselves to form an OS/2 system that can
be installed on a target machine.  To incorporate these OS/2 elements:

 1. Run INSTALL.CMD (see steps 1-2 at the beginning of this step)

 2. Select action 4, "Load OS/2 Licensed Material"

 3. When prompted select the correct version of OS/2 that will be used.  If the
    LCF will install both versions 2.0 and 2.1, you should run this action
    twice, once for each release of OS/2.

 4. If you selected to install OS/2 2.1, a prompt will ask whether your copy of
    OS/2 2.1 had blue or salmon (pink) diskette labels.  OS/2 2.1 was shipped
    with two different compression schemes and each must be decompressed in a
    different way.

 5. When prompted, enter the source drive of the OS/2 diskettes or other
    installation media (i.e. CD-ROM).  For a diskette, this may be either the A
    drive (A:) or the B drive (B:)

 6. The LCF will now prompt the user for some of the OS/2 diskettes.  If CD-ROM
    was selected, then the LCF will display its progress as it accesses the
    different diskette images on the CD.

The last part of this installation step loads the LAN licensed materials.  If
the selected LAN package is LAN Server, then the installation command file will
prompt the user for certain diskettes.  However, if the LAN package is Novell's
NetWare, then all that is required for this step of the installation is to
point the install command at an existing NetWare directory.

For other LAN operating systems you will need to load the LAN material by hand
and you may have to create directories at the code server to hold it.  Then the
scripts and model configuration files will have to be modified to reference
these.  LAN Manager users should consult the "LCF and LAN Manager" special
notes in the LCFDOC.INF book.

If the LCF is to install multiple versions of OS/2, then the installation
program's "Load OS/2 Licensed Material" step will need to be run for each OS/2
version.

Note that the LCF scripts, as distributed, can only support one version of IBM
LAN Server at a time for a given OS/2 version.  This is because both versions
2.0 and 3.0 of LAN Server share the same directory structure under the OS/2
version directory.  The LCF scripts can be changed if this is a problem.

To incorporate LAN Access:

 1. Run INSTALL.CMD (see steps 1-2 at the beginning of this step)

 2. Select action 5, "Load LAN Licensed Material"

 3. From the menu, select which LAN package to load.

 4. The LCF will now prompt the user for the LAN package diskettes or the path
    of an existing LAN system in the case of NetWare.


ΓòÉΓòÉΓòÉ 4.3.4. Authorizing the Trial ΓòÉΓòÉΓòÉ

This step involves contacting ForeFront Software to obtain an authorization key
for your trial.  It can be performed any time after action 2, "Unload LCF
product from the distribution diskette", of the installation process has been
completed successfully.  If you are unable to immediately obtain the
authorization key, you can come back to this action later without any need to
rerun the previous actions.  In fact, you may temporarily skip this step and
continue with the rest of the installation process up to where the code server
needs to be started.

To authorize your trial:

 1. Run INSTALL.CMD (see steps 1-2 of the previous section)

 2. Select action 7, "Authorize the LCF to run."

 3. At the menu asking if you want to authorize a trial or production system
    enter 1 to select authorization of a trial.

 4. After the next menu is presented, you will be prompted to enter your
    company or organization name.  Enter from 12 to 50 characters of
    information. The company name is combined with the trial expiry date, code
    server name and number of concurrent accesses to form a checksum which will
    be updated on the menu once the company name is entered.

 5. Next contact ForeFront Software to register your trial.  You will be given
    an authorization key which is based on the values shown in the menu.  When
    relaying the information on the menu be carefull to note capitalization and
    spaces in your company name as these will affect the checksum and
    authorization key.  This is especially important to note if you are sending
    CompuServe mail to obtain the key.  You must relay the code server name,
    expiry date, number of accesses, company name and the checksum in order to
    have a key generated.  If you are sending CompuServe mail also include your
    name, mailing address, phone number and fax number with the request.


ΓòÉΓòÉΓòÉ 4.3.5. Continuing with the Installation ΓòÉΓòÉΓòÉ

Because this README.INF book was not compressed on the LCF distribution
diskette, only the first part of the installation is contained here.

If you are doing a reinstallation of a new release or level of the LCF then the
upgrade is complete and you may restart the code server and proceed with the
LCF as before.

If this is a new installation you must now go and open the LCFDOC.INF book and
continue with the installation instructions contained there.  The instructions
there will guide you through the setting of LAN parameters for your code server
and will allow you to create a seed diskette which the Installation
Verification Procedure (IVP) will use.  The IVP will perform your first
installation of an OS/2 system and familiarize you with LCF use.  It is highly
recommended that you perform the IVP.


ΓòÉΓòÉΓòÉ 5. LCF Upgrade ΓòÉΓòÉΓòÉ

The procedure contained in this section describes how to upgrade a previous
release or level of the LCF which has already been installed on a PC.

The release and level contained in the ZIP files or diskettes that correspond
to this README.INF file is LCF Version 1, Release 1, Level 3 or V1R1L003 for
short.  This release and level is the one that is distributed in the LCF103.ZIP
file found on CompuServe and other BBS's.  V1R1L000 was previously distributed
in the LCF100.ZIP file and levels 1 and 2 has been shipped to selected
customers.  The programs and scripts previously distributed in LCFDOS.ZIP on
the BBS's are now included in this release.

To upgrade to a newer release or level:

 1. Finish reading this README book.  Make sure you look at the summary of
    changes contained in the next section.

 2. Stop all LCF code servers which access this PC's \LCF directory.

 3. Backup your current \LCF directory structure.

 4. Run the new INSTALL.CMD for the new release and level.

 5. Select action 2, "Unload LCF product from the distribution diskette".  This
    will unload all programs, scripts and samples.  It will overwrite any
    changes you may have made to the previous LCF material.

 6. Restart your code server(s) and proceed to use the LCF.  You own scripts
    and model configuration files will not be affected by this upgrade if they
    have names other than those used by our samples.  Packages you have
    previously taken and your authorization code will not be affect.


ΓòÉΓòÉΓòÉ 6. LCF Update Description ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 6.1. Changes for V1R1L001 ΓòÉΓòÉΓòÉ

o The LCFBOOT and LCFDIRSR programs were added to support the installation of
  DOS and DOS-OS/2 dual boot systems.  The TAKEDOSW and INSTDOSW sample scripts
  where included to show how the programs are used to adjust non-OS/2 boot
  records.  The use of these programs is mandatory when DOS or dual boot
  systems are installed by replication with the LCF.

o The BIOSID utility program was added to easily determine a machine's BIOS
  model and submodel identification.


ΓòÉΓòÉΓòÉ 6.2. Changes for V1R1L002 ΓòÉΓòÉΓòÉ

o The INSTIVP script was changed to handle ABIOS.SYS properly.  The ABIOS.SYS
  taken from the installation diskette was being overwritten by the one in the
  image.  This sometimes caused failures when the reference system and target
  systems were dissimilar PS/2's.


ΓòÉΓòÉΓòÉ 6.3. Changes for V1R1L003 ΓòÉΓòÉΓòÉ

o On script errors, the LCF program now allows the attendant to  skip the
  error, shell out to a full screen OS/2 session or quit the script.  This
  greatly help in debugging scripts.

o The OPTION command was added to allow single step tracing of scripts and
  model configuration files.  This allows an attendant to walk though the lines
  of scripts and mcf's and see the result of each.  It is possible to shell out
  to an OS/2 full screen after each and look at the audit log and LCF
  variables.

o The DELPACK command now has a /A option which allows it to delete any
  directory structure, not just LCF packages.  It can be used in scripts under
  control of the LOCAL command to optionally delete unwanted parts of a
  package.

o LCFBOOT was changed so that it can now update the BOOT.DOS or BOOT.OS2 files
  even when they are marked with the readonly, hidden or system attributes.

o DELPACK, LCFBOOT and LCFDIRSR's error messages were better documented.

o The LOCAL and CMD commands where modified so that return codes of their guest
  programs are no longer truncated to one byte (for instance 8002 was being
  shown as 66 in error messages).

o A new built-in LCF variable, BUSTYPE, was added.  This variable is
  automatically set by the LCF to the PC's channel type (ISA, MCA, EISA). The
  IVP scripts have not been changed to use this variable yet, the scripts still
  prompt the attendant for PCTYPE.

o LCF variable names are now always stored in uppercase as in OS/2 (but not
  variable values).

o OS/2 for Windows distribution diskettes and CDROM are now supported by the
  INSTALL command when loading OS/2 licensed material.

o The INSTALL command was modified to include comments on how to modify it to
  load OS/2 licensed material from OS/2 media for which it has not been
  pre-programmed.  This method can be used to install from "International
  CDROM" media.

o The INSTALL command now allows the expiry date to be changed when authorizing
  a trial.  This makes it easier to synchronize the authorization to a code we
  may have sent by e-mail or fax.

o Lan Manager restrictions have been better documented.

o Documentation was enhanced.