home *** CD-ROM | disk | FTP | other *** search
- ** ArchiveLAB Frequently Asked Questions:
-
- ----------------------------------------------------------------------------
-
- To upgrade from any older version of ALAB, all you have to do is to
- replace all files with the new ones in the archive and look through the
- ALAB.CFG file for any changes.
-
- ----------------------------------------------------------------------------
- 1. I can't get HS/Link to work with FileDoor v2.xx :
-
- TC: I've discovered that some of you sysops have encountered problems
- with the FileDoor/HSLink combination. Namely, not being able to
- enter descriptions, and lost credits. The reason is because you
- have not installed the protocol properly in FILEDOOR.CFG. Here's
- how the protocol definition should look like:
-
- ┌───────────────────────────────────────────────────────────────────┐
- │ Protocol 98 H B 20 0 HS/Link (Bi-directional!) │
- │ DSZ C:\PROTOCOL\hslink.exe -p$1 -b$2 -hx -a -nt -u$8 $3 │
- │ │
- │ Protocol 98 H U 20 0 HS/Link (Fast!) │
- │ DSZ C:\PROTOCOL\hslink.exe -p$1 -b$2 -hx -a -nt -u$8 $3 │
- │ │
- │ Protocol 98 H D 20 0 HS/Link (Fast!) │
- │ DSZ C:\PROTOCOL\hslink.exe -p$1 -b$2 -hx -a -nt -nu -u$8 $3 │
- └───────────────────────────────────────────────────────────────────┘
-
- For your info, the $8 represents the upload path as calculated by
- FileDoor. So for all protocols (including HS/Link), you should use $8
- for the upload path instead of directly specifying it.
-
- Note that FileDoor v3.01 and up supports HS/Link as a BiDSZ protocol
- directly and you don't have to block the uploads anymore during
- downloads.
- ----------------------------------------------------------------------------
- 2. I get a messed up screen in DesqView when ALAB is processing the file.
-
- TC: DV users please take note, if you do not want a messed up screen, you
- will have to set the DV advanced settings such that 'Text Pages' is set
- to at least 2.
- ----------------------------------------------------------------------------
- 3. I have setup ALAB. Everything works ok, but FILE_ID.DIZ and file statistics
- are not imported into the FILES.BBS.
-
- TC: Make sure that you set the ALAB environment variable to point to the
- directory the ALAB files are in. Also, make sure that FDOOR.EXE is
- located together with FILEDOOR.EXE. Make sure to turn off
- 'InternalOverUser' in FILEDOOR.CFG as well.
- ----------------------------------------------------------------------------
- 4. What do I get by registering ALAB?
-
- TC: Technical support, a clear conscience, and registered features.
- The list of features enabled with registration are :
- 1. Conversion of archive format
- 2. Addition of GIF/JPG information (GIF testing is still
- available in non-reg versions)
- 3. Addition of Archive information and statistics
- 4. Posting of mails to users and sysops on failed upload(s)
- ----------------------------------------------------------------------------
- 5. I have found a bug in ALAB. How do I report it?
-
- TC: Check carefully to make sure it is not a configuration error. If
- so, please leave me all bug reports in the ArchiveLAB Support
- Conference, available at all support/beta sites, or send me a
- netmail. Your bug report must contain details of the hardware on
- your system, the extract of the log file (with the DEBUG option
- in ALAB.CFG turned on) where the error appears, the phase ALAB
- was in when you get the error, ALAB.CFG and a description of the
- situation and problem.
- ----------------------------------------------------------------------------
- 6. I wish to be a beta site for ALAB. How do I go about doing it?
-
- TC: I need beta sites with unique setups, and equipment. If you think your
- system is sufficiently different enough from the existing beta sites,
- please send me details of your system setup, and the reason for your
- interest via a netmail or in the ArchiveLAB Support conference.
- ----------------------------------------------------------------------------
- 7. I am a developer. I do not wish to have extra advertising blurbs
- inserted into my archives.
-
- TC: I have added protection for developers to prevent ALAB from
- altering archives. If you are a genuine developer, please
- contact me personally to get information on doing this.
- ----------------------------------------------------------------------------
- 8. What is the Hack Report that ALAB supports?
-
- TC: Quoted from the FILE_ID.DIZ of the Hack Report Archive -
-
- "A monthly list of potentially dangerous files including hacks,
- hoaxes, Trojan Horses, and pirated commercial files found posted
- for download on many BBS systems worldwide. SysOps and Users
- alike may benefit from this report by using it to avoid
- potentially dangerous files. By Lee Jackson, Co-Moderator,
- FidoNet International Echo SHAREWRE (1:382/95)."
-
- ALAB supports both the .COL and the .IDX files in the Hack Report
- archive, and will intelligently determine which one is being used
- when you specify a filename under 'UseHackReport'. If the .IDX
- file is being used, the reasons for rejecting will be shown. But
- the .COL file is updated monthly while the .IDX is not updated so
- regularly.
- ----------------------------------------------------------------------------
- 9. Does ALAB support RA 2.00?
-
- TC: Rename ALAB4RA2.EXE to ALAB.EXE, and follow the instructions
- given in the README.1ST and in the documentation.
- ----------------------------------------------------------------------------
-