Problem detected when using Simple Airport Scanner

#1
I am not sure of where to place this question, so I thought I'd try here, since Simple Airport Scanner detected the problem.

I think an auto-installer screwed something up for me. When I run Simple Airport Scanner, I get the text shown in the attached file. The path shown is the one where I unpack zipped files to, and where I point auto-installers to so I can install their stuff where I want it in my installation.

I have tried to run Flight One's FSX registry reset tool, that didn't fix the issue.

Does anyone have an idea of how to fix this? Every bit of help is appreciated - I don' want to face (another) reinstallation....

Thanks -

Jorgen
 

Attachments

scruffyduck

Administrator
Staff member
FSDevConf team
Resource contributor
#2
How about a screenshot of the application main window? It seems to me that you haven't set a valid path to the FSX active scenery.cfg
 
#3
Here you go.....

The thing is, in the scenery.cfg file refernced here, everything looks normal. This changed after I ran an autoinstaller to install some Chilean scenery to C:\Dnload\FSX\Work1 earlier today, before that everything worked normally.

Jorgen
 

Attachments

scruffyduck

Administrator
Staff member
FSDevConf team
Resource contributor
#4
I can't actually read the path in the scenery.cfg. If it is correct then the other problem would be where FSX is installed or where the registry for FSX points. If you ran an autoinstaller then is there a risk that could change the registry path? It shouldn't but.... From your error.txt file it looks like SAS thinks that the path to FSX is C:\Dnload\FSX\Work1\ and it would look in the registry for that.
 
#5
This is the path from SAS:

C:\ProgramData\Microsoft\FSX\Scenery.CFG

It's been like that forever. FSX is installed in F:\1FSX.

Just for fun, here's the scenery.cfg file in question. I had to append .txt to the file name to get it to upload.

Jorgen
 

Attachments

#6
I also have GEX in my FSX installation, and last night used the GEX interface to see if there were any updates. The interface said it could not find FSX (apparently in the registry, like SAS), but then asked me to point it to the main FSX folder. After I did that, it remembered where FSX was and ran normally when I tried it the next time. Maybe something like that could be built into SAS?

Thanks -

Jorgen
 
#7
This morning I ran another autoinstaller, and it pointed itself to C:\Dnload\FSX\Work1 automatically.

So it appears the first autoinstaller changed a registry setting somehow, and Flight One's FSX Registry Reset tool does not fix that.

Does anyone know if this is something one could repair "manually" (and no, I haven't even tried to do that) or repair in some other way, maybe with Ccleaner's registry cleaning tool?

Thanks -

Jorgen
 

scruffyduck

Administrator
Staff member
FSDevConf team
Resource contributor
#8
Try the resgistry tool from tweakfs.com - it seems they are down for maintenance at the moment but they do have a free registry fix tool.
 
#9
I found the registry tool there, thank you.

It finds the Setup path for FSX at HKEY_LOCAL)MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0, and the App path at HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0, and in both cases the path was F:\1FSX - as it should be.

Where does SAS look for the path?

Thanks -

Jorgen
 

scruffyduck

Administrator
Staff member
FSDevConf team
Resource contributor
#10
SAS is looking in HKEY_LOCAL_MACHINE

For FSX it looks first for:

"Software\Wow6432Node\Microsoft\Microsoft Games\Flight Simulator\10.0"

then if it can't find that it looks for:

"Software\Microsoft\Microsoft Games\flight simulator\10.0"

In both cases it checks the value in "SetupPath"

It also goes on to check for FSX Steam Edition if neither of those are found:

"Software\Wow6432Node\DovetailGames\FSX" and in this case looks for "install_path"
 
#11
Bingo! Culprit found.

Under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft Games\Flight Simulator\10.0 the value in SetupPath was set to C:\Dnload\FSX\Work1.

The 2 other paths were not found.

Now, just asking before I do anything stupid,, but changing that value to F:\1FSX SHOULD solve my issue, right? And, of course only doing this after backing up the registry.

I understand the implications of changing that value, and declare herewith that I assume full responsibility of the consequences of changing said value.

Thanks -

Jorgen
 

scruffyduck

Administrator
Staff member
FSDevConf team
Resource contributor
#12
You are correct that it should solve the issue. Also it should be quite safe to change it to the proper path. It seems that the installer you used is messing with the registry and changing an important key. The only issue might be whether changing it to the proper path will affect whatever you installed with the rogue installer.
 
#13
Issue solved. Yep, changing that value took care of it.

And what I installed was not affected. When I install scenery, I unpack stuff or run the installers, pointing them to folders on my C: drive. Then I manually move the sceneries to where they should be on my E: or F: drives and then activate them in Scenery Configuration Editor.

Thanks a lot for your help -

Jorgen
 
Top