
                   Installing the ARCserve 5.01e 
               --------------------------------------

This document contains instructions for installing ARCserve 5.01e.
Before you read the installation procedures, please read the important
information below:

ARCserve 5.01e is available in three different varieties depending on
your currently installed ARCserve version.  Your version can be determined
by typing MODULES on the file server console screen and reviewing the
versions of the ARCSERVE.NLM and TAPESVR.NLM.

If you are currently running ARCserve version 5.01d you will need to
download AW0074.ZIP and AW0075.ZIP.  These two files contain only
the patched ARCserve files.

If you are currently running ARCserve version 5.01 you will need to
download AW0076.ZIP, AW0077.ZIP, and AW0078.ZIP.  These three files
contain the patched ARCserve files plus several Novell patches
including BTRIEVE version 6.10c.

If you are currently running ARCserve version 5.0 you will need to
download AW0079.ZIP, AW0080.ZIP, AW0081.ZIP, AW0082.ZIP, AW0083.ZIP
and AW0084.ZIP.  These six files contain the full ARCserve release
with the exception of the license diskette which should already
have been included in your original ARCserve package.

For a complete description of ARCserve 5.01e enhancements, fixes,
and files, consult the ARCserve 5.01e Update Notes.  For a list of
frequently asked ARCserve questions and their answers, consult the
ARCserve 5.01e Q&A file.  Icons for these two files will be added
to your ARCserve program group when you install the 5.01e Update 2.

Run setup
---------
To install ARCserve 5.01e from within Windows:

1.      Insert Update Disk 1 into your workstation floppy drive.

2.      Choose Run from the File Menu in the Windows Program Manager
        and type [drive]:SETUP.

        e.g. B:SETUP

--
OR
--

1.      Create directories off the root of any drive call DISK1, DISK2,
        DISK3, etc.  UnZip the AW00xx.ZIP files to the respective
        directories.

2.      Run the SETUP.EXE found in the DISK1 directory.

The ARCserve 5.01e Update screen displays:

3.      Choose an Update option.

        Option 1:

        "Update ARCserve Server and Manager, NetWare and Btrieve
        6.10c NLM Files to the File Server" when updating from ARCserve
        version 5.0 to 5.01e or from 5.01 to 5.01e.

                                  or

        "Update ARCserve Server and Manager and Server Files
        to the Server Only" when updating from ARcserve version 5.01d to
        5.01e.

        One of the above options MUST be used first in order
        to update both Server and Manager to version 5.01e.

        Option 2:

        "Update ARCserve Manager Only".  This option should be used only
        to update workstations on which the ARCserve Manager is installed
        to the local hard drive.

   ***  NOTE: This option MUST be performed IN ADDITION to the server
        update, if the ARCserve Manager files reside on the workstation
        (e.g. C:) drive  ***


Instructions for each setup option follow.

Server Update
-------------
1.      Enter the path to the directory where ARCserve 5.x is currently
        installed.

        Make sure that you are attached to the ARCserve server and that
        you have mapped a drive to the volume that contains the ARCserve
        home directory.

2.      Confirm the directories to update.

        You will only need to perform steps 3 and 4 if your NetWare system
        and BTRIEVE files need updating.

        If you have already run the ARCserve 5.01d update, or if the files
        on your ARCserve server are of the same revisions as those in the
        Upgrade 2 release, steps 3 and 4 do not apply to your installation.

3.      If you are installing the update from ARCserve 5.0 or 5.01 to 5.01e,
        you must decide whether or not to update the NetWare System and
        BTRIEVE 6.10c NLMs and related files.

        If, for compatibility reasons, you decide not to update these files,
        then you may skip steps 3 and 4.

        If you select "Yes," any NetWare System and BTRIEVE files that are
        older than the ones on the Update disks will be replaced.  The
        5.01 Update copies the new files to your server's SYSTEM directory
        and to your ARCserve home directory.  If your NetWare system and
        BTRIEVE files are all current, only the ARCserve files will be
        updated.

        If you select "No," all NetWare system and BTRIEVE files will be
        copied to the \ARCSERVE\NWSYSTEM directory on the ARCserve 5.01
        host server.  If you decide at a later time that you wish to
        update any of these files, you can manually copy them to the
        directory where the old versions resided (SYS:SYSTEM, in most
        cases).

        Even if you select "No," your ARCserve files still will be updated.

        The Setup program will now update any NetWare system and BTRIEVE
        files that require updating.

4.      Decide which files to update.

        Answer "Yes to All" to let Setup update all of the NetWare system
        and BTRIEVE files.  You can also selectively install files by
        answering "Yes" or "No" for each file.  Unless you have a specific
        reason for not wanting a file to be updated, you should select
        "Yes to All" to update all the files at once.

5.      Follow the instructions that appear on your screen to begin using
        the updated version of ARCserve.

Manager update only
-------------------
1.      Enter the path to the directory where the ARCserve 5.x Manager
        is currently installed.

2.      Confirm the directory path to the ARCserve 5.x Manager files.

        Continue with Step 2 of the "Server Update" instructions outlined
        above.

        The Setup program then updates the ARCserve 5.x Manager.

3.      Follow the instructions that appear on your screen to begin using
        the 5.x updates.

-----------------------------------------------------------------------
                    
                    ARCserve 5.01e June, '94
                          Release Notes

This document contains important information that is not
included in the ARCserve Installation Guide, ARCserve User
Guide, ARCserve Supervisor Guide or ARCserve Online Help.

Using Write to View This Document

If you enlarge the Write Window to its maximum size, this
document will be easier to read. To do so, click the
Maximize button in the upper-right corner of the window, or
open the Control menu in the upper-left corner of the Write
window (press ALT+SPACEBAR), and then choose the Maximize
command.

To move through the document, press PAGE UP or PAGE DOWN or
click the arrows at the top and bottom of the scroll bar
along the right side of the Write window.

To print the document, choose the Print command from the
File menu.

For Help on using Write, press F1.

To read other online documents, choose the Open command from
the File menu.

Contents

This document contains software updates and information in
the following areas:

I.   ARCserve Manager
II.  ARCserve Server
III. ARCserve Tape Server
IV.  ARCserve Agents
V.   Technical Tips
VI.  Packing List
______________________________________________

I. ARCserve Manager

The following enhancements and fixes have been added to the
ARCserve Manager in the ARCserve 5.01e release:

Enhancements:

1.  In the Restore Manager, the browsing speed of the backup
history tree has been improved.

2.  In the Database Manager, the OS Type "NT" has been added
to the PC Clients database to allow you to specify NT
clients in your enterprise.

3.  The speed of job submission on NetWare 4.x servers
containing thousands of objects has been improved.

4.  To prevent the message "Error - Agent is not loaded"
when trying to browse a remote PC client that is a notebook
running the Xircom adapter and has the agent loaded, create
an ARCSERVE.INI file to a specify retry count for accessing
remote clients.

In the ARCSERVE.INI file, the following entry should be
made:

[PC]
retry=n

where,  n is a value from 1 to 255.

The default retry count is set at 4, and seems to work with
most PC targets.

In addition, it may be required to modify the SPX ack wait
timeout and the SPX default retry count.
For example:
 Load spxconfg
 set spx ack wait timeout to max (3240)
 set spx default retry count to max (255)

Since this message seemed to occur only with notebooks
running the Xircom adapter, be sure to also upgrade to the
latest Xircom LAN drivers.

5.  The Purge utility has been enhanced to retain empty
directories.  To use this feature, add the following switch
to the ARCSERVE.INI file:

[Task]
RemoveDirectories=0

The default is 1 and the directories are removed.

Fixes:

1.  ARCserve will now be able to display the script type
when viewing a script that has been saved to a deep
directory.

2.  The Description field in the Run dialog for backup and
restore jobs has been lengthened to allow for longer
descriptions.

3.  Backing up the FTS will now report the correct
throughput.  Previously, it was reported as 0 KB/min.

4.  After the estimate of a backup, ARCserve will not
display the error message "Failed to get <filename>'s AFP
information, ff" if the file referenced has been deleted.

5.  A problem which caused file truncation errors when
backing up a workstation using WINAGENT on a token ring
network with a 4k packet size has been fixed.

6.  ARCserve now properly displays version history when
restoring MAC folders and files.

7.  ARCserve now properly displays version history,
regardless of the job status.

8.  If truncated files are received from the agents during a
workstation backup, the error  message
 will be printed in the ARCserve Activity Log as well as on
the ARCserve Server Console.
____________________________________________________________
_________________________

II. ARCserve Server

The following enhancements and fixes have been added to the
ARCserve Server in the ARCserve 5.01e release:

Enhancements:

1.  ARCserve now allows for partial backup and restore of
the NDS.   In order to perform this, use the Description
field in the Run Dialog to manually enter the complete name
of the starting container from which to start the backup or
restore.  To differentiate this from a regular description,
however, be sure to place a '.' (period) in the first
position before entering the name of the starting container.

To back up the QA Department's container, add the following
line to the Description field:

  .OU=QA_DEPT.OU=ENG_DIV.O=ABC_CO

To back up the Engineering Division's container and all
containers within, add the following line to the Description
field:

  .OU=ENG_DIV.O=ABC_CO

See also the Technical Tips section later in this document.

2.  ARCserve now supports backup, restore, and copy of
Windows NT machines through the use of  Windows NT Agent
(NTagent).  The NTagent is available as an option.

3.  A message in the Activity Log will now be displayed to
tell the user to retire an old Auto Pilot tape.

4.  If a repeating backup job is cancelled after a tape
fills up and before a new tape is formatted and used
(because the job spans tapes), ARCserve allows you to make a
blank tape the next sequence tape.

5.   A new command line option has been added to CLIENTS.NLM
to allow you to include or exclude Macintosh zones.  The
command line option is:

Z[I|X]=zone.lst

where, I = include zones listed in the zone.lst file, and X
= exclude zones listed in the zone.lst file.

Create the file zone.lst and enter the name(s) of the
Macintosh zones you want included or excluded.  For example,
contents of a zone.lst file may be:

zone_1
zone_2

6.  A command line switch, NO_DEL_MSG, has been provided to
prevent the Activity Log from filling up when ARCserve is
grooming files.

LOAD SYS:\ARCSERVE\NLM\ARCSERVE NO_DEL_MSG

This is not applicable to a Backup Job with the Delete
Source Files Option selected.

Fixes:

1.  A check has been implemented to prevent sparse files
that were almost 4GB from hanging the file server.

2.  Copying files on a NetWare 4.X server using DBagent has
been fixed.  Previously, the following message would appear,
" Failed to get database names."

3.  If you are running NetWare 4.x with compression on, you 
MUST use the new NOSPARSE command line switch when 
loading ARCSERVE.  This switch will prevent the corrupted 
compressed files from rebooting the file server when they are 
being uncompressed.  In addition, you must use FULL SMS.

In the ASTART.NCF file, add the switch NOSPARSE to the line
that loads ARCSERVE.NLM.  For example,

LOAD SYS:\ARCSERVE\NLM\ARCSERVE NOSPARSE

4.  ARCserve has fixed the problem of creating paths when
files backed up with SMS are restored with the options
"Don't Create Base Directory" or "Create Base Directory"
selected.

5.  FSTAPE.NLM has been fixed to release the connection with
TSANDS when restoring the NDS.

6.  ARCserve will now properly clear connections after users
have been warned to log out.

7.  ARCserve has been fixed to prevent source files from
being deleted after a backup that has "Delete Source files"
selected has been cancelled.

8.  You can now cancel backup jobs that contain ORACLE log
files.

9.  ARCserve now does not try to get AFP information on a
volume, so the error message "Failed to get <volume>'s AFP
information, ff" will not display for a volume.

10.  All DBagent parameters will be initialized to ensure
DBagent backups on NetWare 4.01 servers.

11.  ARCserve now works with SECURE CONSOLE.  Refer to the
Technical Tips section later in the document for more
information.

12.  Auto Pilot grooming has been fixed to correctly groom
files based on the month and day as specified.

13.  The number of segments will not be checked if the file
is a sparse file.  This ensures that sparse files that have
less than two segments will be backed up as such.

14.  The bindery will not be opened until all bindery files
have been restored and attributes set to ensure that
Hidden/System attributes are set.  This also prevents the
bindery from being closed and opened more than once for
restore jobs.  In addition, ARCserve has been fixed to set
all bindery attributes after restore jobs.

15.  The name of the file server that the NDS is being
restored to is entered in the log, instead of the name of
the file server that was backed up.

16.  The Pre/Post Wait period has been fixed to wait the
specified time in minutes.

17.  ARCserve will now prepend a broadcast message with the
host server name that sent the message.

18.  Previously, a large time slice was encountered when
viewing a large Activity Log.  This has been corrected.

19.  ARCserve will now record OS/2 client backup sessions as
such, rather than as a DOS backup session.

20.  The correct error code will now be displayed when
backing up SMS files.

21.  ARCserve has been fixed so that it will not truncate
the name of the NDS object when backing it up.

22.  The Auto Pilot daily Differential counter has been
fixed to properly record the number of daily Auto Pilot
tapes.

23.  ARCserve now uses TSA to query the name space for a
file.  This eliminates displaying the message "Failed to
return name space info for <filename>,ff" when attempting to
back up Macintosh files with extended ASCII characters in
the short name on remote NetWare 3.12 and 4.01 file servers.

24.  Novell has changed the name of SMDR31x.NLM to SMDR.NLM
in the next SMS drop.  As a result, ARCserve will look first
for SMDR.NLM.  If this file is not found, then it will load
SMDR31x.NLM.  A change has been made to load SMDR or SMDR31x
from the SYSTEM directory rather than the SYSTEM\DR
directory.

25.  An Auto Pilot  Differential (Modified date) backup job
will perform a full backup if a Full backup has not been
previously done.

26.  The tape timeout period for users of tape changers will
be reset to 30 minutes if it is originally set for less than
that.  This will allow you more time to insert the correct
magazine if the tape is not found in the current one.

27.  The tape option "Append to tape", selected from the
Backup Manager, has been fixed to override the specification
of "YES" to the option "Overwrite any tape in the drive" at
the ARCserve Server console.  Previously, if, from the
ARCserve Server console, "overwrite any tape in the drive"
was set, ARCserve would overwrite the tape even if, from the
Backup Manager, the tape option "Append to tape" was
selected for a backup job.

28.  When using changers for backup jobs that specify the
destination option "Append to *", ARCserve will now attempt
to use the tape in the drive.  If the tape can't be used,
ARCserve will then try to use the next tape.

____________________________________________________________
_________________________

III.  ARCserve Tape Server
The following fixes and enhancements have been added to the
ARCserve Tape Server in the ARCserve 5.01e release:

Enhancements:

1.  ARCserve now works properly with SECURE CONSOLE.  Refer
to the Technical Tips for more information.

2.  A new [CONFIG] parameter, "FASTBIT = ENABLED/DISABLED"
was added to the TAPESVR.CFG file.  When "FASTBIT =
DISABLED" is used, the Tandberg FASTBIT will not be able to
be used by TAPESVR.NLM.  This parameter was put in to fix
some possible firmware compatibility problems with the
Tandberg tape driver.

3. Added support for DEC TZ86 drive.

4. Added Auto-mount feature to the changer. If a magazine is
ejected and put back in (possibly with new tapes), the
changer will reinitialize.  If a job requires a certain tape
which is not in the magazine, you can   eject the magazine,
insert the required tape, and put the magazine back in.  At
this point the changer will reinitialize and the job will
continue.

5. Adaptable block size support was added.  Tapesvr will now
automatically customize itself to the default block size of
a Cheyenne formatted backup tape.

6.  The Adaptec AHA-2490 PCI adapter card has been certified
with the updated ARCserve 5.01E
software.   Please note that  the AHA-2940 requires the file
AIC7870.DSK  (Version:   1.05, Dated  June 27,  1994  File
Size:  41295 ).  This only applies to NetWare 3.x servers.

7.  Support has been added for the following tape drives and
adapters for this release.

Drives                   Host Adapters

DEC Changer TZ877             Adaptec AHA-2940
DEC Changer TLZ6              BusLogic BT-545C
Exabyte 8505XL
MDI SE 2000DF

* Please contact Cheyenne Software for latest certified
device list

____________________________________________________________
_________________________
IV.  ARCserve Agents
OS2 Agent

Files:
          OS2AGENT.EXE -      Presentation Manager version
of the OS/2 Agent
          OS2AGENT.HLP -      Help file associated with the
OS/2 Agent
          FS_AGENT.EXE -      Full Screen version of the
OS/2 Agent
          LS_ACL.DLL   -      Dynamic Link Library required
by OS/2 Agent

Installation:
1.  Copy OS2AGENT.EXE and FS_AGENT.EXE to a directory
specified in your PATH.  The PATH
statement can be found in your CONFIG.SYS file.

2.  Copy OS2AGENT.HLP in a directory on your HELP.  This can
also be found in your CONFIG.SYS
file.

3.  Copy LS_ACL.DLL into your \NETWARE directory.  This file
must be in this directory for the OS2
Agent to work properly.

New Features:

1.  Backup jobs with the Clear Archive Bit option selected
work properly.

2. The LS_ACL.DLL is now included to back up/restore
LANServer 3.0 and LAN Manager 2.x Access
Control Lists and sharing information.

3. The ARCAGENT.LOG file now resides on the boot drive.  It
previously resided on the C: drive.

4.  CD-ROMs will now be automatically excluded in the query.
You still need to have a CD-ROM in the
drive for our software to work.

5.  Drives listed in the ARCAGENT.LOG file will be excluded
in the Queries.  Include your CD-ROM
drive(s) in this file, so that they are also excluded.
Doing this resolves the"must have CD-ROM in drive"
problem.

6.  The AGENTERR.LOG  file that gets created when an error
occurs now will be created at the boot drive.

7.   A switch, /512, has been added which forces the agent
to transmit at 512 bytes. This only forces the
backup to transmit at 512 bytes.  Restore is still
determined at the ARCSERVE.NLM side.

8.  Pre-Post job execution support has been added.  The OS/2
Agent will now execute a batch file
"PRE_EXEC.CMD" from the root directory of the boot drive
before every job.  At the end of the job,
"POSTEXEC.CMD" will be executed.

9.  Support for a text configuration file, 'OS2AGENT.CFG'
has been added.  This file contains default
configuration settings that the agent will read every time.
The syntax is similiar to the NET.CFG  file
where ';' indicates comments.  Commands and the default
values are as follows:

     BUFFERS = n              (16, which is the maximum)
     PRIORITY = n             (15; maximum is 32, and
minimum is -32
     VERBOSE = on/off         (OFF)
     PACKET_SIZE = n          (1024, which is the maximum;
minimum is 512 )
     PRE_EXEC_DELAY = n       (100 milliseconds)
     EXEC_TIMEOUT = n         (300000 milliseconds)
     PRE_EXEC_FILENAME = name (\pre_exec.cmd)
     POST_EXEC_FILENAME = name     (\postexec.cmd)
     ACTIVITY_LOG = name      (\agenterr.log)
     PASSWORD = password      (<none> )

A filename whose first character starts with a '\' would
imply the boot drive.  If you want a specific drive,
use "D:\".

10   A Max thread use parameter has been added to the OS/2
Agent.  By default, the parameter will be 5
with a minimum of 3.

At the command line, enter the following:

/tN

where, N is the number of threads allowable for the OS/2
Agent.

If you want to place this parameter in the OS2AGENT.CFG
file, the following syntax should be used:

            THREADS =     (default value is 5)

____________________________________________________________
_________________________

V.  Technical Tips

In this section you will find information about the
following:

A.  Recommendations for backing up and restoring the NetWare
Directory Services (NDS) database
B.  Running ARCserve with SECURE CONSOLE
C.  Recommended NetWare 3.x, 4.x NLMs for ARCserve 5.x

A.  Recommendations for Backing Up and Restoring the NetWare
Directory Services Database

Backing Up the NDS

1.  Load the TSANDS.NLM on at least one NetWare 4.x server
being backed up.  The NDS will be backed up only once per
job.

2. Load the TSA400.NLM on every NetWare 4.x server being
backed up.

3.  "Use SMS Logic for DOS and MAC files also" parameter
must be set to YES in the ARCserve Server Configuration
screen to preserve the owners and trustees in case of an NDS
restore.

4.  For each of the NetWare 4.x servers being backed up,
there must exist a user in bindery emulation that has
Supervisor Object Rights to the corresponding Server Object
in Directory Services.  The TSAs login in Directory Services
mode, but ARCserve logs in Bindery Emulation mode.
Therefore, the user must exist in both modes.  (SUPERVISOR
does not exist in both modes, and cannot be used to do a
backup.)

5.  For the server that has the TSANDS.NLM loaded, there
must exist a user in bindery emulation that has Supervisor
Object Rights to the Root Object in Directory Services in
order to  backup the full NDS tree.  In the case of a
partial NDS backup, the user must have Supervisor Object
Rights to the starting object specified.

6.  These user names and passwords must be entered in the
Job Form for the corresponding server.  The steps below
describe how you do this:
a)  Select Node Options from the Source Configuration dialog
box.
b)  From the Browser, select the server to be backed up.
c)  Under Server Security Login, enter the user name and
password for the server.

7.  At least one Full volume must be selected on the server
that has the TSANDS.NLM loaded in order for the NDS to be
backed up.

Restoring the NDS

1. The NDS must not be in a corrupted state when restoring
it.

2. All partitions must have at least one replica on a server
that is currently running.

3. Any servers that are in the NDS before doing a restore
that were in the NDS before the backup, must be
in the same contexts.  There can be only one server object
in the tree with the same name.

4. For each server that was re-intsalled into the tree, run
DSREPAIR in order remove old user IDs.  If TSANDS.NLM was
loaded before running DSREPAIR, unload and reload it so that
it uses the new NDS database.

5. Make sure the TSANDS.NLM is loaded on one NetWare 4.x
server.

6. For the server that has the TSANDS.NLM loaded, there must
exist a user in bindery emulation that has Supervisor Object
Rights to the Root Object in Directory Services in order to
restore the entire NDS tree.  In the case of a partial NDS
restore, the user must have Supervisor Object Rights to the
starting object specified.

7. This user name and password must be entered in the Job
Form for the corresponding server.

8. Any servers that were removed from and re-installed into
the NDS tree before the restore will lose the owners and
trustees of the files and directories unless the volumes are
restored also.

9. Any objects that were not present when restored, will not
have any trustees.  The volumes or objects to which the
objects had trustees to must be restored.

10. After a Full NDS Restore, type ASTOP and ASTART at the
server so that ARCserve will use the Queue that was
restored.

11. A quick way to restore the directory trustees would be
to Exclude Files *.* so that only the directories get
restored.


B.  Running ARCserve with Secure Console


A new command line parameter was added to TAPESVR.NLM and
STANDARD.NLM to allow these NLMs to load properly when
SECURE CONSOLE is activated.  The syntax to use is as
follows:

        Load TAPESVR H=SYS:ARCSERVE
        Load STANDARD H=SYS:ARCSERVE ...

The "H" parameter informs TAPESVR.NLM and STANDARD.NLM of
the location of the "NLM" directory based off the home
directory.  The home directory contains their DATA and
MESSAGE files.  Based on the above example, the home
directory of TAPESVR.NLM and STANDARD.NLM is
"SYS:ARCSERVE\NLM".

Novell  provides for the "SECURE CONSOLE " command  to
implement  certain security features , one of them being to
prevent any loadable modules  from being loaded from any
directory other than  SYS:SYSTEM  .

In order to check if you have Secure Console  loaded , try
typing  "load sys:system\clib.nlm" at the  server console.
If the system is running Secure  Console , it would respond
with a message "The console has been secured  , path
specifiers are no longer allowed ......".

If  you have SECURE CONSOLE  running on your ARCSERVE  HOST
SERVER  , you  need to follow these steps to in order to run
get ARCSERVE  to work on your system:

1.  Copy all the NLMs from the VOL:ARCSERVE \NLM
directory(where, VOL:ARCSERVE is the directory you installed
ARCserve) to the SYS:SYSTEM directory.

2.  Copy SMDR31X.NLM (if  you are using  Netware v3.11 or
Netware v3.12) or SMDR .NLM (if you are using Netware 4.01)
to the SYS:SYSTEM diretory.  (You may find it in the
VOL:ARCSERVE\NWSYSTEM directory) .

3.  Copy TSA311.NLM or TSA312.NLM or TSA400.NLM & TSANDS.NLM
, as appropriate, to the SYS:SYSTEM directory.  (You may
find these files in the VOL:ARCSERVE\NWSYSTEM directory)

4.  Copy ASTART.NCF  to  ASTART.CSI

5.  Edit  the ASTART.NCF  file. Since Secure Console does
not allow any path specifier in load statements, you must
remove all path specifiers.  In other words, you must change
"Load PathName\ModuleName" to "Load ModuleName".  Also, you
must append "H=VOL:ARCSERVE"  as command line arguments to
each of the ARCSERVE modules.   This is done as follows:

a) change LOAD  SYS:\SYSTEM\STREAMS
     to LOAD  STREAMS

 b) change  LOAD  SYS:\SYSTEM\CLIB
     to LOAD CLIB

c) change LOAD  SYS:\SYSTEM\TLI
     to LOAD  TLI

d) change LOAD  SYS:\SYSTEM\SPXS
     to LOAD SPXS

e)change LOAD  SYS:\SYSTEM\AFTER311
     to LOAD  AFTER311

f) change LOAD  SYS:\SYSTEM\NWSNUT
     to LOAD NWSNUT

g)change  LOAD VOL:ARCSERVE\NLM\ASDB
          to    LOAD ASDB   H=VOL:ARCSERVE

h) change   LOAD VOL:ARCSERVE\NLM\FAXLIB
          to  LOAD FAXLIB

i) change   LOAD VOL:ARCSERVE\NLM\ARCSERVE
          to  LOAD ARCSERVE   H=VOL:ARCSERVE

j) change   LOAD VOL:ARCSERVE\NLM\TAPESVR
     to  LOAD  TAPESVR   H=VOL:ARCSERVE

k) change  LOAD VOL:ARCSERVE\NLM\CLIENTS
     to   LOAD CLIENTS    H=VOL:ARCSERVE

l) change LOAD VOL:ARCSERVE\NLM\AHAXXX  [OPTIONS]
     to  LOAD  AHAXXX  [OPTIONS]
     ( where AHAXXX is your  board  driver)

6.  Modify the  TAPESVR.CFG file (you'll find it in the
VOL:ARCSERVE\NLM directory) so as to append "H=VOL:ARCSERVE"
to each of the NLMx  parameters in use.

For example:
change  NLM1=standard group -ARCSERVE scsiid -3
to   NLM1=standard group -ARCSERVE scsiid -3  H=VOL:ARCSERVE

7.  At  the console , type ASTART.


C.  Recommended NetWare NLMs for ARCserve 5.x

These are the minimum set of NLMs needed to run ARCserve 5.x
on a NetWare server.  The versions of the NLMs should be
equal to or greater than those listed.  The files were
included on the ARCserve 5.01d Update Diskettes but have
since been updated by Novell.  The updates are in LIBUP1.EXE
and STRTL2.EXE  or later updates on NetWire.

Netware 3.11 NLMs

TSA311.NLM
  NetWare 3.11 Target Service Agent
  Version 4.01b   November 5, 1993
  Copyright 1993 Novell, Inc.  All rights reserved.
SMDR31X.NLM
  NetWare 3.1X SMS Data Requestor
  Version 4.01b   October 28, 1993
  Copyright 1993 Novell, Inc.  All rights reserved.
TLI.NLM
  NetWare Transport Level Interface Library
  Version 3.12a   September 14, 1993
  (C) Copyright 1989-1992 Mentat, Inc.
  Portions (C) Copyright 1989-1993 Novell, Inc.
  All Rights Reserved.
CLIB.NLM
  NetWare C NLM Runtime Library v3.12d
  Version 3.12d  November 10, 1993
  (C) Copyright 1989-1993, Novell, Inc. All rights reserved.
      Patent Pending--Novell, Inc.
AFTER311.NLM
  NetWare 3.11 Forward Compatibility Support v3.0.8
  Version 3.00h   October 1, 1993
  Copyright 1993 Novell, Inc.  All rights reserved.
STREAMS.NLM
  NetWare STREAMS
  Version 3.12    July 20, 1993
  (C) Copyright 1989-1992 Mentat, Inc.
  Portions (C) Copyright 1989-1993 Novell, Inc.
  All Rights Reserved.
SPXS.NLM
  NetWare SPXII STREAMS Driver
  Version 3.12a   September 14, 1993
  (C) Copyright 1989-1993 Novell, Inc.
  All Rights Reserved.
NWSNUT.NLM
  NetWare NLM Utility User Interface
  Version 4.01a   June 15, 1993
  Copyright 1993 Novell, Inc.  All rights reserved.
BSPXCOM.NLM
  BSPXCOM
  Version 6.10b   November 24, 1993
BTRIEVE.NLM
  Btrieve NLM
  Version 6.10c   November 19, 1993


Netware 3.12 NLMs

TSA312.NLM
  NetWare 3.12 Target Service Agent
  Version 4.01b   November 5, 1993
  Copyright 1993 Novell, Inc.  All rights reserved.
SMDR31X.NLM
  NetWare 3.1X SMS Data Requestor
  Version 4.01b   October 28, 1993
  Copyright 1993 Novell, Inc.  All rights reserved.
TLI.NLM
  NetWare Transport Level Interface Library
  Version 3.12a   September 14, 1993
  (C) Copyright 1989-1992 Mentat, Inc.
  Portions (C) Copyright 1989-1993 Novell, Inc.
  All Rights Reserved.
CLIB.NLM
  NetWare C NLM Runtime Library v3.12d
  Version 3.12d  November 10, 1993
  (C) Copyright 1989-1993, Novell, Inc. All rights reserved.
      Patent Pending--Novell, Inc.
AFTER311.NLM
  NetWare 3.11 Forward Compatibility Support v3.0.8
  Version 3.00h   October 1, 1993
  Copyright 1993 Novell, Inc.  All rights reserved.
STREAMS.NLM
  NetWare STREAMS
  Version 3.12    July 20, 1993
  (C) Copyright 1989-1992 Mentat, Inc.
  Portions (C) Copyright 1989-1993 Novell, Inc.
  All Rights Reserved.
SPXS.NLM
  NetWare SPXII STREAMS Driver
  Version 3.12a   September 14, 1993
  (C) Copyright 1989-1993 Novell, Inc.
  All Rights Reserved.
IPXS.NLM
  NetWare IPX STREAMS Driver
  Version 3.12a   August 10, 1993
  (C) Copyright 1989-1993 Novell, Inc.
  All Rights Reserved.
NWSNUT.NLM
  NetWare NLM Utility User Interface
  Version 4.01a   June 15, 1993
  Copyright 1993 Novell, Inc.  All rights reserved.
BSPXCOM.NLM
  BSPXCOM
  Version 6.10b   November 24, 1993
BTRIEVE.NLM
  Btrieve NLM
  Version 6.10c   November 19, 1993

Neware 4.0x NLMs

DS.NLM
  NetWare Directory Services (291)
  Version 4.01    August 11, 1993
  Copyright 1993 Novell, Inc.  All rights reserved.
TIMESYNC.NLM
  Time Synchronization Services
  Version 4.00    February 8, 1993
  (C) Copyright 1991-93, Novell, Inc.  All rights reserved.
CLIB.NLM
  NetWare C NLM Runtime Library v4.01D (PTF 940309)
  Version 4.01d   March 9, 1994
  (C) Copyright 1989-1994, Novell Inc. All rights reserved.
      Patent Pending - Novell Inc.
STREAMS.NLM
  NetWare STREAMS
  Version 4.00a   September 14, 1993
  (C) Copyright 1989-1992 Mentat, Inc.
  Portions (C) Copyright 1989-1993 Novell, Inc.
  All Rights Reserved.
TLI.NLM
  NetWare Transport Level Interface Library
  Version 4.00a   September 14, 1993
  (C) Copyright 1989-1992 Mentat, Inc.
  Portions (C) Copyright 1989-1993 Novell, Inc.
  All Rights Reserved.
SPXS.NLM
  NetWare STREAMS SPXII Protocol
  Version 4.01a   September 14, 1993
  (C) Copyright 1992-1993 Novell, Inc.
  All Rights Reserved.
NWSNUT.NLM
  NetWare NLM Utility User Interface
  Version 4.01a   June 15, 1993
  Copyright 1993 Novell, Inc.  All rights reserved.
DSAPI.NLM
  NetWare Directory Services API Library v4.01
  Version 4.01  May 5, 1993
  Copyright 1993 Novell, Inc.  All rights reserved.
SMDR.NLM
  NetWare 4.0 SMS Data Requestor
  Version 4.01b   October 28, 1993
  Copyright 1993 Novell, Inc.  All rights reserved.
AFTER311.NLM
  NetWare 3.11 Compatible NLM Support Module
  Version 1.00    February 10, 1993
  Copyright (C) 1993 by Novell, Inc. All Rights Reserved
BTRIEVE.NLM
  Btrieve NLM
  Version 6.10c   November 19, 1993
BSPXCOM.NLM
  BSPXCOM
  Version 6.10b   November 24, 1993
TSA400.NLM
  NetWare 4.0 Target Service Agent
  Version 4.01b   November 5, 1993
  Copyright 1993 Novell, Inc.  All rights reserved.
TSANDS.NLM
  NetWare NetWare Directory Services v4.0 Target Service
Agent
  Version 4.01b   October 26, 1993
  Copyright 1993 Novell, Inc.  All rights reserved.


VI.  Packing List

The packing list for the June release of ARCserve 5.01 is
the same as the packing list provided in the March release
notes(seen below), with the following additional files:

OS2 Agent Files

          OS2AGENT.EXE
          OS2AGENT.HLP
          FS_AGENT.EXE
          LS_ACL.DLL



               ARCserve 5.01 March, '94 Update
                        Release Notes

This document contains important information that is not
included in the ARCserve Installation Guide, ARCserve User
Guide, ARCserve Supervisor Guide or ARCserve Online Help.
Using Write to View This Document

If you enlarge the Write Window to its maximum size, this
document will be easier to read. To do so, click the
Maximize button in the upper-right corner of the window, or
open the Control menu in the upper-left corner of the Write
window (press ALT+SPACEBAR), and then choose the Maximize
command.

To move through the document, press PAGE UP or PAGE DOWN or
click the arrows at the top and bottom of the scroll bar
along the right side of the Write window.

To print the document, choose the Print command from the
File menu.

For Help on using Write, press F1.

To read other online documents, choose the Open command from
the File menu.

Contents

The ARCserve 5.01 Update is a comprehensive compilation of
enhancements and fixes which have been incorporated since
the ARCserve 5.01 Release of January 1994.  The enhancements
in this release include full international language support
for German, French, Italian, Spanish and Japanese.
Additionally, support has been added for over 40 tape drives
and SCSI adapters.   To ensure the proper operation of the
entire network environment, we have also included 39 Novell
files for the server and 5 Novell DLLs for the workstation.

This document contains software updates and information in
the following areas:

I.   ARCserve Manager
II.  ARCserve Server
III. ARCserve Tape Server
IV. Technical Tips
V.   Packing List
______________________________________________

I. ARCserve Manager

1.   WINDOWS 386 ENHANCED MODE

Both ARCserve Setup and ARCserve Manager  will not load
under Windows Standard mode.  Both require Windows 386
Enhanced Mode to run.

2.   WIN-OS/2 ENHANCED MODE

ARCserve 5.01 Update does not run under WIN-OS/2 Enhanced
Mode.

3. WINSTART.BAT and BREQUEST.EXE

WINSTART.BAT is configured by ARCserve Setup to
automatically load BREQUEST.EXE (Btrieve client requester)
upon starting Windows.  It has been found that when using
WINSTART.BAT to start Windows 3.1 in enhanced mode,
everything works fine until you exit Windows, which
intermittently hangs the workstation.   You can avoid this
problem, by placing all the commands found in your
WINSTART.BAT into your AUTOEXEC.BAT.  WINSTART.BAT commands
should be loaded after your workstation shells i.e. ipx,
netx.  Alternatively, you can load BREQUEST.EXE before
starting Windows.  Be sure to rename or delete your
WINSTART.BAT file.

4.   NWIPXSPX.DLL

Older versions of NWIPXSPX.DLL may have been loaded by other
Windows applications that work with NetWare. Make sure you
use the NWIPXSPX.DLL provided by ARCserve Setup.

5.  ARCserve Attended Tasks

 Report files generated by Attended Tasks cannot be FAXed,
printed or E-mailed through the Reporter.

6.  NetWare Bindery Files

The NetWare bindery is a database which contains information
about users, password requirements, security equivalences,
etc.  The two bindery files in NetWare version 2.2 are
NET$BIND.SYS and NET$BVAL.SYS.  Under NetWare 3.x, the
bindery files are:  NET$OBJ.SYS, NET$PROP.SYS, and
NET$VAL.SYS.

To maintain the integrity of your NetWare file server, the
bindery files should always be backed up and restored as a
group.

Given that the bindery files are backed up when the SYSTEM
directory is backed up, ARCserve restores the bindery
whenever the SYSTEM directory is restored, unless the
"EXCLUDE FILE FILTER" is directly applied to those files.
____________________________________________________________
______________________

The following fixes and enhancements have been added to the
ARCserve Manager since the ARCserve 5.01 release:

Enhancements:

1.  The ARCserve Manager now supports International
Date/Time Formats.   Changing the system  date/time format
will now be reflected by ARCserve.

2.  The Tape Session Detail Report will now display MAC Long
Names, in addition to displaying the equivalent Short Name
of files.

3.  The E-Mail configuration form has been extended from 8
to 120 characters for the "MHS DIR", "MHS ID" AND "MHS
USERNAME" fields.

4.  A "workaround" has been applied to the Novell Client
API, NWScanForTrustees(),  to prevent an intermittent
General Protection Fault which occurred when using Attended
Copy.

5.  ARCserve has been enhanced to support SVGA cards with
800x600 resolution.

6.  Find File is now able to retrieve MAC files which
contain special characters inside the filename (specifically
ANSI characters between 129 and 255).

Fixes:

1.  Repeated saves and modifications of a backup job will no
longer create a phantom session password on tape.

2.  If  the last backup in an Auto-Pilot set was an
incremental or differential backup, then on restore,
ARCserve would not prompt for the tapes in the correct
order.  This problem only occurred for restores done at the
directory level.  Volume restores were not affected.

3.  Session numbers will now be displayed accurately in the
Tape Session Detail Report.

4.  For backup, the database now records the time of the
backup as the last time the directories were updated (files
are not affected).  This is needed to age the backups and
find the most recent backup.


____________________________________________________________
___________________________________

II. ARCserve Server

The following fixes and enhancements have been added to the
ARCserve Server since the ARCserve 5.01 release:

Enhancements:

1.  An additional console command  has been added to pack
all the ARCserve Database files.   Packing frees redundant
space in the database files and makes it available for other
use.  At the file server console prompt, type the following:

          ASDB P=ALL

 2.  The ASDB.NLM will now display a confirmation message to
reflect what has been entered in as an
 ASDB console command.  For example,  if the user types in:

          ASDB  P=ALL
          [ASDB] P=ALL                        confirmation
message displayed by ASDB


3.   When a Merge operation is performed, redundant entries
are no longer stored in the database which helps in
controlling the size of the database.

4.  The  Client Tracker now supports the following console
commands:

          CLIENT D=<Y/N>  displays the workstations as they
are tracked
          CLIENT H  displays help console command syntax
          CLIENT T=NN    time interval between each tracker
cycle where NN is   minutes
          CLIENT W=<Y/N>retrieve workstation information

5.  The Client Tracker now supports up to eight LAN cards in
a server.

6.  The MAC Tracker (MACDB.NLM) will now recognize the
following strings to track Macintosh
workstations:     "Macintosh", "Quadra", and "PowerBook".

7.  Support has been added to the ARCOPY.NLM to enable copy
of  Gupta SQLBase Databases via Cheyenne's DBagent to other
NetWare destinations.

8.  Broadcast messages will now also be sent out to queue
operators, as well as the job owner.

9.  Occasionally certain MAC files would be treated as DOS
files on remote 3.12 and 4.01 servers.   This has been
resolved and MAC files will now be properly identified.

10.  A "workaround" to a CLIB API, LogoutFromFileServer(),
which occasionally causes a NetWare 4.x server to crash, has
been implemented to the Client Tracker.

11.  A "workaround" to the problem caused by a call to the
CLIB API, GetInternetAddress(), which caused a NetWare 4.01
host server to abend if the "Clear Connections" Options was
set, has been implemented.

12.  If the target volume is dismounted in the middle of a
backup job,  ARCserve will be able to detect that the volume
has been dismounted and properly terminate the job.

13.  ARCserve will no longer attempt to back up additional
volumes, if there is a tape media error detected.  The job
will now be cancelled.

14. A "workaround" to the problem which occurred when
backing up NetWare Directory Services as a user without
Supervisory Object Rights to the root has been implemented.
Previously, the message, "Failed to allocate short term
memory" would appear on the server console screen.

15.  When backing up a remote 3.x file server, the message
"Failed to open NET$OBJ.SYS's data fork", will no longer
appear.

16.  OS2 and NFS files with names up to 31 characters are
now supported in the database.

17.  ARCserve has been enhanced to properly handle filenames
containing the string "%s" during an Unattended Copy
operation.

18.  Backup/restore filters will no longer be ignored when
the server has low memory conditions.   If ARCserve detects
low server memory conditions, it will now abort the job.

19.  If you do not require SMS to backup the OS/2 and UNIX
name spaces, add the following switch when loading ARCserve,
in order to conserve memory:

          LOAD ARCSERVE -F

Fixes:

1.  The Client Tracker (CLIENTS.NLM),  by default,  now
retrieves only Network and Node addresses of
workstations.  It will no longer retrieve workstation
specific information, as the default.  This helps reduce
network traffic and  improves the performance of the Client
Tracker.  However, to enable retrieval of workstation
specific information, such as,  IPX/SPX version, shell
version, hardware settings, etc., load the Client Tracker as
follows:

          LOAD SYS:\ARCSERVE\NLM\CLIENTS W=Y

or, if CLIENTS.NLM is already loaded, type the following:

          CLIENTS W=Y           (type W=N to turn off)

2. The Client Tracker has been modified to limit its
diagnostic broadcasts if it fails to receive a response from
the workstations on a specific network.  This will prevent
workstations from locking up.

3.  A problem with the Auto-Pilot logic, which occurred when
the "Overwrite any Tape" option was selected in the ARCserve
configuration screen has been corrected.  ARCserve will now
check the database to see if  the tape in the drive may be
recycled.  It will no longer overwrite tapes that are
required by the Auto-Pilot set, even if the "Overwrite any
Tape" switch is selected.

4.  The problem which prevented ARCserve from using SMS
logic when file servers had similar names, i.e. ZEUS and
ZEUS401 has been corrected. Previously, the following
message would be displayed, "Failed to connect TS on server,
fffdffdd".
____________________________________________________________
_______________
III.  ARCserve Tape Server

Support for the following equipment has been incorporated
since the release of ARCserve 5.01:

Drives                   Host Adapters

Aerial DAT Tower              Adaptec 2740
Cipher T860s DLT              Adaptec 2740T
Compaq DDS-2 DAT
Conner MS20 DLT               Adaptec 2742
Conner MS6000            Adaptec 2742T
Data General  Clarion Tape Array        Adaptec 1540CF
Digital TLZ06 DAT        Adaptec 1542CF
Digital TLZ202                BusLogic 445 VESA
Digital DLT-2000              BusLogic 542D Differential
Digital DLT-6000              IBM Fast/Wide SCSI II
GigaTrend SL Turbo DAT        IBM Future Domain ASPI
HP C1533A                IBM RAID SCSI
MDI LaserBank 1300D      Perceptive Solutions PSI 3290
MDI LaserBank 2000       Procomm Xelerator
Sony 5200 DDS2 DAT       UltraStor 14FB
Storage Solutions 851B DAT         UltraStor 24F
StorageTek 409 DLT       UltraStor 34F
Tandberg 3650            Vortex GDT 3000A
WangDAT 3400DX DDS2 DAT

* Please contact Cheyenne Software for latest Certified
Device list.

The following fixes and enhancements have been added to the
ARCserve Tape Server since the ARCserve 5.01 release:

Enhancements:

1. ASPI50.NLM was enhanced to support the latest version of
AHA1510/AHA1520.

Fixes:

1.  ARCserve will no longer prompt for a non-existent
Sequence 2 tape during a selective Tree/Tape View Restore.

2.  Tape Test Verification will now work properly.

3. A Contemporary Cybernetics (CCG) 8200 Tape drive is now
correctly identified such that a selective Tree/Tape View
Restore can be performed correctly.

4.  ASPI50.NLM will no longer display incrementing scrolling
numbers on the file server screen.

5.  The Exabyte 2501 tape drive will no longer generate
erroneous media errors when a brand new tape is used.
____________________________________________________________
_________________________

IV. Technical Tips

SYMPTOM :

An active job (backup or restore) is in progress and you
unload ARCserve by typing ASTOP at the NetWare Server
Console.  The server abends.

SOLUTION:

ASTOP.NCF should only be run when there are no active jobs.
A SCSI data transfer may take place after ARCserve is
unloaded but before the TAPESVR is unloaded.  This may cause
an abend.  Therefore, if you wish to run ASTOP.NCF to unload
the ARCserve NLMs, use the ARCserve menu option to
"Deactivate ARCserve" and wait for all jobs to be completed
or aborted.


SYMPTOM:

ARCserve is loaded by placing ASTART.NCF in AUTOEXEC.NCF.  A
server abend occurs when typing an ARCserve console command
at the NetWare console.

SOLUTION:

It is highly recommended that you do not load ASTART.NCF
through AUTOEXEC.NCF.


SYMPTOM:

The database pie chart appears to be incorrect and the
server's disk spaces is greater than 2GB.

SOLUTION:

 Since, the Novell API, NWGetVolumeInfoWithNumber(), does
not support more than 2GB, the pie chart will not be
displayed correctly.


SYMPTOM:

Backup speed appears to be sluggish and there are thousands
of files in one directory.

SOLUTION:

Since the server is attempting to cache as many file
directory entries as possible, if the Directory Cache
Buffers are insufficient to efficiently handle this task,
the result is a great deal of NetWare overhead.  To
alleviate this situation, it is recommended that you
increase the Minimum Directory Cache Buffers using the
Novell Set command.  Also check to see that the Maximum
Directory Cache Buffers parameter is adjusted accordingly.

     ex.   Set Minimum Directory Cache Buffers =1000


SYMPTOM:

An error message 8848 - Unknown NetWare Error appears on the
ARCserve manager screen and E0139 appears on the ARCserve
Message Screen.  The server is running NetWare 3.12.

SOLUTION:

Make sure you are loading NDS.VLM in your NWCLIENT
directory.  This is generally caused by not having the
NDS.VLM file or that it has been stopped from loading by
setting "USE DEFAULTS =OFF" or  "NETWARE CORE PROTOCOL
=BIND" in your NET.CFG file.


SYMPTOM:

An error message "Error - 70648. Failed to add job
Server:server name" appears on the workstation after running
ARCBATCH. .

SOLUTION:

Make sure you are loading NDS.VLM in your NWCLIENT
directory.  This is generally caused by not having the
NDS.VLM file or that it has been stopped from loading by
setting "USE DEFAULTS =OFF" or  "NETWARE CORE PROTOCOL
=BIND" in your NET.CFG file.


SYMPTOM:

The message "Failed to ScanTrustee", 9d appears on the
ARCserve RunTime Screen and in the Activity Log.

SOLUTION:

An unattended backup or copy job on a 4.x host where the
source is a remote server with more than 1000 directories,
is the cause.  This problem has been resolved by a new CLIB
Version 4.01d (PTF 940309) which is on our BBS and in our
CompuServe forum.   This CLIB is later than the one in
LIBUP2 which is found on NetWire.  An interim workaround to
this problem is to break up the job into smaller jobs with
less than 1000 directories in each.

SYMPTOM:

A host server running NetWare 4.01 abends during unattended
remote job operations.

SOLUTION:

This problem has been resolved by a new CLIB Version 4.01d
(PTF 940309) which is on our BBS and in our CompuServe
forum.   This CLIB is later than the one in LIBUP2 which is
found on NetWire.

SYMPTOM:

A server running NetWare 4.01 reboots upon loading ARCserve.

SOLUTION:

This is a very rare situation and can be attributed to a
problem in NetWare.  ARCserve tries to put a station
restriction on the CHEY_ARCHSVR user so that only the host
server can login as CHEY_ARCHSVR.   A solution to this
problem is to load the ARCSERVE.NLM with this feature
disabled as follows:

          LOAD ARCSERVE -R

If  the ARCSERVE.NLM produces a "Failed to login " message
when loaded, then remove the Station Restrictions on
CHEY_ARCHSVR manually through NETADMIN.

____________________________________________________________
_______________________

V. Packing List

This section contains a list of the files and locations for
the ARCserve 5.01 Update Release.  A short description of
each file and its purpose follows.

MANAGER

arcserve.exe   ARCserve Manager for Windows
asbackup.exe   ARCserve Backup
ascompar.exe   ARCserve Compare
asconvrt.exe   ARCserve Conversion Utility
ascore.dll          ARCserve Core API
ascopy.exe          ARCserve Copy
ascount.exe    ARCserve Count Utility
asctp.dll      Cheyenne Tape Protocol
asdb.dll       ARCserve Database routines
asmerge.exe    ARCserve Merge Tape Utility
aslocale.dll        ARCserve Internationalization Library
asnet.dll      ARCserve NetWare C Routines
aspurge.exe    ARCserve Purge Utility
asres.dll      ARCserve resource file
asrestore.exe  ARCserve Restore
asscan.exe          ARCserve Scan
astape.dll          ARCserve Tape DLL
astask.dll          ARCserve Attended Task DLL
asupdate.wri   This file
astutil.dll         ARCserve Tape Support DLL
asutil.dll          ARCserve Utilitity Dialogs

NetWare Files

nwcalls.dll         NetWare Calls DLL
nwipxspx.dll   NetWare IPX/SPX Protocol Routines
nwlocale.dll   NetWare Local DLL
nwnet.dll      NetWare Network DLL
wbtrlocl.dll        NetWare Btrieve Local Database DLL


ARCserve SERVER FILES
                              
aconsole.msg   Message file for arcserve.nlm
aprocess.msg   Message file for aprocess.nlm
aprocess.nlm   ARCserve backup, restore, merge and compare
coordinator
arcopy.msg     Message file for arcopy.nlm
arcopy.nlm          ARCserve file copy nlm
arcserve.hlp   Help file for arcserve.nlm
arcserve.nlm   ARCserve Scheduler
asdb.nlm       ARCserve database API
asdb.msg       Messages for asdb.nlm
clients.msg    Message file for clients.nlm
clients.nlm         ARCserve Client Tracker
faxlib.nlm          FAXserve interface
fstape.msg     Message file for fstape.nlm
fstape.nlm     ARCserve fileserver backup/restore/compare
NLM
macdb.msg Message file for macdb.nlm
macdb.nlm      NetWare Macintosh Workstation Tracker
      rwdb.nlm           ARCserve support NLM
standard.msg   Message file for standard.nlm
standard.nlm   ARCserve Standard Tape Support
tapesvr.hlp         Help file for tapesvr.nlm
tapesvr.msg    Message file for tapesvr.nlm
tapesvr.nlm    ARCserve Tape Server
wstape.msg     Message file for wstape.nlm
wstape.nlm     ARCserve workstation backup/restore NLM

ARCserve TAPE DRIVERS
                              
aspi50.nlm          ARCserve ASPI tape driver

ARCserve REPORT FILES

copydtl.rpt         Runtime report file
device.rpt          Runtime report file
job.rpt        Runtime report file
media.rpt      Runtime report file
report.lst          Runtime report file
sessdtl.rpt         Runtime report file
tapesess.rpt   Runtime report file
target.rpt          Runtime report file

NetWare Btrieve  Files

bdirect.msg    Btrieve Directory Services Message File
bdirect.nlm         Btrieve Directory Services Utility
bdrouter.msg   Btrieve Directory Services Support Module
brebuild.msg   Btrieve Rebuild Message File
brebuild.nlm   Btrieve Rebuild Utility
brouter.msg    Btrieve Router Message File
brouter.nlm    Btrieve Server-Based Record Management Help
File
bsetup.hlp          Btrieve Setup Utility Help File
bsetup.msg     Btrieve Setup Utility Message File
bsetup.nlm          Btrieve Installation and Configuration
Utility
bspxcom.msg    Btrieve SPX Communication Message File
bspxcom.nlm    Btrieve Communications Program
bspxstub.msg   Btrieve Stub Message File
bspxstub.nlm   Btrieve Stub Monitor Utility
btrieve.msg    Btrieve Message File
btrieve.nlm         Btrieve Server-Based Record Management
btrmon.hlp          Btrieve Monitor Utility Help File
btrmon.msg     Btrieve Monitor Message File
btrmon.nlm     Btrieve Monitor Utility
btrvstub.nlm   Btrieve Stub for SFTIII Support
butil.msg      Btrieve Utility Message File
butil.nlm      Btrieve Maintenance Utility
rspxstub.msg   Btrieve SPX Stub Message File
rspxstub.nlm   Btrieve SPX Stub File


NetWare 3.1x System Files

after311.nlm
ipxs.nlm
nwsnut.nlm
smdr31x.nlm    (only installed to NetWare 3.x servers)
smdr.nlm       (only installed to NetWare 4.x servers)
spxs.nlm
streams.nlm
tsa312.nlm          (only installed to NetWare 3.x servers)

NetWare  4.01 SYSTEM Files

ipxs.nlm
spxs.nlm
smdr.nlm
streams.nlm
tli.nlm
tsa400.nlm          (only installed to NetWare 4.x servers)
tsands.nlm          (only installed to NetWare 4.x servers)

