SFSEC v3.11 from MetaSys Page 1 --------------------------------------------------------------------- OVERVIEW -------- In short, SFSEC is a door that will allow a sysop to "reserve" a file for a given caller (or callers). For example, let's say a caller would like to download a copy of your AUTOEXEC.BAT. You wouldn't want to give this to the general public, but you would like to give it only to them for download. Another use would be for those large files that callers can request. You don't want the file to stay on disk, but if a subscriber asks for it, you may want to let only them download it and you may want to automatically delete it after the download to free up your valuable disk space. SFSEC will automatically manage your files and will optionally delete them after your caller has successfully downloaded the file. If the caller never calls back, SFSEC will wait "x" days and then delete the file freeing up your disk space. This is also optional and sysop configurable. SFSEC will also display an ASCII file to a caller (like showing them a message). You could accomplish this with Spitfire, but SFSEC simply "reads and displays" an ASCII file off of your disk. You can have 100 callers all read the same file. Once the caller reads it, they can even request to download it (as if it was a Private File). All of these features support multi-node operation. SFSEC has successfully been run on a 3 node system, under Lantastic, under Desqview and on a single node system. SFSEC supports Xmodem, Ymodem, Ymodem Batch and Zmodem for file transfers. SFSEC also use Z_IO routines, making it's I/O operations extremely fast under a variety of circumstances. SFSEC has been successfully run at 2400 baud as well as locked at 38400. SFADD ----- SFADD controls who can get to what file(s). It is used to maintain the .DAT file used by the SFSEC door. There is a separate doc file called SFADD.TXT which explains how to use that program. It also use Z_IO routines. SFADD is how you add and maintain records for the door SFSEC. SFSEC v3.11 from MetaSys Page 2 --------------------------------------------------------------------- SFSEC INSTALLATION ------------------ Installing SFSEC is fairly simple. The following steps will work for both single and multi-node systems. 1. Create a directory (anywhere) which will be used for SFSEC. If you already have SFSFSEC or SFSFCOM, you can use that directory. 2. Decide where you want to run the SFSEC door from. It is designed to be run from both the SFLOGON file and from the files menu (or extension menus). It can be run as a door. After you decided where you want to run it, edit the file with any ASCII editor. AS an example, let's say you will be running it from the SFLOGON.BAT file. The following lines would be added to the SFLOGON.BAT: a. COPY SFDOORS.DAT C:\SF\SFSEC b. C: c. CD \SF\SFSEC d. SFSEC /LOG=C:\SF\CALLERS.TMP Line a. above copies the SFDOORS.DAT file to the SFSEC directory. If you are running this from the file menu, you would copy SFFILE.DAT. Replace C:\SF\SFSEC with whatever directory you are installing SFSEC into. Lines b. & c. above will change the current drive and directory to the drive and directory containing SFSEC. You should change these lines so that you are moving to the directory containing SFSEC. Finally, line d. runs the program SFSEC. The /LOG parameter points to the SPITFIRE directory containing the SFNODE.DAT file. This way the log will automatically get updated by SFSEC as callers use it. 3. That's all there is too it. COMMAND LINE PARAMETERS ----------------------- /LOG= Specify the location of the callers.tmp file. If you have installed Spitfire in the D:\SF directory (this is where your .MNU and SFNODE.DAT files are) then /LOG=D:\SF\CALLERS.TMP is recommended. SFSEC v3.11 from MetaSys Page 3 --------------------------------------------------------------------- /seclevel Normally, when a caller uses this door, any time used to download a file is subtracted from his logon time. For example, if a callers calls and has 30 minutes of time left, and he spends 25 minutes downloading data from SFSEC, he now only has 5 minutes left. If you specify a security level on the command line (e.g. /100 for security level 100), then callers with that security level will have their download time restored. So if they entered the door with 30 minutes left and they downloaded a file for 25 minutes, they will still have 30 minutes left. You can specify as many security levels as needed. /UPDATE_DL This parameter will update the callers stats for downloaded files. For every file downloaded, his "files downloaded" will be incremented as will the kdownloaded. /MAXDAYS This parameter specifies when to automatically delete records from the SFSEC file. For example, if you have added a file for a caller to download, and he never calls back, the record and file will be removed after "maxdays". Simply specify /maxdays=30 (for example for 30 days). You can use any number of days here. This will apply to all files that do not have an AUTODELETE date specified by SFADD. If when SFADDing a file, you specified an auto-delete day parameter, then this parameter is ignored. /MSGMAXDAYS This parameter is identical as MAXDAYS. The difference is that MAXDAYS only applies to binary files for download. MSGMAXDAYS applies to ASCII files (messages). /IGNORE_EVENTS This parameter will ignore ON Time events. If you don't have this parameter on the command line, and a caller attempts to download files, and the download would interfere with a system event that MUST run on time, then the door will tell the caller that they cannot download those file(s) now. He can try to download a smaller file or not a batch (if he was trying a batch)... The point is, the door won't interfere with the Event. However, if you specify /IGNORE_EVENTS, then the door will always let them download the file. SFSEC.CFG SFSEC v3.11 from MetaSys Page 4 --------------------------------------------------------------------- ---------- Instead of placing all of these command line options on the command line in the .BAT file, you may specify these commands in a file called SFSEC.CFG. Simply create this file in your SFSEC directory. Use an ASCII editor and list any parameters in this file. You may list all parameters on a single line or list individual parameters on separate lines. For example, the following is a sample .CFG file: /update_dl /100 /200 /maxdays=30 The above lines in a CFG file will update the callers statistics, restore their logon time so any time in SFSEC does not count against them, and will drop all records older then 30 days. If the files with those records are marked for Delete, then they will also be deleted. You should not specify the /LOG parameter in this file. That should be specified on the command line in the .BAT file. SFSEC.LOG --------- Anytime you add, delete or edit a record, or a caller downloads or removes a record, a notation is made in the SFSEC.LOG file. It will also show all records that are automatically deleted. This will give you a trace of how long it has been since a caller got an upgrade (for example) and how long after you added it did they actually download it (if at all). SFSEC.DAT --------- This file is the database of callers and files. It is maintained and updated by SFADD.EXE and SFSEC.EXE. You should not attempt to edit this file. It is no longer ASCII as it was in SFSFCOM and SFSFSEC. SFSEC v3.11 from MetaSys Page 5 --------------------------------------------------------------------- SUPPORT ------- If you have any questions or need assistance, please don't hesitate to call us on the Mainframe at 708-223-2344. Registration is $20 for a full registration entitling you to free upgrades. $10 will get you a single copy of the door. You will not be entitled to future upgrades for free, unless the upgrade is to fix a bug. To register, send $10 for no-upgrades or $20 for free upgrades to: MetaSys PO Box 1387 Arlington Hts, IL 60030 You must send US Currency. Checks should be made out to Bob Zimmerman or MetaSys. Once your registration is received, your registered software will be available for download from the Mainframe. If you prefer to have your software mailed to you, you should add $5 for 5¬" disks and $7.50 for 3«" disks. When registering any software, you should: 1. Your BBS Name 2. Your BBS Phone and Max Baud 3. Your Voice Phone 4. Your Sysop Name. You must supply the "exact" spelling of your sysop name. This is found by typing option T off your Main Menu. There will be a single line saying: Your Sysop is... I need this spelling exact (upper and lower case). 5. Your mailing address 6. The name of the product you are registering. Thanks for supporting shareware! Your registration encourages me to continue improving this program and providing quality shareware. SFSEC v3.11 from MetaSys Page 6 --------------------------------------------------------------------- HISTORY ------- v3.11 Well, our first bug in SFSEC was found , if you have an ontime event scheduled, but not in the next 48 hours, SFSEC would consider the event to starting in less then a minute. It gave you a message about "unable to download file, event starting in -1 minutes". I have fixed this problem.