
Conner Backup Exec, Version 3.0


Copyright Arcada Software, Inc. 1995.


This file contains important technical information about
your program.

To print this file, type COPY README.TXT PRN at the DOS
prompt.

The following subjects are discussed:

   1.  Installation
   2.  Memory Requirements
   3.  ASPI SCSI Manager Requirements
   4.  Compatibility Test Failure
   5.  Verify Your First Backup
   6.  Running Conner Backup Exec under DesqView
   7.  Compressed Drives
   8.  Installing Conner Backup Exec on a System with Stacker
   9.  The DOS Append Command
  10.  Setup File Compatibility with Conner Backup Exec for Windows
  11.  Laptop Power Management Conflicts
  12.  NetWare Files With an Execute Only (X) Attribute
  13.  Files Not Backed Up
  14.  Potential Conflict with PC-DOS 6.1 RAMBOOST
  15.  Using Removable Media Drives
  16.  Supported SCSI Controllers
  17.  Restoring Files with NetWare Delete Inhibit or
       Rename Inhibit Attributes
  18.  IDE Tape Drive Connection Restriction


   1.  Installation


Conner Backup Exec for DOS will not install or operate correctly
from a DOS box within Windows. It must be installed and operated
directly from the DOS prompt.

The FILES command in your CONFIG.SYS file must be set to 10
or more files.



   2.  Memory Requirements


Conner Backup Exec for DOS requires at least 512K of free memory.
To check your free memory, type MEM at the MS-DOS prompt. To
free memory, remove any TSRs before running Conner Backup Exec.
See your system documentation for other methods.



   3.  ASPI SCSI Manager Requirements

An installed and configured ASPI Manager for the system SCSI
controller is required for use of Conner Backup Exec with SCSI
tape drives. Refer to your SCSI controller or system manual for
availability of an ASPI manager for your controller.



   4.  Compatibility Test Failure


The compatibility test consists of a small backup and
compare, automatically performed by Conner Backup Exec to verify
that reliable backups can be performed with your current
configuration.

The most common cause of compatibility test failure is DMA
error. Therefore, when the compatibility test fails,
Conner Backup Exec automatically resets the DMA
(Direct Memory Access) to Low Speed.

During installation, other factors may contribute to
compatibility test failure. For this reason, the following
procedure is recommended if the compatibility test fails
during installation:

    1. Complete the installation
    2. Restart Conner Backup Exec
    3. Choose Configure
    4. Choose Configuration Tests
    5. Set the Direct Memory Access to High Speed
    6. Redo the compatibility test

If the compatibility test fails again, follow the guidelines
presented in the on-line help, available by pressing F1.



   5.  Verify Your First Backup


When you make your first backup with Conner Backup Exec, it
is highly recommended that you use the Read and Compare
option. During the Compare phase, Conner Backup Exec compares
each file on the tape with the original on your hard drive to
ensure that they are identical. While comparing will increase
the time of the backup, it will confirm that your computer
system, tape drive, and Conner Backup Exec are working
together correctly. If compare fails, run a hard disk utility
program to determine whether the hard drive is free of errors
and try the backup again.



   6.  Running Conner Backup Exec under DesqView


To run Conner Backup Exec under DesqView, make the following
selections in DesqView:

    Create an entry in the Program Menu for Conner Backup Exec.

    Under Advanced Options, specify that Conner Backup Exec
     cannot share CPU when in the foreground, and that
     it cannot run in the background.

    Select Uses Its Own Colors.

    Set the Memory Size option to 512 K.



   7.  Compressed Drives


If you are using compression software such as Stacker or
DoubleSpace, do not back up the compressed file, back up the
logical drive instead. Because these compressed files are
typically very large, attempting to restore may cause problems
if you do not have enough disk space to restore the compressed file.



   8.  Installing Conner Backup Exec on a System with Stacker


If you have Stacker software installed on your computer,
you may not want to let Conner Backup Exec make changes to your
AUTOEXEC.BAT file. Some versions of Stacker create their
own AUTOEXEC.BAT file which should not be modified, and it
is this file that Conner Backup Exec will find.

You can tell if this is the case on your computer if, during
Conner Backup Exec installation, the AUTOEXEC.BAT file that is
displayed says "DO NOT MODIFY THIS FILE." In this case, you
will need to find your original AUTOEXEC.BAT file and make
the following changes:

  Add the Conner Backup Exec directory to your PATH statement.

  Add the command "SET QBACKUP=path_name"

      where path_name is the directory you want Conner Backup Exec
      to use for setup and catalog files

  If you want to load the Backup Scheduler each time you
   start your computer, add the command QSCHED as the last
   command in your AUTOEXEC.BAT file.

For more information on loading the Backup Scheduler, see the
help topic "Installing the Backup Scheduler TSR."



   9.  The DOS Append Command


If you use the DOS Append command with the /X or /X:ON
option, when you perform a restore, some files may not be
restored.  This is because of the way DOS reports names of
existing files when this command is in effect.

It is highly recommended that you deactivate the Append /x
command before performing restores.



  10.  Setup File Compatibility with Conner Backup Exec for Windows


Conner Backup Exec for Windows, version 3.0, can read, use,
and modify setup files created by Conner Backup Exec for DOS,
version 3.0. If you have made individual file or directory
selections in a setup file that is opened and resaved by
Conner Backup Exec for Windows, you may notice that some
filenames and directory names are displayed in a different
color (red if default colors are used). This display change
will not affect the selections.

Conner Backup Exec for DOS, version 3.0, can use setup files
created by Conner Backup Exec for Windows, version 3.0,
with the following limitation:

    Individual file and/or directory selections made with
    the keyboard or mouse will not transfer from the Windows
    setup file to the DOS setup file.



  11.  Laptop Power Management Conflicts


Some laptop power management systems take a "snapshot" of RAM and
store it on the hard drive when they power down. This may create
a conflict if it occurs during a backup or restore or a tape
formatting operation.

When using Conner Backup Exec, it is recommended that you turn
OFF all power management features and plug your laptop into an
outlet rather than using the battery.



  12.  NetWare Files With an Execute Only (X) Attribute


NetWare files with an execute only (X) attribute will not be
backed up, compared, or overwritten during a restore.



  13.  Files Not Backed Up


Conner Backup Exec does not log or back up a number of files
to avoid potential system conflicts if they are restored.

  Compressed Volume files:

     DBLSPACE.0??
     DRVSPACE.0??
     STACVOL.*

  Windows swap files:

     386SPART.PAR
     WIN386.SWP

  NetWare System files:

     BACKOUT.TTS
     NET$SPL.QUE
     NET$MSG.SYS
     DIRSTAMP.SYS
     NET$OBJ.SYS*
     NET$PROP.SYS*
     NET$VAL.SYS*
     NET$BIND.SYS*
     NET$BVAL.SYS*
     SYS$LOG.ERR

 * These NetWare bindery files will be backed up or restored
   only if you are logged on to a server as Supervisor. See your
   User Guide for more information.

Additionally, Conner Backup Exec will not back up a number of
temporary files used by the program when these files are found
in the program's directory.



  14.  Potential Conflict with PC-DOS 6.1 RAMBOOST


If you wish to use the Scheduler TSR, QSCHED.COM, with PC-DOS
6.1's RAMBOOST device, you must use the /SKIPHIGH switch to load
it in conventional memory. Type QSCHED.COM /SKIPHIGH at the
command line or include it in your AUTOEXEC.BAT line. NOTE: The
QSCHED.COM TSR must be loaded last.



  15.  Using Removable Media Drives


For your backup software to recognize and use a removable media
drive such as a Bernoulli drive, the drive must be locked.



  16.  Supported SCSI Controllers


The following SCSI controller cards are supported by this
software:

        Adaptec AHA-1542CF
        Adaptec AHA-1510
        Adaptec AHA-1500
        Adaptec AHA-1522A
        Adaptec AHA-1530P
        Adaptec AHA-1540B
        Adaptec AHA-1542B
        Adaptec AHA-1542C
        Adaptec AHA-1640
        Adaptec AHA-2940
        Adaptec AHA-2842A
        Adaptec AHA-2742AT
        Adaptec AHA-1510A
        Adaptec AHA-1742A
        
        BusLogic BT-747C
        BusLogic BT-747S
        BusLogic BT-545C
        BusLogic BT-445C
        
        DPT  PM-2022/95
        DPT  PM-2122/95
        DPT  PM-2021/95
        DPT  PM-2012/95
        
        Future Domain TMC-850MCD
        Future Domain TMC-1670
        Future Domain MCS-600
        Future Domain MCS-700
        Future Domain TMC-850M
        Future Domain TMC-3260
        Future Domain TMC-3260SVP
        Future Domain TMC-1610MCD
        Future Domain TMC-1680
        Future Domain TMC-1670SVP
        Future Domain SCSI2GO (PCMCIA)



  17. Restoring Files with NetWare Delete Inhibit or Rename
      Inhibit Attributes


During a Restore, you cannot overwrite files which have
the NetWare Delete Inhibit (D) or Rename Inhibit (R)
attribute set. To restore these files, you must first manually
remove the Delete Inhibit or Rename Inhibit attribute.



  18.  IDE Tape Drive Connection Restriction


The IDE tape drive must be the only device connected to the
cable that connects it to the system board or IDE controller.
Conner Backup Exec does not support operation of
the tape drive when it is used concurrently with another
IDE device on the same cable.
