Version History of SFDNC ~~~~~~~~~~~~~~~~~~~~~~~~~ V1.0 - Initial Release V2.0 - Now can be run anytime, making in multinode compatible. V2.1 - Hopefully corrected the problems with version 2.0. The callers log should be written correctly now, no double lines, and no missing callers log. Also fixed bug where SFDNC would terminate a multiple line description if it was the last file in the list. V2.2 - Corrected bug where if first character of filename was not a letter or number SFDNC would attribute the download to the wrong file. - Corrected bug where a file line description over 80 characters would cause the # downloads to be written on that same line. No file description should be this long, but if they can now be up to 120 bytes per line. - Cosmetic changes. Display improved greatly. V3.0 - FIXED MAJOR BUG WHICH WOULD CAUSE SFDNC TO LOCK UP IF USED IN CONJUNCTION WITH SFFILES AND OTHER UTILITIES. (b1) - You will now (if you didn't before) see the  character in your file lists, if you are viewing them from DOS. Don't worry, this character is supposed to be there, and Spitfire will display the file list correctly. (b1) - SFDNC is now capable of running in Network environments. See the documentation for information. (b2) - New command line parameter added. If you append /BACKUP to your command line SFDNC will now create a backup file of your SFFILES.BBS files. The filename will be SFFILES.OLD V3.01 - The last date a file was downloaded is now displayed on the # of downloads line, instead of the date the utility processed the download. (01) - The # of downloads line is now changed to : # Downloads : x Last D/L'ed : mm-dd-yy V3.02 - Completly changed registration key system. - Now SFDNC starts processing the callers log on the second line instead of the first. This is other Spitfire utilities can read the date of the callers log correctly. V3.03 - Error handling capabilities improved. V3.10 - It looks like the error handling over did it in some cases, if you tried to use the /BACKUP option after not using it before, then the program would abort with an error. - SFDNC now considers any line with a character on any of the first three spaces, to be a new file or header in the file listing. - This version fixes a problem in version 3.03. Under certain conditions SFDNC would report a false error. - SFDNC now creates an error log file called "SFDNC.ERR". This will be placed in the directory SFDNC.EXE is ran from.