UPGRADE INFORMATION -------------------------------------------------------------------------- FDC v5.00 Release Notes: ------------------------ Here is the latest and greatist version. No modifications should be necessary to your setup. Simply replace the FDC.EXE file. Note FDC is now available on the world wide web at the following site: http://www.cc.utah.edu:80/~bmb4764 FDC v4.60 Release Notes: ------------------------ Apparently v4.50 was complied in NON-OVERLAY mode of the complier. This caused all sorts of headaches for users. I apologize. The new version should work much better. This should also help eliminate the -42 database error many of you were getting. If you happen to run FDC v4.50 please delete the files FDC.P and FDC.T before upgrading. FDC v4.50 Release Notes: ------------------------ If you are running an ungregistered version of FDC you will not be notified of the download count exceeding 25 more than once. FDC should be slightly smaller in size as compared to version v4.30 due to some optimizations I did on the code. Throughly tested FDC with PCBoard v15.2 Beta. Updated the screens and documentation to show authors new BBS. FDC v4.30 Release Notes: ------------------------ Fixed a bug when using the /STRIP option that was not striping entries if they were greater than 80 characters long. If you specify a LAST_RUN_DATE with the year 1983 or earlier FDC will by default read the entire DOWNLOAD.TXT file. FDC will not search for the last run date as it would for dates > 1984. I figured since PCBoard was created in 1983 no one should have a DOWNLOAD.TXT file with entries prior to that date. Therefore if you want to re-init FDC simply change the LAST_RUN_DATE to 1/1/1983 and run FDC again. FDC will read every entry in your DOWNLOAD.TXT file that is a download. Unregistered versions of FDC are now FORCED to have a LOG file. Why? You ask? Because there is vital information recorded in the LOG file for unregistered users. FDC v4.20 Release Notes: ------------------------ Fixed the bug window bug that was causing information to overwrite the top line of the screen. Many sysops have asked how to set the PCBDAT= variable. Simply add this line to you autoexec.bat file: SET PCBDAT=C:\PCB\PCBOARD.DAT Then reset your system. Of course you will want to substitute the "C:\PCB\PCBOARD.DAT" with the path and name of your PCBOARD.DAT file. I have quadruple checked the accuracy of the download count and I have found it to be 100% accurate. A couple of sysops have reported that other 'door' utilties that scan the DOWNLOAD.TXT are reporting different numbers than FDC for the number of times a file has been download. The only suggestion I have for these sysops is to run "FDC /STRIP" and then reset the date counters in the FDC.CFG to a date back to 1980, then run "FDC". This will strip all entries from the DIR files and then rescan the entire DOWNLOAD.TXT file for the number of times a file has been downloaded. In a nut shell it will reset the download count. FDC v4.1 Release Notes: ----------------------- If you are upgrading from FDC v4.1 you will want to note the following changes. FDC now uses the PCBDAT= enviroment variable. The PCBDAT= enviroment setting must be set in order for the proper operation of FDC. For 99% of the sysops this should already be set. But for the %1 of you that will recieve the error "PCBDAT= eviroment variable not found." you will want to set it. By utilizing the PCBOARD.DAT file FDC can find information such as the location of the DOWNLOAD.TXT file and LOG file. Therefore the parameter DOWNLOAD= in the FDC.CFG file is an OVERRIDE for the values found in the PCBOARD.DAT file. If you would like FDC to default to the path\file found in the PCBOARD.DAT file then simply comment out the DOWNLOAD= option in the FDC.CFG file. A bug has been reported by several users that FDC was not reading the DOWNLOAD.TXT file correctly when searching back XX number of days. I have found the bug and corrected the problem. Thanks to those of you who have been patient in helping correct this bug. FDC v4.0 Release Notes: ----------------------- If you are upgrading from FDC v3.x RUN FDC v3.x ONE LAST TIME RIGHT BEFORE YOU UPGARDE to FDC v4.0. This ensures the last run date and time paremeters are set to the current system date and time. Then to install FDC v4.0 simply overwrite your FDC.EXE file with the new version. You will then want to make 2 addtions to your FDC.CFG file. These additions are LAST_RUN_DATE= and LAST_RUN_TIME=. Set these parameters to be the *current* system time and date, since the last time your ran FDC was right before the upgrade. (right?) For example if you upgrade on February 27, 1994 at 2:30pm then edit the paremeters to be: LAST_RUN_DATE=02-27-1994 LAST_RUN_TIME=14:30 Note the LAST_RUN_TIME= parameter is in the 24 hour time format.