Barra Airport progress

[TSR2]

Honest answer is I'm not sure Mike, and I've no wise words I'm afraid, just experience, and on this topic I've none of that.
You could try .x and .xml and see if MCX can open it? Its worth a try.

[Airspeed]

OK Ben,
I have finally read the script in the following dialogue box slowly and carefully, and realize that I do not understand what they mean by the registry being correct or not.

My installation is in C:\FSX. I entered that in the path box at the bottom, but this is ignored, and the setup then assumes that I only have FS9, which FSDS happily finds at C:\FS9. Why it doesn't see FSX must be to do with that registry business.




BTW, the puns supplied by the peanut gallery are becoming insurfable.

[DaveB]

Mike.. as taken from the Developers Corner wording..

A quiet place for budding model makers to share thoughts, get answers to questions and request and share references.

I wish I could help you with FSDS mate. That box would suggest it can't see FSX in the registry.. nor FS9 for that matter.. both of which you have installed It's not a Win7 thing is it. I can't imagine it is with how old it is now

ATB
DaveB

[DaveG]

Pop over to Flight1 (http://www.flight1.com/view.asp?page=library) and download the registry repair tool.
Run it and tell it where FSX is located and it should fix any missing or incorrect registry entries.
See if that helps.

[Brian Franklin]

Does it not find it if you use the little button on the right of the Simulator path and navigate to it manually?

[TSR2]

Right, try running FSDS by right clicking on the shortcut and selecting run as administrator and then see if it sees the registry keys.

[Airspeed]

Thank you Gents,
DaveB,
Understood, my friend.

Brian,
Actually, that's exactly what I have been doing, but the next screen allows me to set only FS9 paths regardless. Oddly, FSDS then says it's found FS9,[note how the box above says it can't find either of them] and will make models for that.
Neither is in the default location, I use C:\FSX & C:\FS9.

DaveG,
I use System Mechanic from IOLO to check and fix my registry and everything else. It has been run often, so unless you think that your suggested fixer is better than SM, I'd prefer not to confuse myself further with another tool whizzing round the place.

Ben,
I've tried that one before, though every user; me, me, or me, has full control, and I am always logged on as admin. I will repeat that procedure again anyway.

BTW I've sent another support query to Abacus asking them to focus help on this registry point.

[TSR2]

Mike, in Vista and later, by default, Admin is not admin. This stops little nasties doing things they shouldn't without you at least getting a prompt. By right clicking and selecting "run as administrator" you're effectively telling windows that that particular program is trusted to do anything it needs.

[Airspeed]

Ben,
As promised, I right clicked at every step, deleting and fully reinstalling FSDS.
Then, rather than clicking the shortcut, I went down the tree and right clicked the application file and ran as administrator.
It still can't find any version of FS. I'm going to stop wasting my time and yours, until I hear back from support.

[DaveB]

This always confuses me with Win7 Ben.. can't get my head around why some programs can be run without the dreaded 'Admin' warning coming up yet others don't. ASA installed perfectly and doesn't have the 'Admin' shield attached to it. ASN is installed to the same drive yet it comes up with 'Do you want to run this program' warning

Sri Mike.. don't want to drag this off topic.

ATB
DaveB