FREQIT V1.0 by Sean Mollitt preliminary docs: A file request door. This door was created to make freqing files easier for Sysops and users (optional). It will read and process every file list i've encountered so far (though I'm sure there must be one that won't work). What it does is parse the file list, adds numbers (for marking -thus eliminating typo's) and pulls the filename, bytes, date and description from each line. (it actually re-formats the display on-the-fly so you'll never get a column out of line) it works with file lists with the following formats: filename.lha 345678 12-jan-92 A file about filenames used in naming files for the purpose of filing names. or... filename.lha 345k 12-jan-92 A file about filenames used in naming ^^ files for the purpose of filing names. or... filename.lha 345678 12-01-92 A file about filenames used in naming ^^ files for the purpose of filing names. or... filename.lha 345678 A file about filenames used in naming files for the purpose of filing names. If anyonce runs across another format, please send me a sample and I'll work it in. in the Freqit.cfg file these different formats are reffered to as: NBDI (name bytes date info), NKDI (name kilobytes date info),and NBI (name bytes info) and NKI (name kilobytes info). INSTALLATION: you should have the following files in the freqit archive: FREQIT.rx <- main executable * FREQIT.msgtxt <- txt used by MM to inform user of waiting freqs * FREQIT.hlp <- Help file * FREQIT.txt <- File diplayed after files ahve been marked for freqing * FREQIT.cfg <- configuration file FREQIT-OUT.rx <- outgoing freq processor, rx'it nightly in your cron (not finished this one yet) FREQIT-IN.rx <- incomming freq processor, rx'it nightly in your cron (after freqit-out -like maybe an hour later) FREQIT.log <- log file of incomming freqs FREQIT.usr <- list of file requests by user. maintained by freqit FREQIT.doc <- what yer reading EILIST.TXT <- sample file partial list (my bbs) so you can see this thing work. Put it whever you set "FILELISTDIR" in your Freqit.cfg file * means you can edit this to you needs. dont mess with the others unless you can program arexx and can follow my convoluted kludgy code. (hey it works!) create a directory in your "doors:" called "freqit" copy all the files from the archive to this directory (except EILIST.TXT). insert the following line in your filemenu.src file (or whereever) and compile it. REXX "^30000^1^doors:FREQIT/FREQIT.rx" the stack size I used is arbitrary, if you think it will run with less, go for it. The next thing you want to do is edit the freqit.cfg file. this is well commented so you should have no trouble with it. Be sure *NOT* to put tabs in the file since I made no provisions for stripping them out (I'll no doubt fix this later) also having any spaces in the paths you specify in this file will probably break it (also on the to do list). the main thing you want to do here is add any file list you want the program to use. the individual bbs list info follows the keyword "BBSLIST" and ends with a blank line. Enter the bbs name (for the freqit menu), followed on the next line by the name (not a path) of the file list for that bbs. the next line should be the node address followed by the time schedule that bbs uses for freqs. Next is a word that defines the type/format of file list (NBDI, NKDI, NBI - see above) make sure you set this right. The last line is the min access needed to see that list. This way you can have your own personal lists as well as ones that the users will see. Freqit makes use of 4 other xenolink utilities: "Mail Machine" by Janne Paakkonen (for notifying users of incomming freqs and file attaches), "XquickAdd" by Magnus Lilja (for freqing files automatically into your file catalogues -may not be enabled in this release) "Freq" by Jonathan Forbes (for creating the .REQ files -included in your xenolink archive/disk). You also need the WB 2.0 cli command "search" for the file search routine. this last one may mean that this door will not function properly under 1.3 let me know. freqit needs to be able to find these files in your paths in order to work. oh ya, you'll need the rexxsupport.library, but you'll no doubt have this if your using arexx once you have freqit set up and feel confident it can work for you, edit your cron file so that you run FREQIT-OUT.rx and FREQIT-IN.rx at least once a night. What you want to do is set up a Freqing "window" so that FREQIT-OUT can generate the nessesary .REQ files and call out for the files afterwhich you can run FREQIT-IN.rx to check incomming files and process them accordingly. this doc file is preliminary, I'll work on it some more once I add a few more features I've been thinking about. anyway you'll figure it out. You can reach me if you want to give me shit for realeasing such a pile of crap, or you want to congratulate me on my noble effort, in the Xenolink echos or in person on my board: Electronic Image (14.4k DS/HST) 514-937-9984 Fidonet 1:167/165 Amiganet 40:500/165 ACKNOWLEDEGMENTS: Janne Paakkonen for Mail Machine, never used it till now, it's wonderfull! Magnus Lilja for Xquickadd and other terrific "less is more" utilities Jonathan Forbes for Z3, for that comfortable confident feeling all sysops should enjoy. LEGALESE: I take no responsibily whatsoever for anything that may go wrong while using this program. (wonder if that covers me?)