ÚÄÄÄÄ¿ ³ÄÄÍij ROMProc Revision History File ³ ÄÄ ³ ÄÄÄÄÄ¿ ÚÄÄÄÄ¿ ³ ³ ROMProc ³ÄÄÍij The following is a list of the most ³ ³ ÀÄÄÄÄ> ³ ÄÄ ³ recent changes made to ROMProc by ³ ³ ³ ³ revision level, in reverse order. ³ ³ ³ ³ ÄÁÄÄÄÄÁÄ ÄÁÄÄÄÄÁÄ 1.34 - ROMProc would not properly pass the FOSSIL port number to the (9/18/93) transfer protocol, preventing the use of any FOSSIL protocols. Please refer to the documentation for more information on how to install ROMProc for FOSSIL use! 1.33 - ROMProc will now accept an environment variable as input for the (9/11/93) WORK_DIR parameter. This should help simplify multinode LAN installations with different drive configurations in different machines. Discovered (from a RBBS sysop) that the drive letter matching was inadvertently case-sensitive during batch file transfers (PCBoard's PCBSETUP automatically capitalizes all paths and filespecs, so it never happened here on my system). Fixed. 1.32 - Oops...if a sysop configured ROMProc to not display user status (8/18/93) information (COMM_IO set to NO), ROMProc would still produce an error if the required communication parameters were not supplied. 1.31 - Fixed a bug introduced in 1.30 where variables were not being (8/17/93) replaced when no space was provided between the command key and the variable. For example, "port @PORT@" worked fine, but "-p@PORT@" did not. Changed the file handling logic where if a file is encountered that does not include the drive spec, ROMProc will assume the current drive. This will correct problems when sysops don't include the drive in the download paths. Fixed a "Null pointer assignment" message that appeared on unregistered versions. 1.30 - CONFIGURATION FILE CHANGE!!! ROMProc now has a configurable amount (7/30/93) of time before the delay prompt is displayed to the online user. Refer to the new DELAY_TIME parameter in the documentation. CONFIGURATION FILE CHANGE!!! ROMProc now has a configurable string to display when a transfer is aborted due to exceeding the configured lock time; see the ABORT_PROMPT parameter. To help alleviate confusion, the old LOCK_TIME parameter has been renamed to ABORT_TIME. ROMProc's display has been revamped to include a new window, the "Online User Display" window. This window displays a copy of what is being transmitted to the remote user by ROMProc. I also tried to make things a little nicer looking while I was at it. It is now permitted to configure a text file for ROMProc to display the online user via the DL_PROMPT, PROC_PROMPT, DELAY_PROMPT and ABORT_PROMPT parameters. If the first character of the string is a "%", ROMProc will display the indicated text file. Note that PCBoard @-variables and @X## codes are not permitted, although ANSI codes may be used. Changed the number of display lines locked from three to two in order to give ROMProc some extra room for information display. Updated the documentation to include my new BBS phone numbers and home address effective August 16, 1993, as I've moved to Raleigh, NC. 1.22 - Found that my FOSSIL routines were broken using Microsoft C. As an (7/10/93) interim fix, I have recompiled ROMProc using Borland's compiler. 1.21 - If ROMProc failed with an error during the copying procedure on a (7/6/93) locked drive, the locking semaphore file would be left behind, essentially locking the drive indefinitely until the semaphore file was removed manually. Fixed. Added some code to detect blank lines within a batch list file generated by some BBS software (e.g. Prodoor). 1.20 - CONFIGURATION FILE CHANGE!!! ROMProc now supports drive locking for (6/17/93) slow drives. This will prevent massive slowdowns due to thrashing CD-ROM drives and changers. Refer to the LOCK_DRIVE and LOCK_TIME parameters. CONFIGURATION FILE CHANGE!!! With the addition of locking, ROMProc will display the text defined by DELAY_PROMPT to the user indicating the reason for the delay if ROMProc waits on the drive longer than 5 seconds. Some sysops stated that the error message display would go by too quickly to read, therefore the delay was increased to 5 seconds from 3...this should help. 1.12 - Learned that some BBS software do not stay in their node directory (6/2/93) for the file transfer (e.g. RBBS). This poses a problem if two nodes are executing batch downloads simultaneously, since the temporary batch download list file was named "ROMPROC.LST" by default. Now the list file is named "ROMPROC.#", where # is the node number. Note that you must pass the node number using the -N command line parameter for successful multinode implementation within these BBS systems. 1.11 - With the new versions of ARJ (2.39d and higher), secured ARJ (5/25/93) archives cannot be modified in any way, including adding a BBS ad file or commenting the archive. Therefore, ROMProc has been modified such that it will not abort the transfer if an archiver error is detected, but will continue and transfer the unmodified files. The error will be displayed and logged for the sysop's information. Added error detection to ensure that incorrect COM port information (e.g. IRQ, DTE rates) cannot be accepted by ROMProc. ROMProc could not automatically identify PKZIP 2.04? SFX archives created with the -j (SFX junior) switch, resulting in them not being commented and/or not having BBS ads inserted. Fixed. 1.10 - CONFIGURATION FILE CHANGE!!! ROMProc can display sysop-defineable (4/28/93) text to the user indicating the processing status. Refer to the COMM_IO, PROC_PROMPT and DL_PROMPT parameters in the documentation. CONFIGURATION FILE CHANGE!!! ROMProc is now capable of logging error messages to disk, if desired. This will help track down configuration errors in ROMProc. 1.00 - Oops...if a single-file download was initiated from a drive not (3/25/93) specified to be preprocessed, ROMProc may delete it from the disk after download. Broke the SFX archive identification routine, so no SFX archives were commented or had BBS ads inserted. Fixed. 0.99á - CONFIGURATION FILE CHANGE!!! Archive commenting is now user- (3/23/93) configurable via the COMMENT_ARC parameter. Enter YES if you desire archive commenting, otherwise enter NO or comment the line out. CONFIGURATION FILE CHANGE!!! The drives to be preprocessed (BBS ad insertion and/or commenting) by ROMProc must now be specified using the PROC_DRIVE parameter. Any file not on a specified drive will be transferred from the original location. This feature is for sysops who only want to preprocess CD-ROM files, but not files on hard disks. Refer to the documentation for more information. Modified code to process all the files from a drive prior to accessing another drive. This will prevent excessive CD changing on multi CD-ROM changer drives. If an ARC_COMMENT command-line is left blank in the configuration file, ROMProc will now skip commenting for that format. This will enable BBS ad insertion into archives that do not support commenting, such as LHA. Improved error-checking of command-line switches and archiver processing. 0.98á - Initial public beta release. (3/20/93)