ACFSYSOP.DOC

85.6 KB 48b09756e64537b0…

┌───────────────────────────────────────────────────────────────────┐
│ The Auto Control File System - AKA, ACFiles │
│ The Originator of File Tagging │
├──────────────┬─────────────────────────────────────┬──────────────┤
│ ▀▀▀▀▀▀▀▀▀▀▀│ ACFiles Version 5.40 │▀▀▀▀▀▀▀▀▀▀▀ │
│ ▀▀▀▀▀▀▀▀▀│ BBS File System Replacement Utility │▀▀▀▀▀▀▀▀ │
│ ▀▀▀▀▀▀│ The Best File System Available │▀▀▀▀▀ │
│ ▀▀▀│ By: Ray 'C'ole │▀▀▀ │
└──────────────┴─────────────────────────────────────┴──────────────┘

Documentation By
Ray Cole and Al Hays

Dedication
──────────

This version is dedicated to the ACFiles Beta Team, without whose
many ideas, dedicated support, and tireless efforts this version of
ACFiles would not have been possible, and

To my Father, Ivey Cole, whose constant inspiration prompted me to
write, release, and continue to improve ACFiles ... and who taught me
that the only idea that absolutely "can not be done" is the one that
has not yet been attempted.

I thank you all, especially you Dad.

- Ray 'C'ole

ACFiles SysOp Documentation - Table of Contents
─────────────────────────────────────────────────────────────────────
Disclaimer, License Agreement, Overview ........................... 3
Feature Highlights ................................................ 5
Important Terminology ............................................. 7
Errorlevels ....................................................... 7
Requirements ...................................................... 7
Getting Started ................................................... 8
ACFCONF.EXE (ACFiles Configuration Program)
General Configuration ........................................ 8
File Area Configuration ..................................... 12
Node Configuration .......................................... 16
Protocol Configuration ...................................... 17
PROT_LOG.EXE ............................................. 19
Control Files
LIMITS.CTL .................................................. 21
ARC_VIEW.CTL ................................................ 22
DRIVES.ACF .................................................. 22
ACFIDX.CTL .................................................. 23
ACF_MOVE.CTL ................................................ 23
ACMASTER.CFG ................................................ 23
Other Setup Considerations
DSZ/GSZ, DSZLOG ............................................. 24
Interfacing ACFiles to BBS ....................................... 24
Batch Files for TOTAL Configurability
MOVEFILE.BAT ................................................ 25
COPYFILE.BAT ................................................ 25
PRE-DOWN.BAT ...................... See Multi-Node Operations
DROP_DOS.BAT ................................................ 26
AFTERUP.BAT ................................................. 26
SysOp Command Menu ............................................... 27
On-Line SysOp Keys ............................................... 29
Custom ANSI/ASCII Menu Screens ................................... 30
Utility Programs ................................................. 31
ACMAINT.EXE ................................................. 31
ACMASTER.EXE ................................................ 31
ACF_UPL.EXE ................................................. 31
ACFIDX.EXE .................................................. 32
FD2ACF.EXE .................................................. 32
ACF_ADD.EXE ................................................. 32
ACF_OPT.EXE ................................................. 32
ACF_OFF.EXE ................................................. 33
ACF_RET.EXE ................................................. 33
NEWDATE.EXE ................................................. 34
ENTERKEY.EXE ................................................ 34
LOGUPD.EXE .................................................. 34
Multi-Node Specific Operations and Utilities ..................... 34
ACF_MOVE.EXE ................................................ 34
CLEANDIR.EXE ................................................ 35
PRE-DOWN.BAT ................................................ 35
Common Questions and Answers ..................................... 36
Product Support .................................................. 37
BETA Site - Support System List .................................. 37
Registration ..................................................... 39

DISCLAIMER:
─────────────────────────────────────────────────────────────────────
ACFiles is only guaranteed to take up disk space if you have it on
any type of computer media. However, if you or your system deletes
it then it is no longer guaranteed to do anything.

LICENSE AGREEMENT
─────────────────────────────────────────────────────────────────────
ACFiles ver 5.40 is a shareware product. It may be freely copied and
distributed for evaluation as long as:

1) All files and documentation are distributed intact and not
modified in any way,
2) A copy of this documentation is provided with the program,
3) No charge, other than a media and handling charge when copied,
is levied when distributing ACFiles, and
4) Users of this program purchase a license for its use prior to the
expiration of the evaluation period. A reasonable evaluation
period of 60 days is granted. All copies of ACFiles in use
beyond the 60 day evaluation period must be either registered or
deleted.

One license per machine is required, with the exception of a single
multi-node BBS operating from a single location via LAN technology.

Please note that if you purchased a disk containing this software
from a public domain/shareware software distributor, you have paid
the media and handling charges as permitted above. You have not
purchased a license or registered this product with the Author.
Purchasing a license and registering this product is required for
continued use beyond the evaluation period.

OVERVIEW
─────────────────────────────────────────────────────────────────────
Auto Control Files (ACFiles) is a unique full File System for
EXITINFO.BBS (RA/QBBS/SBBS) BBS systems with a different twist. It
has a unique "Quick-Select" bar so that you and users can select
files while viewing a file list. From there the user can download
the files without having to ever enter a filename. The Sysop "tag"
files to do such things as mass file movement to other areas, mass-
deletion, un-hide the file for users, and even edit the description.

While ACFiles is a nice program for users, you will find it even
better from the SysOp side. The status bar looks similar to the
QuickBBS/RA Status bar. Setting it up is quite easy. There are a
variety of SysOp commands available and it even includes a full
-screen chat brought up with ALT-C by the SysOp.

ACFiles SysOp Documentation
Page 3

ACFiles now incorporates a full file indexing system to facilitate
immediate acquisition of files from even the largest BBS, whether via
a large hard drive(s), WORM Drives, or multiple CD-ROMS.

ACFiles can handle up to 260 file areas. Each one is configured for
access security, upload area, configured FILES.BBS path and name (so
you aren't forced into having it 1 particular way), area Name, and
even area description.

ACFiles also has a General Configuration for the BBS name, SysOp
level security, screen write mode (BIOS or Direct), whether or not
you want uploaded files to be hidden from a user, inactivity timeout
in seconds, and an Upload Time Credit ratio.

Tired of the way the MOVE commands are? Well, configure your own!
ACFiles calls a batch file upon moving a file. The batch file is
passed 4 variables that allow you to make it "smart" enough to
convert to various compression formats, scan for viruses, or whatever
you want it to do! Samples are included.

And finally, ACFiles is great for having a "File Section Co-SysOp"
with all of its powerful commands. No longer does a Co-Sysop need to
know your paths to all your file areas. Each area is easily
identified.

ACFiles SysOp Documentation
Page 4

ACFiles Feature Highlights
─────────────────────────────────────────────────────────────────────
* Complied under Borland C++ v2.0
* Takes less than 180K RAM to run
* Supports read/write/update to EXITINFO.BBS for RA/QBBS/SBBS
* Up to 260 File Areas Supported
* Private files/areas Supported
* GLOBAL operations sub-menu
* COMPLETE CD-ROM Support via indexed File Database (FAST!) and
support for Carousel/Cartridge Multi-Disk CD-ROMs and Multi-node
usage of Multiple Disk CD-ROMs
* PREDEFINE Drive Types (HD, CD-ROM, WORM) for Optimal performance
* Unlimited FREE areas
* Complete On-Line user Help
* FILE LISTING - ACFiles the Originator of File Tagging:
- File tagging for Ansi *AND* ASCII users
- Stop/Pause/Continue file listing for tagging, viewing, etc.
- Home/End keys available for File listings
- Users may view PREVIOUS PAGE while listing files
- All Archive manipulation commands available during listings
- VERBOSE/EXTENDED description support for File Listings
- External ANSI Full Screen editor support for VERBOSE/EXTENDED
descriptions (QuickED, TopED), Internal Line editor included.
* Logoff after upload
* Full Carrier detection - No Watchdog or CTTY required
* QuickBBS/RA style Status Bar display
* Configurable Keyboard inactivity timeout
* INTERNAL Split Screen Chat with word wrap
* ADVANCED SysOp Features include:
- ALL SysOp commands available to SysOp REMOTELY
- CONFIGURABLE Shell to DOS
- Sysop may return caller to BBS, send Garbage, or Drop Carrier
- SysOp may obtain RAW Dir listing of *ANY* path
- SysOp may Download/Upload from/to *ANY* Path
- Sysop configurable Upload credit multiplier
- SysOp configurable upload directories for each file area
- SysOp defined viewing of Upload "By-lines" by security level
- SysOp may configure level of "forced entry" for U/L descriptions
- SysOp may MOVE, EDIT, DELETE, etc. "Tagged" Files quickly
- Sysop may permanently edit user SecLev/Flags from within ACFiles
- Internal FILES.BBS Maintenance
- # days to keep file configurable to purge OLD files automatically
* ADVANCED ONLINE Archive manipulation:
- MULTIPLE file extension support for up to 10 Archive types
- View/Read Textfiles from within archive on-line
- Remove specific files for Download into custom packet
- Build a custom packet into ANY user-named, user-specified archive
format for download ONLINE! ZIP <==> ARJ, etc.
* Virus Scan, Comment and reARC upload files to any archive
Format using AFTERUL.BAT ... POWERFUL, FLEXIBLE, CONFIGURABLE!
* EXTENSION INSENTIVE Dupe checking for defined ARC formats
* FULL Configuration Program for system customization
* FULL external protocol support

ACFiles SysOp Documentation
Page 5

* FULL ratio enforcement via LIMITS.CTL support
* FULL security check by Flags and Security level
* Scans ONLY areas where user has access
* Batch Transfer Support
* Wildcard Support for file searches AND Transfers
* FULL Multinode Support
* Detects and Displays IntraNode Messages
* New file search from user specified date
* On-line or Off-line Files Counter support
* Configurable ASCII/ANSI Menus in Registered Version
* Still only $15.00 USD for non-commercial registrations

ACFiles SysOp Documentation
Page 6

IMPORTANT TERMINOLOGY
─────────────────────────────────────────────────────────────────────
Even if you think you know all the terminology of a file system, I'd
suggest you read this to keep you from getting confused. Some of
these may be new to you:

Area Tag: This is a short 2-key code for a file area. It consists of
the key combination pressed to get to the area. For
example, B5 would refer to Set B, Number 5. Area tags will
be displayed at the top of each area in ACFCONF. Anytime
you see something asking for an Area Tag, it is NOT a path.
Throw that idea out of your mind and think about each area
being assigned a specific tag and *NOT* a path.

Tagged File: This refers to a file that has been "tagged" using the
selection bar in the file listing. Tagged files can
have many things done with them upon your command.

FILES.BBS: This is the filename used by QuickBBS and other systems to
refer to a file consisting of the filenames and short
descriptions of the files in a particular file area. I
will refer to those lists as FILES.BBS's. However,
ACFiles does not force you to name it this. It is an
ASCII file with the filename beginning in column 1 and the
file description beginning in column 14.

MISCELLANEOUS ITEMS AND REQUIREMENTS
─────────────────────────────────────────────────────────────────────
ErrorLevels: Upon exit, ACFiles exits with the following errorlevels:

0 - Exit Program (Normal)
1 - General Error (File Not Found, Etc.)
2 - Carrier Dropped
3 - Time Up For User
4 - Fossil Init Failure
6 - Inactivity Timeout

Requirements:

IBM or compatible computer running Dos 3.X and later. An
EXITINFO.BBS (QBBS/RA/SBBS) style BBS and the achivers (up to 10) of
your choice. It may be possible, through the use of a "Door Type
Conversion Utility", to run ACFiles on other types of BBS Systems
although this has not yet been tested. I would be interested to hear
if you do this.

ACFiles SysOp Documentation
Page 7

STARTING OUT
─────────────────────────────────────────────────────────────────────

ACFiles setup in a NUTSHELL:

1) Run ACFCONF according to the instructions below.
2) Insure that all necessary CONTROL files are in place
3) Customize any BATCHFILES that you wish
4) Interface it to the BBS

! ! ! IMPORTANT ! ! !
****** ANSI.SYS MUST BE INSTALLED FOR ACFILES TO RUN CORRECTLY ******

Place all of the ACFiles files into their own sub directory. Run
ACFCONF.EXE. You will notice a selection of either General or Area
configuration. Select G first.

You will now see this screen:
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
1) BBS Name:
2) Desc Files:
3) SysOp Sec.:
4) Screen Write:
5) UpLoads Hidden:
6) Inactivity Timeout: Secs
7) Upload Time Ratio: Times
8) Auto-D/L File 1:

9) Auto-D/L File 2:

0) BBS Path :
A) Menu Twirl Prompt:
B) On-Line Counter Update:
C) ANSI External Editor:
E) Free Download K:
F) UL Drive Space Check K:
G) Show UL By Information:
H) Forced Pre-Upload Info:
I) SysOp Name:

▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Selection:

ACFiles SysOp Documentation
Page 8

Let's Cover the general setup area:

1) BBS Name:

Enter the name that you wish ACFiles to display as the BBS's name on
all menus. NOTE: The BBS name will appear as UNREGISTERED COPY
until registration.

2) Desc Files:

The path to the Extended Description directory. i.e. C:\ACFILES\DESC\
This is the area where ACFiles will maintain Extended File
descriptions. NOTE: If this area is UNDEFINED the Verbose/Extended
description feature will be DISABLED.

3) SysOp Sec.

The SysOp access security level. This is the level at which a user
will be able to access the advanced SysOp features via the SysOp
menu. It is recommended that this level be set EXTREMELY high.

4) Screen Write:

If you don't have an old CGA card that produces Snow with direct
screen writes, then select (2) for Direct writes. If this doesn't
work right for you when ACFiles is run then reset it to (1) (BIOS
Writes) which is a bit slower. If you run under a multi-tasker (like
Desqview) select 1 (BIOS Writes). It is possible to use DIRECT
screen writes under DESQview if VIRTUALIZATION is set ON.

5) Uploads Hidden:

If you want ALL uploaded files to be hidden from users (Users are
defined as those with access lower than the SysOp security defined
above) then select (1) for YES, Else select (2) for No and all
uploaded files will appear normally to all using the file system.

6) Inactivity Timeout:

Enter the number of seconds of user inactivity that you wish for
ACFiles to return to the BBS.

7) Upload Time Ratio:

This is the Upload/Time Ratio multiplier and determines how much time
credit a user gets when they successfully upload a file. For each
minute of upload time, the user will receive additional time based on
this factor. If you specified (3) here, and the user's successful
upload took 5 minutes, then ACFiles would award the user (3*5 mins),
or 15 minutes of additional time.

ACFiles SysOp Documentation
Page 9

8-9) Auto-D/L File 1 ( and 2): (OPTIONAL)

You may optionally assign 2 specific files for availability instantly
and "auto-download" by the user. This option assigns keys "1" and
"2" in the Main Menu to transfer these files without the necessity
for the user to enter a filename. The description is also included.
This is useful so that the user can download your master file list
(or other file) without knowing the name.

0) BBS Path:

Enter the MAIN BBS Path where your BBS .CTL files are maintained and
where intranode messages are written by the BBS Software.

A) Menu Twirl Prompt:

ACFiles will display a "twirling prompt" while waiting for a menu
selection, if desired. Select "1" to enable this feature or "2" to
disable.

B) On-line Counter update:

ACFiles will maintain a "download counter" of the number of times a
file has been downloaded when viewing the file listings. If you wish
the download counter to be updated on-line immediately following all
downloads, select "1". Selecting "2" will disable this feature, but
you may still update the counter during your daily maintenance by
using LOGUPD.EXE if desired.

IF YOU USE BIMODEM: It is recommended that this option be disabled
and upload counters be updated OFF-LINE.

C) ANSI External Editor:

A Line editor is included in ACFiles to edit the Verbose/Extended
descriptions. If you wish to use a FULL SCREEN ANSI editor, such as
QuickED or TopED, specify the FULL PATH and EXECUTABLE filename here
to invoke the editor.

E) Free Download K:

Enter the amount of "FREE" Kb that the user may download before
ratios take effect. A "0" would cause ACFiles to enforce ratios
beginning with the first byte.

F) UL Drive Space Check:

Enter the minimum amount of Drive Space that MUST be available before
ACFiles will allow an Upload.

ACFiles SysOp Documentation
Page 10

G) Show UL by Information:

Enter the MINIMUM security level to view the "Uploaded By:" line. To
disable By-line viewing, enter "0". This option only affects the "UL
By" lines created by, and stored in, ACFiles File Database areas. An
"UL By" line may be added to FILES.BBS with an external utility, but
ACFiles will have no control over the display of this information.
H) Forced Pre-Upload Info:

One of the problems with Batch Uploads is that the user may begin a
batch upload, wander away from the computer, and not be at the
console when the upload finishes. This is particularly annoying when
you get multiple files with no descriptions due to user timeout. By
selecting "1", you may force the user to enter the filename before
beginning an upload, selecting "2" will force the user to enter BOTH
the filename and description before beginning an upload, and
selecting "0" will not require any advance information.

NOTE: Upload info will be available to the user REGARDLESS of which
option you choose above. Setting the option to "0" will simply not
FORCE the user to enter the information PRIOR to beginning the UL.

I) SysOp Name: Your Name

This completes the GENERAL setup. Striking <ENTER> will return you
to the main ACFCONF menu.

ACFiles SysOp Documentation
Page 11

FILE AREA CONFIGURATION
─────────────────────────────────────────────────────────────────────
Next define your file areas. Hit A. You will see this screen

▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Area Tag: A0
1 - Name: <Deleted>
2 - Desc:
3 - Path:
4 - FILE.BBS:
5 - Upload Area Tag:
6 - Sec.: 0
7 - Type: Public
8 - Free: No
9 - Database Name:
E - Kill After: 0 Days A - Flag A: --------
F - D/L Sec.: 0 B - Flag B: --------
G - U/L Sec.: 0 C - Flag C: --------
H - Dupe Check: Yes D - Flag D: --------
Regular File Area
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
[+] Next, [-] Previous [J] - Jump to Area [U] - Global U/L Tag Change
[M] - Move Area [CR] - Exit
Enter # To Change:

The first area displayed is area "A0". Each area must be configured
separately to specify access limits, paths, descriptions, etc.

1 - Name:

Enter the SHORT name of the file area to be displayed at the ACFiles
main menu. i.e. Communications, Bulletin Board, DOS Utils, etc.

2 - Desc:

Enter the file area description that will be displayed at the sub-set
area menu. i.e. for the SHORT name "Communications", the description
might be, "Terminal Programs, Protocols, Etc." on the sub-set menu.

3 - Path:

Enter the FULL PATH to where the files for this area are stored. The
PATH, although important, is not critical if the File Data Base
option is used as ACFiles will keep a separate index of where the
files are located (see #9 below). Trailing backslashes are not
required.

ACFiles SysOp Documentation
Page 12

4 - FILES.BBS:

Enter the FULL PATH and FILENAME of the file area's list. The default
is the area's path and FILES.BBS as the name for your convenience.
The FILENAME may be ANYTHING you wish. However, if you decide to
name it differently from conventional methods, then the ACFiles utils
may be the only ones that will correctly identify the list names. If
you are new to this or want to be able to use your previous utilities
then leave it as the <Path>\FILES.BBS.

5 - Upload Area Tag:

THIS IS NOT A PATH NAME!!!! IT IS AN AREA TAG! ENTERING A PATH NAME
OR AN INVALID TAG WILL CAUSE ACFILES TO RETURN YOU TO THE BBS.

ACFiles allows you to force all uploaded files to any specifically
defined area when [U]pload is selected by a user from the current
area you are configuring. Let's say that you want all uploaded files
in this area to go to your Uploads Directory that just happens to be
area tag A0 (area tags are displayed at the top of each area's
configuration. See above example.) You would simply put A0 here.
This allows you to force uploads into a specific directory.

6 - Sec.:

Enter the MINIMUM Security Level necessary for the user to access
this area. Note that this area will not even be displayed in the
menus of ACFiles if the user's security level is less than the level
specified in this section. This includes GLOBAL downloads, searches,
etc.

7 - Type:

ACFiles allows "Private" uploads to/from users BY AREA. If you wish
this area to allow PRIVATE uploads, enter "1". Private files are
only available to you, the SysOp, and the intended recipient. No
other users may DOWNLOAD or VIEW a file marked as Private.

NOTE: Any user may download a "Private" file *if* they know the
filename. ACFiles, however, WILL NOT display the name except as
noted above to the intended recipient and the SysOp.

8 - Free:

ACFiles allows you to specify that all of the files in a specific
area are "FREE" and not subject to ratios. This is particularly
handy for product support, network coordinators who wish to provide
Nodelists/Nodediffs as "FREE" files, etc. If you wish this area to
be "FREE" select (1), else selecting (2) will enforce defined limits
and ratios.

ACFiles SysOp Documentation
Page 13

9 - Database Name: (Optional, but highly recommended)*

ACFiles will maintain a Database Index of all files in the area for a
near-immediate response to search queries, global downloads, etc. It
will also speed the file list display on larger systems. This is
particularly helpful for systems with optical drives like CD-ROMs or
WORMs and very large hard drives. If you wish to make use of this
advanced feature, specify a UNIQUE database name for the area of 8
characters or less. This name must be UNIQUE for each file area and
will be used by ACFIDX to create the area's index.

*NOTE: VERBOSE/EXTENDED descriptions are only available if the area
is a "Database Area" with a corresponding .FDB index file created by
ACFIDX.

E - Kill After <#> Days

This field is used by ACMAINT to automatically purge "old" and out
dated files from your system automatically. Enter "0" if you do not
wish ACMAINT to perform this feature or if you wish to determine
which files are kept. A perfect example of usage would be for a
network NODEDIFF area where the diff files are automatically purged
as their age precludes effective usage.

F - D/L Sec.:

Specify the minimum user security level to download files from this
area. This WILL NOT affect the users ability to view the file list,
but ONLY disallows downloads from the area if the user's security
level is less than that specified.

G - U/L Sec.:

Same as D/L Sec. but applies to uploads for this area.

H - Dupe Check

If you wish ACFiles to check for duplicate files BEFORE accepting an
upload into this area, select (1). ACFiles is "extension
insensitive" in it's treatment of "dupes" for all file extensions
that have been specified in ARC_VIEW.CTL. For example, if the Dupe
Check feature is enabled and the user attempts to upload MYFILE.ZIP
and the file MYFILE.ARJ exists, then ACFiles will treat the file as a
duplicate *IF* both ARJ and ZIP have been defined in ARC_VIEW.CTL.
MYFILE.TXT, however, would NOT be treated as a duplicate.

[A-D] - Edit Security Flags

This allows you to specify the necessary flags needed for a user to
access these file areas. All 4 flags sets are supported.

You've now configured your first file area. Hit [+] to go to the
next file area until you have configured all the areas you wish for
your system. Areas do not have to be contiguous.

ACFiles SysOp Documentation
Page 14

You will also notice the [J] and [U] commands. [J] allows you to
Jump To a file area by entering it's tag. If you wish to go directly
to area H8 from area A0, select [J] and enter H8.

[U] allows you to globally change EVERY file area's upload directory
to 1 area tag. Use this with care!

Once you are satisfied with your area configuration, hit Enter to
save your changes.

Finally, there is an option to [M]ove file area. This option is VERY
simple and you may move an entire file area by simply specifying the
AREA TAG (i.e. H8) that you wish to move the file area to.

ACFiles SysOp Documentation
Page 15

NODE CONFIGURATION
─────────────────────────────────────────────────────────────────────
The final step of the ACFiles configuration is Node Configuration.
This step must be completed ... single node BBS's will need only
complete it once. Multi-node BBS's will need to complete this step
for each node.

You must now execute a copy of ACFCONF *FROM WITHIN* your main BBS
directory. ^^^^^^^^^^^

Select [N] to enter the Node Configuration area. You will see this
screen:

▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
A) ACFiles Data Path:
B) Log File Name:
C) Node Number:

▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Selection:
A) ACFiles Data Path :

Specify the FULL PATH to your ACFiles data files.

B) Log File Name:

Specify the name of the LOG file for this node.

C) Node Number: Specify the Node Number (Whew!)

That's it. Upon exiting, insure that the file ACFNODE.CFG was
created by ACFCONF in your main BBS directory. Multi-node systems
should execute a copy of ACFCONF *IN EACH* directory specific to
*EACH NODE*, following the steps above and insuring that the file
ACFNODE.CFG is created in each directory.

ACFiles SysOp Documentation
Page 16

PROTOCOL CONFIGURATION
─────────────────────────────────────────────────────────────────────
In the ACFCONF program you'll notice a Protocol editor. For those
that don't need anything other than what is pre-configured with
ACFiles, I'd suggest leaving it alone. However, if you want to add a
protocol I've tried to make it as easy as possible.

ACFiles calls the external protocols and MUST be able to read a log
file which IT creates telling what it transferred, if it was
successful, and how many bytes were transferred. For that reason,
there may be 1 or two external protocols that won't work alone. You
may be able to use these protocols with the PROT_LOG.EXE utility
included with ACFiles (See description/examples below on Page 19-20).

If you have troubles, please send me a copy of the protocol you are
installing and I'll get you a configuration for it.

You'll notice a screen containing "slots" for each external protocol.
Select the letter of the slot you wish to edit.

It will now ask for the Protocol Name. This is how the name will
appear to the user when they select the protocol. This should be
short. <ENTER> by itself on the line will delete the protocol so BE
CAREFUL not to strike <ENTER> on a line with a Protocol that you wish
to keep.

Next specify whether this is a batch protocol. This is for protocols
like Zmodem that allow multiple files to be transferred. Answer Yes
or No accordingly.

Now specify whether this is a two-way protocol ... like Bimodem. Set
this to Yes if this protocol allows receiving and transmitting of
files at the same time, or No if not.

The next statement is the command to send a file. This and the next
one, command to receive, are explained in detail below.

ACFiles will call these lines exactly as entered. The following
symbols are special for ACFiles and causes it to substitute
information in place:

%1 - Filename(s) to send
%2 - Baud Rate
%3 - Com Port
%4 - File Containing List Of Files To Send
%5 - Upload Path
%6 - Download Path
%7 - Time Left in Minutes
%8 - Drive Of Upload Path - Ex. F:
%9 - Path of Upload Path - Ex. \IBM\RECEIVE

ACFiles SysOp Documentation
Page 17

Where does %8/%9 come in handy??

If you are NOT a registered DSZ user then you will NOT be able to
specify a path for where uploaded files go. Therefore you can call
the batch file with the %8 and %9 parameters and do:

%8
cd%9

NOTE: Once these parameters are passed to a batch file the numbers
will probably be reassigned by DOS. I'd suggest that if you call a
batch file (unlike what my examples show..) to *not* call it with ALL
9 parameters. Lengthy PATHNAMES, etc. can cause the command line to
exceed DOS length limitations causing undesirable results.

My PROTOCOL.CFG contains this for Xmodem:

XMODUP.BAT %3 %2 %1 %8 %9

Example File: XMODUP.BAT

@echo off
%3
cd%4
DSZ port %2 estimate 0 %1 rx %5

Example File: XMODDN.BAT

@echo off
DSZ port %2 estimate 0 %1 sx %3

Note that the statements in the batch file change because the batch
file uses the %'s that you sent and renumbers them from %1 on. So it
is MUCH easier to just send all %'s to a batch file and that way you
don't have to do any conversion.

Now we are down to the log file format. It is explained here:

Log File Format:

This is the ONLY way that ACFiles will know if a file is sent or not.
It will NOT update your counters, etc. correctly if this is not set
correctly.

You must know what type of log entries your external protocol makes.

Example of DSZ.LOG:

Z 149372 2400 bps 217 cps 0 errors 506 1024 F:\10\21.ZIP -1

ACFiles SysOp Documentation
Page 18

The Log Format statement in PROTOCOL.CFG represents a "format" of the
log file's lines. It has a few flags that represent various things:

%s - Status Flag Location
%b - Bytes Sent
%f - Filename - With or Without a Path
%g - Garbage

These represent locations. Spacing between them doesn't matter. So,
for the above log entry, the format would be:

%s %b %g %g %g %g %g %g %g %g %f

This means the first word will be the flags, which are checked with
the Sent Good/Received Good flags defined in Protocol.cfg. They are
case sensitive.

The second word is expected to be the # Bytes sent/received. The next
8 words are garbage and not needed by ACFiles. The 11th spot is the
filename. Since the rest of the log entry isn't needed, there are no
other "format" flags in the log format line and the rest is ignored.
Good Flags:

The next information asked for is what the protocol will put in it's
log file for the %f slot if it is successful at transfer. ACFiles
checks these case sensitive. These are allowed for both send and
receive flags. Z in the log example above would be a Receive good
flag.

Next is the protocol log name. THIS IS NOT a log file for you...This
is telling ACFiles what the log file name is that the external
protocol creates for it to read in needed information. Failure to
have this set right as well as the flags will cause the Byte counters
and Download # counters to not be updated.. That is it. For more
information or help, call the support BBS.

PROT_LOG.EXE Protocol Log Maker

Makes a log file for ACFiles for protocols that only return back an
errorlevel.

Usage: PROT_LOG PATH\FILENAME FLAG

Example:

PROT_LOG C:\0\ACFTEST.ZIP S

ACFiles SysOp Documentation
Page 19

Output:

PROT.LOG will contain a line in the following format:

Actual: FILENAME BYTES FLAG(Sent/Not)
ACFConf Setting: %f %b %s

FLAG can be whatever character you want. PROT_LOG will only
write the first letter (case-sensitive) to the log.

Here's an example batch file to use PROT_LOG:

Let's call this protocol "A-Modem":

@echo off
A-MODEM port %2 filename %3
if errorlevel 1 goto bad
:good
prot_log %3 SENT
goto end
:bad
prot_log %3 BAD
:end

That's it. This assumes that %3 in the batch file is the
path\filename of the file to be sent. Note that errorlevel protocols
can not be batch protocols using PROT_LOG. It is the opinion of the
author that batch protocols should create a log file of some sort in
order to be widely supported.

So, an example upload would be similar:

@echo off
A-MODEM receive port %2 filename %3
if errorlevel 1 goto bad
:good
prot_log %3 RECEIVED
goto end
:bad
prot_log %3 BAD
:end

ACFiles SysOp Documentation
Page 20

CONTROL FILES
─────────────────────────────────────────────────────────────────────
You have now completed configuring ACFiles. The next step is to
insure that all necessary control files are in place. LIMITS.CTL,
DRIVES.ACF and ARC_VIEW.CTL are the only REQUIRED control files.
ACFIDX.CTL is required ONLY IF you wish to take advantage of the
advanced file database feature of ACFiles (which is highly
recommended).

LIMITS.CTL

K-Byte limits are defined in a file called LIMITS.CTL. This file is
required for operation of QuickBBS/RA/SBBS, but a review of it is
provided here.

ACFiles will look to the MAIN BBS directory (as defined in the
General Config setup) for this file. QBBS/RA/SBBS uses LIMITS.CTL in
their daily operation. The format of LIMITS.CTL is:

Multiple spaces between entries are ignored. ACFiles will read from
300 --> 9600 until the end of the line has been read. If ALL of the
entries are not completed for every baud rate, ACFiles will assign
the last read baud rate to all higher rates. In the above example,
users with Security Level 500 will receive 2048Kb daily at 300 and
1200 Baud, and 9999Kb at 2400 and above. All Level 1000 users receive
9999Kb daily at ALL baud rates.

The # Files Ratio and Kb Ratio are WHOLE numbers. A ratio of 10 in
the Kb Ratio area will allow the user to download 10 Kb for every 1
Kb uploaded. Similarly, a ratio of 5 in the # FILES area will allow
the user to download 5 files for every 1 uploaded. Ratios will be
ignored if not included in LIMITS.CTL. An entry for 300 *THRU* 9600
daily kb limits must be included in LIMITS.CTL for ACFiles to
properly read/assign ratios. In the example above, NO RATIOS are
assigned to SecLev 100 and above.

ACFiles SysOp Documentation
Page 21

ARC_VIEW.CTL

Extension Types and Archive commands are specified in ARC_VIEW.CTL
and this ASCII file must reside in the ACFiles master data directory.
Up to 10 different extension/archive types may be specified.

ARC_VIEW.CTL comes configured for ZIP, ARC, ZOO, PAK, ARJ, and LZH
which is the majority of archive types in use on BBS systems today.
It may not, therefore, be necessary to change to the file unless you
wish to add other archive programs or alter those in existence.

Format: EXT View_Call Example: ZIP pkzip -v %s
Extract_Call pkunzip %s
Add Call pkzip -a %s
Delete Call pkzip -d %s

%s is the target filename and is passed by ACFiles to the archive
utility when invoked.

NOTE: There are two methods of invoking the archive programs:

RECOMMENDED: Place all of your archive utilities in a single
directory and insure that this directory is in your DOS
"PATH=" statement.

ALTERNATE: If the archive utilities are not in your system
path then you must specify the FULL PATH in the call of
ARC_VIEW.CTL:

Example: ZIP c:\util\pkzip -v %s
c:\util\pkunzip %s
c:\util\pkzip -a %s
c:\util\pkzip -d %s

DRIVES.ACF

This ASCII file defines the Drive types of your system for optimal
performance.

Drive Types Definitions:

0=Hard Drive (DEFAULT)
1=WORM Drive
2=CD-ROM (Read Only)

Example:

C 0
D 0
E 0
F 0
G 0
H 0
I 2

ACFiles SysOp Documentation
Page 22

ACFIDX.CTL (Optional, but required for File Database Feature)

This file defines ALL POSSIBLE PATHS (which have not been previously
defined in ACFCONF) for the location of files that may be contained
in your FILES.BBS and is read by ACFIDX.EXE when creating the File
Databases.

If the path has been previously defined in the AREAS set-up of
ACFCONF, then it is not necessary to list it in ACFIDX.CTL. This is
specifically designed to support large HD's, CD-ROMs and WORM drives
whose setup may not include all files to a particular "GROUP" in the
same directory, but which you wish to list in a single FILES.BBS. It
also means that you may list a file in several areas while
maintaining only one actual copy of the file on your system.

ACFIDX.CTL is an ASCII file, created with you favorite text editor.
The paths must begin on the first line of the file, each path on it's
OWN line, and continue (without any blank lines) until all paths have
been listed. The paths may be listed in any order.

EXAMPLE (PARTIAL ACFIDX.CTL for RBBS In-a-Box V2N3 CD-ROM):

I:\720K
I:\AJUT
I:\BREA
I:\CRAZ
I:\DISC
I:\EQUI
I:\FORD
I:\FWRD
I:\HDNO
I:\INST
I:\ZZAP

BCHAT.WIN

A One-Line ASCII file that defines the window available to the user
for SysOp Paging. Format is in 24 hour (military time) in the format
<BeginTime>-<EndTime>. Example: 0800-2300 would specify 8AM-11PM.
If BCHAT.WIN does not exist, 24 hour paging is assumed.

ACMASTER.CFG

For use with ACMASTER.EXE See UTILITY PROGRAMS on Page 31.

ACF_MOVE.CTL

For use with ACF_MOVE.EXE. See MULTI-NODE OPERATIONS on Page 34.

ACFiles SysOp Documentation
Page 23

OTHER SETUP CONSIDERATIONS
─────────────────────────────────────────────────────────────────────
The following environment variables must be set either in your
AUTOEXEC.BAT file or, within your BBS.BAT file or the ACF.BAT file.

SET DSZLOG=C:\QUICKBBS\DSZ.LOG
or
SET DSZLOG=C:\NODE1\DSZ.LOG

DSZLOG is the full path and filename to your DSZ.LOG. This MUST be
set to the same directory as the CURRENT NODE and must be named
DSZ.LOG. Failure to have this set right will result in NO download
counters/time ratios, etc. to be updated. Multi-node operations
pointing to the SAME PATH\DSZ.LOG will result in SHARE VIOLATIONS.

If you are multitasking then these variables may be set within a
batchfile (BBS.BAT or the ACFILES.BAT file) inside of the DV window
specific to the node in question rather than globally.

INTERFACING ACFILES WITH THE BBS
─────────────────────────────────────────────────────────────────────
Make a Type 15 (or Type 7 if you are using QuickBBS 2.75 or above)
that calls the door like the following:

C:
CD\ACFILES <c:\QuickBBS>

-You may specify the path to the EXITINFO.BBS

Simply put

-the path when calling ACFiles. Ex. ACFILES C:\QUICKBBS
-Trailing backslash is optional.

EGA43 <--------- This statement is to switch to 43 line mode
ACFILES IF you have EGA/VGA. Use whatever comes with
C: your video card!
CD\QUICKBBS
{call QuickBBS again}

You are now ready to try it out. Either run the BBS and call ACFiles
with the menu you have just created or go to the ACFiles directory
and type ACFILES L (for Local access).

If you have EGA or VGA, I'd suggest you have your batch file make
your screen length 43/50 lines upon start up. That way you can use
all the lines yourself as well as viewing the file list properly when
a remote is on-line. ACFiles will figure out your screen length for
both remote and local.

ACFiles SysOp Documentation
Page 24

BATCHFILE CONFIGURATION
─────────────────────────────────────────────────────────────────────
If a batch file FREQDOOR.BAT exists, then ACFiles will be triggered
to display a [R]equest Door command for users. ACFiles will call
Freqdoor.bat to run the door. This is in case you like one of those.
Moving Files - ACFiles

MOVEFILE.BAT and COPYFILE.BAT allow total configurability of how you
MOVE/COPY files. 3 examples are given -MOVEFILE.BAT does nothing
(will act like QuickBBS's Move command), TOZIP.BAT will convert all
files to .ZIP, and SCANZIP.BAT will scan the files being moved for
Viruses and convert to .ZIP format. USE EXTREME CAUTION WHEN
ALTERING THE MOVEFILE.BAT/COPYFILE.BAT files!!!

MOVEFILE.BAT

Called from ACFiles when the MOVE command is selected for the SysOp
Command menu. It is passed the following parameters:

MOVEFILE.bat {filepath} {filename} {filename *W/O.EXT*} {.EXT ONLY}

So let's say I'm moving a file TEST.ZIP from area A2 (which you
have configured as having a files path of D:\BBS). ACFiles
would pass the following:

MOVEFILE.BAT D:\BBS\ TEST.ZIP TEST ZIP

Therefore you can check %1, %2, %3, and %4 in your batch file to
do all sorts of things.

Upon exiting, MOVEFILE.BAT must create a file called FILENAME
that contains the file's name. This allows you to change to
filename during a conversion from .PAK to .ZIP. If the filename
above was not modified, then you could do ECHO %2.%3 >FILENAME.
That would put the name TEST.ZIP into the file FILENAME.
ACFiles will read this in and put that name in the file area's
list. Let's say we changed the extension to .PAK. We'd do an
ECHO %2.PAK >FILENAME and QuickBBS would know that the file's
name has been modified and will use it in the new file list.

Look at TOZIP.BAT and SCANZIP.BAT for good examples.

COPYFILE.BAT

Used exactly like MOVEFILE.BAT, but called with the COPY command
from the ACFiles SysOp menu.

PRE-DOWN.BAT

Called before all downloads (if exists). See MULTI-NODE OPERATIONS
on Page 34-35 for a complete description.

ACFiles SysOp Documentation
Page 25

DROP_DOS.BAT

Selecting the "Drop to DOS" option on the SysOp menu from within
ACFiles calls this batchfile. It may be used to invoke DOORWAY,
PCANYWHERE, or any other remote DOS shell that you wish to employ.
Two parameters are passed: Baud Rate (%1) Comm Port and (%1).

Example:

@echo off
DOORWAY %1 %2

AFTERUP.BAT

This batchfile is called immediately following a successful upload.
It is used to scan files for a potential virus, convert the file to a
specific archive format, include BBS comments/ads within the archive,
etc. Used in conjunction with ACF_RET, SCAN, and other utilities
makes this a very powerful utility.

Arguments:

%1 - Path to File
%2 - Filename
%3 - Filename Without .EXT
%4 - Extension of Filename (EXT without filename.)

A complete, fully commented example is included with ACFiles making
it usage "self-documented".

ACFiles SysOp Documentation
Page 26

SYSOP COMMANDS MENU
─────────────────────────────────────────────────────────────────────
Hitting [*] in any file area (for SysOp's) causes ACFiles to display
a complete sysop menu. Here you can Move a file(s), Delete a
file(s), Hide/Unhide a file(s), or Edit a file(s) description. All
of these operations may be performed on up to 100 tagged files at a
time.

[M] - Move Files

The move command will ask for files to move. If you have tagged
files in the file list using the selection bar then it will have
these names on the name prompt already. In either case, enter the
names of files you want to move and hit Enter. If the names were
valid it will ask you which area you want to move the file(s) to. A
complete list of file area names and their tags are displayed. Enter
the area tag associated with the file area you want to move the
file(s) to. ACFiles will then move the files calling the
MOVEFILE.BAT for any conversions you want.

[X] - Copy File(s)

The Copy File command works identically to the Move command, but
calls the batchfile COPYFILE.BAT.

[D] - Delete File(s)

Delete works in the same manner as above in enter the filenames. Hit
enter on the filenames you want to delete and it will delete them.
Space out the prompt and it will abort.

[H] - Hide/Unhide Files

Hide/Unhide works the same way with entering the filenames. For each
one entered it will tell you if it is currently hidden or not and
then asks if you want it Hidden or Unhidden. Hidden files will only
be displayed to those with SysOp access. What may be helpful to know
is that ACFiles does this by placing a @ in the front of the filename
in the area's list. This tells ACFiles (and it's utils) that these
are hidden files. This also works for comment lines, but comment
lines can not be hidden from this menu. You can go in and manually
edit the list with an ASCII editor to do this.

[E] - Edit Descriptions

All files entered here will be displayed and you will be asked to
edit the description. Hit enter after it is how you want it to be
and that becomes the file's new description.

ACFiles SysOp Documentation
Page 27

[A] - Add Filename(s)

This option allows you to add a filename into the listing. Upon
hitting A it will search the directory for any files that are not
listed in the FILES.BBS. It'll display their filenames. You can
then enter in the filenames you want to add. After entering the
filenames to add it'll ask for descriptions. Hitting enter on the
descriptions skips the addition of the files.

[V] - View Log File

This lets you view the log file. This is useful to tell who has
uploaded and downloaded throughout the day.

[R] - Remove Log File

This lets the sysop remove the log file. Confirmation of answering
Yes is required before it'll be deleted to keep away from accidents.

[C] - Clear Tagged List

Will clear the current Tagged List in preparation for more work.

[F] - FILES.BBS Editor

The FILES.BBS of the current area will be displayed when the
FILES.BBS editor is called. Here you may TAG files using the
selection bar. You will then be presented several options:

[M]ove: to Move the entry
[C]opy: to copy the entry
[D]elete: to delete the entry
[E]dit: to edit the entry
[I]nsert: to insert a line at the cursor position

[L] - Long Desc. Edit (Database Areas Only)

Similar to [E] (Edit Desc.) but pertaining only to the
VERBOSE/EXTENDED files descriptions.

[O] - OS Raw Directory

This command will allow you to view the Operating System's RAW
directory listing of any given path. ACFiles will prompt you for the
FULL PATH and will then display the listing. Using this option will
help you locate files on your system that are not available to
ACFiles as uploadable/downloadable but which you may access via
ACFiles's ability to Upload/Download via ANY path.

This is a VERY powerful option and is available to ANYONE whose
Security Level is greater than, or equal to, the defined SysOp level.
It is, therefore, recommended that CoSysOp assignment be tightly
controlled and monitored.

ACFiles SysOp Documentation
Page 28

[P] - PathEdit Files (Database Areas Only)

This command will allow you to edit the PHYSICAL path to a file(s)
and is intended for use in Database areas only. Because it is not
necessary to maintain a copy of the file physically in every area,
you may list a file in several area's FILES.BBS and simply "point" to
the path using ACFiles File Database Feature.

ON-LINE SYSOP KEYS
─────────────────────────────────────────────────────────────────────
CTRL-LFTARROW will increase a user's time by 1 minute.
CTRL-RGTARROW will decrease a user's time.

Other keys work like QuickBBS's status bar commands. PgDn will move
through the different status bars. F9 will display the available
SysOp keys. They should be self-explanatory.

ALT-C calls ACFiles' internal split-screen chat.
ALT-F to edit the user's FLAGS. (Permanently changed)
ALT-S to edit the user's Security Level. (Permanently changed)
ALT-T to edit the time instead of adding or subtracting it.
ALT-G Sends Garbage to the user
ALT-H Drops Carrier

SYSOP UPLOAD/DOWNLOAD EXTENDED OPTION

Anytime a user with SysOp SecLev Access selects [U]pload - [D]ownload
they will first be presented with an [A]nywhere option. This is a
very POWERFUL (and potentially DANGEROUS) feature. With this option
the SysOp may specify the FULL PATH and download a file from ANYWHERE
on the system. It also allows the SysOp to prepare batchfiles and
upload them directly into place. ... GIVE SYSOP ACCESS CAUTIOUSLY!

ACFiles SysOp Documentation
Page 29

CUSTOM ANSI/ASCII MENUS (Registered Version Only)

Upon Registering ACFIles you can create custom ANSI/ASCII screens for
use with ACFiles. If the ASCI/ANSI files below exist in your ACFiles
directory, then ACFiles will use that screen as a "template" for your
main screen menus

Note as well that you can also have ACFSET.A?? and ACF.A??.So, here
are the files you can have for templates:

ACFMAIN.ASC <- ASCII
ACFMAIN.ANS <- 25 Line ANSI
ACFMAIN.A43 <- 43 Line ANSI Main Menu
ACFMAIN.A50 <- 50 Line ANSI

ACFSET.ASC <- ASCII
ACFSET.ANS <- 25 Line ANSI
ACFSET.A43 <- 43 Line ANSI "A" through "Z" Sets
ACFSET.A50 <- 50 Line ANSI

ACF.ASC <- ASCII
ACF.ANS <- 25 Line ANSI
ACF.A43 <- 43 Line ANSI Specific Areas
ACF.A50 <- 50 Line ANSI

ACFSUB.ASC <- ASCII
ACFSUB.ANS <- 25 Line ANSI
ACFSUB.A43 <- 43 Line ANSI Global Operation Sub-Menu
ACFSUB.A50 <- 50 Line ANSI

Control Codes:

The following characters will produce substitutions in the ANSI/ASCII
files. Note that ACFiles is "smart" and won't (theoretically)
overwrite the data to the right of your control characters like most.
Use the enclosed ACFMAIN.ANS as an example and let your imagination
take over.

The codes are:
ASCII KEY-COMBO DESCRIPTION
-------------------------------------------------------------------
001 CTRL-A Area Name
002 CTRL-B Area Description
003 CTRL-C Area Tag (3-Character Format i.e. "A-0")

Simply place them in the same order as their corresponding parts
appear in the ACFiles Internal screens.

ACFiles SysOp Documentation
Page 30

UTILITY PROGRAMS:
─────────────────────────────────────────────────────────────────────
ACMAINT.EXE

This is the maintenance program. It reads in the area's lists and
cleans them up a bit by making the first letter of each word in
Upper-case, Like This Line Is. It also sorts the filenames
underneath the comment lines. This should cut down on your
maintenance.

ACMASTER.EXE (ACMASTER.CFG REQUIRED)

This creates a human-readable file of all the files and descriptions
in your file system. The filename is defined in ACMASTER.CFG, as
are the security levels for multiple allfiles listings.

If you run ACMaster then you can now check for duplicate uploads.
After upload, ACFiles will scan the master list for the newly
uploaded file's name. If it exists it'll mark the file as a
duplicate by putting DUPLICATE FILE!! in the description.
IF ACMASTER.HED exists (a SysOp created ASCII textfile) it is
appended to and displayed at the top of the ACMASTER list.

ACMASTER.CFG

This file is used by ACMASTER.EXE to create multiple master file
listings according to security level. The ONLY required
parameter is a single filename for the master list. In this
case, a single list would be created and accessible to all
users.

Syntax: LISTNAME <SEC> <FLAGS>

EXAMPLE:

ADULT.TXT 10-90 DX-------
ALLFILE.TXT 500

In the example above, the file ADULT.TXT would be created for
users with SecLev 10 through 90 with Flag D1 ON and ALLFILE.LST
for users with a SecLev of 500 or greater. Flags may be in any
order and are ignored if not specified. (X or 1=ON, - or 0=OFF)

ACF_UPL.EXE

This utility was provided for those who wish to include "Uploaded
By:" lines, but who do not wish to use the File Database Option of
ACFiles. It should be run during maintenance and appends the user
name DIRECTLY to the FILES.BBS file. For this reason, it will be
available for viewing by ALL users and will not be affected by the
SecLev Upload Viewing option in ACFCONF. If you use the FDB area
option, then you will not need this utility.

ACFiles SysOp Documentation
Page 31

ACFIDX.EXE

This utility need only be run once, an only if you intend to operate
ACFiles using the File Database Feature (recommended). It is run
from the main ACFiles directory with no parameters and will build the
initial .FDB indexes.

PRIOR to running ACFIDX, be sure that you have completed your file
area configuration in ACFCONF.EXE and listed any paths not contained
in the file area configuration in ACFIDX.CTL.

ACFIDX may optionally be called with AREA TAGS as command-line
parameters (i.e. ACFIDX.EXE A0 A3 H8). This will cause ACFIDX to
create .FDB indexes ONLY for those areas specified on the command
line. Default is ALL areas.

FD2ACF.EXE

Converts FileDoor-Style FILES.BBS's to ACFiles format. The formats
are 99% the same with the exception of the # Times a file has been
downloaded counter. This will make the conversion.

ACF_ADD.EXE (Database Areas Only)

ACF_ADD.EXE will search your FILES.BBS' and compare them against the
File Database Indexes for files NOT included in the indexes. It will
update the indexes for any occurrences of this nature. If the area
tag is passed as a command line parameter ACF_ADD will act on that
area only. Default is all areas.

ACF_OPT.EXE (Database Areas Only)

Over time, the order of files listed in FILES.BBS will not correspond
to the File Database Indexes due to alphabetizing the lists, etc.
This will slow the listings for the on-line user. Running ACF_OPT
will scan your FILES.BBS', compare them to the index files, and
reorder them for optimization where necessary. Running ACF_OPT in an
event on a weekly or monthly basis will insure the fastest response
time for your ACFiles users. If the area tag is passed as a command
line parameter ACF_OPT will act on that area only. Default is all
areas.

NOTE: If you NEVER re-arrange your FILES.BBS (alphabetically, by
subject matter, etc.) then you will not need to run this utility.

ACFiles SysOp Documentation
Page 32

ACF_OFF.EXE (Database Areas Only)

This does the same thing as ACF_OPT except it will also check
to see if files are off-line or not in the FDBs. This is useful
for those that like the speed of FDB's but like to use other
utilities to manage them or if they like deleting them during maint.
and would like for it not to show it as being there anymore. If the
area tag is passed as a command line parameter ACF_OFF will act on
that area only. Default is all areas.

ACF_RET.EXE

This utility is used in conjunction with AFTERUP.BAT, MOVEFILE.BAT,
and COPYFILE.BAT. It is called as follows:

ACF_RET <parm> [Message]

Parameters:

MSG Echos a message to the user upon return to ACFiles.
Used to explain delays and/or advise user of current
operation. i.e. "Thanks for the Upload!", "VISUS
DETECTED - FILE DELETED!", etc.

NAME Used to rename the file following an archive
conversion, etc.

DELETE Causes ACFiles to NOT update FILES.BBS. In
AFTERUP.BAT this can be used following a virus scan
that results in identification of a possible virus
within the file.

NODELETE (Default) Updates FILES.BBS with file description.

NOCREDIT Instructs ACFiles to NOT give credit for the file.
Can be used to eliminate credit for files that were
found to contain a virus.

CREDIT (Default) Restores user credit.

HIDE Hides upload from all users except users with
SysOp level access.

NOHIDE UnHides upload making it visible to all users.

TIME <ratio> Changes upload time multiplier for this file.

PATH Redefines the path in .FDB areas following movement of
the file in MOVFILE.BAT or AFTERUL.BAT.

ACFiles SysOp Documentation
Page 33

NEWDATE.EXE

This utility will "touch" files and change the date to "today's"
date. It can be used in AFTERUP.BAT, MOVEFILE.BAT, COPYFILE.BAT, or
anywhere you wish to touch file dates.

LOGUPD.EXE

If you have configured ACFiles to update download counters on-line,
LOGUPD will be of no use to you (unless you wish to update your
download counters based of FREQs as well). LOGUPD will scan the
ACFiles transfer log (or Binkley Log, Front Door Log, RA LOG, etc.)
for downloads (or FREQS) since the last time LOGUPD was run and
update the corresponding download counters in the FILES.BBS.

LOGUPD.EXE will work on ANY logfile that uses the QuickBBS/Binkley/FD
log format. This means that you may update your file counters to
include file requests from your mailer's logfile. LOGUPD maintains
an "index" of each logfile in the ACFiles master directory in the
format <logfile>.LUD (i.e. SYSTEM.LUD). This file is maintained by
LOGUPD to keep track of where it last conducted an update.

USEAGE: LOGUPD <path\logfilename>

MULTI-NODE SPECIFIC OPERATIONS

Besides the Node Configuration section of ACFCONF.EXE, there are a
few additional considerations when running ACFiles in a Multi-node
environment.

DOS's SHARE.EXE must be loaded. Simply follow the instructions in
your DOS manual.

ACF_MOVE.EXE

ACF_MOVE is intended to be run during the PRE-DOWN batch interface
for ACFiles. This program merely moves the files off of the drives
specified in ACF_MOVE.CTL. A copy of ACF_MOVE.CTL must reside in
each node's directory making sure the path defined in acf_move.ctl is
unique to each node. This will ensure that there will be no
conflicts. If you use ACF_MOVE, you'll need to use CLEANDIR or
another means of removing the directory specified in acf_move.ctl
so that you won't be consuming too much space.

ACF_MOVE.CTL is a simple ASCII control file which specifies the
temporary directory for ACF_MOVE.EXE to place the files prior to
downloading, and the drives from which this operation should
take place. A full self-documented example is included with
ACFiles.

ACFiles SysOp Documentation
Page 34

CLEANDIR.EXE

Intended to be used with the PRE-DOWN.BAT batchfile. Clears the
temporary directory of all files following a successful download.
Equivalent to DEL *.*

PRE-DOWN.BAT

This batchfile, if it exists in the ACFiles master directory, will be
executed prior to any download. It is particularly useful for multi-
node systems with CD-ROM(s) or Carousel/Cartridge type multi-disk CD-
ROM systems. Used in conjunction with ACF_MOVE.EXE and CLEANDIR.EXE,
this batchfile will allow you to copy the files FROM the CD-ROM to a
temporary directory on the Hard Drive, thus freing up the CD-ROM for
immediate access by another node.

A temporary directory should be created for each node to copy the
files to. i.e. C:\ACF_MOV1 for Node 1.

An example of PRE-DOWN.BAT:

@echo off
ACF_MOV %1 %2
CLEANDIR C:\ACF_MOV1

ACFiles SysOp Documentation
Page 35

COMMON QUESTIONS AND ANSWERS
─────────────────────────────────────────────────────────────────────

1. Q. ACFiles isn't updating the download counters or the user's
statistics. It also doesn't untag files after it transmits.

A. This is a symptom of not having your protocol's log setting
correct or could be you don't have the correct log format or
receive flags right. Check to make sure that your external
protocol is creating a log and that you have an appropriate log
format statement in ACFConf. If you need assistance with this,
don't hesitate to contact me. I'm willing to give you
configurations for any protocol.

2. Q. When moving/copying, it doesn't always get the name right after
conversion. What is happening?

A. You are not returning the correct filename to ACFiles via. the
ACF_RET program. If you need more help send your batch to me
and I'll get it patched up for you.

3. Q. When a user is on-line I sometimes don't see the statistics
information at the bottom of a file list or the file list looks
strange as they scroll.

A. This is not an error. ACFiles detects the remote system's
screen length and uses that. So if it detects them to have 50
lines and you only have 25 on your end then you will naturally
be missing some information. The user will see the screens
just fine though.

4. Q. What is an area tag???

A. An area tag is a 2-character I.D. for a file area instead of
having to give ACFiles a path all the time for moving files,
etc. It is the same key combination that you would do to get
to the area. So, area B5 would be Set B, Number 5. The area's
area tag is displayed at the top of the configured file areas
in ACFConf as well as ACFiles.

5. Q. When doing a file list I see ANSI codes.

A. You don't have ANSI.SYS installed. Or, if you have a 50 line
screen or something you may not have the correct ANSI.SYS
involved. Read your system's manuals for more information
there.

6. Q. ACFiles isn't returning to the BBS with the correct time left.

A. You are using a Type 7 that doesn't read the EXITINFO.BBS back
in or are failing to make sure the updated EXITINFO.BBS is in
the BBS/Node directory. QuickBBS 2.75+ will work fine with
Type 7. Earlier versions should run Type 15.

ACFiles SysOp Documentation
Page 36

7. Q. When running ACFiles under the File Database Option the
listings seem to grow gradually slower over time.

A. This happens when the FILES.BBS and the .FDB are "out of sync"
due to constant maintenance on the FILES.BBS (alphabetizing,
sub-grouping, etc). Run ACF_OPT which will optimize the .FDB
database files to correspond with the FILES.BBSs.

THAT'S ALL FOLKS
─────────────────────────────────────────────────────────────────────
That should be it. If you have any questions then please contact Ray
Cole at 99:9100/8, 1:382/83, or 50:5512/0. I'd be glad to hear from
you! If the demand is large enough I will create a Fido echo for
ACFILES support. Any responses to your netmail will be left on HOLD
for your system to pick up from me. I usually respond within 24
hours but I am in college at the University of Texas and school is of
the utmost importance ... so please be patient. Or you may call
(512)778-6246 at 300-14.4K HST and leave a message/page me there.

Support may also be obtained in the RA_UTIL, QUICKBBS, and SUPERBBS
echos as well as directly from the ACFiles Support/Beta Team Listed
below:

Larry Stultz PVT 9600 HST
The Technical Connection QuickBBS
Wellborn, Florida

Al Hays 1:363/89 407-438-7093 9600 HST/V32
Mystic Pharos BBS Remote Access CD-ROM
Orlando, Florida

Gary Joneson 1:351/621 604-752-5249 9600 HST
Shangri-La BBS Remote Access 3 CD-ROMs
Qualicum Beach, BC, Canada (2+ Gigs)

Johnny Pulliam 1:382/77 512-259-4896 9600 HST
Far Point Station Remote Access
Leander, TX

Matt Chapin 1:382/66 512-328-8078 2400
Eclectic Connection Remote Access
Austin, TX

Tom Lane 1:382/91 512-282-3941 2400
Flotom Enterprises BBS Remote Access
Austin, TX

ACFiles SysOp Documentation
Page 37

Steve Mitchell 1:14/643 701-594-9805 9600 CSP
Magic's Corner Remote Access
Grand Forks AFB, ND

Stephen Edgar 1:208/100 209-551-2258 9600 HST
Modesto Hub Remote Access CD-ROM
Modesto, CA

Ray Cole 1:382/83 512-778-6246 9600 HST
The Auto Control BBS QuickBBS WORM
Liberty Hill, TX

Thanks for your support!

Future programs by me will be released in support for ACFiles. DO
THE RIGHT THING ... By registering you will help me to be encouraged
to continue developing ACFiles and keep it in the forefront as the
world's premiere BBS File System.

ACFiles SysOp Documentation
Page 38

REGISTRATION for ACFiles v5.40 By Ray 'C'ole
──────────────────────────────────────────────────────────────────

First Name, Last Name: __________________________________________

Mailing Address: __________________________________________

__________________________________________

Voice Telephone Number: (______)________________________

Data Telephone Number: (______)________________________

BBS Software Configuration: ______________________________________

Are you a member of a network? [ ] Yes [ ] No

If so, please give your primary address: _________________________

Name of network: _________________________________________________

Where did you hear about ACFiles? _______________________________

_________________________________________________________________

Please list any comments, ideas, suggestions for improvement, or
additional features that you would like to see included in future
versions of ACFiles (PLEASE use additional pages if necessary <g>):

__________________________________________________________________

Registration Type and Amount Enclosed (check one):

[ ] Non-Commercial - $15.00 [ ] Commercial - $30.00

Make all checks payable to: Ray Cole
(US Currency only please!)

Mail Registration to: Ray Cole
Route 6 Box 255
Leander, TX 78641