FSX Airport Chart Gauge

This gauge seems to NOT like Windows 7

Here is a forum post on issues building the database;

https://www.flightsim.com/vbfs/showthread.php?209096-APChart-in-Windows-7-64bit&highlight=airport chart gauge

 

Short story; build the data base in Safe Mode

There is an alternate way to get into safe mode in windows 7 and windows 8 just search "msconfig" under charms bar or windows 7 search function. Then go to the boot tab and select safe mode.

 

You may find you have to adjust your screen resolution to see the entire data base builder.

 

You may find you have to press "Build" several times for it to work; you should see in excess of 25000 airports found in lower notification text in the data base builder.

 

Page three of this forum thread lists location of the data base text file in case you wish to save it elsewhere.

 

The DB file is located in your app data folder -

C:\Users\YOURACCT\AppData\Roaming\DBAirport (note the appdata folder is hidden by default)

 

And the file is named data_x.db

 

I used this cool gauge for years until it just quit working and the author's email is no longer valid.

There is other information in the thread and elsewhere in forums.

PS,

Over at Avsim Dave 'Opa' Marshall has a companion download of a panel icon to bring the chart up.

Finally, the software installs by default in program files (x86); I changed to 'C'; anyway there is a folder called Mahsoft. In there you will find the manual on how to use the gauge.

Happy flying and now, taxiing!

I accidently found out how to run the databse update under Windows 7. Using a program called oSpy (freeware), I thought I would try to trace the program execution to see what exactly was causing the problem - only to find out that, once the process is spawned via oSpy, the database updater runs perfectly fine :- so, no need to mess with your boor processes :)

I accidently found out how to run the databse update under Windows 7. Using a program called oSpy (freeware), I thought I would try to trace the program execution to see what exactly was causing the problem - only to find out that, once the process is spawned via oSpy, the database updater runs perfectly fine :- so, no need to mess with your boot processes :)