1 Sample template files

The TEMPLATE.ZIP file contains several sample template files. The purpose of most of the files has already been explained in section 6.14. The following list explains the purpose of the other template files:
Template NameDescription
BANNERThis is a Banner template used to create a banner for archives.
MESSAGEThis is a Netmail announcement template used to write messages to accompany forwarded files.
REPORTSThis is a New file report template used to generate new file reports.

2 EAC utilities

The SAMPLE.ZIP file contains a sample configuration fil (PALMSCAN.CFG) for PalmScan.

3 Hatching files without moving them

When files are hatched, they are normally moved from an origin directory to a destination directory. ALLFIX will hatch a file each time the file specification entered in the Hatch manager exists in the configured origin directory.

Sometimes it is necessary to hatch files that are already in the destination directory.

When this occurs, ALLFIX will turn off the archive bit in order to signal that the file has been hatched. Otherwise, ALLFIX will hatch the files over and over again.

It is extremely important that no other program turns the archive bit back on, unless the file has to be hatched again.

It is known that this system is not entirely fool proof. There are many other programs, namely backup software, that make use of the archive bit. However, at the moment it is the most efficient way to handle this problem. Even though it has a number of disadvantages, it does offer the ability to easily re-hatch a file, by simply turning the archive bit back on.

The magic filename manager offers another way to hatch files with the Hatchnew option. The Hatchnew option is more dependable and, therefore, recommended above this particular method.

4 Errorlevels

ALLFIX reports the error levels of child processes with the statement error level [xx] from The meaning of the error level depends on the process and is totally independent of ALLFIX.

The following is a list of error levels for PKZIP/PKUNZIP and ARJ. For a list of the error levels for other programs, please consult the accompanying documentation.

Error levels for PKZIP
0No Error
1Bad file name or file specification.
2,3Error in ZIP file.
4-11Insufficient Memory.
12No files were found to add to the ZIP file, or no files were specified for deletion.
13File not found. The specified ZIP file or list file was not found.
14Disk full.
15ZIP file is read-only and can not be modified.
16Bad or illegal parameters specified.
17Too many files.
18Could not open file
19-23,29Insufficient Memory
26DOS 3.2 or later needed to span disks
28Destination for .ZIP is same as temporary file or Source and destination is the same
255User pressed control-c or control-break

Error levels for PKUNZIP
0No error.
1Warning error (such as failed CRC check).
2,3Error in ZIP file.
4-8Insufficient Memory.
9File not found. No ZIP files found.
10Bad or illegal parameters specified.
11No files found to extract/view etc.
50Disk Full.
51Unexpected EOF in ZIP file.

Error levels for ARJ
0No error.
1warning (specified file to add to archive not found, specified file to list, extract, etc., not found, or answering negatively to "OK to proceed to next volume..." prompt)
2fatal error
3CRC error (header or file CRC error)
4ARJ-SECURITY error or attempt to update an ARJ-SECURED archive
5disk full or write error
6can't open archive or file
7simple user error (bad parameters)
8not enough memory

4.1 Common errorlevels

The most common errorlevels are ones dealing with not enough memory. For PKZIP that means levels 4-11, for PKUNZIP levels 4-8, and for ARJ level 8. ALLFIX is capable of swapping the program memory to XMS, EMS, or Disk, and it is recommended that option is used when memory problems occur.

Another common errorlevel occurs when ALLFIX attempts to extract a FILE_ID.DIZ file from an archive. ALLFIX is not capable of looking inside an archive to determine if it contains a FILE_ID.DIZ file. Therefore, it simply attempts to unpack it from the archive. The decompression program will exit with an error if the FILE_ID.DIZ file is not contained in the archive. This error is very normal and should not cause any alarm.

First consult the appropriate documentation about errorlevel before approaching the author.

5 Common errors while importing files

Following is a list of common errors that occur when importing files:
Invalid destination drive: '<drive>' This error occurs when the drive on which the destination directory, for this fileecho, is located does not exist. The files for this fileecho will be moved to the bad tics directory. After the problem has been corrected, they can be reprocessed using the -Tossbad switch.
Invalid destination directory: '<directory>' This error occurs when the destination directory of a fileecho does not exist. The files for this fileecho will be moved to the bad tics directory. After the problem has been corrected, they can be reprocessed using the -Tossbad switch.
Insufficient disk space on the destination drive: '<drive>' This error means that the file being imported does not fit on the destination drive or that the space left on the destination drive after importing this file would be less than the minimum space required, as configured in the Global Options menu.
Duplicate file: '<filename>' This error means that the file being processed has already been processed. The criteria used to determine if a file is a duplicate can be configured in the Global Options menu. Less stringent criteria should be used if there are too many problems with duplicate files or based on the needs of the system.
CRC check failed: '<filename>' This error means that the file being processed has failed the integrity check. There are several possible explanations for this problem. The most likely explanation is that the file was damaged during transmission. Another likely possibility is that the CRC stored in the .TIC file was calculated wrong. Do not use the -Crc switch in order to process files with a CRC error.
Invalid password '<password>' from <node> This error means that this node is using the wrong password when sending files to this system. Change the configuration for this node in the Node manager or contact this node and correct the problem.
Node is not allowed to send files in this fileecho: <node> This error means that this node is not allowed to send files to this system. The configuration for this node in the systems list, for this fileecho, specifies that no files are to be received from this node. Update the configuration or contact this node to determine why it is sending files to this system.
File missing: '<filename>' This error means that the file referred to in the .TIC file does not exist.
Undefined area: '<fileecho tag>' This error means that the fileecho referred to in the .TIC file does not exist. ALLFIX, when configured, can automatically add new fileechos, in which case this error will not occur.
Undefined node: <node> This error means that this node is not listed in the Node manager. ALLFIX requires that each node, that files are received from, must be configured in the Node manager.
No Queue directory defined for pass through areas This error means that the queue directory, used to store files for pass through areas, is not defined. The consequence is that ALLFIX is not able to process the pass through files. They will be moved to the bad tics directory.
Can not auto-add new fileecho: No matching Mask found in group manager This error is reported when ALLFIX can not find a group in the group manager with a mask that matches the name of this fileecho. ALLFIX uses the masks in the group manager to determine which group defaults should be used for the new fileechos. Please see section [xx] for more details.
Unable to update file database! This particular error is reported when ALLFIX is not able to open the BBS specific file database files. This problem is often encountered when changes have been made to the BBS file area configuration without running FCOMP afterwards to signal the changes to ALLFIX. If running FCOMP does not solve the problem, then make sure that the destination directory of the fileecho is defined exactly the same way as the associated file area directory in the BBS configuration. ALLFIX uses the directory names to find out which filearea it should use.
Skipping <filename.TIC> not for us (node) This error means that the .TIC file contains a To verb, which is used to specify the destination system for that particular file. If the destination address following the To verb is not one of the AKAs of this system, then ALLFIX will give this particular error. It is possible that the To verb is left in the .TIC file by another type of fileecho processor. In this case, simply remove that line in the .TIC file with a standard ASCII text editor and execute the File command again.
Skipping <filname.TIC> file (<filename.ext>) is not complete This error means that the file transfer is not complete. A possible cause is that the mail session was prematurely aborted. Another cause is that the file size listed in the .TIC file is not correct. It is possible to force ALLFIX to process this file, by using the -NoSize switch, which turns of the file size check.
Unable to initialize B-Tree Filer, error 10310 This error sometimes occurs when running ALLFIX! for WildCat! under Windows 95/98. There is no real solution for this problem, however, a work-around has been developed. Add the following environment variable (in AUTOEXEC.BAT, for example):
If ALLFIX detects this environment variable, it will initialize the B-Tree Filer as if the "Network" option in MAKEWILD was set to "No network".

6 Using ALLFIX without a compatible (or no) BBS

This section does not pertain to those people using ALLFIX! for WildCat! since it is not possible to use that type of ALLFIX without a BBS system.

Most of the features in ALLFIX can be used without having a BBS. However, of the features, such as the FileFind feature and the Allfiles listings (FIXUTIL) can only be used when you have a BBS.

In order to make it possible for those people not using a BBS to also make use of these types of features, FCOMP has the ability to scan the fileechos instead of the fileareas. Everywhere, where people running a BBS would see their BBS file areas, you will see your fileechos. Simply run FCOMP with the parameter 255.

ALLFIX will, by default, create FILES.BBS files in each of the fileecho destination directories. If this is not required, simply toggle the No Touch switch in each of the fileechos and those files will not be created.

7 Creating a FILEBONE.?? file

FIXUTIL can be used to generate a FILEBONE.NA style file. A sample template has been included with ALLFIX. This template, however, is not the only thing one will need to generate a real FILEBONE.NA file.

The template, FILEBONE.APL, will generate a list of fileechos conform the standard of the FILEBONE.NA file.

A real FILEBONE.NA file has a textual description of each group of fileechos in the list. In order to include descriptions of each group in the generated FILEBONE.NA file, comment out the following lines in the FILEBONE.APL file:


This section in the template is used to include text files into the template output. The name of the include files are GROUP.XXX where XXX is the number of the group. If you make such a file for each group, in the Group manager, then you can generate a real FILEBONE.NA file using this template.

If you require headers and footers in the output, simply add @include() macros to the beginning and end of the template.

8 Frequently asked questions

This section contains a number of frequenly asked questions. Some of these questions and answers have been put together by dedicated beta team members.
ALLFIX/2 aborts with a runtime error when I use the File command. ALLFIX/2 may abort with a runtime error if the FILEDUPE.FIX file or the ALLFIX.DAT files are corrupt. Therefore, move the FILEDUPE.FIX file to another directory, to see if that solves the problem. If that does not solve the problem, then move the ALLFIX.DAT file. If this does not solve the problem either, then please contact the author.
My BBS software is not supported by ALLFIX, what I do about it? Section 3 in the documentation explains how to use ALLFIX with a non-supported BBS. However, due to the rapid development in ALLFIX, there is a good chance that ALLFIX will support your BBS within the near future.
Some of my downlinks are complaining about the file transfer rate when they receive lots of new files. It is way below the normal performance. Is there anything that I can do about this? Yes there is. The reduction in transfer rate is caused by the numerous .TIC files. These files are generally to small to accomplish a good transfer rate when sending them via a modem. In the node manager, there is an option called "Packing mode". By setting this option to "Pack .TIC files" or to "Pack ALL files", the transfer rate will increase since only larger files are being sent.
I have a downlink who is interested in receiving files from one or more of the file distribution networks available on my system, but he does not want to receive the acompanying .TIC files. Is this possible? Sure, just set up your downlink as you would setup any normal downlink in the Node manager. If you set the "Tic file mode" option for this downlink to "None", then ALLFIX will not send this node any .TIC files.
Some of my downlinks take part of a cost sharing system. I have dfined the fileechos as Cost sharing echos (by setting the Div costs option to C/S nodes), still I can't seem to force ALLFIX to send them any bills. How come? You probably failed to define your downlinks as participating in the cost sharing system. Go to the Node manager in ASETUP and for every node that should participate in the cost sharing, set the Billing option to Yes.
ALLFIX does not seem to be passing the costs of files on to my downlinks. Why is this happening? The Cost verb, used in the .TIC files to define the cost of the file, is only used in Advanced .TIC files. You should setup all your cost sharing nodes to use Advanced .TIC files. The option to toggle is called "Tic file mode".
What is the difference between "Add %" in the fileecho manager and "Add %" in the node manager? The "Add %" found in the fileecho manager is the percentage value that you can add to the cost of all incoming files. This value can be used to compensate for currency exchange rates. The "Add %" in the node manager is the percentage value that you can add to the total bill for a node. This value can be used to add the local VAT to the bill, for example.
I have a downlink that is interested in some particular files in a fileecho, but not in the rest of the files. Is there a way to only send those files to that system. For example, only send the NODEDIFF.* files and not the NODELIST.* files? Yes, this is possible. You need to make a new Magic filename entry in the Magic filename manager. Select as type "ForwardTo". In the From Area field select the fileecho in question. In the Spec field, select the file specification, such as NODEDIFF.*. In the systems list you can enter the node numbers of all the people that should receive this file.
How can I quickly create an "UNWANTED" file? If you use TranScan, you can simply use your TS5.DEL file.
What good is the "Update DESCRIPT.ION" file option, if I do not use 4DOS? The DESCRIPT.ION file is a FILES.BBS file that contains the filename and the associated description. Such a file can be very usefull to find out what each file is in a directory. So even if you do not use 4DOS, you may find this feature usefull.
ALLFIX is not reporting newly uploaded files on my BBS. What am I doing wrong? There are two things that can be wrong. First, you may need to run FIXUTIL -BuildDataBase, to rebuild the FILES.FIX in each of the BBS new file dirs directories. All new files uploaded, after FIXUTIL has been run, will be reported. The second source of the problem may be that you need to run FCOMP again. If you have made any changes to your BBS file areas, then run FCOMP and double check your BBS new file dirs configuration.
Why is ALLFIX not writing to my file database as it is supposed to do? In order to write to your specific BBS file database, you must turn the "Use FDB" option on for each fileecho associated with a BBS file area. You must also make sure to run FCOMP periodically, especially after making any changes to your BBS file areas.
Why is ALLFIX is not responding to any FileFind requests I enter on my own system? In the "Global options" menu, there is an option that tells ALLFIX whether or not is should process local requests. If this option is turned on, ALLFIX will respond to local requests. If this option is turned off, which is the default value, it will not. The name of this option is "Process local requests".
I am running Xenia as my mailer. What type of mailer should I select in ALLFIX? If you have the statement "NODOMHOLD" active in Xenia, then use "Portal of Power" or "BinkleyTerm" without any domain names defined in ALLFIX. If you do not hae that statement active in Xenia, then use "BinkleyTerm" and in that case you are able to use domain names in ALLFIX.
How should I setup the file descriptions for ProBoard? LongDesc character + One line LongDesc No LongDesc width 0 Max len of LongDesc 0 Spaces to indent 1
How should I setup the file descriptions for Maximus? LongDesc character One line LongDesc No LongDesc width 0 Max len of LongDesc 0 Spaces to indent 31 (if no DL counter is used) 36 (if a 2 digit DL counter is used)
I am trying to add an area to the "BBS new file dirs" menu, but ASETUP complains that the area is a duplicate area, even though I am certain that it is not. Running ASETUP Pack will solve the problem. This problem occurs periodically and is caused by changes in your BBS file area configuration. In order to make ALLFIX aware of those changes, you need to run ASETUP Pack.
How do I setup various virus scanners in ALLFIX? F-Prot : SCAN F-PROT.EXE @1\*.* /COMMAN /NOMEM /NOBOOT AVP
(lite) : SCAN AVPLITE @1\*.* /M /P /B
McAfee (OS2): SCAN OS2SCAN @1\*.* /ALL /SUB
ALLFIX only shows 4 lines of a file description in new file report or in a FileFind report. Check the announcement or FileFind template for the statement "setoflimit(x)", where x is a number. Increase the number x to the desired value.
Where can I find information about the structures of the ALLFIX configuration files, so that I can write my own utilities for ALLFIX? The structures are contained in the DEVELOP.ZIP archive which is included with each release of ALLFIX.
ALLFIX is not placing new files for new auto-added fileechos in the auto-add directory. Earlier versions did do that. As of ALLFIX 4.32, new fileechos are added to specific groups which can be defined in the group manager. ALLFIX will select a group that has the best matching "mask". A mask is nothing more than a specification such as WIN* or just the string *. A destination directory can be defined for each group. It is also possible to have ALLFIX automatically create unique directories within that directory for each new fileecho added to that group.
Sometimes when I enter ASETUP, the menu is flashing. The only way I have been able to solve that problem is by rebooting. One possible solution to this problem is to exit ASETUP and then type MODE CO80 on the command line.
How do I set up the request processor in ALLFIX for my mailer? Below is a list of the command line parameters that you need to use for the following mailers:
FrontDoor: Rp =A =O =X =T =R
InterMail: Rp %a %n %x %f
MainDoor: Rp =A =O =X =T =R
Xenia: Rp -SRIF
McMail: Rp -SRIF
When converting files from the .RAR format, RAR sometimes asks for a password and waits until the user has entered one. This affectively stops my system until I notice this and enter a fake password, to get RAR to continue. Is there a work-around for this problem? The way to solve this problem is to pass a bogus parameter to RAR. In the External program menu, add the following parameter to the decompression command line options for RAR: -pp The -p switch tells RAR that the password is, in this case, the letter p. RAR will ignore this switch when a password is not necessary. When one is necessary, it will use the given password (letter p) and most likely exit with an error, since the password is wrong. But this is not a problem, since ALLFIX can continue.
Is ALLFIX forwarding files but they are not turning up in your netmail folder attached to netmails (or in your Binkley style outbound directory)? The problem might be that you have the "Holding" directory option turned on for your downlinks. The Holding directory specifies a special directory where all outbound files for a particular system are stored. If you use the Holding directory, ALLFIX will NOT send the files via the mailer. In other words, ALLFIX will not make any netmail file attaches or update any .?LO files (for Binkley style mailers).
RAR files sometimes contain passwords. When ALLFIX tries to convert such a RAR file, RAR will wait for the user to enter the password. How can this be prevented? The -pp parameter can be used for RAR, which will instruct RAR to try the password "p" for a file. If the file contains a password, this password will most likely not be correct, which causes RAR to report an error and it will then exist. The end result is that ALLFIX will not convert the file.
I use QEMM and I have the problem that ALLFIX Universal does not run. Instead of starting up it either hangs my system or crashes in the active DESQview window. The problem may be related to the Stacks verb in your CONFIG.SYS file. The following settings have proven to help with this problem: stacks=9,256
ALLFIX often reports "You are using an illegal key", even though I am a registered user. Why? There are two error messages that ALLFIX can generate, one is that you are using an invalid key and one that says you are using an illegal key. ALLFIX will report that you are using an invalid key if the key does not match the sysop name in ASETUP. ALLFIX will report that you are using an illegal key if your key is not in the keyfile. The problem is, therefore, that the keyfile is either out of date, corrupt, or missing. The solution is to pickup a new keyfile from your registration site.
How should I setup the file descriptions for BBBS. The only thing that you need to do to use ALLFIX with BBBS is run FCOMP with the correct parameters and turn the "One line LongDesc" option on. Lastly, it is important that the "Use FDB" option is turned on for each fileecho.