                      Welcome to the Quattro Pro
                       Installation README File
                     =============================

This file contains important information regarding installation
of Quattro Pro--please read all of it. All information here
supersedes information in the User's Guide.

If you are installing Quattro Pro on an OS/2 system, please
consult the README.OS2 file.

Table of Contents
-----------------
  1.  Installation Procedure
  2.  Installation Problems
  3.  Directory/File Layout
  4.  Installing with Previous Versions of Quattro Pro
  5.  Installing with a Windows Screen Saver
  6.  Simplifying Your Windows System
  7.  Additional Troubleshooting and Configuration Details
  8.  Uninstalling Quattro Pro

1. Installation Procedure
-------------------------
 To install Quattro Pro:
   1. Start Windows.
   2. Choose File | Run from the Program Manager.
   3. Place the Quattro Pro disk 1 in the appropriate disk drive.
   4. Type A:INSTALL (or B:INSTALL if you're using drive B) 
      and choose OK.
   5. Follow the directions on the screen.
   6. To start Quattro Pro, start Windows, locate and double
      click the Quattro Pro icon. If you have a previous version
      of Borland Office or PerfectOffice the icons will be
      automatically placed in the Office group.  If you do not
      have the Office they will be placed in the Quattro Pro for
      Windows group.

 The installation program creates a C:\OFFICE\QPW directory (or
 whatever name you specified in the Install screen) and copies
 program files into that directory.

 For a list of files in the QPW directory, see the topic
 "Directory/file layout" later in this document.


2. Installation Problems
------------------------
 If you encounter a "Novell Installation Alert:  Install has
 detected you are currently running IDAPI" message, please exit
 the Quattro Pro installation and close any IDAPI supported
 applications and then restart the installation.  If you
 encounter this message again with all IDAPI applications
 closed, exit Windows to release IDAPI from memory, restart
 Windows, and then restart the installation.


 If you encounter any other type of error message while
 installing, there are two things to try: installing from a
 directory on your hard drive, and simplifying your Windows
 system. The "Simplifying your Windows system" section can
 also be applied if you encounter strange problems when running
 Quattro Pro.

 Alternate Installation Instructions
 -----------------------------------
 Make a temporary directory on your hard drive (e.g. MD C:\TEMP)
 and copy all files from all the install disks to that directory. 

 NOTE:  You will need approximately 42MB of available hard disk
 space to complete this method of installation.

 Then, from Program Manager, choose File | Run and enter

   C:\TEMP\INSTALL.EXE

 When the initial install screen is displayed, make sure Install
 From: is C:\TEMP and Install To: is another directory where you
 want QPW to reside. Once the install is complete, you can delete
 all files in the TEMP directory and remove the directory.

3. Directory/File Layout
-------------------------
 The installation program creates several directories on your
 hard disk. Install copies files into those directories and into
 various Windows directories, as listed below. For descriptions
 of the files on the Quattro Pro disks, see the FILELIST.DOC file
 on Disk 1.

 C:\WINDOWS\ directory:

   QPW.INI        QPW.GRP        WINHELP.INI    QPW6.INI
   SYSTEM.NOV

C:\WINDOWS\SYSTEM\ directory:

   TYPELIB.DLL    STORAGE.DLL    OLE2PROX.DLL   OLE2NLS.DLL
   OLE2DISP.DLL   OLE2CONV.DLL   OLE2.DLL       NWCALLS.DLL
   COMPOBJ.DLL    OLE2.REG       TTYTWIN.DRV    CTL3DV2.DLL
   BWCC.DLL       BOLE16.DLL     VSHARE.386


C:\OFFICE\SHARED\OBEX\ directory:

   No files, only subdirectories.

C:\OFFICE\SHARED\OBEX\BIN\ directory:

   MAILBOOK.EXE   OBXSTORE.DLL   OBXORG.DLL     OBXGEN.DLL
   OBXADDBK.DLL   MBKVWIN.DLL    MBKVEDIT.DLL   MBKAVM.DLL
   MBKADDUI.DLL   MBKABKUI.DLL   IOBEX.VEW      BORLAND.VEW
   BMAILV.VEW     OBEX.FLT       OBXNOTES.DLL   NOTES-CF.DLL
   OBXBKLD.EXE    OBXXFM.DLL     OBXSVSUP.DLL   OBXPX.DLL
   UNCOMP.EXE     OBXALERT.EXE   MTA.EXE        WGDESK01.DLL
   OBXMHS.DLL     MHS-CF.DLL     OBEX.EXE       MBEXPAND.PIF
   OBXALERT.HLP   OBEX.HLP       ARCHIVE.DLL    MAILBOOK.CMP
   OBEXLAN.EXE    OBXTOOLS.DLL   OBXCOMX.DLL    OBXADDHL.DLL
   OBXFLT.DLL     OBXCORE.DLL    OBXCONF.DLL    OBXGATE.DLL
   MAILBOOK.HLP   UNCOMPFL.EXE   RTF.DLL        MNP.DLL
   OBXMAPI.DLL    MAPI-CF.DLL    OBXLAN.DLL     LAN-CF.DLL
   VIM-CF.DLL     OBXVIM.DLL     OBXBVIM.DLL    WPO-CF.DLL
   OBXWPO.DLL     OBXMCI.DLL     MCI-CF.DLL     OBEX.INI

C:\OFFICE\SHARED\OBEX\BOOK\BOOK\ directory:

   BOOK.DB        BOOK.PX        F1.DB          F1.PX
   F1.XG0         F1.XG1         F1.XG2         F1.YG0
   F1.YG1         F1.YG2         PERSADDR.DB    PERSADDR.MB
   PERSADDR.PX    PERSADDR.X02   PERSADDR.X06   PERSADDR.XG0
   PERSADDR.XG1   PERSADDR.Y02   PERSADDR.Y06   PERSADDR.YG0
   PERSADDR.YG1   PERSON.DB      PERSON.PX      PERSON.X08 
   PERSON.XG0     PERSON.Y08     PERSON.YG0

C:\OFFICE\SHARED\IDAPI\ directory:

   IDDBAS01.DLL   IDBAT01.DLL    IDAPI01.DLL    IDAPICFG.EXE
   ILD01.DLL      IDR10009.DLL   IDQRY01.DLL    IDPDX01.DLL
   IDODBC01.DLL   IDASCI01.DLL   IDAPICFG.HLP

C:\OFFICE\SHARED\WPC20\ directory:

   WT60EN.MOR     WTSP60MS.DLL   WTCC60XX.DLL   WTCC60EN.DLL

C:\OFFICE\QPW\ directory:

   README.TXT     QPW.EXE        REGQPW.DLL     QPWRTL.DLL 
   COACH123.WK3   SCREEN.HLP     QPWQ&A.HLP     QPW.HLP
   QHELP.HLP      HPU.DLL        BOBJHLP.DLL    COACH.WB2
   LIBRARY.UI     DBD.EXE        DBSRV.DLL      DBDVIEW.DLL
   DBDQBE.DLL     DBDCREAT.DLL   DBCOEDIT.DLL   QPW.SOM
   SERIES.INF     REGFIX.EXE     COOLFUN.DLL    QPW.STY
   OPTMIZ.DLL     DB.DLL         QFORM.DLL      QCHART.DLL
   QCALC.DLL      DART.DLL       CUI.DLL        QSTAT.DLL
   QFINANCE.DLL   QENG.DLL       QBOOL.DLL      BSCRRUN.EXE
   QPWHOST.DLL    QPWCALL.DLL    BSCROBJ.DLL    BSCRENG.DLL
   BOXMGR.DLL     BEVTWIN.DLL    BEVTQPW.DLL    BEVTMGR.DLL
   BERRMGR.DLL    BCBTRES.DLL    BCBTQPWS.DLL   BCBTQPWL.DLL
   XLATEABK.WB2   WORKGRP.UI     WORKGRP.HLP    OBXQPWA.DLL  
   DBD.HLP        DMODELER.EXE   EXPERT.UI      BWCC.LZ
   LANINFO.TXT    QPW.PAL        ORIGINAL.INF   FORMATS.INF
   UNINSTAL.EXE   UTILITYS.DLL   DMODELER.HLP   README.INS
   README.NET     README.OS2

C:\OFFICE\QPW\TEMPLATE\ directory:

   TRAVELEX.WB2   TEMPLATE.WB2   SINVOICE.WB2   SALESORD.WB2
   QUOTE.WB2      PURCHREQ.WB2   POPORT.WB2     POLAND.WB2
   ORDRFORM.WB2   NETWORTH.WB2   MORTGAGE.WB2   HSINVEN.WB2
   HINVOICE.WB2   CONFROOM.WB2   COLLEGE.WB2    BANKREC.WB2
   AUTOEXP.WB2    ARREG.WB2      APREG.WB2      TEMPLATE.INI

C:\OFFICE\QPW\SAMPLES\ directory:

   3D_BLOCK.WB2   WW.DB          VOLUMES.PX     PERSONAL.PX
   CUSTOMER.PX    BOOKORD.PX     VOLUMES.DB     PERSONAL.DB
   CUSTOMER.DB    BOOKORD.DB     WINES.WB2      SMBEV1.WB2
   QUIKSAVE.WB2   TASKLIST.OVD
 
4. Installing with Previous Versions of Quattro Pro
---------------------------------------------------
 You should install into the directory where the previous version
 is stored so that the installation program knows to clean up all
 older files.  Any notebook files you have in the directory will
 be left alone as long as they don't have the same names as the
 sample files.

 Version 6.0 does not require QPW to be in the path, so you can
 remove your PATH statement along with the ODAPI directory in
 your AUTOEXEC.BAT file (you may need to keep ODAPI in your path
 if you have other applications that require it).

 If for some reason you need both versions of Quattro Pro
 installed on one machine, simply install this version into a
 separate directory and leave ODAPI in the PATH statement.

5. Installing with a Windows Screen Saver
-----------------------------------------
 The install program does not force the display of the next disk
 message if a Windows screen saver has triggered.  You must press
 the space bar to see the disk prompt and then click the OK
 button to continue.  The Enter key is disabled.

6. Simplifying Your Windows System
-----------------------------------
 If you still encounter errors after using the alternate install
 procedure described in section 2, more action may be required.  

 UAE's (Unrecoverable Application Errors), GPF's (General
 Protection Faults), printing discrepancies, and other
 unexplainable problems in Microsoft Windows are frequently due
 to software or hardware conflicts or incompatibilities with
 other applications. If you encounter frequent errors or unusual
 problems, we recommend eliminating all variables that can cause
 problems. This procedure is a test, not a permanent solution.
 If this procedure succeeds, you should restore your system and
 narrow down the exact problem by trial and error (steps 6-7
 explained below).

 An outline of the steps involved in eliminating variables is
 provided here (detailed steps follow):

   1. Backup your system files.
   2. Simplify the AUTOEXEC.BAT, CONFIG.SYS, and WIN.INI
      files.
   3. Eliminate third party drivers from Windows SETUP
   4. Close Windows, reboot your system and restart Windows.
   5. Try to repeat the error.
   6. Restore your system, using the process of elimination to
      narrow down the problem or problems.
   7. Resolve the conflict.

 DETAILED STEPS:

   1. Backup your system files.

      Create a bootable floppy disk by formatting a disk using
      the /s parameter (e.g. FORMAT A: /s). See your DOS manual
      for more information about the FORMAT command. Copy your
      AUTOEXEC.BAT and CONFIG.SYS files from the root directory
      of drive C:, and your WIN.INI and SYSTEM.INI from the
      WINDOWS directory to this disk. If you have difficulty
      during the following process, you can completely restore
      your system by booting from this disk and replacing these
      files.

   2. Simplify the AUTOEXEC.BAT, CONFIG.SYS, and WIN.INI files.

      You can do this by running SYSEDIT within Windows. From
      the Program Manager, select File | Run and type "SYSEDIT".
      The files AUTOEXEC.BAT, CONFIG.SYS, WIN.INI, and SYSTEM.INI
      are now available to edit.  Select the AUTOEXEC.BAT file
      and add REM (REM should always be followed by a space) in
      front of all commands not listed below. REM turns the
      command into a "Remark;" see your DOS manual for more
      information on the REM command.

      For example, if you have Windows in a sub directory
      C:\WINDOWS, DOS in C:\DOS, and a temporary sub directory in
      C:\WINDOWS\TEMP, the only lines without REM statements in
      the AUTOEXEC.BAT file should be:

      PROMPT=$P$G
      PATH=C:\WINDOWS;C:\DOS
      SET TEMP=C:\WINDOWS\TEMP
  
      NOTE: Be absolutely sure the C:\WINDOWS\TEMP directory
            exists!

      Select the CONFIG.SYS file and remark (REM) each line which
      does not match one of the lines listed below. If you have
      a third party hard disk driver (e.g., DMDRVR.BIN,
      SPEEDSTOR, SCSIHA.SYS, or STACKER) you must include this in
      the CONFIG.SYS file. If you are not sure about this, please
      check with the person who set up your system. If the
      meaning of any command is unknown, leave it alone. We
      recommend that you research any unknown commands,
      eliminating them only if possible.

      For example, if Windows is in C:\WINDOWS, and COMMAND.COM
      is in the ROOT directory, your CONFIG.SYS should look like
      this:

      SHELL=COMMAND.COM /p /e:2048
      DEVICE=C:\WINDOWS\HIMEM.SYS
      FILES=99
      BUFFERS=20
      STACKS=9,256


      Select the WIN.INI file and find the commands "LOAD=" and
      "RUN=". Place a ";" in front of these two commands.
      Leave everything else in this file alone. Select the
      SYSTEM.INI file and find the SHELL= line. For maximum
      simplification, make sure this line reads
      SHELL=PROGMAN.EXE. Save these files and exit Windows (don't
      shell out to a DOS Window).

   3. Eliminate third party drivers from Windows SETUP.

      If you have installed a special third party device driver,
      you might experience problems which are the result of its
      use. Complete simplification of your system includes the
      removal of these drivers to see if the problem is related.
      If you have not installed any third party drivers you may
      skip this step.

      From DOS, execute the SETUP.EXE program in the Windows
      sub directory. Eliminate any OEM (Original Equipment
      Manufacturer, i.e., third party) drivers (especially screen
      drivers). Replace these with the standard Microsoft
      drivers. Please consult your Microsoft documentation for
      information about proper SETUP settings. (The Microsoft
      User's Guide section called Running SETUP from MS-DOS has
      information about running SETUP from DOS.)

   4. If you restarted Windows at the end of the SETUP program,
      close Windows.

      In any case, reboot your system and restart Windows. After
      rebooting (and BEFORE LOADING WINDOWS) execute the CHKDSK
      command to check for hard drive errors and fix them if any
      are found (see your DOS documentation for details). From
      the DOS prompt type:

      WIN /S

      This starts Windows in standard mode.

   5. Test Quattro Pro.

      Run Quattro Pro. If you have specific steps to reproduce
      the problem, follow them. If it is a problem that does not
      occur regularly or predictably, you may have to leave this
      configuration intact until you feel enough time has elapsed
      for the problem to reoccur. If the problem does not 
      reoccur, the assumption is that the conflict was eliminated
      in steps 2 through 4.

   6. Restore your system, using the process of elimination to
      narrow down the problem or problems.

      In your AUTOEXEC.BAT, CONFIG.SYS, and WIN.INI files, add
      one command back into the configuration, reboot, and retest
      the application to discover if that command is part of the
      problem. To add one command back into the configuration,
      remove the REM command from a single command and save that
      file. If the problem reoccurs, the line that you removed
      the "REM" statement from caused the conflict. Otherwise,
      remove another remark, reboot, and try to reproduce the
      error. Continue this process until the problem reoccurs.

      Use the same procedure with the OEM drivers. Add each one
      back into your system, one at a time, testing for the
      problem between changes.

   7. Resolving the conflict.

      If you discover the errors disappear at step five and can
      narrow down the cause in step six, you have found the
      conflict. To resolve the conflict, first check the
      documentation of the conflicting application, device
      driver, or memory resident program to be sure it is used
      correctly. If this does not correct the problem, check with
      the publisher of the conflicting application for possible
      workarounds, or updated versions of their software. If you
      cannot resolve the conflict any other way, you may need to
      avoid using Quattro Pro and this application
      simultaneously.

7. Additional Troubleshooting and Configuration Details
--------------------------------------------------------
 1. Exclude the network interface card (NIC) BIOS area from
    your memory manager (i.e., EMM386).  Consult your memory
    manager documentation for the specific commands to exclude
    a range of memory.

    Also exclude the NIC BIOS from Windows by adding an
    EMMExclude= line to the [386 Enh] section of SYSTEM.INI.
    See the example below.

        [386 Enh]
        EMMExclude=D800-DFFF
 
    Exclude the video region (A000-C7FF) from the memory
    manager and from Windows.  Consult your memory manager
    documentation and the sample above for more details.

 2. Add the line MaxBPs=768 to the [386 Enh] section of
    SYSTEM.INI.  This is an entry which specifies values for
    virtual memory and paging.

 3. Make sure all ~*.TMP files are being deleted from the TEMP
    directory when Windows is exited. To determine the location
    of the .TMP files type SET at the DOS prompt and look for
    the line TEMP=.

    Adding the following command in the AUTOEXEC.BAT file after
    the SET TEMP line will cause the temp directory to be cleaned
    up every time the computer is booted.

        DEL %TEMP%\*.TMP > NUL

 4. Start windows with the /D:XSV parameters (i.e., WIN /D:XSV). 
    This will launch Windows without executing the LOAD= and RUN=
    lines of the WIN.INI.  This will also disable any virtual
    memory and exclude all high memory.

 5. Turn off 32 bit disk accessing the  Windows Control Panel
    and choosing 386 Enhanced | Virtual Memory | Change | Use
    32-Bit Disk Access: unchecked.

 6. Turn off external RAM caches using the computers CMOS setup
    utility.  

8. Uninstalling Quattro Pro
---------------------------
 There is a utility installed in the QPW directory called
 UNINSTAL.EXE that you can use to selectively remove modules
 of Quattro Pro after they have been installed. To run it, double
 click the QPW Uninstall Utility icon. Check all the modules you
 wish to remove, make sure the indicated directories are correct,
 and click the "Delete" button. If you remove the IDAPI engine or
 OBEX, you can then delete those directories also.
 
 Information for completely removing all references to Quattro
 Pro from your system follows:

 There are several .INI files in the WINDOWS directory that can
 be deleted: QPW.INI, QPW6.INI, DBD.INI, BORSPELL.INI, OBEX.INI
 and DMODELER.INI.

NOTE:   If you have Paradox for Windows installed you may not
        want to delete the OBEX.INI file from the
        \OFFICE\SHARED\OBEX\BIN directory.
 
 The following lines can be removed from the WIN.INI file:
   The [Extensions] section has a .WB2  and .WB1 reference
   The [embedding] section has four Quattro Pro references
   The [IDAPI], [DDE Servers], [DBD], and [OBEX] sections
   can all be completely removed.
 
 NOTE:  If you have Paradox for Windows you may not want to
        delete the [IDAPI] and [OBEX] sections from this file.
 
 Quattro Pro was registered as a DDE application, so you can
 run REGEDIT.EXE and choose Edit | Delete File Type for both
 Quattro Pro Graph and Quattro Pro Notebook.