
                           INSTALL.TXT
                           ===========

SEARCH INSTRUCTIONS:  To go directly to a specific section,
search for "SECTION -#-" replacing the # with the appropriate
section number.


                        TABLE OF CONTENTS

SECTION 0       System Requirements

SECTION 1       Booting Clean
                A)  Making a Boot Disk
                B)  Contents of CONFIG.SYS
                C)  Contents of AUTOEXEC.BAT
                D)  Changes to WIN.INI and SYSTEM.INI

SECTION 2       Installation Notes
                A)  Boot Clean
                B)  Network Installation
                C)  Installing Under Windows NT or OS/2
                D)  Installing Under OS/2
                E)  Installing Under Windows NT
                F)  Avoid Extended Characters in Path Names

SECTION 3       Trouble Shooting Installation Problems
                A)  Internal Error, Unable to Start Install
                B)  Data Integrity or Bad Sector on Disk Errors
                C)  Install Program Terminates Prematurely
                D)  General Protection Fault/Unhandled Exception
                E)  Problems With Installing Win32s

SECTION 4       How to Get a Technical Information Document
                A)  From TechFax
                B)  From an On-Line Service



SECTION -0- SYSTEM REQUIREMENTS
===============================

Before installing Resource Workshop (RW) please
review the system requirements listed below:

        4 MB system memory
        Intel 386 or higher
        PC-DOS (MS-DOS) 4.01 or later
        Microsoft Windows 3.1 or later
        3.5" High Density Disk Drive 
        6 MB of hard disk space

   The Install program requires Windows enhanced mode.  It
   does not run under standard mode.
        
   The installation program requires about 5MB of
   additional hard disk space to run.

   More space is required on hard drives with large cluster
   sizes (typically drives with a capacity of 1GB or more.)


SECTION -1- BOOTING CLEAN
=========================

It is highly recommended that you boot clean before installing
RW.  Booting your system with a clean configuration will
eliminate many potential software conflicts that might cause the
installation to fail.  You will need one blank floppy diskette.
After making the disk bootable, use a text editor (EDIT, for
example) to create and/or modify the files mentioned below.  

Note that the instructions below assume that DOS is installed
into the directory C:\DOS, and that Windows in installed into the
directory C:\WINDOWS.

Twice below there is a statement "<insert required drivers
here>".  For the purposes of the clean boot, a "required
driver" is one that must be loaded so that you can access
the devices necessary to complete the installation.  For
example, if you are installing onto a network drive, your
network drivers are required.  Examples of things that are
not "required drivers" include EMM386.EXE, QDPMI.SYS, and
SMARTDRV.EXE.  If you are unsure whether a driver is
required, assume it is not.

A) Making a Boot Disk

It is suggested that you create the clean boot configuration on a
floppy disk, in order to minimize the number of changes made to
your normal system configuration.

In most cases, inserting a blank diskette in drive A: and typing
the command

    format a: /s

will work.  See your DOS documentation for more details
on creating a bootable floppy.


B) Contents of CONFIG.SYS (on boot floppy)

    DEVICE=C:\DOS\HIMEM.SYS
    FILES=40
    <insert REQUIRED drivers here>

C) Contents of AUTOEXEC.BAT (on boot floppy)

    REM the path statement should be copied verbatim
    REM from your current AUTOEXEC.BAT.  The line included
    REM below is an example only.

    PATH=C:\WINDOWS;C:\DOS

D) Changes to C:\WINDOWS\WIN.INI and C:\WINDOWS\SYSTEM.INI

Before modifying these files, be sure to back them up: Windows
will not properly start if they are corrupted (i.e., copy WIN.INI
WIN.BAK).

    1)  Edit WIN.INI

    2)  Find all lines that begin with either "load=" or "run="
    and place a single ";" at the start of each line.

    3)  Edit SYSTEM.INI

    4)  If the line that starts with "shell=" is set to
    something besides "progman.exe", place a ";" at the start of
    the line, and replace it with "shell=program.exe" (no
    quotes).  



SECTION -2- BEFORE YOU BEGIN
============================

A)  Boot Clean

    It is highly recommended that you boot clean before
    installing Resource Workshop. Booting your system with a
    clean configuration will eliminate any potential software 
    conflicts that might arise during installation. Refer to
    Section 1 for instructions on how to boot clean.

B)  Network Installation

    The Install program needs to update Windows system
    files.  If you do not have write privileges for the LAN
    Windows system directory, a system administrator will have
    to perform the installation for you.  

    If you launch SETUP.EXE from a network directory, Setup 
    will not be able to display INSTALL.TXT for you.  You 
    can find INSTALL.TXT on floppy disk #1, and Setup will
    still copy it to your installed directory.
    
C)  Installing Under Windows NT or OS/2

    The install will fail if you enter any paths that use long
    file names (more than 8 letters in the name, more than 3
    letters in the extension, or exceeding a total path length
    of 128 characters).

D) Installing Under OS/2

    When installing under OS/2, WinOS/2 should be run in either
    a full screen WinOS/2 session, or from Program Manager.
    Also, the session must be in Enhanced Mode rather than 
    Standard.  To check this, see the WinOS/2 settings for
    the appropriate icon.  Note that if run from a full screen
    session (preferred), near the end of the installation,
    focus will switch to the OS/2 desktop as a DOS program is
    run; when this program exits, OS/2 will not return the
    focus back to the WinOS/2 session, you will need to do
    this manually.

E) Installing Under Windows NT
    
    If you install RW from a shared read-only network 
    drive under Windows NT, the Install program will not open
    the INSTALL.TXT and README.TXT files.  Look for them in
    your WORKSHOP directory after Install finishes.

F) Avoid Extended Characters in Path Names

    If you use extended ASCII characters (with numbers over
    127) in the path names for installing RW, the Install
    program will not correctly update your INI files.


SECTION -3- TROUBLESHOOTING INSTALLATION PROBLEMS
=================================================

This section explains common errors encountered during
installation. System configuration and software conflicts
might cause the installation process to fail. If the
installation fails, follow the instructions in Section 1
on how to boot clean.  This will eliminate many possible
software conflicts.  Also, check the integrity of the file
systems on your hard drive using a utility like CHKDSK or
SCANDISK; proceeding with an installation while file system
errors are present increases the risk of a failure resulting in
data loss.  If these two steps do not solve the
problem, or you encounter a problem not mentioned here, 
contact Borland Technical Support.

A)  Internal Error, Unable to Start Install

    1) Error -2:  The install program was unable to create a
    temporary directory needed for the installation.  Check that
    if you have either TMP or TEMP set as environment variables
    that they point to a valid directory on a drive with at least
    two megabytes of free space (four megabytes if you are using
    disk compression).  If you do not have a TMP or a TEMP
    environment variable set, the install will place its
    temporary files in the directory WINDOWS\TEMP.  

    You will also see Error -2 if the Install program
    cannot create this directory--if, for example, there
    is already a file called TEMP in your WINDOWS
    directory, or if your Windows drive does not have two
    megabytes of free space.
    
    2) Error -3:  There was an error while copying and decompressing
    the file INSTRUN.EXE, which is used to launch phase two of
    the installation.  Check that there is sufficient free space
    in your temporary directory (see above) and boot the machine
    clean.  Also, a hard drive installation is often helpful.

    3) Error -69:  The execution of INSTRUN.EXE (phase two of
    the installation process) failed.  Probable causes:  file
    corruption (see above), memory corruption (see the section on
    booting clean).

B)  Data Integrity or Bad Sector on Disk Errors

    If you receive either one of these error messages, you
    may need to get a replacement disk set. If running a
    disk checking utility (such as "chkdsk" or "scandisk") 
    reports a bad sector or data integrity problem contact
    Borland's Disk Replacement Line at (800-621-3132). 
    Otherwise, see the Section 1 on booting clean, and if 
    the problem persists, contact Borland Technical Support
    (408-461-9133) for further assistance.

    Outside the US, contact your local Borland representative.

C) Install Program Terminates Prematurely 

   If the install program stops for no apparent reason without 
   error messages, it is possible that certain support files
   are write protected. To check this, do the following:

          1) Go to your WINDOWS directory
          2) Type  attrib *.*
          3) Check for the "r" attribute. If any file has this
             flag set, then you must clear it by typing:
                     attrib -r <filename>
          4) Repeat steps 2-3 for the WINDOWS\SYSTEM directory.

D)  General Protection Fault/Unhandled Exception 

    If you encounter a General Protection Fault or Unhandled
    Exception during installation, try the following steps:

    - Make sure your system meets the minimum requirements.
      Refer to Section 0 for a list of the minimum
      installation requirements.

    - Boot your system with a clean configuration. Refer to
      Section 1 for instructions on how to boot clean.

    - Perform an integrity check on your hard drive, using
      a utility such as "SCANDISK" or "CHKDSK".

    - Turn off Disk Caching and Video/Shadow RAM in CMOS.
      Refer to the documentation for your computer.


SECTION -4- HOW TO GET A TECHNICAL INFORMATION DOCUMENT
=======================================================

Technical Information Documents contain tips, techniques, 
and enhanced information on using Borland development tools,
and information on commonly asked programming questions.  
Such documents often include programming examples.  
 
Here is a list of commonly requested Technical Information Documents:

      * 3       General Catalog of All C/C++ Documents Available
      * 649     General Protection Faults
      * 738     Memory Corruption
      * 1171    Problem Report Form
      * 1561    Clean Boot
      * 1738    Network Installations

A)  From within the US, fax the document from Borland's TechFax 
Service.

Call (800) 822-4269 from a touch-tone phone. When prompted, enter
your FAX number, then enter the document number you want to
receive. The document will be faxed to you shortly.


B)  Download the document.  The file name for document number NNN
would be tiNNN.zip.

   -The Borland Download Bulletin Board Service (DLBBS)
        (408) 431-5096, protocol 8N1

    [When downloading files from the DLBBS, you will
    need to select the appropriate "conference" from
    the main menu.]

   -The Borland Automated Online Service (OAS)
        (408) 431-5250, protocol 8N1

   -The Borland World Wide Web server
        http://www.borland.com

   -The Borland FTP site on the Internet
        ftp.borland.com (IP address: 143.186.15.10)

    [all file names are case-sensitive on the FTP
    site, and almost always lower-case.]

   -Borland-supported forums on CompuServe and Genie.
        for CIS type: go BCPPWIN or and choose library 2
        for GENIE type: Borland

With rare exception, all files on the DLBBS and FTP site will be
compressed with a PKZIP 2.04 (or later) compatible archiver.  If
you do not have a version of PKZIP, you can download the file
pkz204g.exe; execute this file in an empty directory to extract
pkunzip.exe.


                   *** END OF FILE INSTALL.TXT ***
