README FOR AIRCRAFT USAGE LOG

NOTE: All files in this folder must remain together in order for the program to operate.

The program AircraftUsageLog is copyrighted 2004 by Scott L Goodrick.

It may be downloaded free and disseminated in zipped form at no charge without any other restriction. However, all original files in this folder must remain together or the program will not operate.

This program lets you see how many hours you have flown each of your FS9 aircraft. You will see a list that can be sorted alphabetically or according to hours flown. (Click on the column header to sort ascending. Click again to sort descending.) An Update feature lets you see the hours each has been flown since the last run of this program.

INSTRUCTIONS:

1.Place this folder anywhere you wish in your system. 

2.Use NotePad to edit the AircraftUsageLog.ini file so it contains the two path names that locate the two Aircraft folders created by FS9. The line AircraftDir refers to your normal Aircraft Folder - where all the files defining each aircraft reside. The line StateDir refers to the Aircraft folder that contains all the State files that show the engine hours for each aircraft. Microsoft has hidden this somewhere on your system. The two lines for a normal installation in Win98 are shown below:

AircraftDir = C:\Program Files\Microsoft Games\Flight Simulator 9\Aircraft
StateDir    = C:\WINDOWS\Application Data\Microsoft\FS9\AIRCRAFT

Edit them in the .ini file as needed for your system.

To run the program double click on the file: AircraftUsageLog.exe
in this folder. 

If you wish, you can drag the icon for that file to your desktop and then just double click on the icon to run the Aircraft Usage Log.

My son Scott does not fly FS9. But he agreed to write this code in executable form after I tried a similar code but ran into complications - namely caused by the various places Microsoft puts the engine data in different versions of Windows.  He chose to use the Python Language.  Because Scott does not have FS9 on his machine (and he lives several hundred miles away), debugging has been a long process.

If you have any questions, send them to me:

Tom Goodrick
goodrick@hiwaay.net