home *** CD-ROM | disk | FTP | other *** search
Text File | 1993-02-12 | 115.9 KB | 3,004 lines |
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ▐▀▀▀▀▀▀▀▀▀▀▌ ▐▀▀▀▀▀▀▀▀▌ ▐▀▀▀▀▀▀▀▀▀▌ ▐▀▀▀▀▀▀▀▀▀▀▀▀▌
- ▐▄ ▄▄▄▄▄ ▌ ▐ ▄▄▄▄ ▌ ▐▄ ▄▄▄▄▄ ▌ ▐ ▄▄▄ ▄▄▄ ▌
- ▐ ▌ ▐ ▌ ▐ ▌ ▐ ▌ ▐ ▌ ▐▄▌ ▐ ▌ ▐ ▌ ▐ ▌
- ▐ ▀▀▀▀▀ ▌ ▐ ▀▀▀▀ ▌ ▐ ▀▀▀▌ ▐ ▌ ▐ ▌ ▐ ▌
- ▐ ▄▄ ▄▄▄▌ ▐ ▄▄▄▄ ▌ ▐ ▄▄▄▌ ▐ ▌ ▐ ▌ ▐ ▌
- ▐ ▌▐▄ ▀▌ ▐ ▌ ▐ ▌ ▐ ▌ ▐ ▌ ▐▄▄▌ ▐ ▌
- ▐▀ ▀▌▐▄ ▀▀▌ ▐▀ ▀▌▐▀ ▀▌ ▐▀ ▀▌ ▐▀ ▀▌ ▐▀ ▀▌
- ▐▄▄▄▄▌ ▐▄▄▄▌ ▐▄▄▄▄▌▐▄▄▄▄▌ ▐▄▄▄▄▌ ▐▄▄▄▄▌ ▐▄▄▄▄▌
-
- ──────────────────────────────────────────────────────────────────────
- RemoteAccess File Manager version 1.21 - Copyright by René van Hoorn
- ══════════════════════════════════════════════════════════════════════
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- ╒═════════════════════════════════════════════════════════════════════╕
- │░░░ Contents ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
- ╘═════════════════════════════════════════════════════════════════════╛
-
- Introduction and credits . . . . . . . . . . . . . . . . . . 1
-
- Legal aspects . . . . . . . . . . . . . . . . . . . . . . . 3
-
- General . . . . . . . . . . . . . . . . . . . . . . . . . . 4
-
- Installation . . . . . . . . . . . . . . . . . . . . . . . . 8
-
- Upgrading from 1.20 version to 1.21 . . . . . . . . . . . . 9
-
- Environment . . . . . . . . . . . . . . . . . . . . . . . . 9
-
- Rafm . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
- Commandline parameters . . . . . . . . . . . . . . . . . . . 11
- Tagging . . . . . . . . . . . . . . . . . . . . . . . . . . 12
- Multi-line systems . . . . . . . . . . . . . . . . . . . . . 12
- Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
-
- RafmEdit . . . . . . . . . . . . . . . . . . . . . . . . . . 25
- Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
- Files . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
- Protocols . . . . . . . . . . . . . . . . . . . . . . . . . 32
- Protocols (External) . . . . . . . . . . . . . . . . . 32
- Protocols (Internal) . . . . . . . . . . . . . . . . . 34
- Configuration . . . . . . . . . . . . . . . . . . . . . . . 35
- General . . . . . . . . . . . . . . . . . . . . . . . 35
- Colors . . . . . . . . . . . . . . . . . . . . . . . . 36
- Downloading . . . . . . . . . . . . . . . . . . . . . 36
- Uploading . . . . . . . . . . . . . . . . . . . . . . 38
- Maintenance . . . . . . . . . . . . . . . . . . . . . 40
- Archives . . . . . . . . . . . . . . . . . . . . . . . 41
- User Info . . . . . . . . . . . . . . . . . . . . . . 42
-
- RafmCln . . . . . . . . . . . . . . . . . . . . . . . . . . 42
-
- RafmCD . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
-
- RafmChk . . . . . . . . . . . . . . . . . . . . . . . . . . 46
-
- RafmAll . . . . . . . . . . . . . . . . . . . . . . . . . . 47
-
- RafmLCom . . . . . . . . . . . . . . . . . . . . . . . . . . 48
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: i
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- RafmCnvt . . . . . . . . . . . . . . . . . . . . . . . . . . 50
-
- Bugreports, address etc. . . . . . . . . . . . . . . . . . . 51
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: ii
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- ╒═════════════════════════════════════════════════════════════════════╕
- │░░░ Introduction and credits ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
- ╘═════════════════════════════════════════════════════════════════════╛
-
- Welcome to RAFM, the ultimate file-manager for RemoteAccess (tm)
- version 1.11 and up. First of all, I'd like to thank you for showing
- interest in this program, believe me, you won't be disappointed!
-
- Rafm is the product of well over two years of programming and testing.
- And over the course of these years it has developed into what can only
- be described as the best file-manager available for Remote Access.
-
- The author (René van Hoorn) debated for some time wether or not to
- release Rafm as shareware. Although shareware is without doubt the
- best way to spread programs to a widest possible audience (and the
- only way for you to try before you pay). It is an unfortunate fact of
- life that very few people that use shareware programs after the
- initial trial period will actually bother to register them.
- Finally, it was decided to release the first versions as shareware.
- Maybe the shareware philosophy still works? On the other hand, maybe
- not, it is up to YOU to keep the shareware ideal alive!
-
- RAFM has a couple of registered-only features which are marked in the
- documentation with a +. These features are not available to non-
- registered users but will be activated when a valid key is present.
-
- This document makes reference to the following third-party products,
- all copyrights, trademarks and reserved rights held in these products
- are acknowledged.
-
- Copyrights:
-
- RemoteAccess : copyright by Andrew Milner & Continental
- Software
- Bimodem: copyright by Eric Labs
- PkArc, PkZip: copyright by PKWARE Inc.
- Pak: copyright by NoGate Consulting
- Arj: copyright by Robert K Jung
- Lha, LhArc : copyright by Haruyasu Yoshizaki
- Hyper : copyright by P. Sawatzki and K.P. Nischke
- Squeeze it: copyright by Jonas I. Hammarberg
- Scan: copyright by McAfee Associates
- DSZ, GSZ : copyright by Omen Technology INC
- HsLink: copyright by Samuel H. Smith
- QFF, RFW,
- FileDoor: copyright by Robert W. van Hoeven
- RAFM Documentation: Eddy Matthews & René van Hoorn
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 1
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
-
- I would like to thank:
-
- Andrew Milner for writing RemoteAccess
- Maris for her mental support
- Pim van Kralingen for testing some very early alpha-versions
- Eddy Matthews for re-writing the document files
-
- and of course my beta-team! Thanx guys!
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 2
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- ╒═════════════════════════════════════════════════════════════════════╕
- │░░░ Legal aspects ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
- ╘═════════════════════════════════════════════════════════════════════╛
-
-
- By installing RAFM and its associated programs on your system, you
- indicate your agreement to the following terms and conditions. If you
- do not agree to these conditions, you should not install and use RAFM.
-
- Users of RAFM must accept this disclaimer of warranty:
-
- The author, René van Hoorn, disclaims all warranties, expressed or
- implied, including, without limitation, the warranties of
- merchantability and of fitness for any purpose.
-
- The author assumes no liability for damages, direct or consequential,
- which may result from the use of RAFM and its utilities.
-
- RAFM is copyrighted material by René van Hoorn, Hilversum, The
- Netherlands
-
- THIS PRODUCT IS SHAREWARE
-
- You may use it for 30 days without registering in order to assess the
- contents of this package. Continued use of this package after the
- initial period of 30 days requires you to pay a registration fee as
- defined in the various RAFM registration files to René van Hoorn or to
- one of his alloted registration sites.
-
- The registration fee will license one copy for use on any one computer
- at any one time.
-
- You are allowed to copy and distribute the unregistered version of
- this package, providing that you make no charges other than are
- necessary for copying, materials and handling. The files must not be
- separated or altered in any way whatsoever including reverse
- engineering.
-
- Registration entitles you to use RAFM for as long as you wish, removes
- the intro-message and activates the extra registered only {+}
- features.
-
- The author (René van Hoorn) is in no way obliged to give future
- support for any version of RAFM.
-
- If you don't agree with these rules, you may NOT use RAFM!
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 3
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- ╒═════════════════════════════════════════════════════════════════════╕
- │░░░ General ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
- ╘═════════════════════════════════════════════════════════════════════╛
-
-
- Ok, now for the good part: What is RAFM?
-
- Rafm is a complete file management system. It supports all of RA's
- internal functions and many more besides. Perhaps you thought Rafm was
- just another FileDoor?, it isn't!.
-
- For users of RA it's quite revolutionary, because it doesn't rely on
- RA's Files.Bbs anymore (although it still fully supports their use).
- Instead of those files, it uses ONE database and for high-speed access
- a small index-file. At this moment in time there isn't a faster
- program around. Also, the full-screen editor is unique and offers you
- a powerful set of tools for editing and maintaining the file-section
- of your BBS. You will no longer need to edit those long ASCII-files...
-
-
- Now for a brief and incomplete overview of the main features:
-
- - Global download from every area.
- - Internal ProtocolEngine with support for Xmodem, Xmodem/1K,Ymodem
- and Zmodem (incl. -G versions for reliable connects only).
- - Enhanced protocol interface. All protocols can be used, not only
- those creating a log-file.
- - Support for Bi-directional protocols (Send and Receive
- simultaneously).
- - Built-in Bimodem interface, no need for an external program.
- - Multi-language support using compiled .LNG files.
- - Use of multi-line file-descriptions.
- -{+} Users have the option to download a file containing the
- description of downloaded files.
- - Users have the ability to select a maximum of 20 files to
- download, even if the selected protocol doesn't support batch-
- tranfers.
- - Support for ZIP/ARC/PAK/ARJ/LZH and HYP archives, including self-
- extracting archives.
- - Users can view archives, extract files from archives and convert
- archives to another type.
- - 2 types of file-listing (RAFM and RA-alike).
- - Estimated time to download a file is shown in the listing.
- - Users can be forced to enter filenames and descriptions before
- the actual upload.
- -{+} (On-line) Virus-checking and re-archiving of uploads.
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 4
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- - Full-screen ANSI/Avatar cursor-tagging, no need to enter
- filenames anymore.
- - Built in Chatmode (or use an external program).
- - Fully user-definable colours.
- - Dupe-checking (all or selected areas).
- - Duplicate files can be moved to a special area or killed. (Same
- for bad archives).
- - Uploads can be restricted to one area.
- - Working (!) Kb and File-ratios, with an option to leave out the
- first x number of files and x Kb.
- - Functional private (sysop-only) files.
- - Support for Free Files (Won't affect the user's time- and
- download-limit).
- - Support for unwanted filenames.
- - Option to give upload-credit both in time and/or in increased
- download-kb-limit.
- - Full use of FILE_ID.DIZ and DESC.SDI files describing the
- uploaded file.
- - Rafm can delete unwanted files from archives (especially those
- stupid BBS-advertisements).
- - (Optional) Automatic log-off after transfer.
- - Auto-Adopt. (Scanning directories for files and adding them to
- the database).
- - File-maintenance. Optionally you can let Rafm move and/or kill
- static files that aren't downloaded within a certain (definable)
- period.
- - Fully multi-line aware.
- - CD-ROM support.
- - Avatar-support.
- - Internal ANSI and Avatar-driver for fast screen display.
- - and much much more...
-
- Perhaps the most important feature of Rafm:
- except for the offline virus-check and re-archiving of uploads, ALL
- options are contained in only ONE program! There is no need for
- constant switching between programs! (In fact, this was the main
- reason for writing Rafm.)
-
- What's in the archive?
-
- - 120to121.EXE: Upgrade utility for converting your datafiles from
- version 1.xx to 1.20.
- - RAFM.EXE: The main program. A fossil-driven door with carrier-
- detect and time-check (of course).
- - RAFMALL.EXE: The all/new-file list creator. With its own internal
- full-screen configuration. Can create upto 10
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 5
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- different all/new-file list combinations in only one
- run.
- - RAFMCD.EXE: A little program to convert your file-listings to a
- special format, designed to be used with CD-ROMs.
- - RAFMCD.DEF: Example of a coniguration file for RAFMCD.EXE
- - RAFMCLN.EXE: Maintenance-program for use in your nightly(?) batch-
- file. Used to keep the database up-to-date.
- - RAFMCHK.EXE: Virus-check and re-archiving program. Used to
- manipulate newly uploaded files.
- - RAFMCNVT.EXE: The conversion-program. Used to read the files.bbs
- into Rafm's database.
- - RAFMEDIT.EXE: The full-screen editor. Used to edit areas, files and
- protocols.
- - RAFMLCOM.EXE: Language compiler. Used to compile .LNG files
- - *.OVR: Several overlays, used by the different .EXE's.
- - README.1ST: Important note!
- - BETA.APP: Beta-application form. Use this form when you want to
- become a beta-tester for RAFM.
- - COMMON.Q-A: An overview of commonly asked questions about RAFM.
- - RAFM.DOC: That's what you're reading now.
- - ENGLISH.LNG: Default language file (English)
- - DUTCH.LNG: Dutch language definition.
- - GERMAN.LNG: German language definition file.
- - RAFMPROT.DDD: Description of the most often used protocols (rename
- this to RafmProt.Dat if you want to use it).
- - RAFMZIP.BAT: Batch-file used by RafmAll to archive the created
- All/New-files-listings.
- - REGISTER.DOC: Information about prizes and registration procedures.
- - REGISTER.*: Several registration-forms for each country where a
- support-node is located.
- - RAFMSUP.DOC: List of support-nodes which will help you setting up
- RAFM.
- - RAFMVAR.DOC: File desciribing RAFM's strucures.
- - EXAMPLE.ARJ: Set of menus and .A?? files.
- - WHATS.NEW: Short overview of all changes since 1.00
-
-
- After installation, the following files will be created:
-
- - RAFMAREA.DAT: Contains the area-information.
- - RAFMCONF.DAT: Configuration-file.
- - RAFMFILE.DAT: The file-database.
- - RAFMIDX.DAT: Index-file.
- - RAFMPROT.DAT: Contains all info about installed protocols.
- - ALLCONF.DAT: Created and used by RafmAll.
- - *.CLG: One or more compiled language file(s).
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 6
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- What other programs do you need apart from these files?
-
- - One or more archivers.
-
- Rafm uses following programs:
-
- - ZIP: PkZip.Exe (tested with version 1.10 and 2.04C)
- - ARC: PkArc/PkxArc (tested with version 3.5)
- - LZH: LhArc.Exe/Lha.Exe (tested with both versions 1.13 and
- 2.12)
- - PAK: Pak.Exe (tested with version 2.51)
- - ARJ: Arj.Exe (tested with version 2.30)
- - HYP: Hyper.Exe (tested with version 2.5)
- - SQZ: Sqz.Exe (tested with version 1.08.02)
-
- Note: Please use only the tested versions (or higher) of the
- archivers. Some functions (like adding comments to ARJ archives)
- will NOT work with earlier versions!
-
- - A virus-scanner, f.e. Scan from McAfee.
- - RemoteAccess (V1.1x or higher)
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 7
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- ╒═════════════════════════════════════════════════════════════════════╕
- │░░░ Installation ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
- ╘═════════════════════════════════════════════════════════════════════╛
-
-
- Installation is quite easy, just follow these steps:
-
- 1. Create a new sub-directory and copy the *.EXE and *.OVR files to
- this directory (Multi-liners: place a copy of RAFM.EXE in each of
- your line-directories).
-
- 2. Rafm uses an environment-variable called "RAFM" (without the ""
- of course) to find the data-files. If this variable is NOT set,
- Rafm will use the current directory.
-
- Edit your autoexec.bat and add following line to it:
-
- SET RAFM=<Full Path>
-
- Don't forget to reboot before you run Rafm for the first time and
- don't put any spaces in the SET command or else it won't work!
- (refer to your DOS-manual)
-
- 3. Copy all .A?? files to your textfile-path and all .MNU files to
- your menufile-directory.
-
- 4. Run RafmCnvt.Exe and answer the questions asked.
-
- 5. Run RafmEdit.Exe. The first time RafmEdit is run, it will create
- the configuration- and protocol-datafile. Walk through all menu-
- options and change whatever you want.
-
- 6. Run RafmLCom.Exe to compile the language files.
- You have to rename or create a language file first! The archive
- contains three different language files (*.LNG).
-
- 7. Create a type 7 menu-entry in RA (using RaConfig -m). The
- dataline should contain following:
-
- C:\RA\RAFM\RAFM.EXE *N *M
-
- *N is only necessary when running a multi-line system. (*M is
- RA's memory swap feature) It's advised to use the memory-swap,
- because Rafm has to call other programs (archivers, transfer-
- protocols etc).
-
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 8
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- Now you're ready to run Rafm local. Run RAFM with the -L parameter and
- enter your name . For easy operation it's advised to place the RAFM-
- directory in your PATH (refer to your DOS manual). In that case Rafm
- and all accompanying programs will always be able to find the *.DAT
- files.
-
-
- ╒═════════════════════════════════════════════════════════════════════╕
- │░░░ Upgrading from 1.20 version to 1.21 ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
- ╘═════════════════════════════════════════════════════════════════════╛
-
-
- This release (v1.21) uses different structures to earlier versions so
- you will need to convert your old datafiles to the new format.
-
- Please follow these 3 steps:
-
- 1. Copy 120to121.EXE to the directory where Rafm is located and run
- it from there.
- (Note: multiline users should run 120to121.EXE from each of their
- line-directories when using different datafiles for each line!)
-
- 2. Run RafmEdit and change the new fields as necessary.
-
- 3. Edit and re-compile your language files by using a standard
- ASCII-editor and RafmLCom!
-
-
- ╒═════════════════════════════════════════════════════════════════════╕
- │░░░ Environment ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
- ╘═════════════════════════════════════════════════════════════════════╛
-
-
- Rafm can use three different environment-variables:
-
- (If necessary refer to your DOS manual for more information on the use
- of environment-variables.)
-
- RAFM:
- Should point to the directory where the *.DAT files are
- located.
-
- i.e SET RAFM=C:\RA\RAFM
-
- If not present, Rafm will look for these files in the
- current directory.
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 9
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- RAFMTEMP:
- If present, Rafm will use the directory pointed to by this
- variable to store the memory-swapfile. If you have a RAM-
- disk, speed will increase when you let Rafm swap to this
- disk.
-
- i.e SET RAFMTEMP=E:\RAFM
-
- RAFMOVR:
- If present, Rafm will look for the OVR-file in the
- directory pointed to by this variable. If not present, Rafm
- will first look in the current directory and then search
- through the PATH. As with RAFMTEMP, speed will increase
- further when placing the OVR-file on a RAM-disk.
-
- i.e. SET RAFMOVR=E:\RAFM
-
- If using this variable, the OVR-file should be placed in
- the directory pointed to by RAFMOVR before executing Rafm.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 10
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- ╒═════════════════════════════════════════════════════════════════════╕
- │░░░ Rafm ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
- ╘═════════════════════════════════════════════════════════════════════╛
-
-
- RAFM is the main program of the package. Rafm takes care of whatever a
- remote user wants to do on-line. Rafm can read and understand the
- standard RA-menus, so you should only need to make minor changes to
- your menus when installing Rafm. Please refer to the Menus section of
- the this manual for a full description of all menu-types used by Rafm.
-
- There are a few hard-coded names for some screens used by Rafm. All
- .A?? files should be placed in the textfile-path, as defined in
- RaConfig. RAFM is fully compatible with RA's multi-language support,
- just place the .A?? file in the special textfile-directory for each
- language. RAFM will search the specified language-directory first, and
- only if a file isn't present in that directory, it will look in the
- default-textfile-directory (as defined in RaConfig).
-
- - ARCHHELP.A??: The Archive-helpfile is shown when a user presses H,
- when using the full-screen archive-viewer.
- - RAFMDOWN.A??: Download-menu. Should show all protocols available to
- the user.
- - RAFMUP.A??: Upload-menu. Should show all protocols available to
- the user.
- - RAFMAREA.A??: Displayed when a user presses the ?-key whenever
- he/she has to choose an area. This is only the case
- when NOT using templates!
-
- The Rafm-Archive contains examples of all these files.
-
- ╒═════════════════════════════════════════════════════════════════════╕
- │░░░ Commandline parameters ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
- ╘═════════════════════════════════════════════════════════════════════╛
-
-
- Normally, Rafm only uses one commandline-parameter. This parameter
- indicates on which line Rafm is running. Since Rafm assumes it's
- running on line 1, single-line systems don't have to use this.
-
- f.e. C:\RA\RAFM\RAFM.EXE *N
-
- (RA will replace *N with the current node number and pass it to Rafm)
-
- MULTI-LINE SYSTEMS MUST USE THIS PARAMETER !!
-
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 11
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- For offline testing purposes only, you can use the -L parameter. Do
- NOT use the -L parameter when executing Rafm from RA! (Note: during
- local operation, RAFM will ignore most of the system-parameters and
- show 0 instead of the actual value (f.e. number of calls etc.). Don't
- worry, when executing RAFM from RA, the correct values will be shown!)
-
- ╒═════════════════════════════════════════════════════════════════════╕
- │░░░ Tagging ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
- ╘═════════════════════════════════════════════════════════════════════╛
-
-
- One of the most practical and user-friendly features of RAFM is file-
- tagging. ANSI/Avatar users can select a file using the cursor-keys and
- pressing [Enter] when the highlight is over the chosen file. Doing
- this eliminates the need for entering filenames manually, users don't
- even have to know the actual filename!
-
- ASCII users can still tag files, but will be prompted to enter the
- filename before proceeding.
-
- Please note that Rafm will turn off the status-line whilst displaying
- a file listing otherwise your local screen would become a mess when a
- user selected the cursor-tagging option. You can force the status-line
- on by pressing [F10] if you wish. RAFM supports the ANSI-escape codes
- for Home, Cursor Up/Down and End. Unfortunately, ANSI doesn't have a
- code for the PgUp/PgDn keys, so if a user wants to use these keys,
- he/she will need to turn on Numlock or put the software into Doorway
- mode.
-
- You as Sysop can manually add, delete or change files in the taglist
- by pressing [Alt-T] when a user is on-line.
-
- ╒═════════════════════════════════════════════════════════════════════╕
- │░░░ Multi-line systems ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
- ╘═════════════════════════════════════════════════════════════════════╛
-
-
- Rafm is completely multi-line aware. All files that should be shared,
- are shared and record-locking is available. Note: Rafm will ONLY use
- record-locking if it's indicated in RaConfig that you really are
- running multi-line. For record-locking, Rafm uses share, so this
- should be loaded first (you probably already have share installed,
- because RA uses share too). Screen-writes are never direct, unless
- indicated by RaConfig. Because Rafm will always search the current
- directory for it's datafiles first, you can easily create different
- configuration- and protocol-files for each line.
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 12
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- IMPORTANT: The maintance program RafmCln does NOT use any record-
- locking. Make sure ALL lines are down when using this program,
- otherwise you run the risk of ruining your database!!!
-
- {+} Another nice feature of Rafm: everytime a new menu is being read,
- Rafm will check the filedates of the *.DAT files. If the filedate has
- changed Rafm will re-read these files automatically. This allows you
- to change your configuration using RafmEdit whilst users are on-line!
- No need to close-down the system!
-
- {+} RAFM will also listen to the semaphore file RAXITn.xxx. When this
- file is found, RAFM will immediately exit to RA.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 13
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- ╒═════════════════════════════════════════════════════════════════════╕
- │░░░ Menus ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
- ╘═════════════════════════════════════════════════════════════════════╛
-
-
- This is perhaps the most important part in configuring Rafm. The menus
- you create will give your files area it's own "feel", and will make
- your system look completely different from any others. The menu system
- gives you immense flexibilty, not only visually, but in allowing or
- disallowing access to certain functions or file areas to groups of
- users.
-
- The menus can be edited using RaConfig -m. Each menu line has a line
- of text that is displayed to the user, a menu "type", a minimum
- security level and various flags that can be set to any required value
- needed to access that line, and some optional data that is required by
- some menu types.
-
- There are approximately 30 menu functions available to Rafm that may
- be activated by a user pressing the key you have assigned to a
- particular function.
-
- Rafm reads and understands the standard RA-menus. However, not all
- types can be used and Rafm does NOT always use the same optional data
- as RemoteAccess!. An overview showing all menu-types and a short
- explanation follows.
-
-
- IMPORTANT NOTE!
-
- There is ONE hard-coded menu-name, and that's RAFMTOP.MNU. This is the
- first menu to be shown. If NOT present, Rafm will abort!
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 14
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- Type: 1
- Name: Goto another menu
- Optional Data: <Menu Name> /F=<File Area>|+|-
-
- Description: This function causes a jump to another menu <Menu
- Name> If you enter "QUITRAFM" (without the "") on the
- optional dataline, Rafm will end the session and
- return to RA, without disconnecting.
-
- Examples:
-
- FILES : Jump to the menu 'FILES'.
-
- FILES /F=20: Jump to the menu 'FILES' and set the
- selected file area template to file area '20'.
-
- FILES /F=+: Jump to the menu 'FILES' and set the
- selected file area template to the current file area
- plus 1.
-
-
- Type: 2
- Name: Gosub another menu
- Optional Data: <Menu Name> /F=<File Area>|+|-
-
- Description: As for menu type 1, but saves the path to the last
- menu on a "stack", making it possible to return to
- the calling menu with a type 3 menu.
-
-
- Type: 3
- Name: Return from gosub
- Optional Data: None
-
- Description: Returns from a Gosub (type 2) to the previous menu in
- the stack.
-
-
- Type: 4
- Name: Goto menu after clearing menu stack
- Optional Data: <Menu Name> /F=<File Area>|+|-
-
- Description: As for menu type 1, but before jumping to the new
- <Menu Name>, the gosub menu stack is cleared. Beware!
- you cannot use a type 3 return after this!
-
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 15
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- Type: 5
- Name: Display a *.A?? text file
- Optional Data: <1-8 character name>
-
- Description: This menu will display the named file from your
- textfile directory. Depending on the current users
- settings, either <filename>.ASC, <filename>.ANS or
- <filename>.AVT will be displayed. Should a user have
- AVATAR enabled, but <filename>.AVT is missing then
- <filename>.ANS would be displayed. Similarly if .ANS
- was missing then <filename>.ASC would be displayed.
- As with RA's type 5 menu function, it is possible to
- display comprehensive system or user details by
- inserting special control codes in the files. Please
- refer to Ra's Text File Control Codes in the RA docs
- for more information.
-
- Examples:
-
- STATS: If STATS was inserted in the optional data
- line, it would display the file 'STATS.AVT' if the
- user had AVATAR enabled, 'STATS.ANS' if the user had
- ANSI enabled or the file 'STATS.AVT' was missing and
- 'STATS.ASC' if the user only had ASCII enabled or
- both the AVT and ANS files were missing.
-
-
- Type: 7
- Name: Run an external program in a shell
- Optional Data: <Command Line> [Control Codes]
-
- Description: This command will run an external program in a shell
- whilst the user is online. The full name of the
- program and its path must be specified if it is an
- .EXE or a .COM file. If you wish to call a batch
- file, this must be done via COMMAND.COM (see RA docs
- for more info)
-
- Many external programs require certain parameters to
- be passed to them on the command line, so the
- following control codes may be used. In each case the
- code is replaced by its value:
-
- *A : Insert the users handle (if used) in
- DORINFO.DEF instead of the users real name.
-
- *B : Set baud rate to the users speed, or 0 if local
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 16
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
-
- *C : Full path and name to COMMAND.COM
-
- *D : Automatically generate the DOOR.SYS file needed
- by some external utilities.
-
- *F : Users first name.
-
- *G : Determine wether the user has ANSI graphics
- enabled. 0=Off/1=On.
-
- *L : Users last name.
-
- *M : Activate the memory-swap feature. Rafm will
- attempt to swap itself and all the memory it
- occupies to EMS (if installed) and disk,
- leaving only a small portion resident. Useful
- for memory hungry programs, but it can take a
- few seconds to do the swap.
-
- *N : Line number, as passed from RA
-
- *P : Communications port being used.
-
- *R : Users record number in RA's user file.
-
- *T : Time remaining for current call.
-
- *! : Freeze the system timer whilst in the shell.
- Useful for external chat programs etc.
-
- *# : Turn off the "Wants chat" indicator on return
- from the shell.
-
-
- Please note!!
-
- RemoteAccess also supports the following control
- codes which are NOT supported by Rafm. They are: *H,
- *O and *1
-
-
-
-
-
-
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 17
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- Type: 8
- Name: Product information
- Optional Data: None
-
- Description: Displays Rafm's product information to the remote
- user.
-
-
- Type: 9
- Name: Terminate the session
- Optional Data: None
-
- Description: This option will disconnect and doesn't let the user
- return to RA! If you want to do that, use a type 1!
- Please note: when running RA locally, this option
- will NOT log you off the system, it will ONLY drop
- you back into RA. Rest assured it WILL work correctly
- when a user is online!.
-
-
- Type: 11
- Name: Page sysop for a chat
- Optional Data: <Paging string>
-
- Description: This function will display the <paging string> to the
- user and page the sysop for a chat. You may break in
- for a chat at any time by pressing ALT-C, which will
- initiate a chat using Rafm's internal chat routine or
- an external chat program if configured in RaConfig.
-
- Type: 14
- Name: Time / Display statistics
- Optional Data: <None>
-
- Description: Will show some information about the user's limits,
- and how much has already been used.
-
-
- Type: 30
- Name: Directory
- Optional Data: <Full path> or /F
-
- Description: Displays a DOS style directory of the directory
- specified in the optional data field.
-
-
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 18
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- The use of the "/F" parameter will enable you to use
- the current file template area instead of the <Full
- path>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 19
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- Type: 31
- Name: List Files
- Optional Data: /F
-
- Description: Displays a list of files available for download. If
- the "/F" parameter is present in the optional data
- field Rafm will assume that you're using templates
- and will display the listing instantly. If not, Rafm
- will first ask the user which area should be
- displayed. Besides entering the area-number, there
- are 2 special keys:
-
- - ?: Displays an overview of all areas that the user
- can access. If present, RafmArea.A?? will be
- displayed.
-
- - +: Will list all files in ALL areas.
-
-
- Type: 32
- Name: Download a File
- Optional Data: None
-
- Description: First, RafmDown.A?? is displayed and the user has to
- select a protocol. Besides the hot-keys defined in
- RafmEdit, there is also an extra option: "-", which
- will abort the download.
- After choosing the protocol, the user can enter
- filenames and/or download any files that he/she has
- tagged.
- Wildcards (* and ?) are allowed. Rafm will refuse *.*
- however.
- Please note that RAFM will always allow a user to
- download files from any area (but only if they have
- access to it AND you have enabled this option!).
- There's no difference between a type 32 and a type
- 59!!
-
-
-
-
-
-
-
-
-
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 20
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- Type: 33
- Name: Upload a File
- Optional Data: </F=Area Number>
-
- Description: Similar to type 32. Uses RafmUp.A?? instead of
- RafmDown.A??.
- If you've activated "Restrict uploads" Rafm will
- place the file in the area you've defined in
- RafmEdit.
- When you enter a valid "/F=Area Number" on the
- optional data line, Rafm will place the file in that
- area.
- If you've done neither of these, Rafm will just place
- the file in the currently active area.
-
-
- Type: 34
- Name: View Archive
- Optional Data: None
-
- Description: Activates the full-screen archive viewer. Rafm can
- handle all popular types of archivers. Be sure to
- place the necessary archive-programs in your Path, or
- else Rafm won't be able to find them. There is a
- possibility to show a help-file, called ARCHHELP.A??.
-
-
- Type: 35
- Name: File scan by keyword.
- Optional Data: None
-
- Description: This function searches all file areas that a user has
- access to for a keyword that is supplied by the user.
- Any entries that match are displayed with the name of
- the area the match was found in. The user also has
- the option to tag any files that are displayed.
-
-
- Type: 36
- Name: File scan by Filename.
- Optional Data: None
-
- Description: Same as type 35 menu, except that the user enters a
- filename to be scanned for.
-
-
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 21
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- Type: 37
- Name: Show new files
- Optional Data: None
-
- Description: Same as RA, with an extra option to ask the number of
- days to scan back instead of a single date.
-
-
- Type: 39
- Name: Display a fully named text file
- Optional Data: <Full path and name>
-
- Description: Similar to the type 5 menu, but allows you to specify
- the full path and filename including extension of the
- file to be displayed. You can also use the control
- characters as explained in the type 5 menu function.
-
-
- Type: 40
- Name: Display an *.A?? text file with hot-keys
- Optional Data: <1-8 character name>
-
- Description: Same as RA. Similar to a type 5 menu function except
- that the current menu hot keys remain active whilst
- the file is displayed.
-
-
- Type: 45
- Name: Display a text file and wait
- Optional Data: <1-8 character name>
-
- Description: The same as a type 5 menu function, but prompts the
- user to press [Enter] before continuing.
-
-
- Type: 46
- Name: Display a direct text file with CR
- Optional Data: <Full path and name>
-
- Description: Displays the specified text file (the path must be
- included in the optional data field) and waits for
- the user to press [Enter] before continuing.
-
-
-
-
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 22
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- Type: 47 {+}
- Name: Make an entry in the systemlog
- Optional Data: <Log entry>
-
- Description: Writes the contents of the optional data field to the
- system log.
-
- There is one special character you may enter: an @,
- which is replaced by the currently active file area.
-
-
- Type: 48
- Name: Download a specific file
- Optional Data: <Full path and name> /F
-
- Description: Allows the user to download a file or files that you
- have pre-defined. The user can select which protocol
- to use.
- Adding the /F parameter instructs RAFM NOT to use
- it's database but directly scan the drive for the
- specfied file(s). Beware that doing this may increase
- speed but you'll lose all special options like free
- file etc.
-
- Examples:
-
- C:\FILES\RA\BBS\RAFM*.ARJ
-
- Would send all files in the C:\FILES\RA\BBS directory
- that matched RAFM*.ARJ.
-
-
- Type: 50
- Name: Select file area
- Optional Data: None
-
- Description: Shows a listing of all areas the user has access to
- and lets the user choose another area. If present,
- the file RafmArea.A?? will be displayed, otherwise
- Rafm will use its own internal listing.
-
-
-
-
-
-
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 23
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- Type: 55
- Name: Download any file
- Optional Data: None
-
- Description: An extremely powerful function that should ONLY be
- accessible by the sysop. It allows anyone that has
- access to it to download ANY file from ANY valid
- directory using any of the available protocols! This
- function takes no account of any download limits that
- may be in force.
-
- Type: 59
- Name: Global download
- Optional Data: None
-
- Description: Same as type 32.
-
-
- Type: 65 {+}
- Name: Change User's flags
- Optional Data: <Flagset><FlagNum><Action>
-
- Description: Allows you to set or toggle any of the users security
- flags. The <Action> determines how the flag is to be
- set:
-
- - : Turn flag OFF
- + : Turn flag ON
- * : Toggle flag
-
- For example, if the optional data field contained
- "A2+ B2- C2*" then flag A2 would be turned on, B2
- would be turned off and flag C2 would be toggled.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 24
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- ╒═════════════════════════════════════════════════════════════════════╕
- │░░░ RafmEdit ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
- ╘═════════════════════════════════════════════════════════════════════╛
-
-
- RafmEdit is the full-screen editor of Rafm. With RafmEdit you can edit
- areas, files, protocols and configuration. Like all Rafm-programs,
- RafmEdit will first search the current directory for *.DAT files. Only
- if one or more *.DAT files can't be found in the current directory,
- will RafmEdit look in the directory pointed to by the RAFM environment
- variable.
-
- Use the cursor-keys and [Enter] to walk through the menu-choices.
- [Esc] will abort input when pressed the first time. Pressing [Esc]
- again will close an edit-window. [F10] will immediately save changes
- and close an edit-window. When exiting RafmEdit will ask if you want
- to save the changes, answering this question with 'N'(o) will discard
- any changes you've made in that session. Please note that changes to
- files will always become permanent instantly.
-
- ╒═════════════════════════════════════════════════════════════════════╕
- │░░░ Areas ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
- ╘═════════════════════════════════════════════════════════════════════╛
-
-
- Areas: Choose an area or an empty slot (indicated with <Not Used>)
- with the cursor-keys. Alternatively you can also directly
- type an area-number to select. When you've reached the
- desired area, press [Enter] and a new window will open. You
- can now edit the chosen area. Since most fields are the
- same as RA, I will only explain the additional fields:
-
- - Password:
- Areas can be protected with a password. Files in
- these areas can still be seen by users, but if they
- want to download from these areas, they have to enter
- the correct password.
- - Header:
- When a user decides to List a particular file area,
- the filename entered here will be displayed first.
- Only the filename (without extension) should be
- entered as Rafm will automatically display either AVT
- ANS or ASC depending on the users settings. The file
- to be displayed should be in your textfile directory,
- and could concievably contain extra info about the
- particular file area, or a banner to brighten up your
- file listings and make them unique.
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 25
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- - Free Area:
- Indicates if a user can download from this area
- without affecting his/her limits. Please note that
- ALL files in the area will be free files (there is
- also an similar option in the files-section that will
- allow INDIVIDUAL files to be marked as free).
- - Protected:
- Areas can be protected against the maintenance
- function of RafmCln. If an area is protected, files
- in this area will never be moved or killed because of
- inactivity.
- - Proc. Arch.:
- If set to NO, files in this area will never be re-
- archived by RafmChk. This can be useful for areas
- where you place your Fidonet-related files for
- example.
- - No Update:
- Indicates whether or not RafmCln has to update the
- sizes and dates of the files located in this area.
- Especially useful when using a CD-ROM or for an
- offline file area.
- - Kill Deleted:
- If set to Yes, deleted files (in this case, a deleted
- file means a file which has been physically erased
- from disk) will be removed from the database when
- running RafmCln -D. If set to No, deleted files will
- never be removed from the database (which allows you
- to create an offline file-area with files you don't
- always want to have on your HD).
- - Skip Dupe:
- If set to Yes, the duplicate-detect routines will not
- scan this area.
- - CDRom:
- If set to Yes, this option indicates the files in
- this area are located on CD-ROM. Rafm will treat this
- area differently from 'normal' areas:
- - Files will be copied to your harddisk just
- before downloading to increase transfer-speed.
- - Rafm will NOT scan this area for new files, NOT
- try to re-archive the files in this area and
- also will NOT perform any kind of updating
- during nightly maintenance.
-
-
-
-
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 26
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- ╒═════════════════════════════════════════════════════════════════════╕
- │░░░ Files ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
- ╘═════════════════════════════════════════════════════════════════════╛
-
-
- Files: Activating this option will open 2 different windows. On
- the left side all files are displayed, on the right side an
- overview of all possible command-keys is shown.
- All commands are activated via an Alt-Key combination.
- Typing without the Alt-key pressed will activate the
- Search-function (look at the 'Search- String'). You can
- clear the search-string by using backspace or [Ctrl-Home].
- The spacebar will tag a file (or if a file has already been
- tagged, remove the tag). Except for the Edit and Add
- function, every function will work with all tagged files at
- once. So, if you've tagged 10 files and press [Alt-M], all
- 10 files will be moved!
-
- - Search on keyword [Alt-K]:
- Allows you to search through the database on
- keywords. Works exactly the same as the menu type 35.
- - Search on wildcard [Alt-F]:
- Allows you to search through the database on
- wildcards. Works exactly the same as the menu type
- 36.
- - Select files in 1 area [Alt-A]:
- Allows you to tag all files in a specific area and
- perform an action on all the tagged files at once,
- Alt-D to delete, or Alt-M to move etc.
- - Delete tagged file(s) [Alt-D] or [Del]:
- Will erase the tagged file(s) from disk and mark the
- record(s) in the database as deleted. Deleted records
- can only be removed from the database by using
- RafmCln -K (and only when you've enabled kill deleted
- files in that area)
- - Move tagged file(s) [Alt-M]:
- Will move tagged file(s) to a different area. You
- will be prompted to enter the area number to move the
- tagged files to, either enter it directly at the
- prompt or press [F2] for a list of available file
- areas. Only the area-number in the database is
- changed, but you can optionally let RafmEdit copy the
- file physically to another directory and reset the
- file date.
- - Edit [Alt-E] or [Enter]:
- Opens another window in which you can edit the
- selected file. Note that Rafm will store the full
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 27
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- directory with each file, so it is possible for a
- file to have a different directory than the area in
- which it is located. This will save you much copying
- and moving, but can cause problems when using
- Bimodem, because when a user has entered Bimodem and
- has access to the directory, there is no way Rafm can
- prevent a user from downloading a file.
-
- The edit-window shows several fields which you can
- change:
-
- - FileName:
- The complete name of the file, including
- extension.
- - Directory:
- The full path to the file. You can prevent
- possible problems if you always include the
- drive-letter. Pressing [F2] will give you an
- overview of all available directories.
- - Area #:
- Determines in which area the file is located.
- As said before, the directory of the file
- doesn't have to be the same as the directory of
- the corresponding area. Again, pressing [F2]
- will give you an overview of all areas.
- - Downloads:
- The number of times the file has been
- downloaded.
- - Size:
- The size of this file in bytes. This is
- automatically detected by RAFM, you can't edit
- it manually. If the filesize has been altered
- then running RafmCln -U will update the
- filesize where necessary.
- - FileDate:
- The date the file was uploaded. This can be
- automatically updated if it is changed by
- running RafmCln -U. If you change the date
- RafmEdit will also update the file itself.
- - Uploader:
- The name of the person who uploaded the file.
- This is automatically determined by Rafm when
- the file is uploaded. Or if it is a local
- upload (a file you've added locally) then the
- upload name will default to that of the sysop.
-
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 28
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- - Password:
- When a file is protected by a password, a user
- has to enter this password first before he/she
- can download the file. Password protected files
- can always be seen in a listing.
- - Last access:
- The most recent date the file was downloaded.
- This date is used by the maintenance function
- to determine whether a file is active or
- inactive.
- - Description:
- The description of the file. You can enter upto
- 210 characters. The description is entered on
- one line, but will automatically word wrap when
- displayed to the user online.
- Note: a "|" will be translated into a CR/LF
- combination in a file-listing. If the entry is
- a comment (see further) this field holds the
- text to be displayed.
- - Free:
- Can this file be downloaded for free? (i.e. It
- will not affect any of the user's limits)
- - Private:
- When a file is private, the file can only be
- seen or downloaded by users that have a
- security level which is equal to or higher than
- set in the corresponding area. Private files
- will also never appear in an All/Newfiles-
- listing.
- - Checked:
- if set to Yes, it means that the file has
- already been scanned and/or rearchived (on-line
- or offline doesn't matter).
- - Deleted:
- Determines if the file has been deleted from
- the database. This doesn't mean the file
- doesn't exist anymore, only that Rafm will
- ignore the file and it will not be displayed in
- the all/newfile listings.
- - Protected:
- If set, the file will never be moved or killed
- by the maintenance function. Use this if you
- don't want to protect the whole area, but only
- a few files in that particular area.
- - Comment:
- Indicates whether or not this entry should be
- treated as a comment. Normally, the text
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 29
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- entered in the description-field is used as a
- comment. You can also use a .A?? file as a
- comment by entering a @ followed by a 8
- character filename. Since it is not (yet)
- possible to insert an entry in the database,
- you will have to choose the filename carefully.
-
- - Add a file [Alt-A] or [Ins]:
- Will create a new (blank) record in the database and
- then activate the Edit-function to let you add a new
- file to the database.
- - Clear all tags [Alt-C]:
- Will clear all previously tagged entries.
- - Global Edit [Alt-G]:
- With this option you can change several files at
- once:
-
- - Directory:
- Change the directory of all tagged files. Files
- are NOT copied to this directory, only the
- entry in the database will be changed.
- - Last access date:
- Change the date on which the files were last
- downloaded on all tagged files.
- - Uploader:
- Change the name of the person who uploaded the
- file. Useful if a user sends a batch of files
- on disk for example.
- - Description:
- Change the description of all tagged files.
- - Statusbits:
- Change the statusbitsof all tagged files. There
- are 5 different statusbits:
- - Free:
- Determines if the file can be downloaded
- for free.
- - Private:
- Determines if the file is private (sysop-
- only)
- - Checked:
- Whether or not the file has already been
- scanned and/or rearchived
- - Deleted:
- Has the file been deleted from the
- database?
-
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 30
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- - Protected:
- If set, the file will not be touched by
- the maintenance function of RafmCln.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 31
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- ╒═════════════════════════════════════════════════════════════════════╕
- │░░░ Protocols ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
- ╘═════════════════════════════════════════════════════════════════════╛
-
-
- Protocols (External):
-
- Rafm can handle 5 types of external protocol:
- - Logfile:
- Protocols that create a logfile (f.e. DSZ)
- - Errorlevel:
- Some protocols don't create a logfile, but exit with an
- errorlevel. Rafm assumes that an errorlevel of 0 means Ok. Any
- other errorlevel should indicate the transfer has failed.
- - Bimodem:
- Rafm has a complete built in Bimodem interface, taking advantage
- of the many features of Bimodem. There is no need for any
- external interface.
- Note: although Rafm will take care of the security (download-
- limit, time-limit, directories etc.) you still have to configure
- Bimodem to suit your own needs!
- - Bi-directional:
- Besides Bimodem, there is at least one protocol than can send and
- receive files simultaneously. You can't use the oridinary Logfile
- type, because RAFM won't scan the logfile for both up and
- downloads. Bi- directional types are expected to create a
- logfile, if not, you can't use them in RAFM. The main difference
- between logfile- and Bi-directional-types is the download
- keyword. Normally RAFM will treat this keyword as case-
- insensitive, but this is NOT the case with Bi-directional types!
- - Other:
- If you can't get the protocol to work with any of the first 4
- types, you probably shouldn't use it, but if you still want to,
- you could try this one. This type will cause Rafm to measure the
- time the transfer took, and compare it to the calculated time
- (size/speed/efficiency*100). If the actual time and the
- calculated time match, then Rafm will assume the transfer was
- succesfull. The success of this type depends very much on the
- accuracy of the efficiency rating.
- If you don't know exactly, set it high (about 95%). That should
- do it.
-
- The archive contains a sample RafmProt.Dat (RafmProt.DDD) with a
- number of often used protocols. The only thing you have to do is
- change the directories. If you want to install other protocols, please
- read the section below first!
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 32
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- - Description: (All types)
- The name and description of the protocol. The first word will be
- placed in the logfile. An underscore ("_") will be translated to
- a blank space when displayed, but you can use this to force Rafm
- to take more than 1 word into the logfile (f.e.: True_Ymodem will
- show "True Ymodem" in the logfile, if you don't use the
- underscore, only the word "True" will be written to the logfile).
- - Enabled/Disabled: (All types)
- Determines whether or not users can use the protocol.
- - Kind: (All types)
- Logfile, Errorlevel, Bimodem, Other or Bidirectional.
- - Hot-Key: (All types)
- The character used in the menu's to select the protocol.
- Obviously ALL protocols must use a different Hot-key.
- - Download command: (All types)
- The complete command and control codes (look at the end of this
- section for an overview of these control codes) to execute the
- protocol in download (send) mode.
- - Upload command: (All types)
- Similar to the Download command, only for upload (receive) mode.
- - Efficiency: (All types)
- The efficiency of the protocol (in %). This is important because
- Rafm will calculate the transfer-time according to this
- efficiency. It is even more important when using the type
- "Other".
- - Max. files: (Logfile/Bimodem/Bi-directional)
- Rafm can transfer a maximum of 20 files in one session. For
- errorlevel and other types, the maximum number is always one,
- even if the protocol itself can transfer more than one file a
- time. When using opus-typeprotocols ( protocols that DON'T use
- control-files to specify the filenames) limit the maximum number
- of files to 4. This is because of the limited size of the
- commandline that DOS can handle.
- - Logfile: (Logfile/Bimodem/Bi-directional)
- The full path to the logfile created by the protocol. With
- Bimodem you should specify the complete path to your Bimodem.Cfg
- and NOT the logfile created by Bimodem!!!
- - Download Keyword: (Logfile/Bi-directional)
- When the external protocol has finished and control is returned
- to Rafm, the log file that was created will be scanned to extract
- information about what files were sent or recieved. Rafm scans
- the logfile for the UPLOAD or DOWNLOAD LOG KEYWORD. When it finds
- that word, it will scan forward x number of words to get the name
- of the file transferred.
- See the RA docs for more information.
- - Upload KeyWord: (Logfile/Bi-directional)
- See Download keyword for explanation.
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 33
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- - Download count: (Logfile/Bi-directional)
- Same as RA.
- - Description count: (Logfile/Bi-directional)
- Same as RA.
-
- Up/Download control codes:
-
- *P: Comport used
- *B: Current baudrate
- *M: Activate memory-swap option
- *AF: Create a control-file with filenames which have to be
- transferred.
- *CF: Is replaced by filename(s) on the command-line.
-
- All control codes are case-insensitive, but you CANNOT mix both kinds!
- So, "cf" and "CF" is allowed, but "Cf" isn't!
-
-
- ╒═════════════════════════════════════════════════════════════════════╕
- │░░░ Protocols (Internal) ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
- ╘═════════════════════════════════════════════════════════════════════╛
-
- The internal protocols are exactly the same as in RA. The hotkeys
- which activate the protocols are the same and you can turn the use of
- these internal protocols on/off via RaConfig. Please note that the
- hotkeys you've entered in RafmEdit overrule the ones for the internal
- protocols. This way, you can still use RA's protocols for f.e. message
- uploading and install a different one in Rafm.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 34
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- ╒═════════════════════════════════════════════════════════════════════╕
- │░░░ Configuration ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
- ╘═════════════════════════════════════════════════════════════════════╛
-
-
- The configuration is divided into 6 different sections. Each section
- is discussed seperately.
-
- ╒═════════════════════════════════════════════════════════════════════╕
- │░░░ General ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
- ╘═════════════════════════════════════════════════════════════════════╛
-
-
- - Default extension:
- Used when a user doesn't enter an extension. Normally this
- would be the same as the "convert archive to"
- - Logfile:
- The name of the logfile Rafm should use. Since the logfile
- isn't shared, multi-line systems may NOT enter a directory,
- only a filename!
- - Allow automatic log-off:
- When enabled, users can choose to log-off automatically
- immediately after a file-transfer (up- or download).
- - DateFormat:
- There are 4 different formats to show dates.
-
- DD/MM/YY (Day, Month, Year)
- MM/DD/YY (Month, Day, Year)
- YY/DD/MM (Year, Day, Month)
- YY/MM/DD (Year, Month, Day)
-
- You can choose between them using the [Enter] and
- [BackSpace] keys.
- - Swapping:
- This only refers to swapping when executing archivers. If
- enabled, Rafm/RafmChk will swap to EMS or Disk to leave
- enough memory free for the archiver to operate.
- - Use EMS:
- Rafm (and the other programs) will always use EMS (if
- available) to store the .OVR files and for the memory-swap.
- If you don't want Rafm to use EMS (f.e. because you need it
- for other programs) you can disable this option. This will
- however slow down Rafm.
- - Auto-Adopt text:
- The default file-description to be used when auto-adopting
- (only if no description is available in the files.bbs).
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 35
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- - Stamp adopted:
- Normally when RAFMCln adopts a file, the filedate will not
- be changed. Some sysops however prefer these adopted files
- to be displayed as new files. If you're one of them, you
- should enable this option and the adopted files will be
- automatically stamped with the current date.
- - List-method:
- There are 2 different kinds of listings. A new kind (Rafm)
- and one similar to RA. You're free to choose the one you
- like best.
- - New files scan:
- When you set this to "Ask for date", a user has to enter a
- complete date. "Ask # of days" will only ask the user how
- many days to scan back up to a maximum of 365 days.
-
- ╒═════════════════════════════════════════════════════════════════════╕
- │░░░ Colors ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
- ╘═════════════════════════════════════════════════════════════════════╛
-
-
- Almost every color in Rafm can be changed if you want. Use the
- cursorkeys to move through the different fields, and [Enter] and
- [BackSpace] to change the colors as desired.
-
- ╒═════════════════════════════════════════════════════════════════════╕
- │░░░ Downloading ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
- ╘═════════════════════════════════════════════════════════════════════╛
-
-
- - Allow global downloads:
- If enabled, Rafm will scan all areas for matching files. If
- disabled, users can only download from the currently
- selected area.
- - No Downloadhours:
- If enabled, users can only download between the hours set
- in "Starting hour" and "Ending hour". Useful for boards who
- do not want users to download at peak times.
- - Search in archives:
- Determines whether or not users can search inside archives
- when using the Keyword or Filename scan. If set to Yes,
- Rafm will ask the user if he wants to search inside the
- archives to see if a particular file is contained in
- another archive. If set to No, the question will never be
- asked, thus making it impossible to search inside the
- archives.
-
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 36
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- - Show files in archives:
- Should Rafm ask if a user wants to see files inside the
- archives during a file-listing?
- - Show long comments:
- Determines if Rafm will show full comments/descriptions, or
- only partial (depending on the type of listing, 1 or 2
- lines).
- - Show downloadcounters:
- Should Rafm display the downloadcounters? (Only in
- available in an Rafm type listing).
- - Show filedates:
- Should Rafm display the dates of the files? (Rafm listing
- only)
- - Show Kb:
- Should Rafm display the filesizes in Kb instead of bytes?
- (Rafm listing only)
- - Show only new:
- Determines if a user will be allowed to list only new files
- in an area.
- - Text when missing:
- This text is displayed when a user wants to download a file
- which is missing from the disk, for files that are stored
- offline for example.
- - Free Files (Kb):
- If set to a level higher than 0, a user may download this
- many Kb, before being confronted by his ratio. f.e.: is you
- set it to 500 and the Kb-ratio is 1:10, a user may download
- 500Kb and after this, has to upload 50Kb to restore his/her
- limits.
- - Free Files (#):
- Similar to the previous option, but now for the number of
- downloaded files.
- - Send infofile {+}:
- If set to Ask, RAFM will ask the user if he/she wants to
- download a file containing descriptions of the files to be
- downloaded. This infofile is created automatically by Rafm
- from the description entered in RafmEdit.
- - Info header:
- Should point to an ASCII file (f.e. your archive-comment).
- RAFM will append the file-description to this file when a
- user chooses to download the infofile.
-
-
-
-
-
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 37
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- ╒═════════════════════════════════════════════════════════════════════╕
- │░░░ Uploading ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
- ╘═════════════════════════════════════════════════════════════════════╛
-
-
- - Private Uploads:
- Whether or not you want to accept private uploads
- (i.e.,sysop-only).
- - Check duplicates:
- Should Rafm scan the database after every upload for
- possible duplicate files?
- - Action duplicates:
- Determines what you want to do with duplicate uploaded
- files. Files can be killed, moved to a special area or you
- can decide to leave the file untouched.
- - Move duplicates to:
- If you want Rafm to move duplicate files, you must enter
- the areanumber that Rafm will move the files to.
- - Check on viri:
- Should RafmChk check new uploaded files for viri? This is
- done when RafmChk is run (in your daily event?). To scan a
- file whilst the user is still online, see -Online check
- later in this section.
- - Restrict uploads:
- If Yes, all uploads will be placed in one area (see -Upload
- area), if No, uploads are placed in the current area at
- that moment.
- - Upload area:
- When restrict uploads is set to Yes, all uploads will be
- placed in this area (can be overruled by putting /F=xx on
- the optional dataline in a type 33 menu).
- - Credit Kb factor:
- If set to non-0, the user's daily download limit will be
- raised by Kb*factor%.
- f.e.: if you set it to 200%, and a user uploads 100Kb, his
- daily limit will be credited with 200Kb.
- - Credit time factor:
- Similar to Credit Kb factor, but now regarding the users
- daily time-limit. When using a batch-protocol, the time
- needed to upload the file is calculated based on the real
- efficiency.
- Note: Rafm will freeze the system timer whilst a user is
- uploading a file.
-
-
-
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 38
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- - Minimum diskspace:
- The minimum free diskspace to allow uploads. If your free
- diskspace is equal to or less than this figure Rafm will
- not allow a user to upload.
- Note: Rafm can't prevent users uploading files via Bimodem.
- - Update Files.Bbs:
- Whether of not Rafm should add new uploaded files to the
- existing Files.Bbs (added for compatibility reasons).
- - Scan path:
- Complete path to the virus-scanner, including the necessary
- parameters. Since RAFM has to know where on the commandline
- the directory to scan has to be placed, you have to put in
- a %1 parameter, f.e.:
-
- C:\UTIL\SCAN.EXE %1 /Nomem /SUB
-
- The %1 is replaced by the directory to be scanned.
- Don't forget to let your virusscanner process sub-
- directories too since RAFM will create them when the
- archive contains directories!
- - Action on infected files:
- Similair to duplicate files you can let RAFM move/kill
- infected files.
- - Area to move infected files to:
- When action on infected files has been set to move, you
- must specify which area RAFM should move these files to.
- - Online Check {+}:
- If set to Yes, uploaded files are scanned for viri
- immediately after the upload is complete.
- - Online re-arch. {+}:
- If set to Yes, uploaded files will be re-archived to the
- default archive-type immediately after the upload is
- complete. Please note that online rearchiving will cost
- your users money! I personally dislike this option, it's
- only there because many sysops asked for it.
- - Ask desc. first:
- If set to Yes, RAFM will ask for a description of the file
- before the actual upload takes place. Useful for the idiots
- that upload a file and don't bother to enter a description!
- - Add Gif specs:
- If set to yes, RAFM will add GIF specifications (Width,
- Height and colors) to the description of uploaded .GIF
- files.
-
-
-
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 39
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- - Gif specification:
- Determines the way RAFM will add GIF specifications to the
- description.
- Characters you can use:
- B or A: Put specification Before or After description.
- W : Width (in pixels) of the picture
- H : Height (in pixels) of the picture
- C : number of colors.
- f.e.:
-
- B(W * H * C) will be translated into:
-
- (640 * 480 * 256) and put before the description.
-
-
- ╒═════════════════════════════════════════════════════════════════════╕
- │░░░ Maintenance ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
- ╘═════════════════════════════════════════════════════════════════════╛
-
-
- - Move inactive files:
- Should RafmCln move inactive files after a certain period?
- Asset in -Days before move.
- - Days before move:
- If move inactive files is set to Yes, inactive files are
- moved if they are not downloaded within this number of
- days.
- - Area # to move to:
- Determines the areanumber to which inactive files area
- moved.
- - Kill inactive files:
- Should RafmCln erase inactive files? If set to Yes, RafmCln
- will erase from the disk any files that are set as being
- inactive.
- - Days before kill:
- If kill inactive files is set to Yes, inactive files will
- be erased if not downloaded within this number of days.
-
- Note: if a moved file has been downloaded from the inactive
- area, RafmCln will automatically move the file back to its
- original area.
-
-
-
-
-
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 40
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- ╒═════════════════════════════════════════════════════════════════════╕
- │░░░ Archives ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
- ╘═════════════════════════════════════════════════════════════════════╛
-
-
- - Convert archives to:
- Determines which type of archive new uploaded files should
- be converted to. Rafm currently supports the following
- types: ARC/PAK/ZIP/LZH (new and old)/ARJ and HYP.
- - Re-archive SFX:
- Nowadays more and more programs are spread in self-
- extracting archives with security-envelopes. When processed
- by RafmChk, these envelopes will be lost. If you want to
- keep these kind of archives, you should disable this
- option.
- Note: Rafm will still be able to perform all actions with
- these files, although searching through SFX-archives takes
- considerably more time than normal archives.
- - Convert directory:
- This should be an empty directory. It's used by Rafm and
- RafmChk to convert or extract files from archives.
- IMPORTANT: ALL FILES IN THIS DIRECTORY WILL BE DELETED WHEN
- A USER EXTRACTS OR RE-ARCHIVES FILES AND WHEN RAFMCHK IS
- RUN!
- Multi-line systems will need to use a different directory
- for each line!
- - Comment path:
- Complete path to a standard ASCII file which can contain
- your BBS-advertisement. This file will be used to comment
- the archives created by RafmChk (only if the archive-type
- can handle comments of course).
- - Archive area:
- Determines in which area the converted archives are placed,
- when a user uses the View Archive menu-type.
- - Stamp archives:
- Normally, uploaded files are stamped with the current time
- and date immediately after the upload. If you turn this
- option on, files are also stamped after converting with
- RafmChk.
- - Action bad archives:
- Similar to duplicate files you can let RafmChk move/kill
- bad archives. Useful for aborted uploads.
- - Move bad archives to:
- The area in which bad archives should be placed.
-
-
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 41
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- - Use FILE_ID.DIZ:
- Many archives nowadays contain a little textfile describing
- the archive, RAFM can read this textfile and replace the
- file's description with the contents of the textfile.
- Note: RAFM also recognizes a different standard: DESC.SDI.
- - Strip Hi-ASCII:
- Unfortunately, many FILE_ID.DIZ files contain Hi-ASCII
- characters (boxes etc.). You can let RAFM remove these
- characters by setting this option to Yes.
-
-
- ╒═════════════════════════════════════════════════════════════════════╕
- │░░░ User Info ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
- ╘═════════════════════════════════════════════════════════════════════╛
-
- RAFM now even more supports the USERDOES.xxx file. The standard
- USERON.BBS file used and created by RA can only display very
- limited information about what the user is doing. USERDOES.xxx is
- much more flexible.
-
- (P.S. RA doesn't support this file, you'll need a program like
- Gerard Hoogterp's USERON program)
-
- The usage of this USERDOES file is enabled by setting Use Info to
- Yes. You can also change the info RAFM writes to this file by
- editing the various messages.
-
-
- ╒═════════════════════════════════════════════════════════════════════╕
- │░░░ RafmCln ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
- ╘═════════════════════════════════════════════════════════════════════╛
-
-
- RafmCln is the maintenance part of the package. It will clean up the
- database and perform various extra functions (such as maintenance,
- creating new Files.Bbs and Auto-Adopting files). You should run it
- daily, normally in your maintenance event.
- Multi-liners: please make sure that every line is down before you
- start RafmCln!!! Failure to do so can result in a corrupted database!!
-
- There are several parameters:
-
- -B: Backup datafiles. Will create backup copies of the data-
- and indexfile. The copies will be placed in the
- Rafmdirectory with an extension of .BAK.
-
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 42
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- -A: Activate the Auto-Adopt function. This function will scan
- all directories in RafmArea.Dat and if a file is found that
- isn't in the database, it will add the file to it, if the
- file passes the duplicate-check (same as in Rafm). If
- RafmCln can find a Files.Bbs (the Listpath is supported)
- then it will look there for a description. If not the
- default description as defined in RafmEdit will be used.
- -AF: Similar to the -A function, but only scans Files.Bbs for
- new files. If you f.e. are connected to a file-echo (SDS
- f.e.) the current utilities won't support Rafm, they will
- however create a Files.Bbs. -AF will scan the Files.Bbs and
- especially when used together with the -E parameter will
- significantly speed things up. The -AF function also uses a
- different duplicate routine. This routine doesn't check the
- extension, so you can now add your nodediffs f.e.
- automatically.
- RAFMCln automatically detects whether your Files.BBS hold
- sizes and dates of the files. When they do, RAFMCln will
- not scan your drive to get this information. This will
- speed up the auto-adopt routine, especially on slow media
- like CD-ROMs.
- -E: Together with the -AF function this function will truncate
- the Files.Bbs after it has been scanned. Using the -E
- function will dramatically increase the speed of the auto-
- adopt function next time it is run.
- -U: Update database. Compares the sizes and dates in the
- database with the actual sizes and dates of the files on
- the disk. If a file has been erased from disk, only the
- size of the file is set to 0, the file will NOT be removed
- from the database! This way, you can easily create an
- offline-area or request-area.
- -N: Creates a new index. Only use this if you've lost the index
- or the index has been damaged.
- -M: Activate the maintenance function (see RafmEdit)
- -S: Sort the database. The files are sorted alphabetically on
- filename.
- -O: Optimize database. Normally, only the index will be sorted.
- With this option the database will also be sorted, saving
- lots of headmovements and decreasing the access time.
- -K: Kill deleted records. Will remove deleted records from the
- database. This function will not kill records in which
- thier filesize=0 (see -D parameter) but only records which
- have the Deleted bit set.
- -D: Delete empty records. Will remove all records containing
- files in which filesize = 0.
-
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 43
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- -F: Create new files.bbs from the database.
- WARNING: using this option will erase ALL existing
- files.bbs!!!
- There is an extra option when using the -F parameter: the -
- c parameter will create a new Files.RA using the paths in
- RafmArea.Dat.
-
- Each extra parameter is considered to be an areanumber which has to be
- processed. By default, RafmCln will process every area, but when a
- valid areanumber is present on the commandline, only that area will be
- processed (you may enter more than just one areanumber!).
- F.e. RafmCln -U /1 /196 will update files in areas 1 and 196 only!.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 44
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- ╒═════════════════════════════════════════════════════════════════════╕
- │░░░ RafmCD ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
- ╘═════════════════════════════════════════════════════════════════════╛
-
- RafmCD is a little program to convert your current Files.BBS to a
- special format. It's designed to be used with CD-ROMs but will in fact
- convert every type of listing. For more information: please read the
- RAFMCD.DEF file!
-
- The special format looks like this:
-
- NAME SIZE DATE DESCRIPTION
-
- Every line in your current listing should only contain 1 file!
- Listings which hold more than one file per line can NOT be processed
- by either RAFMCD or RAFMCLN!
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 45
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- ╒═════════════════════════════════════════════════════════════════════╕
- │░░░ RafmChk ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
- ╘═════════════════════════════════════════════════════════════════════╛
-
-
- RafmChk will check all newly uploaded files, convert them to the
- archive-type of your choice (as defined in RafmEdit) and add a comment
- to it (if supported by the archiver being called). RafmChk only uses 1
- parameter, the -A which overrules the 'Swapping' option from RafmEdit.
- So, if you start RafmChk with the -A parameter, RafmChk will always
- swap whenever an external program has to be called.
- Any other parameter is (just like RafmCln) considered to be an
- areanumber.
- Even when you've enabled online scanning and rearchiving, it is still
- necessary to run RafmChk! Why? Because when the online operation fails
- because of technical problems (disk full etc.) RAFM will abort and the
- file will not be checked completely. That's why you still have to use
- RafmChk to process these files (it's for your (and your users)
- security!).
- An extra option is to let RAFM remove certain files from the archives.
- You can control this by placing a ASCII file called REMOVE.CTL in your
- system-directory. This file should contain filenames (wildcards are
- allowed) which you don't want to have in your archives. Please only
- enter one (1) filename/filemask per line! This option has been
- especially designed to remove BBS-advertisements from archives but can
- be used for anything else (just try and enter *.* ;-))
-
-
- DON'T FORGET: THE CONVERT-DIRECTORY WILL BE ERASED COMPLETELY!!!
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 46
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- ╒═════════════════════════════════════════════════════════════════════╕
- │░░░ RafmAll ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
- ╘═════════════════════════════════════════════════════════════════════╛
-
-
- Since Rafm uses a database, you can't use any of the existing all-
- files creators (except when you first create new files.bbs using
- RafmCln -F) so I decided to write my own. RafmAll has it's own inbuilt
- configuration part, which you can activate by running RafmAll -C and
- can create upto 10 all/newfile listings at once. If you run RafmAll
- without any parameters, the actual all/newfiles listings will be
- created.
-
- Configuration:
-
- If you run RafmAll with the -C parameter, you'll first have to select
- the listing you want to edit, or an empty slot if you want to create a
- new listing. Use the cursorkeys and [Enter].
-
- After pressing the [Enter] key, a new window will open and you can
- edit the listing:
-
- - Areas to include:
- Opens another window, in which you can select the areas. An
- "*" indicates whether or not the area will be included in
- the listing ("*" means include this area).
- - Allfiles path:
- Full path and name to the allfiles listing. i.e where
- should the allfiles list that is created be placed?
- - Newfiles path:
- Full path and name to the newfiles listing. If you leave
- this empty, no newfiles listing will be created.
- - Header path:
- Full path and name to the header file. The header file is a
- standard ASCII file, which is placed at the begining of the
- all/newfiles listing. You can leave this empty.
- - Trailer path:
- Similar to the header path, except that the trailer is
- placed at the end of the listings.
- - Days to include:
- Files newer than this number of days will be placed in the
- newfiles listing. If you set it to 0, no newfiles listing
- will be created. Files older than this will ONLY be listed
- in the Allfileslisting.
-
-
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 47
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- - Separation char:
- The character RafmAll should use between files. Please note
- that anything other than a space will significantly
- increase the size of the listing that is created.
- - Show long comments:
- Should RafmAll process long comments? (i.e. more than 2
- lines). Again as with the seperation character, enabling
- this feature will significantly increase the size of the
- listings that are created.
- - Use ext. ASCII:
- Is RafmAll allowed to use extended ASCII characters (above
- 128) in the listings? Be careful, remember users without
- IBM machines can have great difficulty with these
- characters.
- - Show Xfertime:
- Should RafmAll calculate and write the needed time to
- download a file in the listings? Yet again, enabling this
- option will increase the size of the listings that are
- created.
- - Baudrate 1
- Baudrate 2
- Baudrate 3
- The baudrates to use when calculating the needed time to
- download files.
-
- Archiving the listings:
-
- After creating the listings RafmAll will call a batchfile called
- RAFMZIP.BAT for each individual listing. Please look in the
- RAFMarchive for an example of such a batchfile. You should edit this
- file to enable the creation of the archived listings you want.
-
- ╒═════════════════════════════════════════════════════════════════════╕
- │░░░ RafmLCom ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
- ╘═════════════════════════════════════════════════════════════════════╛
-
-
- RafmLCom is the language-compiler. It will read the standard ASCII
- language file and create a compiled version. The only parameter
- needed, is the number of the language file.
- To create a new language file, you should copy the file 1.LNG
- (contained in the archive) to another file (f.e. 2.LNG). After doing
- this, you can edit the copied file and translate every prompt. Hotkeys
- are always put first on every line without any spaces between them.
- Leading and trailing spaces will be removed by RafmLCom, also, any
- line starting with a semi-colon will treated as a comment and be
- ignored. RAFM will always try to let the translated prompt fit the
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 48
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- layout of the screen, however, it is still your responsibility to
- ensure the prompts are not too long!
- The number of the language file corresponds with the number of the
- language as defined in RaConfig.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 49
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- ╒═════════════════════════════════════════════════════════════════════╕
- │░░░ RafmCnvt ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
- ╘═════════════════════════════════════════════════════════════════════╛
-
-
- RafmCnvt will convert the old Files.Bbs and Files.RA into a database
- to be used by all Rafm-programs. RafmCnvt supports the separate
- Listpath for Files.bbs. Normally you should only need to run RafmCnvt
- once, so you can erase it afterwards if you want to. RafmCnvt will ask
- you some questions which you should answer. Most of the questions are
- pretty straight forward, so I will only explain one of them:
-
- Process missing files (y/n) ?: By default only existing files
- (i.e. files which RafmCnvt can find on your drive) from the
- files.bbs are processed, but if you want you can switch off this
- check so that all files in the files.bbs (wether on the drive or
- not) will be converted.
-
- RafmCnvt supports the extended comments used by QFF, RFW and several
- other packages (comments starting with a +). Downloadcounters are also
- converted, but only if they are placed between [] otherwise they will
- be treated as part of the file description.
-
- Some users of RAFM have asked me to add an extra parameter so that
- they can use RafmCnvt in their maintenance-event. If you add the /N
- parameter, all keyboard-calls will be disabled and the converting will
- take place fully automatically without the need for any intervention
- by you. Please note that running RafmCnvt a second time, will create a
- new database causing all extended information present in the database
- to be lost!
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 50
-
- RemoteAccess File Manager version 1.21
- ───────────────────────────────────────────────────────────────────────
-
-
- ╒═════════════════════════════════════════════════════════════════════╕
- │░░░ Bugreports, address etc. ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│
- ╘═════════════════════════════════════════════════════════════════════╛
-
-
- First of all, if you have a question or a problem, please refer to the
- Common.Q-A file first!
-
- Any bugreports, comments or compliments (:-)) can be sent to me by:
-
- - Posting a message in one of the following (Fidonet)
- echomailareas:
- RA_UTIL (intl) and RA.028 (dutch)
-
- - There is also a special RAFM-Echo called RAFM.SUP. For the time
- being only available at my node and on every support-node, but I
- hope that it will be on the backbone soon. If you want to receive
- this echo, please send a netmail to me.
-
- - Rene Van Hoorn at 2:283/506 or 27:3331/222.
-
- - Posting a message on my BBS:
- EyeS Delight, +31-35-231224
- 24 hours daily, V22bis/V32/V32bis/HST
-
- You can also call one of the support-nodes and post a message there.
- All support-nodes carry the RAFM Support Echo too!
-
- The latest version of RAFM will always be available at my BBS. The
- magic name will be RAFM (of course...). Filerequests are allowed 24
- hours a day, except during ZMH (2.30-3.30 GMT).
-
-
- --==[ THE END ]==--
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ───────────────────────────────────────────────────────────────────────
- Page: 51
-
-