@DATABASE Hydra Implementation for MAX's BBS @NODE main "Hydra Implementation for MAX - Main Menu" @{b} HYDRA-MAX Enhanced A Fully Featured File Area Manager For MAX's BBS - Incorporating the Original Hydra-MAX Release 2.00 (Public Beta)@{ub} @{" Introduction " link "intro"} What is this then? @{" Installation " link "install"} How to get it going... @{" The HYDRA.CFG file " link "config"} Description of Hydra.CFG @{" The FILES.CFG file " link "filecfg"} Description of Files.CFG @{" The AREA.CFG file " link "areaconfig"} Description of Area.CFG @{" Executable Descriptions " link "execdesc"} What everything does. @{" Registration " link "regging"} How to pay me ;) @{" Known Bugs? " link "bugs"} What's up with it guv? @{" Future Development... " link "future"} What I'm working on.. @{" CHANGES from recent versions " link "changes"} @{b}READ ME if you're upgrading!@{ub} @{" The Author " link "legal"} @ENDNODE PROGRAM COPYRIGHT AND PROVIDED `AS IS' AND NO WARRANTY IS GIVEN TO UNREGISTERED USERS. USE THE UNREGISTERED VERSION AT YOUR OWN RISK! NOW LOOK AT THIS IN MULTIVIEW AND READ IT PROPERLY =) @NODE intro "Hydra Implementation for MAX - Introduction" This program add a bit of polish to any MAX's BBS.. a Hydra Bi-Directional transfer capability. Once installed any user can select up to 10 files to transfer, while uploading to a temporary directory to you and chatting. All you need to do is install a couple of doors and MUI 3.1 to use @{b}HydraComMUI 1.11 @{ub}(supplied) which is made by MaXiM ... if you don't have/don't want MUI, you can always use @{b}HydraCom1.00@{ub} which doesn't need MUI. SModem doesn't need MUI at all, you might be glad to know. Hydra, as if you didn't know, is a protocol with a difference - it has the ability to transfer two files at once.. one in each direction - AND you can have a live chat with the remote caller without interrupting the transfer. Transfer rates are generally 1580cps each way at 14k4.. not the best cps rates around, but when you consider that's BOTH ways, you're still halving the time you're going to be online. Of course, being a sysop, you might not give a toss.. But it's nice to offer a Hydra protocol =) ... Many users would appreciate being able to send their latest files at the same time as downloading yours. And chat! With ISDN (we all wish!) rates average 7800cps each way with chat, or so I've been told! Plus since v2.00 an amazing file lister has been added.. Making it more than a mere protocol door! See below.. Interested? Then you'll want to install it.. And if you're not impressed, wipe it again. It's your users' loss. SModem support has now been added. It works in almost the same way as HydraCom, except the BBS end needs to be loaded first, so the prompting is a little different. The user is told what to do. @{b} Addition about Hydra-MAX Enhanced!@{ub} Since v1.40 of this door I've been thinking how good it would be if it weren't just an add-on to get Hydra on your BBS, but instead a full takeover door which does everything. Well, this is the result. I've called it Hydra-MAX Enhanced which isn't very imaginative.. but that's all it is really. The meat of the door is still the Hydra handling. So..if you're maybe setting up a BBS and can't be bothered to set up the menu's needed then you now don't need to. H-MAX Enhanced will do it for you. Just set up the sections, a config for the door to tell it about them and leave it to it. Add a line with `ENHANCED' in the Hydra.CFG to enable it.. See the configs page for more info. It is quite memory hungry too, LZX bundling will probably not work with 2Mb or less. HydraCom may also have problems, however the rest of the door will - SModem will be fine, tried and tested. The enhanced door does take a lot of setting up, but it's worth it.. All you need to do really is edit the Area.CFG to suit you, and the Hydra.CFG - then load it and see what happens. Make sure you've got all the Compulsory text files too. Boring examples are provided. You also need to add the LogOff file to your logoff script in MAX. Also included is a LogOffNoOut which is the same but doesn't open a window. It's also fractionally faster. Therefore far more suited to an automated script =) @{i}NOTE@{ui} : HydraCom isn't perfect. It's not my fault. Ok? Occasionally you will find that a file being sent one way stops - and doesn't resume for over 30 mins. I've had it happen myself and boy.. is it annoying! @ENDNODE @NODE install "Hydra Implementation for MAX - Installation" You can simply run the Install script, or ... @{b}If you are not planning to run the Enhanced version, you can skip all the parts which have an asterisk (*) beside them.@{ub} 1) Make some new directories : BBS:Temp_Receive/ (or appropriate to TEMP) BBS:Doors/Hydra/ BBS:Doors/Hydra/Configs/ BBS:Doors/Hydra/Display/ * BBS:Doors/Hydra/Users/ * BBS:FileAreas/ * BBS:TempArc/ Also ensure RAM: and T: exist (they ought to do!) for temp files etc. 2) Copy all the files in the directories you unpacked to the relevant directory in BBS:Doors/Hydra/ The result should look like this : @{"SAMPLE HYDRA/ DIR" link "sdir"} 3) Copy all the files in the provided C/ drawer from the archive into your own C: or any other place where a standard Shell can find them without a supplied path. 4) Create or edit these config files : @{"BBS:Doors/Hydra/Configs/Hydra.CFG" link "config"} @{"BBS:Doors/Hydra/Configs/Files.CFG" link "filescfg"} * @{"BBS:Doors/Hydra/Configs/Area.CFG" link "areaconfig"} * BBS:Doors/Hydra/Configs/Access.CFG @{i}Regd version only@{ui} 5) Create or edit these ANSI screens : @{i} # denotes a non-compulsory file, IE if it's not there the program will use a boring default display. @{ui} # * BBS:Doors/Hydra/Display/ArchiveList Non compulsory and for Enhanced only, yep =) This is the same as ListingScreen except it is displayed when listing the contents of an archive. Also there are less commmands available when in archives. In archives you can : [M]ark File [R]ead Text File [L]ook at File_ID.diz [D]ownload Marked Files/Selected File # * BBS:Doors/Hydra/Display/Archiving Shown when the compressor is at work archiving the marked files. NOTE on slow processors this can take a long time. You should make sure this is clear on the screen to avoid users hanging up as there is no way to abort the compressor. * BBS:Doors:Hydra/Display/BundleOptions This is a basic table displaying some pretty useless information about the archive which has been created and the files which are in it, so the user can compare them for no reason other than entertainment =) Makes interesting reading I suppose ;) # BBS:Doors/Hydra/Display/CheckUploads Shown while looking for uploads in BBS:Temp_Receive/ or whatever you specified in Hydra.CFG - it flashes past pretty quickly so use a %Y to slow it down if you want anyone to actually see it ;) BBS:Doors/Hydra/Display/DescribeFiles This is basically a blank screen =) It has just two lines at the top which are the titles of 3 columns, ALL YOU CAN DO is change the colours. LEAVE IT WELL ALONE! This is shown when the user is describing their uploads. They can enter up to 50 characters, and describe up to 25 files. If they uploaded more, they will be ignored until the next user uploads, then HE will get to describe them! I'm fixing this. * BBS:Doors/Hydra/Display/FileAreas This is a list of your File areas for the users to choose from in the lister (Enhanced version) - use AREA numbers as defined in the @{"Area.CFG" link "areaconfig"} to number the areas, not section numbers or anything else. * BBS:Doors/Hydra/Display/FileInfo A short file explaining what the File Information function does and expects to be entered. All it requires is a filename, no area/section. Wildcards are not supported! * BBS:Doors/Hydra/Display/ListingScreen The main screen file for the Enhanced version, this file must remain the same in format from line 8 and below to line 24 inclusive - the filelists are displayed in this space. * BBS:Doors/Hydra/Display/MainMenu Shown when first loading with the Enhanced switch on. Look at the example for the possible keys which can be pressed. No prompt is added, so put one in the menu. Leave the cursor where you want the entered letter to appear. It can be enclosed, but leave at least 2 spaces either side so you lose none of the menu. The menu is redrawn after each keypress which is not an available key.. * BBS:Doors/Hydra/Display/NoAccess Shown when the user tries to perform an action which they have insufficient access for. This screen will not be of much use until you register as you cannot define required access levels in an unregistered version. # BBS:Doors/Hydra/Display/NoCreds If the user has insufficient download credits this is shown to them whenever they try to download. The program is NOT `generous' - by this I mean they must have one upload before they can download at all unless they have a 0:1 rt. Example - Rt 4:1 Dns 4 Ups 1 They cannot download more. - Rt 4:1 Dns 0 Ups 2 They have 8 dl's left. # * BBS:Doors/Hydra/Display/NoFiles Shown when an area which has no files is entered. Should not normally appear because your file areas will not be empty! Or so you hope. If unfound, a line of text will be shown instead. An entry is also made into the log. # * BBS:Doors/Hydra/Display/NoFileID Shown when no File_ID.DiZ could be found in an archive or supported filetype. # * BBS:Doors/Hydra/Display/NotFound Shown when a file in file.data is not actually on the drive to read or download. An entry is also made in the logfile. # * BBS:Doors/Hydra/Display/NoInfo Shown when a file isn't found that the user asked for info on, either through the lister or the main menu. An entry is also made into the logfile. # * BBS:Doors/Hydra/Display/NoMem Shown when the user tries to bundle their marked files but the host system has insufficient memory to run the compressor. Use a %Z at the end. # * BBS:Doors/Hydra/Display/NoMarked Shown when the user tries to bundle their marked files when they don't have any marked files. # BBS:Doors/Hydra/Display/NoUploads Shown if no uploads were found. Maybe a plead for the next time ;) Use %Z at the end once again. BBS:Doors/Hydra/Display/PreSelect Shown before the user starts selecting files from the table in the un-enhanced version (also H or D from main menu in the enchanced version) so it should be some help with Hydra and SModem usage and rules, maybe. To keep it onscreen, use a %Z at the end. This is the first file shown when loading without the Enhanced switch. * BBS:Doors/Hydra/Display/Search Short screen on searching help and the format required for the search string. # * BBS:Doors/Hydra/Display/SearchFileAreas As FileAreas but with an extra line explaining the format for selecting areas to search. If it doesn't exist then FileAreas will be used. # * BBS:Doors/Hydra/Display/SearchHeader This ANSI/ASCII file is pasted onto the beginning of a File Search - use it to customize your BBS searching.. =) Best to keep it under 15 lines or you'll get no files on the first page ;) I've also had some problems using ANSI, so if your screen looks distorted, change it to ASCII. Also, don't put a Ctrl-L in, or 2J both of which clear the screen because if you do, you lose the control bar at the bottom. It will re-appear though. If it doesn't exist, no banner is put at the top at all. Nothing is added between the file and the list. It would be advisable to put some column headers in too. The first number is the AREA number, then the Filename, Size and Description. BBS:Doors/Hydra/Display/SelectFiles A table which is displayed while the user selects their files the old way. Don't alter the layout or position, but you can adjust the feel and colours. BBS:Doors/Hydra/Display/WantToUpload A prompt for the non-enhanced version - if the user didn't type any filenames in then normally Hydra wouldn't be started, but if the user presses Y at this screen, it will so they can upload. 6) Create or edit these batch files : * @{"BBS:Doors/Hydra/Rec.BAT" link "batches"} * @{"BBS:Doors/Hydra/???AddAd.BAT" link "batches"} 7) Install HYDRA_ENHN in MAX as a standard door, using Menu Function 34 with no Extra value. 8) EITHER a) Put LogOffNoOut in your logoff script or b) Run LogOff or LogOffNoOut every time you pass the computer or c) Put LogOffNoOut in a cron script to be run at least every 24Hrs 9) If you register, you can either put the key in S: or BBS:Doors/HYDRA when you get it. @ENDNODE @NODE sdir "Sample HYDRA/ dir" BBS:Doors/Hydra/ Users (dir) M.Default Display (dir) AccessSettings ArchiveList Archiving CheckUploads DescribeFiles FileAreas FileInfo ListingScreen MainMenu NoAccess NoCreds NoFileID NoMarked NoMem NotFound NoUploads Online_Help PreSelect Search SearchFileAreas SearchHeader SelectFiles UserPrefs WantToUpload Configs (dir) Area.CFG Files.CFG Hydra.CFG HYDRA.LOG HYDRA_ACC_SET_R HYDRA_ENHN LhAAddAd.BAT LogOff LogOffNoOut LZXAddAd.BAT Rec.BAT --- Don't worry if you don't have all the Display/ files - not all of them are required. After running the door in Enhanced mode you will also notice a new file appear in Users/ - it's called M.InUse - don't delete it, just ignore it, it's used to store the marked files and is reset on each new user coming into the door so doesn't need deleting. Plus lots of small files will appear, being the preference files of your users. Do not alter or delete them. Also you won't have HYDRA_ACC_SET_R as these are registered only programs. HYDRA_ACC_SET_R is used to set the access levels required to perform uploads, downloads and listing in each area seperately, giving total control. After registering you will need to create a new config file as well, Configs/Access.CFG - details will come with the registered program. @ENDNODE @NODE addad "Hydra Implementation for MAX - Advert Batch files" These files, if they exist, are executed just before writing the uploaded files to the file.data and they can actually do anything you want, but they are intended to add BBS adverts to archives if you want to add one.. To get one activated all you have to do is create one similar to LZXAddAd.BAT but replacing the main line which loads LZX with one loading your archiver/adder etc.. Replace the first three letters of the filename with the suffix. MyFile.LZX ; LZXAddAd.BAT MyText.TXT ; TXTAddAd.BAT etc.. It only works for 3 letter suffixes , so guide is not usuable. However you can use gde and hope no other suffix collides with it in the future =) Just edit the batch file to suit your requirements. The only arguement which is supplied is the name and path of the archive, which can be utilised with .key as shown in the examples.. If any one of the batch files doesn't exist, nothing will be added, simple. You can have a batch file for LZX, but none for any other and all will be fine. Note this feature isn't restricted to archives. It can be used on TXT files etc with C:Type >FILE BBS:MyBBSAdvert to add some text to a text file. @ENDNODE @NODE config "Hydra Implementation for MAX - HYDRA.CFG file" The config file must reside in BBS:Doors/HYDRA/Configs/ and must be called HYDRA.CFG You can put these commands in.. each one must have it's own line and be terminated with a CR.@{b} Leave a blank line at the end of the file or the last line may not be read!@{ub} Note the FILE keyword is now gone. See @{"Files.CFG" link "filecfg"} If any keyword is defined more than once, the last one will be used. @{" NOALLOWLZX " link "cfgallowlzx"} @{" NODISPTIME " link "cfgtime"} @{" NOIMMEDUPD " link "immedupd"} @{" ALLOWLZX " link "cfgallowlzx"} @{" DISPTIME " link "cfgtime"} @{" ENHANCED " link "cfgenh"} @{" EXTERNAL " link "cfgext"} @{" FORCEUPLOAD " link "cfgforce"} @{" IMMEDUPD " link "immedupd"} @{" LINE " link "cfgline"} @{" LOCK " link "cfglock"} @{" LOGLEVEL " link "cfglog"} @{" SERIAL " link "cfgser"} @{" TEMP " link "cfgtemp"} @ENDNODE @NODE cfgallowlzx "Hydra MAX Enhanced Guide - HYDRA.CFG file" @{b} (NO)ALLOWLZX@{ub} default off This keyword allows the users to select LZX as a Marked File Bundling method if it appears in the config. If it doesn't, they are restricted to LhA which needs less memory.. If you don't have enough memory to compress the files nothing will happen. eg; ALLOWLZX To ensure that users cannot use LZX even if the default setting of OFF changes, use NOALLOWLZX @{i}Effective only in Enhanced mode!@{ui} eg; @ENDNODE @NODE cfgtime "Hydra Implementation for MAX - HYDRA.CFG file" @{b} (NO)DISPTIME@{ub} default off If in the config, this switch turns on the time display in the Lister window of the Enhanced version. If it's not in, the time will not appear, speeding up operation slightly. The result is stored in the User Prefs file until they change it.. ie if you specify DISPTIME, the users will have it on as default. DISPTIME As with ALLOWLZX, you can specify NODISPTIME to override any changing defualts. NODISPTIME @{i}Effective only in Enhanced mode!@{ui} eg; @ENDNODE @NODE cfgline "Hydra Implementation for MAX - HYDRA.CFG file" @{b} LINE@{ub} default 14400 Used to estimate the transfer times.. and is also passed to HydraCom. Determines the most likely LINE SPEED. If you have a 14k4 then it'll be 14400 more often than not. eg; LINE 14400 LINE 28800 @ENDNODE @NODE cfglock "Hydra Implementation for MAX - HYDRA.CFG file" @{b} LOCK @{ub} default 19200 Determines the LOCKED BAUD RATE which is in MAX's Modem Settings. Set to 19200 if unsure (the default anyway)! eg; LOCK 38400 LOCK 2400 @ENDNODE @NODE cfgser "Hydra Implementation for MAX - HYDRA.CFG file" @{b} SERIAL @{ub}: default serial.device Tells Hydra which serial device you're using. Must match the one in MAX's Modem settings ... eg; SERIAL 8n1.device SERIAL artser.device @ENDNODE @NODE cfgforce "Hydra Implementation for MAX - HYDRA.CFG file" @{b} FORCEUPLOAD @{ub} default 20 Tells the program which MAX section to put uploads in. It will probably crash if you specify a non-file section. Default 20 for the sole reason that's my Files to Sysop section. eg; FORCEUPLOAD 1 FORCEUPLOAD 25 @{i} Enhanced Only addition @{ui} If you have the Enhanced mode enabled you can opt to allow the user to upload to the section they are currently listing. Just specify 999 as the section to upload to. eg; FORCEUPLOAD 999 @ENDNODE @NODE immedupd "Hydra MAX Enhanced Guide - HYDRA.CFG file" @{b} (NO)IMMEDUPD @{ub} default off If this is in the config, LogOffNoOut will be run after each upload to keep the filebase up to date. This means you don't need to run it after logoff too. The only benefit of using this option over after logoff is that users will be able to see their uploads. If you specify NOIMMEDUPD, the program will not be run after logoff, also the default. The result (on or off) will be stored in the User Prefs file as a default, ie if on in the config, each new user will also have it on in their Prefs unless they turn it off. eg; IMMEDUPD NOIMMEDUPD @{b} This function has been removed temporarily! @{ub} @ENDNODE @NODE cfgtemp "Hydra Implementation for MAX - HYDRA.CFG file" @{b} TEMP @{ub} default BBS:Temp_Receive/ Where to put the uploads as they come in (directory) - they will be moved to the Main Path as specified in MAX and put in the filebase after the transfer. You should specify a trailing slash - the program will add one if it's not there, but be safe eh? =) It must already exist. @{b} Make sure this directory is EMPTY. The program will delete ALL files in it. It must exist. @{ub} TEMP File:Temp/ TEMP DH1:TempDir/ @ENDNODE @NODE cfglog "Hydra Implementation for MAX - HYDRA.CFG file" @{b} LOGLEVEL @{ub} default 3 How much logging to do - ranges from 1 to 5 and uses the Hydra.Log file For a breakdown see @{"Logging Levels" link "loglevs"} eg; LOGLEVEL 1 LOGLEVEL 4 @ENDNODE @NODE cfgext "Hydra Implementation for MAX - HYDRA.CFG file" @{b} EXTERNAL @{ub} default HydraCom Whether to use SModem or HydraCom. Not required if you're going to use HydraCom. Only the first letter is actually read (S or H) - note that this command doesn't determine the one-and-only mode that can be used, but it determines the default mode. Users may change what they use if they wish. eg; EXTERNAL SMODEM EXTERNAL S @ENDNODE @NODE cfgenh "Hydra Implementation for MAX - HYDRA.CFG file" @{b} ENHANCED @{ub} default off Put this in the config to enable the Enhanced mode (Lister and ZModem etc) Takes no arguements or strings.. Leave it out to revert to the original Hydra-MAX. eg; ENHANCED @ENDNODE @NODE externals "Hydra Implementation for MAX - External Programs" @{b} Transfer programs and paths..@{ub} HydraCom must be in your search path Version of HydraCOM supplied : 1.11 .. @{b}requires MUI 3.1 @{ub}! The standard Hydra fare door. Works equally well on either side of the connection, caller or BBS. Slow on 020's or below. Buggy. SModem must be in your search path Version of SModem supplied : 1.00r3 .. doesn't need MUI! =)) A newer entrant into bi-directional transfer. Tends to be faster than HydraCom but does sometimes get lots of errors. Suited to slow machines (020 and even below is fine). New version supplied from HM 2.00 which should be better. @{b} Other programs and paths.. @{ub} DMS (in your search path) Used to get info on a DMS archive. @{i} These are needed to get the relevant File_ID.DIZ's@{ui} (Enhanced Only) DMSDescript (in your search path) Extracts DMS File_ID's EXEDescript (in your search path) Extracts Executable File_ID's GIFDesc (in your search path) GIF File_ID extractor LhA @{b}(not supplied)@{ub} (in your search path) LZX @{b}(not supplied)@{ub} (in your search path) Both used to list, enter and extract File_ID's. ModuleDescript (in your search path) Gets File_ID's from modules TXTExtract (in your search path) Gets File_ID's from texts LhA and LZX are not supplied. I assume you have them? =) @ENDNODE @NODE loglevs "Hydra Implementation for MAX - Logging Levels" 3 is the best ratio between info and size, while 4 is better if you want to know more about what's happening. 1 and 2 tell you almost nothing. 5 is full of minor notes which you won't need at all. Experiment till you find a suitable level - when reporting bugs always use 5 and send me your log describing the problem. @ENDNODE @NODE filecfg "Hydra Implementation for MAX - FILES.CFG file" @{b} I've been changing and restoring the use of this file in every other release. A bit confusing. BUT now it's done - and it's gonna stay. It's funtion now is to contain paths to check when files weren't found on the BBS.@{ub} @{b} THIS FILE IS NOW COMPULSORY. @{ub} This config file was introduced with v1.12 and allows you to specify more than one filepath to search when looking for files WHICH ARE OFFLINE. It simply contains a list of directories to scan. If you want to be awkward and like making work for yourself you can just specify one entry and use this file rather than the FILE command in the main config =) You can specify up to @{b}500@{ub} directories. Anyone want more? Simply type them in, one dir per line.. BBS:Files/SYSOPFILES/ RAM: NODELIST: MAIL:Bin/ and so on. You @{b}must put a trailing slash @{ub}and @{b}always leave a blank line at the bottom of the file@{ub}, as with the Hydra.CFG file. @{b} NOTE THAT THIS FILE IS NOT FOR THE PATHS LEADING TO YOUR ONLINE FILES. IT IS FOR THE PATHS LEADING TO OFFLINE FILES WHICH YOU DON'T MIND FRIENDS DOWNLOADING. @{ub} ie - NODELIST: if you don't mind your mates grabbing your nodelist. @{b} REMEMBER ALL USERS CAN ACCESS THESE PATHS AT THE MOMENT - THEY JUST NEED TO KNOW THE FILENAME!@{ub} A problem has been brought to my attention by someone who was using thirty odd entries in this file.. It seemed to crash when it was looking through them all.. In fact it hadn't crashed, but it was so busy working on the directories it seemed as if it had. Please keep the number of directories here to a minimum. Remember you don't need to put BBS:Files/ in here as that's the default path which is used by the MAX File.data thus it is automatically searched. @ENDNODE @NODE execdesc "Hydra Implementation for MAX - Descriptions" @{" HYDRA_ENHN " link "enhance"} Fully Enhanced version @{" HYDRA_ACC_SET_R " link "accset"} Sets access for areas Registered users only.. @{" LOGOFF " link "logoffdoor"} Execute this on logoff @{" Batch files.. " link "batches"} @{" Other External Programs " link "externals"} File_ID extractors.. @ENDNODE @NODE batches "Hydra MAX Enhanced Guide - Batch files" These AmigaDOS scripts are executed at various times and allow you to customise the way HM works to a certain extent.. All batch files go in BBS:Doors/Hydra/ Rec.BAT - executed to start an XPR upload. @{"LZXAddAd.BAT" link "addad"} - executed just before adding the file to the @{"LhAAddAd.BAT" link "addad"} file.data to add BBS adverts to the various @{"ZIPAddAd.BAT" link "addad"} types of archive. In all cases there is an example provided, please look at it! @ENDNODE @NODE logoffdoor "Hydra MAX Enhanced Guide - LogOff description" This small door must be run before you first load Hydra-MAX Enhanced and put in your logoff script, or midnight run script. It must at least be run regularly. What it does is make several files in BBS:FileAreas/ which are small clones of the file.data but split into chunks by area. This makes accessing the files much much faster and makes speedy file searching possible. Also included is LogOffNoOut which is the same but doesn't open an output window - this makes it fractionally faster and better for unassisted running. Requires the path BBS:FileAreas/ Requires the file.data and file.index to be in the path specified as the Main File Path in MAXsBBS. @ENDNODE @NODE accset "Hydra MAX Enhanced Guide - Access Setter" @{i} Access Setter - Part of the Hydra Protocol Door@{ui} This program, also to be run as a door, is for setting the access required to List, Upload, and Download in each individual section. By default every area you specify has List and Download access requirements of 10, and Upload access is 0. It is not possible to change these presets in the unregistered version. Registering will get you this program which generates a file to customize them. I will also provide details on the format of the file it makes so you can directly edit each area without loading this program. Either way, you gotta register first =) Therefore do not put your Sysop Area on an unregistered Hydra-MAX. I will not be responsible for private files downloaded by users. When registered, this is how you use it: You will see a table (BBS:Doors/Hydra/Display/AccessSettings) and each value for Upload/List/Download has a letter next to it - press this letter to type in a new value for the corresponding access setting. Since only 10 areas are displayed on the table, you must press < or > to see more. Press 0 to save, or - to abort the new settings. If no file exists to tell Hydra-MAX what access levels to use, the defaults of List = 10, Download = 10 and Upload = 0 will be used. @ENDNODE @NODE areaconfig "Hydra MAX Enhanced Guide - Area Translations" This file is ESSENTIAL. It tells the door what sections of MAX are in use and what Area number relates to them. It is only essential if you have ENHANCED selected by the way =) To show you what I mean.. In the door there is a text file shown upon loading, (FileAreas) which is a list of the File Areas available. You will not want to put in the actual Section numbers which relate to them unless you're very organised and they start at 1, and increase in alphabetical order to the last one. If that is the case by the way, sorry, you'll still have to do this, but it'll be easy anyway. What you're going to want to do is let the user type 1 to get at the first area and say, 50 for the last one if you've 50 file areas. Yes? Well this file is just for that. This is how you do it. It's simple. The FIRST line of the file is for the Area 01. So.. Area 01 is going to be, Files To Sysop? Yep. Ok, now my Files To Sysop is actually Section 20 in MAX. So on the first line I type 20. The SECOND line will be for Area 02. And so on. You'll end up with this... --- 20 21 22 23 24 etc etc etc --- If your file sections begin at 20 and go up, like mine do. Or this.. --- 20 64 1 6 76 34 etc etc etc --- If they're scattered all over the place. Whatever they're like, that's what you have to do for this file. Leave at least 3 blank lines at the end. They won't be interpreted as blank areas, don't worry ;) You must switch on the From: field for all the File Areas you wish to use, too, otherwise H-MAX won't recognise or use them properly. There is no option for anonymous uploads in H-MAX yet anyway. The only way to find out who uploaded a file is to use the unfinished File Information. Then make a screen to display the Areas, and you're done. There is an example but I'm sure you'll agree the Areas are wrong anyway =) @ENDNODE @NODE enhance "Hydra MAX Enhanced Guide - Executable Description" @{i} Hydra-MAX Enhanced Hydra Protocol Door@{ui} Whoa.. Where do I start? =) Let's just say if you were to install this door properly, you could throw away all your MAX File menus and never need to use Upload and Download menu functions again, or Listing for that matter =) So.. Load it, play with it, then choose a topic : @{"Viewing Functions " link "viewfunc"} @{"Archive Functions " link "arcfunc"} @{"Transfer Functions " link "transfunc"} @{"User Preferences " link "userprefs"} @{"File Searching " link "filesearching"} @{"NewFiles Scanning " link "newfiles"} You will find many references crop up twice, three times, if they are related to both Viewing and Archiving for example. [V]iew Archive is one of them. Twitting works fully in all places. Options from the main menu are as follows.. [H] - This makes the program act as if ENHANCED was not put in the config, and pops up the table (after Display/PreSelect) so users can mark files if they know the filenames. [N] - @{"NewFiles scan." link "newfiles"} [D] - Very similar to the old Hydra-MAX door, except it uses an XPR library to send the files, NOT Hydra/SModem. The library is selected in the [P]references in the lister, or from Main Menu. [U] - Uploads file(s) after asking the user for an area number. Uploads are processed in the same way as normal, dupe-checked, length-checked and then added to the filebase. Reads Display/FileAreas for the screen. [S] - Searches the filebase for a specified piece of text, or looks for any files NOT containing the text (not that that's going to be used!). The user specifies the areas to be searched on a single line ie: 1 2 3 6 8 OR they can just press A to search ALL fileareas. Reads Display/SearchFileAreas which should be the same as FileAreas but with a helpful line detailing how to use the search area procedure. [I] - Information on file. The user needs to type in the filename only, no area/section number is required. It returns information on the file such as Uploader, Size, Area/Section and Path. [L] enters the Enhanced door proper.. Lists files from the area selected from the menu file Display/FileAreas. [Q] - Quits to the BBS. COMPULSORY FILES : * denotes enhanced version only. BBS:Doors/Hydra/Configs/Hydra.CFG BBS:Doors/Hydra/Configs/Files.CFG * BBS:Doors/Hydra/Configs/Area.CFG * BBS:Doors/Hydra/Display/MainMenu BBS:Doors/Hydra/Display/SelectFiles BBS:Doors/Hydra/Display/DescribeFiles BBS:Doors/Hydra/Display/WantToUpload * BBS:Doors/Hydra/Display/FileAreas * BBS:Doors/Hydra/Display/ListingScreen BBS:Doors/Hydra/Display/UserPrefs * BBS:Doors/Hydra/Display/FileInfo * BBS:Doors/Hydra/Display/Search * BBS:Doors/Hydra/Display/NoAccess * BBS:Doors/Hydra/Display/AccessSettings (Only when registered) * BBS:Doors/Hydra/Rec.BAT * XPRD (in your search path) HydraCom, SModem (in your search path) @{"All the File_ID.DIZ checkers" link "externals"} OPTIONAL FILES : * denotes enhanced version only. * BBS:Doors/Hydra/Display/ArchiveList BBS:Doors/Hydra/Display/PreSelect BBS:Doors/Hydra/Display/CheckUploads BBS:Doors/Hydra/Display/NoUploads * BBS:Doors/Hydra/Display/NoMem * BBS:Doors/Hydra/Display/NoMarked * BBS:Doors/Hydra/Display/Archiving * BBS:Doors/Hydra/Display/SearchFileAreas * BBS:Doors/Hydra/Display/NoFileID * BBS:Doors/Hydra/Display/NotFound * BBS:Doors/Hydra/Display/NoFiles * @{"BBS:Doors/Hydra/???AddAd.BAT" link "addad"} @ENDNODE @NODE newfiles "Hydra MAX Enhanced Guide - NewFiles Scan" This function lists new files, either since x days ago or since last logon, read on for more info. When selected, the user gets a prompt asking what type of search to perform. The choices are : [x] - Enter a number to search for files uploaded in the last x days. [L] - Last on, search for files the user hasn't had a chance to see, ie, uploaded between the time the user was last on and now. Accurate to within one minute.. If the user logged off at 11:39 on any one day, and a file was sent at 11:39 on the same day (quick user!) then it won't be picked up. Not going to be a problem though, is it? Really? =) [H] - Help, displays a short help file in the Text Reader, see the example and note it must be called BBS:Doors/Hydra/Display/NewFilesHelp ! Note that the scan is Global, ie, it searches all fileareas. @{b}When searching@{ub}, a filearea is searched at a time, and any matches are displayed at the end of each area. Now, the user can do the following.. [D]ownload one of the files shown - the user has to enter the number beside the file they want and it will be XPR'ed to them. [M]ark File - add the file to the marked list. If you Mark a file then you can enter the lister (enhanced mode) and Hydra/SModem the file down, or just batch download it after you finish browsing. [A]bort - Quits the entire scan. [S]kip Area - skips the rest of the area if more files are to be listed and starts on the next one. [C]ontinue (Return also) - carries onto the next page/area @ENDNODE @NODE filesearching "Hydra MAX Enhanced Guide - File Searching" On the main menu is an option to search the files for a string of text either in or not in the filenames and descriptions. Default action is to search filenames and descriptions for text entered. If the user adds a tilde (~) to the beginning of the text the action is reversed - all filenames and descriptions NOT containing the text will be shown. When selecting the area to search, typing @{b}A@{ub} and pressing Return will seach all areas. Note that wildcards are not required. Just type in a string. To specify an area to search, or multiple areas, just type them in, seperated by a space, at the next prompt. NOTE you don't type the actual section number, but the Area number as defined by Area.CFG - entering 1 here refers to line 1 of this cfg file, and the number on that line calls the relevant section. eg; 1 2 13 3 No specific order is required. The areas will be searched in that order. The search cannot be stopped (yet). Typing @{b}A@{ub} searches all areas in ascending numerical order. The list is put in a file in RAM: and displayed through the text reader. Any calls for it to be downloadable?? Soon to come - an option to search the files IN ARCHIVES. It would then be possible to search all the LZX and LhA archives for one specific file, and once found, bundle it in it's own archive and download it. All this would take less than 10 seconds.. With a moderate filebase of course. On average 50 files are scanned a second, not including inside archives. @{b} Hydra MAX Enhanced@{ub} @{i} - leading the way for MAX'sBBS filebases!@{ui} @ENDNODE @NODE viewfunc "Hydra MAX Enhanced Guide - Viewing Functions" This is a list of descriptions of functions related to viewing files etc... Most of them are self explanatory.. but here we go.. =) @{b}[I]nfo@{ub} The same as [I] from the Main Menu except you don't need to enter the filename now, the file under the cursor is used. @{b}[V]iew Archive@{ub} Merely lists the contents of an archive in the text reader. You can scroll up and down and perform the normal text viewing functions. Currently working for: LhA LZX @{b}[R]ead Text File@{ub} Loads the selected file into the text viewer. While it is perfectly possible to load hex files (executables, libraries etc) into the text viewer it is likely to cause a crash, or simply be rejected. Scrolling up and down is possible, as is Goto Line. Use the keypad number keys to move the cursor left and right, and SPACE selects the highlighted option. @{b}[L]ook at File_ID.diz@{ub} Investigates the selected file and checks it for a File_ID.DIZ and if found, extracts it, and views it using MAX menu function 22. Since they're only 15 lines or so long, it's not worth loading the text viewer. Works in archives, and on archives of course.. These filetypes are supported.. LZX LhA DOC/TXT/MAN MOD/MED EXE DMS GIF It figures it out by filenames... so be normal with filenames! =) Type Search Criteria ~~~~ ~~~~~~~~~~~~~~~ LZXs; Last 3 being equal to LZX LhAs; LhA (case independent, as are all) Docs; DOC/TXT/MAN DMS's; DMS GIFs; GIF Modules; MOD/MED (or first three) EXE; @{i} Tries if no other was found.@{ui} @{b}[W]hat's Marked?@{ub} Shows the list of marked files and their sizes in the text viewer. Very basic at the moment. Will probably be subject to improvement. @{b}[?] Help@{ub} Displays the file BBS:Doors/Hydra/Display/OnlineHelp if it exists. You could PowerSnap this section of the guide or something. If it doesn't exist the user is plonked back to the listing. @ENDNODE @NODE arcfunc "Hydra MAX Enhanced Guide - Archive Functions" Anything connected to archives will appear below... @{b}[E]nter Archive@{ub} Now we're talking.. This looks in the archive and treats it as a directory or file section. You can perform most of the functions that you would do in a normal file area. Anything marked with a green asterisk (on the ListingScreen) you cannot do in an archive. You can : [M]ark File [R]ead Text File [L]ook at File_ID.diz [D]ownload Marked Files/Selected File Currently working for: LhA LZX @{b}[V]iew Archive@{ub} Merely lists the contents of an archive in the text reader. You can scroll up and down and perform the normal text viewing functions. It works best for LhA at present, LZX doesn't have a very friendly layout. Currently working for: LhA LZX @{b}[B]undle Marked@{ub} More cream. This takes all the marked files and packs them into an LZX or LhA archive, providing you have enough memory to run LZX with the BBS loaded. Experience shows you will need 2.5Mb of memory to easily manage this, although it's possible with 2Mb - but you'll be lucky. The file will be added to the marked files list and can only be removed by leaving the door and reloading. I will add a Clear Marked Files asap. @ENDNODE @node transfunc "Hydra MAX Enhanced Guide - Transfer Functions" Transfer functions and file marking functions... Note the user's Downloads/Uploads/Ratio are grabbed from the BBS, so use those to alter ratio's etc. @{b}[M]ark File@{ub} Marks or unmarks a file for download. You can mark up to 100 files then you have to do a download to clear them. Unmark a file by pressing [M] over it when it's marked. @{b}[W]hat's Marked?@{ub} Shows the list of marked files and their sizes in the text viewer. Very basic at the moment. Will probably be subject to improvement. @{b}[C]lear Marked Files@{ub} Erases the list of marked files in case they didn't get wiped after bundling or downloading (remember this program isn't finished!) @{b}[D]ownload File(s)@{ub} Initiates a Uni-Directional file transfer with the selected protocol. You must have the relevant xpr library. XPRD is used to handle the transfer. It must be in C: Marked files are sent, and if none are found, the currently selected file. If marked files are found, the selected file is not sent. @{b}[U]pload File@{ub} Initiates an Uni-Directional upload with the selected protocol. Uses AsXpr again. The file is placed in the current section, if no @{"FORCEUPLOAD" link "cfgforce"} was specified. If FORCEUPLOAD was specified then the file is placed in the section specified by FORCEUPLOAD. To get the upload, an external batch file is launched... Doors:Hydra/Rec.BAT It should basically load an external transfer program and put the uploads in the directory specified by the TEMP keyword, BBS:TEMP_RECEIVE/ by default. There is one supplied which works fine, and uses XPRD. @{i}@{b}[H]ydra/SModem Xfer@{ub}@{ui} The cream of the door. The icing on the cake. Or something. Initiates a bi-directional transfer using HydraCom or SModem depending on the users choice by priority. If they have not altered their setting, it will be what you specified in @{"EXTERNAL" link "cfgext"} in the Hydra.CFG The marked files are sent, if none then the selected file. All uploads are placed using the same procedure as in [U]pload File - see above. @{b}[B]undle Marked@{ub} More cream. This takes all the marked files and packs them into an LZX or LhA archive, providing you have enough memory to run LZX with the BBS loaded. Experience shows you will need 2.5Mb of memory to easily manage this, although it's possible with 2Mb - but you'll be lucky. @ENDNODE @NODE userprefs "Hydra MAX Enhanced Guide - User Preferences" @{b}[P]references@{ub} Enters the User Preferences screen. A bit sparse at the moment. It contains : @{" [A] Marked File Bundling Method " link "markedfilebundling"} @{" [B] Bi-Directional Transfer program " link "bidirprogram"} @{" [C] Uni-Directional Transfer protocol " link "unidirprotocol"} @{" [D] Display time in Lister " link "time"} @{" [E] Maintain filebase online " link "maintain"} @{" [F] List Display Routine " link "disprout"} defaults ; [A] LZX [B] Hydra [C] Z-Modem [D] No [E] No [F] By Row (nicer) All switches work on a toggle basis. If there are more than two options then a cycle is used. @ENDNODE @NODE markedfilebundling "Hydra MAX Enhanced Guide - User Preferences" Under Marked File Bundling there are currently two options, @{b} LZX@{ub} LZX is a very good compressor but requires about 600k of memory for it to work properly. Not yet available on the PC, but if you have the memory and you are an Amiga-Specific board, far better than LhA. @{b} LhA@{ub} LhA on the other hand is not as good at compressing by a long chalk but it will work in 400k or maybe less, and PC users can decompress it. Are there any calls for ZIP, Arc, or Warp...??? Thought not =) @ENDNODE @NODE bidirprogram "Hydra MAX Enhanced Guide - User Preferences" Two possible settings at the moment for Bi Directional transferring, and they are :- @{b} Hydra @{ub} uses HydraCom (needs MUI) and is sometimes unreliable, slow interface - has been known to crash but otherwise good. Nice looking but unfortunately not up to much underneath on low end machines. Avg 1550cps each way at 14k4. @{b} S-Modem @{ub} uses it's own program, no MUI required, very fast both ways, but sometimes can generate countless errors when trying to transfer both ways. See if your modem likes it, it doesn't like mine. Better than Hydra on low end machines. Claims a 99.5% efficiency rate. This is a good protocol to use even for one way transfers when you are sending long files as it's faster than Z-Modem! Avg 1720cps each way at 14k4. @ENDNODE @NODE unidirprotocol "Hydra MAX Enhanced Guide - User Preferences" XPR protocols are possible by using the xpr libraries. If you want any other XPR lib included so it can be used, drop me a line and I'll put it in. These are the only ones I use often... Three possible options for normal Uni Direction transfers, being - @{b} Z-Modem @{ub} Standard protocol, in use by virtually every BBS. Requires the xprzmodem.library file in LIBS: to work. Avg 1690cps at 14k4. @{b} Super Z-Modem @{ub} As above but uses blocks of up to 8k (8192b) in size thus theoretically giving a speed increase.. In practice it's unnoticable, but I use it anyway =) Requires the xprszmodem.library in LIBS: ... Avg 1690cps at 14k4. @{b} Y-Modem @{ub} Not quite as defunct as some people like to make out, Y-Modem can still give Z-Modem a fair run for it's money, especially on uncompressed files, getting 5000cps easily at 14k4. Requires xprymodem.library in LIBS: .. Normal use on compressed files averages 1650cps at 14k4. I am not permitted to include any of the above mentioned library files in the archive for some copyright reason or other (well no-one else does so I thought I'd just stay safe) but they are freely available from just about EVERYWHERE. You've probably already got them. @ENDNODE @NODE time "Hydra MAX Enhanced Guide - User Preferences" Simply determines whether the time will be displayed in the lister for that user.. If yes it looks better but is much slower, if no operation is faster. @ENDNODE @NODE maintain "Hydra MAX Enhanced Guide - User Preferences" If this switch is on the executable LogOffNoOut will be run after each upload to keep the filebase up to date for Hydra-MAX. It may take a few minutes with a large filebase - be careful.. The default is off. @{b} This is not implemented yet! I have run into problems with it =(@{ub} @ENDNODE @NODE disprout "Hydra MAX Enhanced Guide - User Preferences" This switch toggles listing between : @{b} By Row (nicer) @{ub} Shows each line at a time, first doing Name, Size, Star if marked, then Description. The problem with doing it this way is that the pen has to be changed colour very often, slowing output down especially on slow 2400 modems. However this mode does not make mistakes and leave stray bits of description like the alternative could do.. @{b} By Column (faster) @{ub} This method first displays all the filenames, then all the filesizes, then stars, then descriptions. This way the pen only needs to be changed at the end of each column, when going onto the new colour for the next type of data. Theoretically this mode should be faster, and it will be noticeable on 2400 systems more than anything else. Another way to speed up the program generally is to turn off the Time Display. If you have lots of memory, put all executables in RAM: and add RAM: to your CLI search path. @ENDNODE @NODE regging "Hydra Implementation for MAX - Registration" This program is Shareware. It is usuable without registering, but a registered version has many more benefits and functions etc. You also get support and boy are you gonna need it =) Things disabled in the evaluation version : You can't set the Access levels for Downloading/Uploading/Listing There is a 10 second delay before Hydra/SModem transfers start Registration is 10ukp by (International) Money Order or cash (I take no responsibility for lost notes) in UKP only - cheques in UKP are also accepted. Alternatively if you have written any programs I may consider a keyfile for that a good exchange, depending on what it is. Crashmail me 2:250/345 for more details.10:102/0 or 10:102/1 is my MaxsNet_II address. Crashmails only please, no routed netmail. Crashmail between 10pm - 6am UK time. OR the best way of contacting me is via celsworth@borghome.demon.co.uk No responsibility will be accepted for lost routed netmail - it sucks. I can then send a very small keyfile via Internet E-Mail.. @ENDNODE @NODE bugs "Hydra Implementation for MAX - Bugs?" Now I get to slag off my own creation =) Shouldn't be too hard actually, it is a PUBLIC BETA and BETA's do have bugs, right? So here goes... Bugs... ~~~~~~~ HydraComMUI 1.11 crashes a lot. Well it does on my A1200.. Try not to interfere with it - don't move windows around or add too many files quickly. Just chat and enjoy it.. HydraCom 1.00 is much more stable. Contact me for it.. Or any good BBS. SModem is stable enough, but if the user end is started first it'll run into trouble. Make sure the users know what they're doing! You cannot use Section 0 as a File Area for the simple reason that there is no line 0 in the Area.CFG =) I have alos developed the entire program around starting with Section 1, so .. Sorry. You only got 99 possible File Areas, not 100. @{b} Not a bug but not a very helpful `feature' - you must turn on the From: field for all your File Areas which you want to use, or they won't be recognised or used by H-MAX.@{ub} The contents of TempArc/ aren't deleted after use, so make sure you keep it clean yourself for now.. T'will be fixed. Filenames of less than 5 characters long throw up all sorts of problems. It shouldn't be a problem, since the suffixes are 4 chars themselves. Commas in filenames are simply out of the question - it'll f*ck up big time. Commas in descriptions are also a problem when scanning them for string matches. Spaces in search strings are not a good idea. It won't work 100% if there are spaces, probably. After an upload, only the file which has just been uploaded will be displayed in the corresponding area until LogOff or LogOffNoOut has been run.. I'm working on this one. There are hundreds of problems with the new lister - please report them, I need to get rid of them. @{b}Known probs with the lister@{ub} : Searching for text in files is dodgy. I know this so don't report it please... @{b} The chances are, the first time you run the door with the Enhanced mode enabled, it will crash at some point. You're lucky if it makes it through the initial setup, believe me. Always turn up the logging to level 5 and check the log after each crash. It will normally have some help in which can assist you. Don't give up - it does work - it's just a pain in the arse to get going ;)@{ub} Ensure you have ALL the text files, and ALL the config files. Check you have the BBS:Doors/Hydra/Users dir and the BBS:TempArc/ dir. Copy all the executables into C: again. Whether you have them or not. If problems persist, contact me. This is a great door once it's working. No other KNOWN bugs which I can't deal with.. There will be some though! @ENDNODE @NODE future "Hydra Implementation for MAX - Future Development" Things I'm planning for future versions :- Re-writing the entire thing in AmigaE for release 3 if I know enough E by then =) File Searching IN archives. Be slow probably though =( More filetypes to be added to File_ID.DIZ extracting and archive viewing/entering, send me archives and the decompressor to do it.. Possibly a Send.BAT which is similar to Rec.BAT but loaded upon XPR downloads? Anyone want one? Or is the default using XPRD ok? Getting rid of TempArc/ etc and just using one tempdir.. easy to do but tedious. @ENDNODE @NODE changes "Hydra Implementation for MAX - Changes!" Changes as from v2.00 (2/8 13:00) @{b}Third Aminet Release@{ub} ~~~~~~~~~~~~~~~~~~~~~ o Whopping great re-write - the door is now called Hydra MAX Enhanced It can be made to emulate the old door, but please check out the enhanced side, it's cool! MANY changes came about with this re-write. Here are some of them.. o Improved the routine which gets the filesizes in the table selector. o Twitting works now, properly! o [U]ser Options from the Select-By-Name method has gone, it was useless and I didn't want it anymore, edit your SelectFiles to reflect this and delete OptionScreen, both in Display/ ... o The TEMP directory is now checked and if it doesn't exist, T: is used. o Some keywords have a reverse - NO which turns them off, so you don't have to rely on defaults which might change. o Sanity check added to skip directories which definitely didn't have the requested off-line file in, using Exist(). o All external executables can now be put where you like. Hydra-MAX searches the command path to find them. To check that they can be found, go into a Shell and type @{b} CD RAM: @{ub} And provided the program isn't in RAM: the search path will be called. To add more paths to the search path, type @{b} path add@{ub} Or alter the line in your startup-sequence to contain the path of the files. If you don't know what I'm on about here, just dump all the external files in C: and it'll work =) o New config keywords related to the Enhanced side of the door. See the config section. ALLOWLZX and DISPTIME are two which spring to mind. o New version of SModem included - rev 3, has lower CPU usage and various bugfixes. o New config file - Area.CFG - required to run the Enhanced door. o @{b}MANY new text files : See guide.@{ub} Changes as from v1.42 (29/3 14:40) ~~~~~~~~~~~~~~~~~~~~~ o Crashed if no files were present in upload directory. Stupid me.. It tried to process the non-existant file! Sorted. o Discovered it runs fine on most systems accepting Paragon doors.. It's a bit strange. Give it a go.. It works alright on my TransAmiga Paragon Interpreter. You'll need to juggle the files a bit to make sure that everything can be found. Make BBS:Doors/Hydra etc. You'll need a MAXSBBS.Config and File.data plus File.Index too. Ok, so maybe it's not such a good idea after all then. But it does work. Changes as from v1.41 (24/3 12:20) ~~~~~~~~~~~~~~~~~~~~~ o FILE keyword removed. You now need a @{"Files.CFG" link "filecfg"} so make one and just type RAM: onto one line, and leave several blank ones after it. o Space removed from beginning of filename in the Files Editor of MAX. Changes as from v1.40 (23/3 19:40) ~~~~~~~~~~~~~~~~~~~~~ o SModem support added. Enabled by use of new keyword EXTERNAL ..ie @{b}EXTERNAL SMODEM@{ub} Changes as from v1.32 (21/3 15:20) ~~~~~~~~~~~~~~~~~~~~~ o LOGLEVEL keyword added. Allows you to alter the level of logging a bit. o Lower case config keywords will work now. o The defaults are set correctly when the Hydra.CFG file doesn't exist, previously they were set, but only if the file existed! So you could make a blank file and all would be well. Now you don't need one if the defaults suit you. Changes as from v1.31 (20/3 21:50) ~~~~~~~~~~~~~~~~~~~~~ o If the user didn't download any files, they didn't get a chance to upload any. They do now, see new text file `WantToUpload' o Added primitive logging. There are no options to turn it up, down or even off yet. It may help you to find out why it keeps quitting itself at one point as it notes when any file is missing. Changes as from v1.30 (19/3 18:20) ~~~~~~~~~~~~~~~~~~~~~ o Uploads now dealt with - they are added to the filebase under Section 20 by default, changeable in the config. Also they are deleted from the temporary directory and put in the Main Path as in MAX. o New text file - DescribeFiles. Shown when entering descriptions for the uploads. o New config keywords : TEMP - what temporary directory to use, default BBS:Temp_Receive/ FORCEUPLOAD - what MAX Section to put uploads in. o Lots of optimizing - lots of rewriting. Changes as from v1.24 (15/3 14:50) ~~~~~~~~~~~~~~~~~~~~~ o Added an advert for myself at startup, also shows the version number more clearly as it's a bit obscure on the final screen. o @{b}Access checking is now in there.@{ub} If the users access is too high or too low then the program acts as if the file isn't there. It also displays a line of information on the local screen showing : Section of file in question Lo-Access of this section Hi-Access of this section User's Access. You can determine from this whether a file is actually missing or the user doesn't have enough access when a situation occurs where the program won't mark a file. If the file is there and the user has the access, you've found a bug - please report it, giving all relevant information. @{b}This was removed very quickly as it looks terrible =(@{ub} o Hit the 100k barrier =) Changes as from v1.23 (9/3 02:05) @{b}Second Aminet Release@{ub} ~~~~~~~~~~~~~~~~~~~~~ o v1.22 slightly corrected. Works perfectly as far as I can see, as v1.22 should have done. v1.22 didn't know the path to find the files selected from the File.Data - does now. Changes as from v1.22 (5/3 17:00) ~~~~~~~~~~~~~~~~~~~~~ o An hour later... =) I added a feature which allows you to type in as many filenames as you want, which might not be in the BBS, but can be in any path you specify. Still being developed. Just type the filename which should be available in the path given by FILE and it will be marked. Not beta tested YET. Changes as from v1.21b (5/3 16:00) @{i}Unreleased@{ui} ~~~~~~~~~~~~~~~~~~~~~~ o Put in a revised File-Search routine - now returns much more info, but none of it is used yet. There will soon be a List Files option in the File Selecting stage.. possibly in v1.3 o v1.21 complained that it had no file path if you didn't give it one in the config even though it didn't use it. You could get round it by giving it any path.. but it's fixed now. Sorry.. Silly mistake. That would be the one on Aminet as well wouldn't it? Changes as from v1.21 (4/3 21:00) @{i}First Aminet Release...@{ui} ~~~~~~~~~~~~~~~~~~~~~ o Stupid bug fixed in the merging of the new routine and my program - it allowed any files to be selected whether they existed or not. Not any more. Reported by the routine programmer, (3/3 23:35) o Revised File-Search routine which goes part-way to putting in a lister when selecting files.. I still need the File Area though. Changes as from v1.2 (3/3 21:00) ~~~~~~~~~~~~~~~~~~~~ o The FILE keyword is now ignored. Instead of checking a given path, the public door now scans the File.data created by MAX. o ... and it follows that the FILES.CFG file will not be used either in v1.2 at least. o Previous versions had a noticable delay when using filebases of more than 500 files. Noticable being 2 minutes.. Ahem. Fixed thanks to a new routine by Karl Naylor. Changes as from v1.12 (1/3 22:00) ~~~~~~~~~~~~~~~~~~~~~ o The config keyword `PATH' has been replaced by `FILE' ... PATH was too general since I'm going to introduce more paths soon. Check your config and change it! o If no `FILE' keyword is specified in the config, it looks for another config file, named `FILES.CFG' - see the @{"FILES.CFG section" link "filecfg"} o The `Time' column is now correctly aligned when times of over 10 mins are displayed. Previously the colon was pushed over by the extra digit. o Six figure file sizes had a leading comma! Not any more.. Changes as from v1.11 (29/2/96 21:00) @{i}First Release@{ui} ~~~~~~~~~~~~~~~~~~~~~ o Bugfixes - first release. v1.00 to v1.10 were given only to one BBS. @ENDNODE @NODE legal "Hydra Implementation for MAX - Legalities & Author" This archive as it stands without the registered version of HYDRA_ENHN, is freely distributable. Upload it anywhere you can! THE UNREGISTERED VERSION IS PROVIDED `AS-IS' AND NO WARRANTY IS GIVEN OF ANY KIND TO UNREGISTERED USERS. USE THE PROGRAM AT YOUR OWN RISK. THE PROGRAM IS COPYRIGHT C.ELSWORTH - HE DOES WANT TO KNOW IF IT TRASHED YOUR FILE.DATA AND WHY BUT HE ACCEPTS NO RESPONSIBILTY FOR IT. @{b}Make a BACKUP of your FILE.DATA if you feel unsecure at all now =)@{ub} If you register, you are NOT permitted to spread the registered version. Doing so violates copyright law. SUPPORT WILL BE PROVIDED TO REGISTERED USERS AS A PRIORITY. The software is provided `as-is' and the author takes no responsibility for any damage caused with it, by misuse or otherwise. Use it at your own risk! However I am quite sure it won't do anything wrong - I tested it for hours on my private local line. It has also been tested remotely at several BBS'es. It worked safely at the time of release. I won't say it worked 100% because it didn't, but it worked safely. It didn't bomb out, or log me off, or anything. Sometimes it did throw up an error and return me to the BBS, but who cares.. Just run it again. @{b}If you don't like it, don't use it.@{ub} To help prevent piracy, as from v1.30 the registered user's name will be hard-coded into the executable and is displayed while the program loads. If I see any bogus copies I will take action against the people involved. The startup delay is NOT intentional - it is NECESSARY for the program to parse it's config and set up. @{i}Suggestions are welcome to me, at any address below.@{ui} This software is @{b} © @{ub} Chris Elsworth, 1996 That means it's @{b}COPYRIGHT@{ub} (for idiots). Law forbids you to dissect it! Chris Elsworth ( 2 Aug 1996) celsworth@borghome.demon.co.uk @{b}AmigaShack @{i}MAIL@{ui} System @{ub}: 01937 835141 after 10pm Online to take points in all the below nets and nodes in Borgnet and MAXSNet 2! @{b} Free FAST internet address given to ALL points. 5Hr delay MAXIMUM. @{ub} Running DayDream 1.21 & TrapDoor 1.85 @{b}PROUD@{ub} to be the North Yorkshire Hub for @{i}Borgnet @{ui} and @{i}MAXSNet_II @{ui} Fidonet : 2:250/345 Borgnet : 989:3/1 UFO/BBS : 405:100/553 MAXs_II : 10:102/1 ArcLNet : 12:2/1 I'd also like to credit my best modem mate.. He's put loads of time in for some of the routines in this program.. Cheers Karl! Call him.. @{b}Iso's Amiga BBS@{ub} (01132 636973) after 9pm @{i}Fidonet@{ui} 2:250/345.1 @{i}Borgnet@{ui} 989:3/2 @ENDNODE All MY executables and this guide © Chris Elsworth, 1996! All the File_ID.diz extractors, LZX, LhA, SModem and Hydra don't belong to me or anything. Sorry if I'm breaking anyone's rules by including them, but I saved lots of people some hassle didn't I? Contact me if you really have lots of qualms and are creating earthquakes in your region because I included your program and I'll drop support for it just for you. ; end