I'm not sure if this question may have already been answered on this forum or not, but I'll take a chance on asking...I've recently placed my installation of FS2004 onto its own partition on my hard drive, and for the most part, FSNavigator appears to work normally (i.e., FSNavDBC, registration, etc.). However, what I can't seem to be able to do is activate any of my add-on scenery (as the 'OK' button remains disabled).Does anyone have a solution to this problem? I'm suspecting that it doesn't work quite right if it isn't installed to the C:/ drive.

FSNav will take the registry entry for FS9 to look for your scenery.cfg. If you moved your installation rather than uninstall/reinstalled it, that entry will still point to your previous installation.George

Well as it turns out, I'm finding that I can't add scenery files from FS2004 either - I'm sure it must have something to do with a registry entry somewhere (or maybe even a scenery.cfg file problem), but I can't seem to find what the problem might be.My FS2004 is set up on a drive partition with a pathname of (D:Program FilesMicrosoft GamesFlight Simulator 9). The folder "Flight Simulator Files" still copied to the default "My Documents" folder.Are there any other solutions to offer at this point? I've got a fair number of AFCADs I'd like to re-install and re-activate with the new settings.Thanks!

Hi,Try this:First create a Restore Point and then...Run Regedit and browse to...HKLMSoftwareMicrosoftMicrosoft GamesFlight Simulator9.0Look in the right hand pane and check the data for the EXE Path key.Confirm that the path matches where FS9 is currently installed. If not, then right click the key and select Modify. Once you've changed the Value data, click on OK. It may be all you will have to change is the drive letter.This may turn out to be a shot in the dark but fingers crossed anyway!Mike

I did find out what the problem is - but there isn't a way to fix it. Apparently in their infinite wisdom, M$ set the 'read-only' attribute to true for all folders and subfolders (but not for individual files).This setting (while viewable from Windows Explorer) cannot be reset (short of starting 'cmd.exe' and using the 'attrib' command with a '-r' parameter).What I was able to do was cheat it somewhat by adding another entry to the end of my scenery.cfg file (but that would be a pain in the rear to have to edit this file by hand every time I wanted to add a new scenery area).See this link for the knowledge base article:http://support.microsoft.com/?kbid=326549

It's nothing to do with read only attributes. Do as Mike says and correct the registry entry.

The registry entry is correct - the folders are still marked read only, and I still do not have the ability to create any scenery folders (outside of placing the bgls into the default Addon Scenery/scenery folder).At this point, I'm getting very frustrated - neither FS9 nor FSNavigator can create additional scenery areas and have them recognized...Please see the screenshot for a look into my registry*LOL* - so now what?

"My FS2004 is set up on a drive partition with a pathname of (D:Program FilesMicrosoft GamesFlight Simulator 9).".....unless I'm missing something, looking at your attached image it would appear all you need to do is change the drive letter from 'C' to 'D'. (**)Mike**Edit: As I suggested in post #3N.B. Leave the folder Flight Simulator Files where it is on the C: drive. That's where it should be.The attribute on my 'Flight Simulator 9' folder is also 'Read Only' (as are all the sub folders).Scenery.cfg should only have the 'A' attribute set when viewed in Windows Explorer (View - Choose Details and tick 'Attributes')

>The registry entry is correct>*LOL* - so now what?The registry entry is not correct. Your FS9.exe is on your D: drive and not your C: drive. Both FS9 and FSNav use the path from the registry and will not find a scenery.cfg on your C: drive.

Yes, please listen to George and do as we are both asking and you should be sorted.However, I would also suggest you do a search within your Scenery.cfg file for 'C:' as you may have to change the drive letter to 'D:' for a few scenery areas. This is assuming ALL your scenery areas have followed your FS9 folder onto the D: drive. If you have elected to leave some on C: then you need to identify those and leave their path in Scenery.cfg alone.Mike

I should have clarified earlier - I did a complete uninstall of FS2004 from the D: drive, did a registry clean action, and completely re-installed FS2004 to Drive C:Apologies for not clarifying...my thought was thought was that it might have worked better from the default directory.

Could you post an image of your SETTINGS - SCENERY LIBRARY screen?Mike

I'm not sure what help it'll be - but here it is...It's just FS2004 with the standard setup for the scenery library.

I was curious to see whether the 'OK' button was greyed out but it appears to be fine.1. Can you enable/disable existing Scenery Area items and is this reflected in Scenery.cfg?2. Can you manipulate their priorities and, again, is this reflected in Scenery.cfg?3. Have you run FlightSim Manager's Diagnostics Tools (Diagnose Scenery - Scan for Errors)? and what is reported? When I run mine I get: "Congratulations!!! No Scenery problem detected.."4. If all the above appears okay, try renaming Scenery.dat to Scenery.dat.bak in the Addon Scenery root folder (don't worry, I've just tested on my installation and all's well) and then run FS9 to rebuild the file - Any errors reported?Mike

In answer to the above questions (for the record, I used FSM 2.8.5)1. No - if an attempt is made to disable any of the existing (default)scenery libraries, FS2004 informs me that the scenery library is required and cannot be turned off.2. Yes - I can change the priorities for things like Propeller Objects and Vehicle Libraries - these changes are then successfully saved to the scenery.cfg file.3. With FSM 2.8.5, I get the same message "Congratulations!!! No Scenery problem detected.."4. Renamed and then rebuilt. No problems reported.