August 1997

Installation Notes for ISIS version 2.1.x (Windows)

(c) 1997 MDL Information Systems, Inc. All rights reserved.
Note: There is an ISIS Applications installation readme, appinst.txt,
which provides the installation notes for ISIS Applications. It
is located on the top level of the ISIS 2.1.x CDROM.
This document provides information about the following topics:
1. Recommended hardware
2. Paperless installation
3. Running ISIS 1.2 and ISIS 2.1.x simultaneously
4. Additional Readme files available
5. Installation alternatives
6. File and directory structure
7. Deinstallation instructions
1. Recommended hardware
The installation will warn you or notify you if you are attempting to
install ISIS 2.1.x onto a computer that does not meet the minimum
hardware configuration. The following table describes the minimum
hardware configuration for running ISIS and ISIS applications.
- A 486 microprocessor or higher
- 16.5 to 24 Mb of free hard-disk space for ISIS 2.1.x
- 12 Mb of RAM for Windows 3.1, 16 Mb for Windows 95, 24 Mb for Windows NT
- PostScript printer
ISIS 2.1.x installs and runs under Windows 3.1, Windows 95, or
Windows NT.
2. Paperless installation
There are no written instructions for installing ISIS 2.1.x other than
this Readme file. The installation should provide you with all the
information that you need, with the addition of a few notes in this
Readme file.
We highly recommend that you have no other applications running or
iconized during installation. The installation will be able to
complete all installation tasks automatically if this is the case.
If you do have other applications running or iconized during the
installation, any shared System files will be updated at the end of
the installation. The ISIS/Object Library registration must then be
completed manually by running the following command line after the
installation is complete:
For 16-bit ISIS/Object Library:
OLREG c:\isis21x\ISISBASE.EXE
For 32-bit ISIS/Object Library:
OLREG32 /System /Server=c:\isis21x\ISISLIB.DLL
/MDLBOX=c:\isis21x\MDLBOX.OCX /MDLDB=c:\isis21x\MDLDB.OCX
where "c:\isis21x" is the location of the installed ISIS 2.1.x. If
you have a long file name with spaces (like "Program Files"), you
 must put the parameter in quotes to pass it properly.
This registration is required to successfully run any applications
written using the ISIS/Object Library.
Any system files with read-only protection must have that protection
removed in order to complete the ISIS 2.1.x installation. This is only
necessary if the protected file has an earlier version than the
minimum version required by ISIS 2.1.x.
See the "File and Directory Structure" section of this Readme for
exactly which system files are installed and the criteria used for
installation. Shared system files require updating into the Windows/
System folder for Windows 3.1, or for Windows/System32 for
Windows 95/NT. Under these operating systems there are a few files
unique to ISIS 2.1.x (16-bit version only) that are installed into
the Windows/System directory.
The files installed into the Windows/System folder must be installed
into the Windows/System directory used by each workstation. For
network installations, this may mean these files alone must be
installed onto each workstation. See the "Installation alternatives"
section of this Readme for more details.
The installation of ISIS 2.1.x is similar to the one of ISIS 2.0
release, but also includes the installation for the ISIS Applications.
It combines the ISIS 2.0 installer and ISIS/Applications 2.0 installer
into one. The installer installs the ISIS and ISIS Application files
based on the type of seat and the databases you have licensed. You
are provided with a key, or a set of keys, for all of the ISIS seats
and the databases that you have licensed. These keys are located on
a card in your package. You will use these keys during the
installation of each seat. If you have many seats to install, see
the instructions in section 5 of these notes for several installation
alternatives to make installation easier.
This installer has been tested with Excel 5.0 and Word 6.0 on Windows
3.1 and Excel 7.0 and Word 7.0 on Windows 95/NT. These products share
some of the system files installed for ISIS 2.1.x.
3. Running ISIS 1.2 and ISIS 2.1.x simultaneously
Ensure that the following files generated by ISIS 1.2 are moved from
the Windows directory into the ISIS 1.2 directory:
tpl.cfg
isisdraw.cfg
isisbase.cfg
Ensure that these files are removed from the Windows directory
whether this directory exists on the PC hard-disk or network.
Install ISIS 2.1.x into a separate directory (ISIS21x). Copy your
tpl.cfg file from ISIS 1.2 (ISIS12) into your ISIS21x directory.
This retains any customizations you've made while using ISIS 1.2,
and ensures that when the tpl.cfg file is updated while using
ISIS 2.1.x, the file will be updated in the ISIS21x directory
rather than be written to the Windows directory.
This arrangement will allow you to run ISIS 1.2 from the ISIS12
directory, and ISIS 2.1.x from the ISIS21x directory, without any
conflicts, except you can't run mixed versions simultaneously (not
even Base 1.2 and Draw 2.x), or the ISIS/Add-in Manager dies with
fatel error messages.
4. Additional Readme files available
There is an ISIS 2.1.x Readme file for the ISIS/Base and ISIS/Draw
programs, called ISISREAD.TXT. The AIMREAD.TXT file contains
information about the ISIS/Add-in Manager. The SARADDIN.TXT file
has the information about ISIS SAR Table and ISIS/Add-ins. The
APPINST.TXT file provides the installation notes for ISIS
Applications. The APPINST.TXT file is located on the top level
of the ISIS 2.1.x CDROM.
In the Development seat, there is also an ISIS 2.1.x Developer's
Readme file, called ADK_READ.TXT. These files are located under the
ISIS21x directory (or whichever directory you specify during the
installation).
These Readme files contain late-breaking information about improvements
and limitations. We recommend that you read them prior to using
ISIS 2.1.x.
5. Installation alternatives
There are several alternative methods for installing ISIS 2.1.x. This
section describes the options and the steps necessary to perform each
option, and the positives and negatives of each option. Use the
information in this section to determine what method of installation
will best serve the needs of your organization. The options are
listed approximately in order of complexity.
A. Install from CD on each workstation.
B. Copy the installer files onto the your network disk server and allow
each user to run the installer and load the files onto their
workstation.
C. Install ISIS 2.1.x onto your network.
D. Distribute ISIS 2.1.x via your internal web.
E. Install some ISIS 2.1.x files onto each workstation and
some shared files onto your network.
Option A
*********
Option A requires that CDs are distributed to all users, or that
the ISIS administrator installs ISIS and ISIS applications, using the
applicable install key, on each workstation. This works well for small
numbers of workstations, but can be cumbersome for large numbers of
workstations. This is one of the simpler installation mechanisms, as
it only requires running the installer and knowing the install key for
each workstation.
Option B
*********
Option B involves copying the installation files onto your internal
network disk server and allowing each end-user to run the installer on
their personal workstation. This makes Option B relatively simple for
both administrator and end-users, so long as end-users are comfortable
with accessing the network. With this option, a log file, INSTALL.LOG,
will be created in the directory in which you copy the ISIS 2.1.x
installer files. Each time a user runs the installer, the user's
name, the date, and the seat they install (Development, Chemistry,
Life Science, or Retrieval) will be appended to this log file.
Because each user will be automatically writing into this log file,
the network directory containing the ISIS installation files and the
INSTALL.LOG file must be writable. Otherwise, this log will not be
updated and the installation will stop.
This alternative requires that the ISIS administrator:
- Copy all of the installer files from CD into a single directory.
- Create an empty file named "INSTALL.LOG" in this directory. This
flags the installer that you want to keep a log of all users who
install ISIS 2.1.x.
- Provide each end-user with the install key for the seat and the
databases they have licensed.
The end-users then:
- Run setup.exe to install ISIS 2.1.x.
- Type in their install key when prompted during the installation.
If you want to automate the install key input, read the next
paragraphs.
Also, to automate the installation, you can create an installation
data file, INSTALL.DAT, which contains the install key for each seat
and the databases that you have licensed. The INSTALL.DAT must have
the following format:
MDLI.V2 version21x
# company
# users
# comments
4-digitInstallKeyHere

"MDLI.V2" is the reserved word, and must be presented in the installation

data file. This file must be located into the same folder for the
ISIS 2.1.x installer files.
If you have more than one install keys, you need to copy the same
ISIS 2.1.x installer files into different folders for each
licensed key, and create a specific installation data file for each
license.
Option C
*********
Option C allows the system administrator to install the files on the
network for each type of seat the site has licensed, and then have
users run ISIS from each seat area. The advantage is that ISIS is
installed only 3 times (one for each non-Development seat: Chemistry,
Life Science, and Retrieval). This makes it easier to install this and
future versions of ISIS and ISIS applications.
The major disadvantage to running from the network is speed. This
alternative also requires more disk space on the network than Option
B. Also, as described, all users share the same configuration files.
If each user needs to have personal configuration files, then the
tpl.cfg, isisdraw.cfg, isisbase.cfg, and basedraw.cfg files must be
copied to the user's Windows directory. Also, the system files
required by ISIS 2.1.x must be installed into each user's Windows/System
folder.
There are two options for handling this situation:
1. Copy the system files into an "addtowin" directory on the network.
Have all users copy those files into their Windows/System folder.
Pros: This is simple.
Cons: Object Library doesn't get registered. It would have to
be done manually using OLREG.EXE or OLREG32.EXE on the
network. Version and date checking would not get done
on the system files, potentially trashing user's system
folders.
2. Copy the installer files to the network into a single directory.
Have each user run SETUP.EXE on their workstation, selecting the
ISIS/Base, ISIS/Draw, and ISIS/ADK (if applied) options. For 32-bit
Windows, do not performce any registration for Draw and Object
Library. After the completion of the installation, each user
deletes every files in the installation folder.
Pros: This installs the system files into the Windows\System
folder properly, so customer systems will be protected
properly.
OL registration occurs automatically for 16-bit
Windows if applied.
Cons: This requires disk space on each user's workstation for
the executable and other files, which would then have
to be deleted manually.
For 32-bit Windows, Object Library doesn't get
registered. It must be done manually using OLREG32.EXE
if applied.
This alternative requires that the ISIS administrator:
- On a standalone workstation, install all licensed ISIS seats
(except the Development seat) into separate directories; you can
name these directories anything. We suggest ISISCHEM, ISISLIFE,
and ISISRETR. For speed reasons, we do not recommend
installing the ISIS 2.1.x Development seat onto the network--this
should be installed on each developer's workstation.
- Copy the ISISCHEM, ISISLIFE, and ISISRETR directories onto
your network.
- Notify each user what seat they have licensed and from where
to run ISIS for their seat.
- Use one of the methods above so that user's get their system files
updated as needed.
end-users then:
- Update the system files by running the appropreciate ISIS installer.
- For 32-bit, run OLREG32.EXE to complete ISIS/Object Library
registration if you install the seat configuration.
- Run ISIS from the appropriate folder on the network disk server.
Notes for the network installation for SAR Table:
For Excel version 5.0 for Windows, the file SARTABLE.XLA must be
in the XLSTART directory under EXCEL.EXE or in the directory specified
as the Alternate Startup File Location on the Options dialog (Tools >
Options menu command, General tab).
For Excel version 4.0 for Windows, the files SARTABLE.XLL and
SARTABLE.XLA should both be installed in the XLSTART directory under
EXCEL.EXE. If you are using an Alternate startup directory with Excel 4
for Windows, the files SARTABLE.XLL and SARTABLE.ALT should be installed
in the alternate startup directory, and SARTABLE.ALT must be renamed to
SARTABLE.XLA. This cannot be done using the installation program: you
must manually copy the files to the alternate startup directory and
rename the file SARTABLE.ALT to SARTABLE.XLA.
Option D
*********
Option D applies if you have an internal web and are distributing
other software in this manner, or if you want to distribute ISIS in
this manner.
This alternative requires that the ISIS administrator:
- Copy all of the installer files from CD into a single directory.
- Create the installation data file which contains the install
key (see the format of this data file described in Option B.)
- Combine all of the installer files and the installation data file
into a single compressed file using PKZIP (available as share-ware
from the Internet).
- Create a self-extracting archive using Zip2exe (also from PKZIP).
- If you have more than one install key, repeat these steps to create
each self-extracting archive for each license.
- Publish the ISIS 2.1.x self-extracting installer archive via a HTML
download page.
The end-users then:
- Download the single file from the internal web
- From the File Manager, double click on the self-extracting archive
file to expand the installer files.
- Run setup.exe to install ISIS 2.1.x
Option E
*********
Option E involves installing some ISIS files on each user's
workstation (executables and configuration files), and installing the
support files (template, forms, settings, help, and sample) files onto
your network. This is the most complicated of the installation
options, though it does save some disk space on each user's
workstation. This option allows some files to be installed and used
on the network and other files to be installed on each user's
workstation. The files that you might want to keep on your network
include the template, forms, settings, and sample files. We do not
recommend keeping the help files on the network, as the access time
will minimize the help files usefulness. Since the on-line help is
the only documentation available to most end-users, ready and easy
access to the help files is important.
Keeping the sample databases and settings on the network means that
these files can not be modified without impacting all users.
If you are keeping any ISIS support files on the network, provide
instructions to your users as to the directories in which the support
files reside. The first time a user tries to access one of these
files (template, forms, settings, help, and sample), the ISIS program
looks for the files in or below the ISIS 2.1.x executable directory. If
they are not found (which they would not be), a dialog box prompts the
user to navigate to the directory where the file resides. The user
must navigate to the directory on the network one time, and then the
program saves the location of the file.
To set up this file configuration, install the Program only files from
the Chemistry, Life Science, or Retrieval seats onto each workstation.
Delete the Settings and Forms folders from these installations.
Install the full Chemistry seat onto your network. Delete all files at
the ISIS21x level (not the subdirectories) except perhaps the readme
files and the ISISDESK.HLP (though again, we recommend that you install
the help file on each workstation for performance reasons).
6. File and directory structure
The following sections describe the files and directories installed
into the ISIS21x directory, and the files installed into the Windows
directory. These are for your reference in understanding the
installed file structure for ISIS 2.1.x. This list does not include
all files in ISIS21x subdirectories.
Contents of the ISIS21x Directory:
16-bit ISIS Files 32-bit ISIS Files if different
****************** *******************************
ISISBASE.EXE IBase32.EXE
n/a ISISLIB.DLL
ISISDRAW.EXE IDraw32.EXE
ISISPL.INT
ISISBASE.CFG
BASEFORM.CFG
ISISDRAW.CFG
ISISDESK.HLP
INSTALL.TXT
ISISREAD.TXT
ISIS2.LIB
OLREG.EXE OLREG32.EXE
ISISAIM.DLL
DRAWAIM.HLP
BASEAIM.HLP
ADDINHLP.EXE
MDLCTL.DLL MDLCTL32.DLL
Directories
************
BSESTART/
DRWSTART/
SAMPLES/
SETTINGS/
TEMPLATE/
FORMS/
Development Seat Files/Directories
***********************************
ISISPL.EXE
ISISBASE.INC
ISISDRAW.INC
ADK_READ.TXT
ISISDEV.HLP
INCLUDE/
SAMPLES/ACCESS/
SAMPLES/CPP/
SAMPLES/DELPHI/
SAMPLES/EXCEL/
SAMPLES/PB/
SAMPLES/PL/
SAMPLES/VB/
SAMPLES/XIL/
ISISADIN.INC
DRWADDIN.INT
BSEADDIN.INT
MDLBOX.OCX (for 32-bit ISIS/Object Library)
MDLDB.OCX (for 32-bit ISIS/Object Library)
MDLDB.LIC (for 32-bit ISIS/Object Library)
Contents added to the Windows System directory:
Installed by version number (only earlier versions replaced)
For 16-bit ISIS For 32-bit ISIS
************************ **************************
PWSOCK.DLL 5.00.050 PWSOCK32.DLL 1.00.119
SH22W16.DLL 2.21 PWIOCB32.DLL 1.0.006
MDLBOX.DLL 2.0.2.40
MDLDB.DLL 2.0.2.39
COMPOBJ.DLL 2.03 MFC40.DLL 4.1.6130
OC25.DLL 2.53 MFCO40.DLL 4.0.5136
n/a MFC42.DLL 4.21.7022
n/a MSVCIRT.DLL 5.00.7022
n/a MSVCRT.DLL 5.00.7022
OLE2.DLL 2.03 MSVCRT40.DLL 4.10.6038
OLE2CONV.DLL 2.01 NMAPI32.DLL 1.0.009
OLE2DISP.DLL 2.03 OLEAUT32.DLL 2.20.4054
OLE2NLS.DLL 2.03
OLE2PROX.DLL 2.03 OLEPRO32.DLL 5.0.4055
STORAGE.DLL 2.03 CTL3D32.DLL 2.31.00 (Windows 95)
CTL3DV2.DLL 2.31.000 CTL3D32.DLL 2.31.00 (Windows NT)
VBRUN300.dll 3.00.0538
Installed by date (only earlier dates replaced)
OLE2.REG
STDOLE.TLB
MDLDB.LIC
ISISDLL.DLL
During the installation, a backup copy of all the above system files
(which exist prior to installation of ISIS 2.1.x) is made. This
provides a complete list of your existing system files if you need
them. If you do not need backups of your existing system files,
you can delete all of the *.DL1 files created in your Windows/System
directory. Since these backups can take a total of 2.1Mb of disk
space you may want to delete them.
Although backups of all the ISIS-required existing system files are
made, the system files are replaced ONLY if the currently installed
versions (or dates) are older than the version shipped with ISIS 2.1.x.
Contents potentially added to the Windows System directory after
running ISIS 2.1.x:
ISISBASE.CFG
BASEDRAW.CFG
ISISDRAW.CFG
TPL.CFG
7. Deinstallation instructions
7.1 Windows 3.1 or 3.1.1
The configuration files are added to the Windows directory only if
these files exist in that directory from a previous ISIS installation.
To Deinstall ISIS 2.1.x, delete the ISIS21x directory and then delete
the *.cfg files shown above and the following DLL files found in the
Windows/System directory (for 16-bit ISIS only):
SH22W16.DLL 2.21
MDLBOX.DLL 2.1.0.43
MDLDB.DLL 2.1.1.66
ISISDLL.DLL
MDLDB.LIC
The other DLL files are potentially used by other Windows applications
and should not be removed.
7.2 Windows 95 & NT
Go to the "Start:Settings:Control Panel", and double click on
"Add/Remove programs". Highlight the ISIS 2.1.x program group, and click
on "Add/Remove" buttom. Windows 95/NT will deinstall ISIS 2.1.x including
removing the ISIS 2.1.x program group.