Monster Media 1994 #1

home *** CD-ROM | disk | FTP | other *** search

/ Monster Media 1994 #1 / monster.zip / monster / SPITFIRE / SFROM13G.ZIP / SFROM.DOC < prev next >

Wrap

Text File | 1994-02-02 | 81KB | 1,657 lines

SF-ROM DOOR Version 1.30 Released Jan 31, 1994 Copyright 1992-1994 by Mike Robinson The Soft Parade Shelton, Connecticut, USA 1:141/485 203-924-5603 1:141/486 203-922-1794 Fast Online registration using Visa or Mastercard SF-ROM is a file download door designed for Spitfire 3.x BBS. Files may be located on CD-ROM disk or magnetic disk. Features include: up to 100 disks, up to 500 file areas per disk, maintains it's own user/download database, requests from offline disks, full multi-node and network support, batch downloads from within the door, file tagging, fast text search single or all disks, ZIP and text file viewer, insertion of BBS ads into ZIP files, multi-disk changer support, automatic request manager/editor program, user manager/editor program, configurable user limits, chat mode, local drop to DOS, and multitasker aware. Can be run in local copy-to-hardrive mode in the BBS or from the DOS command line. A plain ASCII text file list is used for each file area. These lists are often supplied on the CD-ROM disk and can be used with little or no modification. Special compiled file lists are NOT required. SF-ROM automatically supports multi-line file descriptions and it works especially well with Spitfire and Night Owl format multi-line lists. Optional formatting commands can be used to change the display position on each line of the filename, size, date, and description. Configurable display color too. SF-ROM is unique among CD-ROM doors because it maintains it's own separate DATABASE to record caller download information and limit the number of files/bytes downloaded and requested. It also records files/bytes downloaded in SFFILE.DAT (or equivalent) which is read back by Spitfire and recorded in the main Spitfire database. SF-ROM can also serve as a very configurable menu extension. From the same main menu a caller can choose from a selection of CD-ROM disks, magnetic disk file areas, and external doors. These may be used in any combination. When an external door is chosen, SF-ROM exits with an ErrorLevel which is then used in a batch file to pass control to the selected external door. There is special support designed in for multiple nodes and/or multiple CD-ROM drives such as the Pioneer DRM series disk changers. SF-ROM acts as a traffic cop to control access, avoid collisions, and prevent "thrashing" that can sometimes occur when multiple users try to access the same drive. Considerable time and energy was spent working around the speed limitations of today's CD-ROM drives. Actual CD-ROM drive hardware access time has been minimized by: 1. Maintaining the file lists on the magnetic drive. This is optional. If the CD-ROM itself contains file lists, these can be be accessed directly by the door in order to save hard drive space. The same file lists may be shared by all nodes. 2. Copying the file to a holding directory on the hard drive and downloading it from there. This is also optional. You can configure the door to download directly from the CD-ROM drive. 3. Careful design of the the door logic. The CD-ROM drive hardware is accessed as rapidly as possible and only when absolutely required. FEATURES LIST: ■ Up to 100 disks. Up to 500 file areas per disk. ■ File Tagging while listing and while searching. ■ Fast text search of a file area, a whole disk, or all disks. ■ Online ZIP file and text file viewer. ■ Number of files/bytes downloaded is recorded in the Spitfire main database and daily download limits are enforced. Reads DAILYLMT.DAT to determine allowable download files/bytes per day. (registered version) ■ Maintains it's own user/download database file that tracks daily downloads and requests. (registered version) Configurable limits based on security level, files, bytes, ratios. Includes EZ-User - Database Manager/Editor program. ■ Requests from offline disks. (registered version) Includes EZ-Request - Automatic Request Manager/Editor program. This program prompts the sysop to insert a disk into the drive, and then copies all pending requests for that disk before prompting for the next disk. Caller receives a message when entering the door if requested files are ready for download. If successfully downloaded, the files are deleted when the caller exits the door. If the caller does not download the files, they are held for a configurable number of days and then deleted. ■ Inserts BBS advertisements into ZIP files. (registered version) Uses optional batch file execution before and/or after download. ■ Special support for Multi-disk changers designed with the Pioneer DRM series in mind. I run a Pioneer DRM-600 on my multi-node BBS, so I know from experience that it works well. ■ Batch downloads from within door using Xmodem, Ymodem or Zmodem. A copy of DSZ.COM or DSZ.EXE by Omen Technology Incorporated must be in the current directory or on the DOS path. The correct parameters are automatically passed to DSZ based on whether the caller has chosen X, Y, or Zmodem. Non-standard ports, crash recovery, and Zmodem MobyTurbo are supported. ■ File sharing and locking for multinode and network operation. All file lists, menus, data files and logs may be shared. ■ Multi-colored file lists just like seen in Spitfire 3.x. Supports Spitfire style multi-line descriptions (4 line) using the smiley face (ASCII 02) character. Can specify the character used in determining which lines in a file list contain a valid file for tagging and display purposes. File list display appearance and colors are configurable. ■ Run as a door or menu extension using SFDOORS.DAT, SFFILE.DAT, SFMESS.DAT or SFMAIN.DAT. Low memory requirements. ■ Communication port speeds to 115,200 bps with hardware or software flow control. Automatically reads the communication port hardware (UART) to determine port speed, data bits, stop bits and parity. Port number to use is read from SFFILE.DAT. IRQ number to use is read from SFNODE.DAT. Port number, IRQ number, IO base address, and interrupt vector can be set manually to handle non-standard ports. Handles any UART, including the 16550AFN. Does not require or use a FOSSIL driver, but is compatible with a FOSSIL if one is installed. ■ The door will recognize caller connect speeds from 0 to 230,400 bits per second. It will use the value passed by Spitfire in SFFILE.DAT line 5 to calculate the estimated download times. Note that sometimes this value is incorrect. Some modems connect at 12000, 14400, 16800, 19200, and more but "lie" and tell Spitfire that the connect is 9600 or some other value. The good news is that the door now factors in a speed increase due to error correction. ■ Multitasker aware. Releases time slices (clock tics) to tasks running in other windows when SF-ROM is idle. These multitaskers are automatically detected and supported: DESQview 2.xx, Windows 3.x & NT, DoubleDOS, VMiX 2.xx, MultiDos Plus 4.xx, OS/2 2.0, DOS 5/6 Task Switcher and Compatibles, TaskView, TopView, OmniView, & Compatibles. ■ DSZmodem is "trapped" inside a window so that data does not scroll up off screen as download progresses. ■ ANSI color or plain ASCII text modes. Initial mode is the same as passed by Spitfire. Caller can toggle ANSI on/off from within the door. Door contains its own ANSI driver and can show ANSI graphics on the local screen even if DOS ANSI.SYS is not loaded. ■ Sysops can design their own (optional) custom screens. Door will display WELCOME.CLR or WELCOME.BBS before it runs. (registered version) Place these in the same directory as SFROM.EXE. If ANSI is on then the .CLR file will be shown, otherwise the .BBS file will be shown. ■ Chat Mode ■ Local drop to DOS ■ Carrier detection. Resets the BBS if caller drops carrier. ■ Inactivity timeout configurable from 1 to 10 minutes. ■ Detailed status lines always visible on top of local screen. ■ Detailed status screen displayed during download. ■ Custom display screens. ■ Optional logoff after transfer. ■ Optional time penalty for dropped carrier. ■ Logging of all caller activities to any file. (registered version) ■ Sysop local keyboard controls same as Spitfire. SF-ROM is shareware with a $25 registration. See the end of this file or REGISTER.DOC for registration form and information. ----- SETUP for SINGLE-DISK MODE ---------------------------------------- 1. Unzip this archive into one subdirectory. This will be the SF-ROM home directory, which is named C:\CDROM in the following example, but any subdirectory name may be used. The files contained in MULTI.ZIP are NOT required for single-disk mode. 2. Modify the included SFROM.CFG file to meet your needs. See CONFIGURATION VERBS below for description of each option. Any line in SFROM.CFG that does not begin with a letter is ignored. The lines that begin with semicolons, for example, are used for comments and ignored by the program. Keep this file in the SF-ROM home directory. 3. Prepare an ASCII text file list for each subdirectory on the CD-ROM. These are often included on the CD-ROM and can usually be used with little or no modification. Keep the lists in the SF-ROM home directory or on the CD-ROM. The first line of each file entry in the list should be in the following format: ....+....1....+....2....+....3....+....4....+....5....+....6....+....7....+.. SFROM13.ZIP 110,330 01-31-94 SF-ROM v1.30, CD-ROM Door by Mike Robinson <---Name---><--Size--><-Date---><-------------Description-------------------> This is the standard Spitfire default single line format. The location and display color of each field can be changed by using the FileName, FileSize, FileDate, and FileDesc commands as described below in the Configuration Commands section. If Spitfire style multi-line descriptions (4 line) with smiley face (ASCII 02) character are used, the line may be up to 255 characters long and all on one line. The smiley face marks the separation between lines. Spitfire multi-line format will be automatically recognized by SF-ROM if there is at least one smiley face on the line. For other multi-line formats, (such as Night Owl) the description lines may lie on multiple lines between column 33 and 78 as shown: ....+....1....+....2....+....3....+....4....+....5....+....6....+....7....+.. <---Name---><--Size--><-Date---><-------------Description-------------------> SFROM13.ZIP 110,330 01-31-94 SF-ROM v1.30, CD-ROM Door by Mike Robinson. | CD-ROM File Download Door For Spitfire BBS. | CDROM or magnetic drive, Multi-disk, | Multi-node, Batch download, File tagging, | Text search, Logs downloads, | Enforces daily limits. <-------------Description-------------------> The character "|" is not required, although it is often included in Night Owl type lists. SF-ROM can be configured to not show this character by using the DelChar configuration command. Descriptive headers may be used at the top of each file list or at any point within the list. Any line which does not contain the tag character at the proper location is assumed to be a description line and is displayed without modification. See TAGCHAR in Configuration Commands section below. 4. Modify the included DISK.CLR and DISK.BBS to meet your needs. These two files are the list of file areas on the disk and are mandatory or the program will not run. Try to keep these to under 21 displayed lines or the top may scroll off the screen. Additional options for these files are described below. Keep these files in the SF-ROM home directory. 5. Make sure a copy of DSZ.COM or DSZ.EXE is somewhere on your DOS path or in the SF-ROM home directory. 6. Run the program online using these commands: CD C:\CDROM SFROM C:\SF\SFFILE.DAT C:\CDROM\SFROM.CFG Spitfire creates one of the following files when a door or menu extension is executed. Any one of these may be used in place of SFFILE.DAT in the above example: SFFILE.DAT File menu extension SFMAIN.DAT Main menu extension SFMESS.DAT Message menu extension SFDOORS.DAT Door menu ----- SETUP for MULTI-DISK MODE ----------------------------------------- 1. Unzip this archive into one subdirectory. This will be the SF-ROM home directory, which is named C:\CDROM in the following example, but any subdirectory name may be used. You only need one copy of SFROM.EXE and it must be kept here. Unzip the MULTI.ZIP file. 2. Modify the included SFROM.MAS file to meet your needs. (SFROM.MAS is contained in the MULTI.ZIP file.) See CONFIGURATION COMMANDS below for description of each option. This is the master file that sets the configuration and location for all of the disks. It "points" to all of the separate SFROM.CFG files used by each disk. Any line in SFROM.MAS that does not begin with a letter is ignored. The lines that begin with semicolons, for example, are used for comments and ignored by the program. Keep this file in the SF-ROM home directory. 3. Create a separate subdirectory for each of your CD-ROM disks. The general arrangement should look something like this: ┌──────────────┐ │ SFROM.EXE │ SF-ROM home directory │ SFROM.MAS │ │ MAIN.BBS/CLR │ └───────┬──────┘ │ ┌─────────────────┼─────────────────┬────── - - - etc. ┌──────┴───────┐ ┌──────┴───────┐ ┌──────┴───────┐ │ SFROM.CFG │ │ SFROM.CFG │ │ SFROM.CFG │ │ DISK.BBS/CLR │ │ DISK.BBS/CLR │ │ DISK.BBS/CLR │ │ FILELISTS │ │ FILELISTS │ │ FILELISTS │ └──────────────┘ └──────────────┘ └──────────────┘ subdirectory subdirectory subdirectory for disk 1 for disk 2 for disk 3 4. Copy SFROM.CFG to each of the disk subdirectories. This is the configuration file for that disk and must be modified to suit that disk. SFROM.CFG must contain the disk name and all the paths to the files and lists for that disk. This is all that MUST be included, any of the other settings are optional, but they will be applied if they are there. 5. Prepare an ASCII text file list for each subdirectory on each CD-ROM disk. These are often included on the CD-ROM and can usually be used with little or no modification. Keep the lists in the subdirectory for that disk or on the CD-ROM. See single disk mode section above for the file list format. 6. Copy DISK.BBS and DISK.CLR to each of the disk subdirectories. This is the display menu showing the file areas available on the disk and must be modified to suit the disk. Try to keep these to under 21 displayed lines or the top may scroll off the screen. Addition options for these files are described below. 7. Make sure a copy of DSZ.COM or DSZ.EXE is somewhere on your DOS path or in the SF-ROM home directory. 8. Run the program online using these commands: CD C:\CDROM SFROM C:\SF\SFFILE.DAT C:\CDROM\SFROM.MAS SF-ROM runs multi-disk mode if config file extension is .MAS. (Single-disk mode is selected by using extension .CFG) Spitfire creates one of the following files when a door or menu extension is executed. Any one of these may be used in place of SFFILE.DAT in the above example: SFFILE.DAT File menu extension SFMAIN.DAT Main menu extension SFMESS.DAT Message menu extension SFDOORS.DAT Door menu ----- LOCAL MODE -------------------------------------------------------- SF-ROM may be run in local mode if you log onto the BBS locally. It may also be run in local mode from the DOS command line: CD C:\CDROM SFROM LOCAL If SFROM.MAS is found in the current directory, then multi-disk mode is selected. If SFROM.CFG is found, then single-disk mode is run. Local mode allows you to browse the lists, tag files, and copy the files (and descriptions) to the hard drive. ----- CONFIGURATION COMMANDS -------------------------------------------- The AREAS command must be used in SFROM.CFG for both single and multi-disk mode. If you use multi-disk mode, then the DISKS command must be used in SFROM.MAS. All other configuration commands are optional. Configuration commands are used in SFROM.CFG for both single-disk mode and multi-disk mode. The program reads each line and if it begins with a configuration command, then the configuration is modified as directed by the command. If a line begins with anything other than a letter, it is ignored. The explanatory comments are on lines beginning with a semicolon and are therefore ignored. The commands are NOT case sensitive, but they must be spelled correctly. The order of the lines is generally not important except for the DISKS and AREAS commands. For multi-disk mode, many of the same configuration commands are also used in SFROM.MAS. The configuration commands in SFROM.MAS are read into memory when the program starts. When a disk is selected by the caller, the SFROM.CFG file for that disk is read. When returning to the main menu from a disk menu, program startup values are restored from memory. Most of the configuration commands can be set in either (or both) the master SFROM.MAS or the disk specific SFROM.CFG. The values in the master prevail when the program is at the first menu. The values for each disk prevail whenever that disk is loaded or read. Some of the commands are only read once when the program starts and are so indicated below. AREAS E:\001A C:\CDROM\NIGHT10\DIR1 E:\002A C:\CDROM\NIGHT10\DIR2 E:\003A C:\CDROM\NIGHT10\DIR3 E:\004A C:\CDROM\NIGHT10\DIR4 E:\005A C:\CDROM\NIGHT10\DIR5 E:\006A C:\CDROM\NIGHT10\DIR6 E:\007A C:\CDROM\NIGHT10\DIR7 E:\008A C:\CDROM\NIGHT10\DIR8 AREAS Mandatory. The AREAS configuration command is mandatory for all modes. It is only used in SFROM.CFG, but it is used for both single-disk mode and multi-disk mode. It is used to signify both the beginning and end of a list of file areas. The example above shows 8 file areas, but you can have as many as 500 file areas per disk. There must be one file area per line. The first line is file area number 1 and the rest follow in order until you reach the end. The list MUST BEGIN and END with the keyword "AREAS". The list MUST BEGIN and END with the keyword "AREAS". Each line has two entries separated by at least one blank space. The first is the path to the file area on the CD-ROM. The second is the full path and filename of the associated file list. The list can have any filename. The file lists can be located on a normal magnetic hard disk or on the CD-ROM (if they exist on the CD-ROM). The door will run much faster if you locate the file lists on the normal magnetic hard disk. Note that you can also use this door to access normal file areas on your hard drive. You can mix normal file areas with CD-ROM areas in the same door. The file areas do not have to reside on the same drive letter or same physical drive. If you have a network, you can access file areas on a different machine. You could even put ALL of your BBS file areas in one or more of these doors. For example, you could put adult files in one door and restrict access to adults only. Or you could have special file doors reserved for privileged, contributing or subscribing callers. The example above is a portion of the sample SFROM.CFG supplied in this package. It is for the Night Owl 10 CD-ROM disk first published in 1993. The file lists are resident on the CD-ROM and can be easily copied to a hard drive. DISKS 1 ON >5 0 C:\CDROM\DISK1\SFROM.CFG 2 ON >5 0 C:\CDROM\DISK2\SFROM.CFG 3 REQ >5 0 C:\CDROM\DISK3\SFROM.CFG 4 REQ <20 0 C:\CDROM\DISK4\SFROM.CFG 5 OFF =30 0 C:\CDROM\DISK5\SFROM.CFG 6 OFF >5 0 C:\CDROM\DISK6\SFROM.CFG DISKS The DISKS configuration command is MANDATORY for multi-disk mode. It is only used in SFROM.MAS and is for multi-disk mode only. It is used to signify both the beginning and end of a list of disks. The example above shows 6 disks, but you can have as many as 100. There must be one disk per line. The list MUST BEGIN and END with the keyword "DISKS". The list MUST BEGIN and END with the keyword "DISKS". COLUMN 1 is the string of characters that the caller types to select the disk. Any string of up to 30 typeable characters may be used. No blanks or untypeable characters. Must be one continuous string. Do not use the single characters Q, S, or U since these are used to select options on the main menu. But you may use words of 2 or more characters that begin with Q, S, or U. The simplest method may be to use a number to indicate each disk as done in the example above. COLUMN 2 shows the disk or door status. ON means online. Downloads allowed. No requests. OFF means offline. Browse only. No downloads or requests allowed. REQ means requests allowed. No downloads. REQ is only available in the registered version. COLUMN 3 shows the security level required to enter the disk. For example if it is set to: >5 (only security levels greater than 5 may enter) <20 (only security levels less than 20 may enter) =30 (only security level equal to 30 may enter) There must be no spaces between the symbol and the level number. COLUMN 4 is the type. Set this to 0 for a CD-ROM disk. Set it any value between 10 and 255 and SF-ROM will terminate with this ErrorLevel when this door is selected by the caller. This allows SF-ROM to be used like an external menu program. In this case, you need to catch and respond to these ErrorLevels in the batch file that runs SF-ROM. CD-ROM disks and external doors may be combined freely in the same menu. A normal SF-ROM exit where no door or disk is selected is ErrorLevel 0. Internal errors in SF-ROM exit with ErrorLevel 1. Do not set ErrorLevels 1 to 9 as these are reserved for future use. COLUMN 5 is the full path and file name of the SFROM.CFG used for each CD-Rom disk. Create a separate subdirectory for each disk. Place all the files for that particular disk in the same subdirectory along with the SFROM.CFG for that disk. Column 5 is blank if this line indicates an external door. DISKNAME So Much Shareware 2 Optional. This command is only used in SFROM.CFG and has no effect in SFROM.MAS. This name is used in the local status bar display on the top of the screen and in the door log entries. Default is no name. COPYTOMAG ON COPYTOMAG OFF Optional. Choose one. If CopyToMag ON then files will be copied to the magnetic hard drive just before downloading. These files will then be erased once the download is completed. If CopyToMag OFF then the files will be downloaded directly from the CD-ROM drive. Default is CopyToMag ON. HOLDDIR C:\CDROM\HOLD Mandatory if CopyToMag ON. This is the holding directory where the files are copied to if CopyToMag is ON. The program also writes the batch download file list here in all cases. This list is named EXT1.LST where the 1 indicates the node number. The program takes care of its own housekeeping and deletes the copied files after the download. Just the copied files are deleted. Any other files that exist in this directory will NOT be deleted. In local mode, the files are also copied here and the descriptions are added to a FILES.BBS in this subdirectory. If no FILES.BBS exists, one is created. Default is the directory specified by HomeDir. If no HoldDir is specified and no HomeDir is specified, then the default is the current directory. FILEVIEW ON FILEVIEW OFF Optional. Choose one. Turns the file viewer ON or OFF. Some multi-node systems may want to turn FileView OFF since the CD-ROM drive must be read to view a file and this can create a lot of traffic. If the BusyFlag option is used (see below), then a busy flag is created when a file is viewed and all of the other BusyFlag control parameters apply. The busy flag is erased as soon as the caller returns from viewing the file. Note that this can tie up the drive for the entire time a caller is viewing the file. If busy flags are not used, then multiple nodes can simultaneously access the drive for both viewing and download purposes. If FileView is OFF, then the View option does not appear on the caller menu prompts. The file viewer will show the internal contents of a ZIP file if the file has an extension of .ZIP. Otherwise, the viewer looks at the file and if it seems to be a text file (no unprintable characters) then the viewer display the text file. The viewer cannot display text files within ZIP files (yet). If the viewer gets fooled and a .ZIP is not really a ZIP, or a text file is not really a text file, then the caller may see a bunch of harmless garbage characters. Default is FileView ON. SHARE ON SHARE OFF Optional. Choose one. Turns file sharing and locking ON or OFF. If you have more than 1 node, or you want to fill requests while a caller is online, then set Share ON. In order for file sharing and locking to work, you must use DOS 3.1 or higher and DOS SHARE.EXE must be loaded in your CONFIG.SYS or AUTOEXEC.BAT. If file sharing is not required, then set Share OFF. This program will run noticeably faster with Share OFF. Default is Share OFF. TIMEOUT 180 Optional. This is the caller inactivity timeout delay in SECONDS. If no keystrokes are received for this length of time, the door will exit and return the caller to the BBS. Timeout only applies when the door is run from the BBS. There will be no timeout when run from the DOS command line. Values from 60 to 600 seconds are allowed. Default is 180 seconds (3 minutes). DEBUG ON DEBUG OFF Optional. Choose one. Most program error conditions are logged to ERROR.LOG if Debug is turned on. The program may load a bit faster if you turn this off. If you are experiencing difficulties, leave Debug ON. Default is Debug ON. DROPPENALTY 300 Optional. Number of SECONDS to penalize the caller if carrier is dropped when in the door. This time will be subtracted from the callers time allowed during the next call that day. If the caller does not call back until the next day, then this penalty will have no effect. Values from 0 to 7200 seconds (0 to 120 minutes) are allowed. Default is 300 seconds (5 minutes). ALLOWLOGOFF ON ALLOWLOGOFF OFF Optional. If AllowLogOff ON then the caller will be offered the option to select unattended automatic logoff after each download. Default is AllowLogOff ON. LINESPERPAGE 22 Optional. Determines the number of lines shown for each screen page when the caller is scrolling through the file lists. Values from 5 to 30 lines per page are allowed. Default is 22 lines per page. TAGCHAR 26 - Optional. This determines the line position and character used to determine which lines in a file list contain a valid file for tagging and display purposes. Lines which contain this exact character at this exact position are colorized and assigned a tag letter. Lines which do NOT contain this character at this position are assumed to be header lines or extended description lines. This option allows the use off many different styles of file lists. Default is a dash at position 26 as shown below: ....+....1....+....2....+....3....+....4....+....5....+....6....+....7....+.. SFROM13.ZIP 110,330 01-31-94 SF-ROM v1.30, CD-ROM Door by Mike Robinson ^ character at position (column) 26 is a dash Examples of common file formats: TagChar 26 - (tag lines with a dash at position 26) (DEFAULT) (Typically used in Spitfire & Night Owl type lists) TagChar 28 - (tag lines with a dash at position 28) TagChar 26 / (tag lines with a forward slash at position 26) TagChar 28 / (tag lines with a forward slash at position 28) TagChar 18 , (tag lines with a comma at position 18 ) Only one character and position may be designated as the TagChar. If multiple TagChar are specified in SFROM.CFG then the last TagChar specified is used. For file tagging to work properly, the file name must be listed first on each line of the file list (column position 1 to 12). SF-ROM is smart enough to recognize the file name even if it is "fractured" and not continuous like in these examples: ....+....1....+....2....+....3....+....4....+....5....+....6....+....7....+.. FILE1 .ZIP 344,101 01-31-94 A good game FILE1. ZIP 344,101 01-31-94 A good game FILE1 ZIP 344,101 01-31-94 A good game The last example is typical of file lists that are created based on the DOS DIR command. DELCHAR 32 | This sets a line position and a single character that will stripped out from every line of a file list. "Night Owl" or "PCBoard" style multi-line file lists often have a | character at position 32. Use of this command causes the specified character to be replaced by a blank in the file list display. The file list itself is not modified. In the example shown, on all lines where character | is found in position 32, it will be replaced by a blank space. Only one character and position may be designated as the DelChar. If multiple DelChar are specified then only the last DelChar specified is used. Any character and any position from 1 to 78 may be used. The position is determined by the actual position on the line in the file before any display modifications are made by the FileName, FileSize, FileDate, FileDesc commands. The default is a | at position 32 as shown below: ....+....1....+....2....+....3....+....4....+....5....+....6....+....7....+.. SFROM13.ZIP 110,330 01-31-94 SF-ROM v1.30, CD-ROM Door by Mike Robinson | CD-ROM File Download Door For Spitfire BBS. | Multi-disk, Multi-node, Batch download, | File tagging, Text search, Logs downloads, | Enforces daily limits. ^ character at position (column) 32 is a | FILENAME 1 12 15 FILESIZE 13 10 14 FILEDATE 23 10 10 FILEDESC 33 46 11 Optional. These 4 configuration commands control how the file lists are displayed. For example: FILENAME 1 12 15 This means that the file name starts at line column position 1 and is 12 characters long. The 15 is the display color code. The default values are shown above and in this sample line: ....+....1....+....2....+....3....+....4....+....5....+....6....+....7....+.. SFROM13.ZIP 110,330 01-31-94 SF-ROM v1.30, CD-ROM Door by Mike Robinson <---Name---><--Size--><-Date---><-------------Description-------------------> The total number of characters displayed by all 4 zones should not exceed 78 or the line display may wrap onto the next line. Allowable color numbers are: 9 Light Blue 10 Light Green 11 Light Cyan 12 Light Red 13 Light Magenta 14 Yellow 15 White Default values are shown above. HEADLINE 1 78 11 Optional. This command works just like the four above, except it applies to the optional header section at the top of a file list. It means that 78 characters will be displayed, starting at character number 1 and the display color will be 11 (Light Cyan). The default values are shown above. NODOWNLOAD 10 15 20 Optional. This sets no download status for listed security levels. You may also use the word ALL in place of the listed levels and then all security levels will not be allowed to download. In the example shown above security levels 10, 15 and 20 are not allowed to download. Up to 20 levels can be set on one NoDownLoad line. Use as many lines as your require, each line beginning with NoDownLoad. If running multi-disk and this command is set in SFROM.MAS, then it applies to all disks. If set in SFROM.CFG then it applies to just one disk. The value in SFROM.CFG prevails. Default is downloads allowed. NOREQUEST 10 15 20 Optional. Registered versions only. This sets no request status for listed security levels. You may also use the word ALL in place of the listed levels and then all security levels will not be allowed to request files. In the example shown above security levels 10, 15 and 20 are not allowed to request files. Up to 20 levels can be set on one NoRequest line. Use as many lines as your require, each line beginning with NoRequest. If running multi-disk and this command is set in SFROM.MAS, then it applies to all disks. If set in SFROM.CFG then it applies to just one disk. The value in SFROM.CFG prevails. Default is requests allowed. CHECKSIZE ON CHECKSIZE OFF Optional. Choose one. For use in either multi-disk or single-disk mode. If ON, then the CD-ROM drive will be read during file tagging to determine if the file is actually there and it's size/date. If OFF, then the CD-ROM will not be read during file tagging, and the file size and date will be read from the file list. This will speed up the tagging operation and reduce the load on the CD-ROM drive on multi-node and networked systems. OFF should work well if your file lists have accurate file sizes and are in a format where the size is listed in columns 9 to 21 (default) or the position specified by the FileSize command. Note that if the file size in the list is wrong, a caller could exceed his daily byte or time limit. If set OFF and a file size cannot be read from the list, then a default size of 50 kilobytes is used. If this command is used in SFROM.MAS, then it applies to all disks. If used in SFROM.CFG, it applies to just one disk. Default is CheckSize ON. GRAPHICS ON GRAPHICS OFF Optional. SF-ROM will automatically read the graphics mode from SFFILE.DAT (or equivalent) line 10. This command overides the value passed in SFFILE.DAT. Graphics ON forces SF-ROM to start in ANSI graphics (Color) mode. Graphics OFF forces SF-ROM to start in ASCII graphics (B & W) mode. DLTIMER 30 Optional. This command is used in determining whether a download was successful. The default is 30. If a download takes more than 30 percent of the estimated download time, then it is assumed to be successful. Allowable range is from 1 to 255. Note that there is no decimal point or percent sign on the command line. Just the number 30 alone means 30 percent. Please consider that setting this too low will result in callers being "charged" for failed downloads. Setting it too high may allow some callers to download without being "charged". Default is 30. LISTDRIVE K Optional. Typically, this will only be used on a network where disk drive letters are reassigned. This command applies to both SFROM.MAS and SFROM.CFG. In SFROM.MAS it changes the drive letter of the path to each SFROM.CFG in the DISKS section. In SFROM.CFG it changes the drive letter of each file list in the AREAS section (right column). It does NOT alter the drive letter of the CD-ROM drive in the AREAS section. No matter what drive letter was actually specified, it is changed to the drive letter following the ListDrive command. Example: I run a 2 node BBS using an Artisoft LANtastic network. Node 1 is drive C. My SFROM.MAS file, all of my SFROM.CFG files, and all of my file lists are on node 1 drive C. In SFROM.MAS all of the paths in the DISKS section begin with the drive letter C. In each SFROM.CFG the path to each file list in the AREAS section begins with the drive letter C. When logged onto node 2, node 1 drive C is remapped to K. So I copied the exact same SFROM.MAS file from node 1 to node 2 and added just one line to it: ListDrive K. So both nodes share the same set of SFROM.CFG files and file lists. But each node has it's own SFROM.MAS file. The only difference between the 2 SFROM.MAS files is that node 2 contains the ListDrive K command. On my BBS, each of my CD-ROM drives uses the same drive letter on all nodes of my network. So CD-ROM drive N is CD-ROM drive N on all nodes. See CDDRIVE command if you need to remap CD-ROM drive letters. If the ListDrive command is used in SFROM.MAS then it will apply to SFROM.MAS and also to ALL of the SFROM.CFG files. If it is used in a SFROM.CFG file then it applies to just that one SFROM.CFG file. In general, I recommend that you only use this command in SFROM.MAS. CDDRIVE F Optional. Typically, this will only be used on a network where disk drive letters are reassigned. This command applies to SFROM.CFG only. It changes the drive letter of each CD-ROM drive directory in the AREAS section (left column). No matter what CD-ROM drive letter was actually specified, it is changed to the drive letter following the CDDrive command. Do NOT use this command in SFROM.MAS since it is would then apply to ALL of your CD-ROM disks and it is very unlikely that they all have the same drive letter. BUSYFLAG C:\CDROM\HOLD\DRIVE1.BSY Optional. For use in multi-disk mode. A semaphore marker file system of collision protection is set by this command. SF-ROM checks for the existence of this busy flag file before each CD-ROM read. If the file is there, then it waits until the other node erases the file. SF-ROM creates this file whenever it begins to read from the CD-ROM drive and erases this file when the read is complete. The same busy flag name must be set for each disk that uses the same drive. Default is no busy flag used. FLAGDELAY 30 Optional. For use in multi-disk mode. Sets the maximum time in seconds that the door will wait for a busy CD-ROM drive. In the example above, the door will wait for up to 30 seconds before halting the attempted disk read operation and sending a message of "please try again later." Allowable range is 0 to 300 seconds. Default is 30 seconds. DELOLDFLAG 30 Optional. For use in multi-disk mode. When SF-ROM encounters a busyflag, it checks it's age. If it is older than DELOLDFLAG in minutes, then the flag is deleted. Only the flag declared by the BusyFlag command in the same configuration file is deleted. This is a cleanup feature in case old flags are orphaned by a power failure or other system problem. The default is 30 minutes which means the door will delete any flag older than 30 minutes. The system clocks on a network must be synchronized in order for this command to work properly. It is recommended that you set this value to at least the maximum system time difference between any 2 network nodes. Remember that PC system clocks will drift out of synchronization over time. The allowable range is 5 to 720 minutes. Default is 30 minutes. HOMEDIR C:\CDROM Optional. This is the SF-ROM home directory. In registered versions, this is where the request data file SFROM.REQ and the caller database SFROM.DAT is created and kept. On multi-node systems, these files can (and should) be shared by all nodes if the same HomeDir is specified for all nodes. Default is the current directory. REQUESTDIR C:\CDROM\REQUEST Registered versions only. Mandatory if file requests from offline disks are allowed. This is the holding directory where the requested files are held after they are copied to the hard drive. The program takes care of its own housekeeping and deletes the requested files after the caller successfully downloads the files AND exits the door. So if the caller flubs the download, but SF-ROM thinks the download was a success, the files will remain in place until the caller exits SF-ROM. If SF-ROM thinks the download failed, the files will not be deleted. Just the downloaded files are deleted. Any other files that exist in this directory will NOT be deleted. If more than one caller has requested the same file, the file will not be deleted until all callers have downloaded the file. Default is the directory specified by HoldDir. If no RequestDir is specified and no HoldDir is is specified, then the default is the current directory. DATABASE INTERNAL DATABASE DOORDROPFILE DATABASE COMBINED Optional. Registered versions only. Choose one. Spitfire BBS should use the default of DoorDropFile. The other options are offered should someone want to run SF-ROM on another type of BBS. Registered versions of SF-ROM keep a separate database of files/bytes requested and downloaded in the door in the SFROM.DAT file. This is fully automatic and cannot be changed. This command determines how this information is used to limit the number of files/bytes downloaded per day: INTERNAL ....... Only the data in SFROM.DAT is used. DOORDROPFILE ... The number of files/bytes downloaded today is read from SFFILE.DAT (or equivalent). The number files/bytes requested today is read from SFROM.DAT since SFFILE.DAT does not track requests. COMBINED ....... The number of files/bytes downloaded today read from SFFILE.DAT is added to the number of files/bytes downloaded today read from SFROM.DAT. The number of files/bytes requested today is still read from SFROM.DAT only since SFFILE.DAT does not track requests. Don't use this option with Spitfire. The default is DATABASE DOORDROPFILE which work very well with Spitfire BBS. For other BBS types, the best choice is probably DATABASE INTERNAL. The reason for this is that most BBS types do not read back SFFILE.DAT. So even though SF-ROM updates the number of files/bytes downloaded in SFFILE.DAT, this information is not saved by the BBS. The caller can re-enter the door several times and download several times his daily limit. The solution is to set DATABASE INTERNAL so the downloads today information is read from SFROM.DAT and the proper limits will be enforced. The DATABASE COMBINED command should be used if you want the number of files/bytes downloaded today to be calculated as the SUM of the values in SFFILE.DAT and SFROM.DAT. In this case, if the caller was allowed 10 downloads per day in SF-ROM, but had already downloaded 6 files in the BBS, then the caller would only be allowed 4 more files in SF-ROM. If your BBS does not pass the correct number of files/bytes downloaded in SFFILE.DAT then you should use DATABASE INTERNAL if you want to accurately track and limit daily downloads. KEEPUSERDAYS 90 Optional. Registered versions only. This is the number of days a user's information is retained in the internal database file SFROM.DAT. If the user does not call again after this number of days, the user info is not erased, but the record space will be made available for use by another caller. When a new caller exits SF-ROM, the first available record which is either old or flagged for delete will be overwritten. If no records are older than KeepUserDays or flagged for delete, then a new record is added to the end of the file. This maintenance of the database is automatic and occurs every time a caller enters SF-ROM. The size of SFROM.DAT will never decrease, but will stabilize at some value where the daily number of new callers roughly equals the number of callers who have not called back within KeepUserDays. Default is 90 days. KEEPREQDAYS 30 Optional. Registered versions only. This is the number of days a file request is retained in the request database file SFROM.REQ. If the caller does not download the file within KeepReqDays then the file will be deleted and the request record will be marked DONE. This maintenance is automatic and occurs every time a caller exits SF-ROM. The next time a file is requested, the first available record marked DONE will be used to record the request. If no records are marked DONE, then a new record will be added to the end of the file. The size of SFROM.REQ will never decrease, but will stabilize at some value where the daily number of new requests roughly equals the number of DONE requests. Default is 30 days. LIMIT 10 12 2000 Optional. Registered versions only. SF-ROM automatically reads the callers allowable limit of download files/bytes from SFFILE.DAT. Some may wish to overide these limits and specify special limits for inside SF-ROM only. The 10 is the callers security level. You may also use the word ALL in place of a security level and then the download limit will apply to ALL callers. The 12 is the number files allowed per day. The 2000 is the number of kilobytes per day. So all callers with a security level of 20 would be allowed 12 files totalling up to 2 meg per day. You must use one line like this for each security level you wish to limit. So if you had 3 security levels of 10, 20 and 30 your SFROM.MAS might for example contain these 3 lines: LIMIT 10 12 2000 ( level 10 gets 12 files, 2000K ) LIMIT 20 15 3000 ( level 20 gets 15 files, 3000K ) LIMIT 30 18 4000 ( level 30 gets 18 files, 4000K ) Another example: LIMIT ALL 12 2000 ( everyone gets 12 files, 2000K ) Allowable values are 0 to 2000000000 (2 billion) files per day 0 to 2000000 (2 million) kilobytes per day. REQLIMIT 10 12 1000 Optional. Registered versions only. Works just like the LIMIT command except it limits requests. In the example above, callers with a security level of 10 would be allowed to request up to 12 files per day totaling up to 1000 kilobytes (1 megabyte) per day. You may also use the word ALL in place of the security level and then the request limit would apply to ALL callers. Default request limits are the same as the download limits unless request limits are specified using this command. Allowable values are 0 to 2000000000 (2 billion) files per day. 0 to 2000000 (2 million) kilobytes per day. FILERATIO 10 50 Optional. Registered versions only. Sets FILE ratio limits. In the example above, the 10 is the callers security level, and the 50 is the ratio to enforce. You may use one of these commands on a separate line to set a separate ratio for each security level. Or, you may use the word ALL in place of a security level and then the ratio will apply to ALL callers. If the caller's download to upload ratio exceeds this amount, the caller will not be allowed any more downloads in SF-ROM. This ratio is computed after each successful download by dividing the total number of downloaded files by the total number of uploaded files. For computational purposes, 1 upload is used if the caller has 0 uploads. SF-ROM does not alter the callers security level, so if a caller exceeds his ratio in SF-ROM, he may still be able to download in Spitfire. Spitfire does not recalculate ratios or adjust security levels until after the caller's next download in Spitfire. Allowable ratio values are from 1 to 2000000000 (2 billion). Default is no ratio limits. BYTERATIO 10 50 Optional. Registered versions only. Sets BYTE ratio limits. Works just like the FileRatio except that the ratio is computed based on the number of downloaded to uploaded bytes. The FileRatio and ByteRatio values are independently enforced and can be set to different ratios if desired. Allowable ratio values are from 1 to 2000000000 (2 billion). Default is no ratio limits. TOTALDOWN ON TOTALDOWN OFF Optional. Registered versions only. Updates the Spitfire global record of how many downloads today. It does this by updating SFSYSTEM.DAT. This is the number of downloads today value seen by callers during logon. If the Spitfire file format for SFSYSTEM.DAT changes in the future, then TotalDown should be set OFF. SF-ROM is known to be compatible with Spitfire 3.3 and 3.4 in this regard. TotalDown is forced OFF in the unregistered version. The default is TotalDown OFF. LOGNAME C:\SF\CALLERS.TMP Optional. Registered versions only. Gives the name of the caller activity log file. If no logname is specified, the SF-ROM reads the Spitfire home directory from SFFILE.DAT (or equivalent) line 9 and appends the filename CALLERS.TMP. So if no LogName is specified, then SF-ROM will automatically use the correct Spitfire CALLERS.TMP log appropriate to that node. LOG ON LOG OFF Optional. Registered versions only. Choose one. Turns caller activity log ON or OFF. In unregistered versions the log is forced OFF. In registered versions the default is Log ON. In local mode from the DOS command line the log is always forced OFF. STYLE 1 STYLE 2 STYLE 3 Optional. Registered versions only. Choose one of the style commands shown above. Determines the style of the download line in the caller activity log. Some third party utility programs read the callers log and count or log downloads. These programs require certain download log entry styles which are similar to those created by a normal Spitfire download. Three styles are now offered. More will be added if requested. Only one style may be used in each configuration file. If multiple styles are specified, then the last one specified is used. For Style 1 a typical log entry looks like this: 1800LIST.TXT 2,276 Listing Of 1-800 BBS Systems This is the default style and is the same as all previous versions of SF-Rom. For Style 2 a typical log entry looks like this: Downloaded E:\MODEM\800LIST.TXT Note that this is the path to the file on the CD-ROM. For Style 3 a typical log entry looks like this: Downloaded C:\SF\CDROM1\800LIST.TXT Note that this is the file name appended to the path to the file list that contains the file. LOGLEADER ' ' Optional. Registered versions only. This string of characters between the apostrophes '' is placed in front of each caller activity log entry. The default is 8 spaces as shown above and is designed to match the normal Spitfire caller log. INDENTLOG 2 Optional. Registered versions only. This is the number of characters each line of the caller activity log will be shifted to the right beyond the amount specified by LogLeader. The line with the caller name (optional, see below) is NOT shifted. The default is 2 as shown above. LOGUSERNAME OFF LOGUSERNAME ON Optional. Registered versions only. If ON, then SF-ROM writes the caller's name to the caller log. Some may wish to turn this ON if the BBS software does not write the callers name to the same log. Default is OFF. BEFOREBAT COMMENT.BAT Optional. Registered versions only. This batch file is run after the files are copied to the hard drive, but BEFORE the download. I use it to insert a BBS advertisement into each ZIP file, but you can use it for anything you like. See supplied sample file COMMENT.BAT. In the example above, COMMENT.BAT is in the current directory, but a full path and file name may also be specified. Send me any good working batch file you write and I will make it available to other SF-ROM users. The following DOS variable parameters are passed for use by the batch file: %1 The directory on the hard drive where the files are copied to. There is no tailing backslash. Example: %1 = C:\CDROM\HOLD %2 The callers connect speed. Example: %2 = 14400 %3 The port number. Example %3 = 2 If you are using a non-standard port where you have changed the IRQ number or IO base address, then %3 will be the base address followed by a comma followed by the IRQ number. This is the same as used by DSZmodem for non-standard ports. Example: %3 = 3e8,4 if you are using address 3e8 and IRQ 4. %4 The full path and file name of the list of files being downloaded. This is the holding directory followed by EXT1.LST where the 1 represents the node number as passed on line 4 of SFFILE.DAT. If your holding directory is C:\CDROM\HOLD and you are using node 1 then %4 = C:\CDROM\HOLD\EXT1.LST. This same file name is passed to DSZmodem to tell it which files to download when the caller is using Y or Zmodem. If the caller is using Xmodem, then this list is not created. Note that if you use a separate holding directory for each node, then only the files being downloaded by the caller will be in this directory. So the batch file can do something to each of the files in this directory. Here is an example, which is the same as in the supplied example file COMMENT.BAT: FOR %%F IN (%1\*.ZIP) DO PKZIP2 %%F -K -Z < COMMENT.TXT This puts the BBS advertisement in file COMMENT.TXT into every ZIP file in the holding directory specified by %1. AFTERBAT YOURFILE.BAT Optional. Registered versions only. This batch file is run just AFTER a download. It is run before the files are erased from the hard drive. You may use this for any purpose. Perhaps some kind of logging function or a bulletin maker could be executed here. In the example above, YOURFILE.BAT is in the current directory, but a full path and file name may also be specified. Send me any good working batch file you write and I will make it available to other SF-ROM users. The same set of DOS variable parameters passed to BeforeBat (see above) is also passed to AfterBat. DIRECTVIDEO ON DIRECTVIDEO OFF Optional. Choose one. With DirectVideo ON, all local screen writes will done directly to video memory instead of through the BIOS. Default is DirectVideo ON which seems to work fine on most systems. CHECKSNOW ON CHECKSNOW OFF Optional. Choose one. CheckSnow ON enables "snow checking" when using DirectVideo ON. It has no effect if DirectVideo OFF. Some older CGA monitors may requires this. It should not be a problem on most monochrome, EGA or VGA video systems. Some systems may run a bit faster with CheckSnow OFF. Default is CheckSnow OFF. BIOSSCROLL ON BIOSSCROLL OFF Optional. Choose one. If BiosScroll OFF, then a special scrolling routine is used that suppresses snow and flicker on systems with any kind of color graphics. However, BiosScroll ON is a bit faster. Default is BiosScroll ON. HANDSHAKE ha cts Optional. Sets DSZmodem to use CTS hardware handshaking flow control. This is the best choice for the vast majority of systems. Hardware handshaking is especially important at port speeds of 9600 bps or higher and should reduce the number or errors and resends. Some versions of DSZ have been found (in my experience) to sometimes lapse into software handshaking unless hardware handshaking is explicitly specified on the DSZ command line. SF-ROM will insert this command directly into the DSZ command line at the correct location. Any valid DSZ handshaking command may be used in place of ha cts. Default is ha cts (hardware handshaking) as shown above. SOFTFLOW Optional. Do not use this command unless you are sure you need it. Flow control is ALWAYS hardware (RTS/CTS) unless this command is used. It FORCES software flow control (XON/XOFF) and shuts off hardware flow control. Hardware flow control is better and most modern modems support it. If you use software flow control, please send me a note. I am curious if anyone uses it. FORCECOMPORT 2 Optional. Do not use this command unless you are sure you need it. Com port selection is fully automatic based on the value passed by SFFILE.DAT. Use of this command overides this value and forces use of the specified com port. Allowable for this command is 1 to 8. Use in SFROM.MAS if running multi-disk mode. Use in SFROM.CFG if running single-disk mode. If specified in both, only the value in SFROM.MAS is used. FORCEBASE $02F8 Optional. Do not use this command unless you are sure you need it. I/O port base address selection is fully automatic based on the standard IBM PC values associated with the selected com port number. Use of this command overides this value and forces use of the specified I/O port base address. The $ indicates that the address is specified as a hexadecimal number. Allowable for this command is any value from $02E8 to $5228. Please note that no checking is done on this value and it is entirely possible to specify a non-existant base address. Use in SFROM.MAS if running multi-disk mode. Use in SFROM.CFG if running single-disk mode. If specified in both, only the value in SFROM.MAS is used. FORCEIRQ 3 Optional. Do not use this command unless you are sure you need it. The IRQ number selection is fully automatic based on the standard IBM PC values associated with the selected com port number. Use of this command overides this value and forces use of the specified IRQ number. Allowable for this command is any value from 0 to 15. Use in SFROM.MAS if running multi-disk mode. Use in SFROM.CFG if running single-disk mode. If specified in both, only the value in SFROM.MAS is used. FORCEVECTOR 11 Optional. Do not use this command unless you are sure you need it. The ISR (Interrupt Service Routine) vector number selection is fully automatic based on the standard IBM PC values associated with the selected com port number. Use of this command overides this value and forces use of the specified interrupt. Allowable for this command is any value from 8 to 15 or from 70 to 77. Use in SFROM.MAS if running multi-disk mode. Use in SFROM.CFG if running single-disk mode. If specified in both, only the value in SFROM.MAS is used. ----- DISPLAY FILES ----------------------------------------------------- In multi-disk mode, the following display files may be used to show the list of available disks: ANSI ASCII ----------- ----------- MAINxxx.CLR MAINxxx.BBS MAINxxx.BBS MAIN.BBS MAIN.CLR MAIN.BBS The "xxx" shown above represents a security level. For example, MAIN10.CLR is the ANSI menu for security level 10. SF-ROM searches for the display files in the order indicated above. If specific display files are not found for the caller's security level, then the general MAIN.CLR/BBS files are shown. In both single-disk mode and multi-disk mode, the following display files may be used to show the list of available file areas on a specific disk: ANSI ASCII ----------- ----------- DISKxxx.CLR DISKxxx.BBS DISKxxx.BBS DISK.BBS DISK.CLR DISK.BBS The "xxx" shown above represents a security level. For example, DISK150.BBS is the ASCII menu for security level 150. SF-ROM searches for the display files in the order indicated above. If specific display files are not found for the caller's security level, then the general DISK.CLR/BBS files are shown. - MULTI-PAGE MENUS - You can also create a multi-page MAIN.CLR/BBS and/or DISK.CLR/BBS. In this case, put all the pages in one file. Each page should be no more than 21 displayed lines long and there should be 4 blank lines between each page. The door will pause at the end of each page and allow the caller to select a command or scroll to the next page. A good method for creating multi-page ANSI menus is to create each page separately in an ANSI editor such as TheDraw. Then use the DOS COPY command to join the screens like this: COPY PAGE1.CLR+PAGE2.CLR+PAGE3.CLR ALLPAGES.CLR - CUSTOM WELCOME and GOODBYE SCREENS - Optional. Place these screens in the SF-ROM home directory. If they exist, they will be displayed to the caller. If registered, WELCOME.CLR or WELCOME.BBS will be displayed prior to entering SF-ROM. GOODBYE.CLR or GOODBYE.BBS will be displayed after a download if the caller selects log off after transfer. The .CLR file will be shown if the caller is in ANSI graphics mode. The .BBS file will be shown if the caller is in ASCII graphics mode. ----- LOCAL KEYBOARD CONTROLS ------------------------------------------- These are the same as used by Spitfire: ALT+C --- Chat Mode On/Off ALT+D --- Drop To DOS (local sysop only) ALT+J --- Drop To DOS (local sysop only) F6 ------ Take Five Minutes From Caller F7 ------ Give Five Minutes To Caller F10 ----- Exit The Door ALT+F1 -- Exit The Door ALT+F2 -- Exit The Door ALT+K --- Kill. Throw the caller off the BBS *NOW* ----- STATUS SCREENS ---------------------------------------------------- Here is a typical set status information that is always displayed on the top 2 lines of the local monitor: John Smith 33 Min 3/10 #135 Sec:30 Node:1 Com2 14400 260K Anytown, USA 999-999-9999 Night Owl 10 - Online John Smith --- The caller name. 33 Min ------- The amount of time left. 3/10 --------- The caller has downloaded 3 files. The caller is allowed to download up to 10 files. #135 --------- User file record number for this caller. Sec:30 ------- The caller security level. Node:1 ------- The BBS node number. Com2 --------- The Com port number. 14400 -------- The caller connect speed. 260K --------- The current amount of free memory left after loading SF-ROM into memory. Anytown, USA - The caller address. 999-999-9999 - The caller phone number. Night Owl 10 - The current CD-ROM disk name. Online ------- The status of the current CD-ROM disk. Here is a typical set of status information that is displayed on the top of the local monitor during a download: Download Today.........3 Download KByte Today.......350 BBS Logon: 8:15 pm Download Limit........10 Download KByte Limit......2000 Enter Door: 8:21 pm Download Total........27 Download KByte Total..... 4512 Begin DL: 8:33 pm Upload Total.........5 Upload KByte Total......1050 Time Left: 33 min ----- NOTES ------------------------------------------------------------- 1. SF-ROM uses the powerful and versatile DSZ program from Omen Technologies for file transfers. DSZ makes available Xmodem, Ymodem and Zmodem. Zmodem transfers will be sent using 16 bit, 32 bit, or MobyTurbo, as requested by the receiver (caller). Ymodem transfers will be sent either as true Ymodem or even Ymodem-g if requested by the caller. To utilize Ymodem-g, the caller should select <Y>modem in SF-ROM and then set his terminal program to receive using Ymodem-g. Ymodem-g will not work properly unless both the BBS modem and the caller's modem are set for hardware error correction (such as V.42 or MNP). Ymodem-g is only available in REGISTERED copies of DSZ. 2. The <S>earch text command searches the entire line so that all matches in file name, size, date, and description are shown. This allows some interesting possibilities. For example, a search for "-94" would show all files with dates of 1994. 3. Testing here on my system shows that the ASCII text file list search routines in SF-ROM are several times faster than searches of a compiled database and index file. The text file lists also take up about 1/3 as much space as a compiled database. In most cases, the text file lists as supplied on each CD-ROM disk can be used directly with no modification. If space is limited, you do not have to copy these files to your hard drive. SF-ROM can read them right off the CD-ROM if so configured. ----- IF YOU NEED HELP -------------------------------------------------- Check this document first. Perhaps your problem is discussed here. SF-ROM writes many (but not all) error conditions to file ERROR.LOG in the current directory. Check this file. Call my BBS and leave a message which fully describes the problem. Please upload the following files: 1. Any ERROR.LOG files created by SF-ROM. 2. The batch file that runs SF-ROM. 3. SFROM.MAS and SFROM.CFG 4. SFFILE.DAT or equivalent I will post a reply message on my BBS for you within 24 hours. FidoNet nodes may netmail the same information, and then poll for a reply in 24 hours. I fully support both registered and unregistered versions. This program runs well on hundreds of systems, and I will work with you to get it working on your BBS. I recently opened node 2 203-922-1794 FidoNet 1:141/486 which is dedicated exclusively to handling support for my shareware. Traffic on this node is very light, and it is almost always ready and waiting for callers. ------- REGISTRATION ------------------------------------------------------ This program is SHAREWARE. It represents hundreds (if not thousands) of hours of effort. I have been adding features and improving it for almost 2 years now. All upgrades have been free. The registration fee is only $25 which I believe to be a fair price for a program of this caliber. You may use this program for a free 30 day trial period. After that, you must register it or stop using it. You may give away free copies of this entire unmodified package, but you may not sell it. I retain all rights to this program. As an incentive to encourage registration, the following features are ONLY AVAILABLE IN THE REGISTERED VERSION: ■ The *** UNREGISTERED *** message on the first screen is replaced by your name and your BBS Name. ■ Requests from offline disks feature is activated. Internal download/request database is activated. Allows SF-ROM to accurately track and limit requests. ■ Spitfire's daily download file and byte limits will be enforced by the door. The door will also record all downloads and add the number of files and bytes downloaded to the main Spitfire data base. So the caller's total daily downloads (sum of downloads inside the door and normal Spitfire downloads) will never be more than allowed by Spitfire in DAILYLMT.DAT. These limits are correctly tracked in any combination, even if the caller enters and exits the door several times. If Spitfire says a caller can only grab 10 files per day, he will only be able to grab 10 files total per day. example: A caller is allowed 10 downloads per day. He downloads 3 files in this door. He is then only allowed 7 more downloads when he returns to Spitfire. In the unregistered version, only the caller's daily time limit is enforced. In the unregistered version, downloads are not recorded and file/byte per day limits are not enforced. ■ Batch files are called before and after a download to allow insertion of BBS advertisements into ZIP files or any other function you can execute from a batch file. ■ WELCOME.CLR or WELCOME.BBS file will be displayed (optional). ■ Full logging of all caller activities in the door to CALLERS.LOG or any file you choose. These log entries are designed to blend nicely with the normal Spitfire log entries. In the unregistered version, only error conditions are logged. No caller activity log is created in the unregistered version. HOW TO REGISTER: Please fill out and mail the form below to register the SF-ROM door or call my BBS for fast online registration using your credit card. I accept Visa, Mastercard, Carte Blanche, Diners' Club. Call The Soft Parade BBS at: 203-922-1794 or 203-924-5603 Registered Sysops are entitled to free program support, and free access to all files and features on my BBS. Support is available from me on my BBS, in FidoNet (Wildcat echo), Spitfire CircuitNet (CD-ROM echo) and via direct FidoNet crash netmail. Suggestions for future improvements from registered Sysops will receive careful consideration. When you register, you will receive a customized personal registration key file and instruction file. The key file activates the registered features in the shareware version, so there will be no need to download any specially compiled versions of the executable program itself. Please be sure to specify your name and your BBS name exactly as you would like them to appear on the first door screen. --------------------------------------------------------- --------------------------------------------------------- --------------------------------------------------------- SF-ROM 1.30 Door REGISTRATION FORM Your Name: ______________________________________________ BBS Name: ______________________________________________ Address: ______________________________________________ Address: ______________________________________________ BBS Phone Number: ________________ Please answer the following if you want to charge your registration: Credit Card Type: _____________________ Name as it appears on the card: _______________________________ Credit Card Number: ___________________________________________ Expiration Date: _______ Voice Phone Number: _________________ Please choose ONE of the following registration options: ___ $25 (Twenty Five Dollars) Call Mike Robinson's BBS and download your registration file. I will establish an account for you in advance if you give the following logon information: Password to use on Mike Robinson's BBS: _____________________ BirthDate to use on Mike Robinson's BBS: _____________________ ___ $30 (Thirty Dollars) - First Class Mail anywhere in the world. I will mail your registration to you. Specify floppy disk type. 3.5 inch HD will be used if not otherwise specified. ___ $30 (Thirty Dollars) - USA and CANADA ONLY. Mike Robinson will call your BBS and upload your registration to you or he will NetMail your registration to your FidoNet address. BBS phone number or FidoNet Address: --------------------------------------------------------- --------------------------------------------------------- --------------------------------------------------------- Send this form and payment in US DOLLARS to: Michael Robinson 9 Richard Boulevard Shelton, CT. 06484-4386 I accept Visa, Mastercard, Carte Blanche, Diners' Club. Personal check, bank check, or money orders are acceptable. Checks must be from a bank or financial institution with a cashing address within the USA listed on the front of the check. Most major banks in other countries can issue such an international money order or international bank check. InterNet Mike.Robinson@485.n141.z1.fidonet.org InterNet Mike.Robinson@486.n141.z1.fidonet.org ╔════════════════════════════════════════════════╗ ║ * The Soft Parade - Shelton Connecticut USA * ║ ║ * Home of the EZ-ROM & SF-ROM CD-ROM Doors * ║ ║ * Online Registration using Visa/Mastercard * ║ ╚════════════════════════════════════════════════╝ Node 1 203-924-5603 FidoNet 1:141/485 General Access * USR Dual Standard Node 2 203-922-1794 FidoNet 1:141/486 SF-ROM Support * Hayes 288 V.FC FidoNet File Request EZROM or SFROM for latest versions. Support and Online Registration available on both nodes. Node 2 is for SF-ROM support only and is rarely busy. Legal Stuff: Use this program at your own risk. No guarantees of any sort. File sharing and locking implemented via BCSHARE Beta Version 0.7 Copyright (C) By Mike Woltz 1990 Buffalo Creek Software. DSZ program Copyright by Omen Technology Inc. SF-ROM Revision History Version 1.00 --- May 31, 1992 - Initial Public Release Version 1.10 --- Sep 05, 1992 - Added batch downloads & file tagging. Version 1.15 --- Oct 10, 1992 - Various bug fixes and test versions. Version 1.20 --- Mar 7, 1993 - Multiple disk support. Enhancements. Version 1.20R--- Nov 8, 1993 - 34 line SFFILE.DAT. Version 1.30 --- Jan 31, 1994 - Offline requests, database, ZIP files. Each of these was a free upgrade to all registered users. ******************************************************************* OTHER PROGRAMS BY MIKE ROBINSON: EZROM130.ZIP 110,790 01-31-94 EZ-ROM 1.30 CD-ROM Door for ANY BBS EZ-ROM is based on the same base source code as SF-ROM. It is designed for use on any BBS that can create the standard door drop file DOOR.SYS. The configuration, file format, and appearance is exactly the same as SF-ROM. Whenever new features are added, they appear simultaneously in new releases of both SF-ROM and EZ-ROM. The revision numbering scheme is the same so, for example, SF-ROM 1.30 is the equivalent of EZ-ROM 1.30. So if you run Spitfire BBS, get SF-ROM. All other BBS types should use EZ-ROM. ******************************************************************* PKZIP archive security notice for this archive should read: Authentic files Verified! # FEZ251 MICHAEL N. ROBINSON