A quick history of changes made to E.F.R. in reverse order; Ver 1.5 Test Stage 07/07/91 þ I added one more option which will restore the screen to it's startup condition, after EFR has completed a sucessful run. The Command line option is "/RESTSCR" for restore screen. Not using it saves about 2000 bytes, and I am sure that most of you would not need it, but there are some that would like the program to restore the screen to it's original condition after the run. þ Cosmetic change to clean up display after an aborted run. Previously, the program just dropped out to DOS. Now it will close all of the files, and clean up work files, clear & restore the original screen, then drop to DOS. þ Added monitoring of the key during processing to abort the program. This action will cause the work files to be cleaned up, restore your original display, and return you to DOS. þ Any other requests or options needed? ----------------------------------------------------- Ver 1.4 Test Stage 07/06/91 þ Recieved a suggestion from Larry Steele to allow the SysOp the ability to add a text line describing why a file was moved offline. Check your config file and add the line as shown in the example config file enclosed in the ZIP. To activate this option, use the command line switch "/APPDESC". þ Added a Clear screen command to the end of the code so you can find your cursor when the program completes. þ I forgot to mention this, but as of ver 1.1 there are two versions of expired included in your ZIP file. EXPIRED.EXE is written for 8088 based systems. EXP286.exe is compiled specifically for 286/386 systems, and take advantage of the additional processor speed. þ Updated the WP5 DOCS for the program. ----------------------------------------------------- Ver 1.3 Test Stage 07/03/91 þ Modified the command line option, so if you specify "/print" it automatically assumes the /report option. Previously you needed to specify both to get a printed report. þ Made a correction to the code where I inadvertantly deleted a line that initialized the pointer for the Conferences. This would cause the program to bomb out with a runtime error 103 FILE NOT OPEN when it got to the conferences. ----------------------------------------------------- Ver 1.2 Test Stage 07/02/91 þ Finally found that pesky problem that was preventing the program from deleting the file after moving it from the offline directory. Apparently when I was moving the file with the date and time intact, I was not closing the file, thus the system would not allow deletion. þ Corrected a problem where EFR was not updating the proper callers log if you were on a network. The program will now write to the callers log of the node which is contained in the PCBOARD.DAT file used in the configuration file. þ Added a count of qualified files that were acted on by EFR during processing - into the callers log. þ Cosmetic change to the Report output. Added a little more information. ----------------------------------------------------- Ver 1.1 Test Stage 03/28/91 þ I had to make a change in the filter I was using to read thru your DIRxx headers. With the release of WGMDMS ver 33, your headers can now contain the "@" symbol which is part of the @X## PCBoard color macro. I was filtering out anything in position 1 that was not an alphabetic character, so finding the @ symbol thru the program off the track. I removed the symbol from the filter table. þ Made a minor modification to the output report to clean it up a bit. ----------------------------------------------------- Ver 1.0g Test Stage 03/25/91 þ Reports of a runtime error 162 lead me to find a couple of logic errors if you were using the /move or /remove switch without the /report switch. I was attempting to write to a report file that was not openned if you did not specify /report. Error 162 is a hardware failure, and the address that the error specifies, does not make sense. If anyone gets an error of this nature, please let me know what command line options you are using, and also whether or not your using an exclude file list. I would also like to see your config. This will help me track any problems that might arise. ----------------------------------------------------- Ver 1.0f Test Stage 03/22/91 þ I found another variable that was too short. Recompiled with the correct size. My BBS is now back on line, and the new number is (904)794-0063. 24 hours 7 days. ----------------------------------------------------- Ver 1.0e Test Stage 03/12/91 þ I found that a routine I was using to update the DIRxx file was truncating the header description if you used WGMDMS ver 33. I was not accounting for the @X## macros, thus allowing only an 80 character string to be processed. I increased it to 100 characters. Let me know if that does the trick. ----------------------------------------------------- Ver 1.0d Test Stage 02/23/91 þ Two things happened with the last release. I was testing the /REMOVE, and found that it failed because I didn't clear out one of the variables. It was actually growing larger and larger thru each pass. þ When a file was moved to the off_line directory, the file date was being updated with the current system date. I didn't want that to happen! þ Give me some idea on the statistics you want to see when the program runs.. I am thinking about gathering the percent of files that are expired when a report is run, but where should I put that information. What else? ----------------------------------------------------- Ver 1.0c Test Stage 02/22/91 þ Checked out problem with report file not calculating the age of the file properly to the report output. It was working fine everywhere else. Fixed. þ Corrected a problem where the program would not properly process the all of the conference DIR files. I was only doing the first one, and the Conference Upload Directory. þ Changed the logic in how I was processing files to be kept, moved, removed, or truncated. More efficient now. Check your DIRxx files carefully to make sure that all of the records are there that are supposed to be. I was exiting the routines too early before, and it was loosing the very last line of the file. þ I checked the initial screen. It was fine. It cycles for 15 seconds, then moves on. You can touch any key to make the delay stop, but I made it time out originally so you could run in event. þ Updated the documentation. ----------------------------------------------------- Ver 1.0b Test Stage 02/21/91 þ I had to correct the /TRUNC keyword internally because the keyword I was using, I found out was a Turbo Pascal keyword that had the potential to screw things up. þ I changed the display inteface a bit. I needed more information on the screen while the program was running. þ I corrected a problem where the program was not processing all of the conference dirs that were available...mainly a logic error. þ A run through the Turbo Profiler looked real good! ----------------------------------------------------- Ver 1.0a Test Stage 02/20/91 þ I forgot to dispose of a couple of pointers which created a problem on exit with the command line. þ Added /TRUNC switch which will allow you to ZERO byte files, and leave the description in place with the date field being replaced by "DELETED". þ Tidy'd up the display a little. An initial run thru the profiler looked real good! ----------------------------------------------------- Ver 1.0 Initial Release 02/20/91 þ Here we go again! -----------------------------------------------------