I get 3 error messages when I start up and the first starts this way:

 

SCENERY CFG file error: Local scenery directory (C:\Program Files (x86)\Microsoft Games/Microsoft Flight Simulator X\\FSAddon\DolomitiX-BellunoFR\SCENERY) in scenery Area.117 not found.

 

But when I look for that file it is not in the location indicated so I can't delete it.

Is the C drive the drive you moved it to, or where it was prior to moving FSX?

The C drive is where I moved it from...

If you've moved everything in the FSX folder to your new drive, then your scenery will have moved as well - the problem is, it isn't going to automatically update your scenery.cfg file with the new drive. So I'd imagine you're going to have to go into your scenery.cfg and correct all the directories. If all you've done is moved it to "X:\Program Files (x86)\Microsoft Games/Microsoft Flight Simulator X\\FSAddon\DolomitiX-BellunoFR\SCENERY", where X is the letter of your new drive, you simply need to change the directories in the CFG to X instead of C.

Are you able to delete the entry (or preferably comment it out with two slashes //)?

 

Check the scenery.cfg

 

C:\Users\YouruserName\AppData\Roaming\Microsoft\FSX

 

Oh, nm the guy above has a better idea hehe

When I look at the scenery cfg file the 'area number' does not match the number in the warning message.

When I read the topic title, I only thought "moving FSX is just not a good idea". If you are changing the FSX reference path (eg. C:\FSX to D:\FSX), you should reinstall FSX.

What about registry entrys for FSX and any addons that also make use of registry entries when installed?

When I look at the scenery cfg file the 'area number' does not match the number in the warning message.

 

Hmmm.... yeah I'm Word Not Allowed on this one... I'd do a reinstall. I know it's a PITA esp with addons etc, but it's the only way to ensure everything get's put in the right place.

When I read the topic title, I only thought "moving FSX is just not a good idea". If you are changing the FSX reference path (eg. C:\FSX to D:\FSX), you should reinstall FSX.

 

Nonesense. If you take care there will be no problem.

 

Regarding the scenery errors, go to "Settings->Scenery Library" and edit each of the entries. It will soon be obvious which are causing the problem and you can reset the paths.

...and an easier way altogether is to download and run Scenery Config Editor - here. It will do all the nasty stuff for you. D***** nice little app.

What happens with the programs that rely on registrations, usually stuff from Aerosoft, PMDG, FSDT?

 

You are looking for trouble this way, of course, if you really know what you are doing, you can go that way, but I see it like this:

Fix it once and for all, instead finding errors on the way and fixing them then. Beside, another possible scenario: now all is running fine, then at some point unexplained crashes come up, noone knows how to fix it, long threads about possible fixes, and in the end, he ends up reinstalling. Got my point?

What happens with the programs that rely on registrations, usually stuff from Aerosoft, PMDG, FSDT?

 

Don't know about the others, but with the FSDT activation, it's not a problem moving the FSX root folder.

 

The registration is not stored anywhere in the FSX folder or is related in any way to the actual FSX location. Our registration is stored in the Windows registry, and nothing wil remove it, even a complete FSX removal and reinstall (regardless of the location) will not affect it. The only way to remove an activation, is to either manually and intentionally remove the FSDT keys from registry, or made a major hardware change, making those keys not valid anymore.

 

And besides, if one WANTS to remove the activation from the system, there's no need to fiddle with the registry, since we have a specific function ( "Deactivate" ) in the Addon Manager, that will remove any trace of the activation from the registry AND will communicate with the activation server the product has been removed, giving an additional activation back.

 

And, all our sceneries installer don't put absolute paths in the scenery.cfg ( like C:\Program Files, etc, et ), but only paths relative to the FSX root folder, which means the FSX root can move to a different place, and the scenery will still work.

 

Of course, when moving the FSX folder, it's important to also change its registry keys to point to the new folder, otherwise lots of installers and other utilities will be easily confused.