I built a new computer. I reinstalled FSX from the DVDs, reinstalled all my addons from their original installers.BUTI didn't want to go to the hassle of recreating my key maps and tweaks and everything else, that would take days, assuming I can even remember it all. So I copied the stuff in Users\dseagrav\AppData\Roaming\Microsoft\FSX (fsx.cfg and so on) from my other computer. That was all I copied, nothing else.Apparently, if you do this, most addons think you're a filthy pirate and disable themselves in strange ways designed to foil pirates.The MD-11 was installed from the original download and did its verification with the PMDG server, so I wasn't expecting anything from it. But when I try to load it, all functions are disabled and the initialization never happens.Is this a real bug or is this just the pirate protection?If it is the pirate protection, do I have any hope of convincing it that I actually paid for the software WITHOUT having to delete my FSX config or reinstall FSX yet again?

I've actually had no issue copying over FSX.CFG files from previous installs. I did this just recently as I reinstalled to a new drive. I was surprised which addons put up the "Do you want to run me?" dialogs as I thought that was all stored in the CFG file.You could always open the CFG file and remove the lines under the [Trusted] section (or copy them to another file for backup) and see if that helps.- Richard

You could always open the CFG file and remove the lines under the [Trusted] section (or copy them to another file for backup) and see if that helps.

I tried this and it didn't work. I uninstalled and reinstalled the MD11 and that didn't help either.FSX did ask me to re-authorize the DLLs, so they are being loaded, it's just locking me out.I also noticed that the PMDG menu is not showing in the menu bar.

If it's a new build then perhaps some of the hardware settings in the .cfg, dxdiag and all the other bits and pieces in that directory have changed and they're introducing problems. You've gone to the trouble of doing a nice clean install and just to save yourself an hour (or less) you've introduced problems that probably mean you're going to have to start over again. My recommendation, if you're going to do a clean install do just that, an entirely clean install without anything being copied across from the old install.

Just a suggestion, ??? Have you tried deleting the 'dll.xml' in %APPDATA%\Microsoft\FSX folder ? Make a backup copy first, delete the xml-file and the corresponding lines in your [Trusted]-section of your 'fsx.cfg' and make sure, you've access to everything in your FSX directory. It may be the case that, if you're on Win7/Vista, the UAC (User Access Control) is blocking things. In my case, I've switched off UAC the first time I started Win7.

[Trusted]..D:\GAMES\Microsoft Flight Simulator X\GAUGES\PMDG_MD11.DLL.....D:\GAMES\Microsoft Flight Simulator X\GAUGES\PMDG_MD11_ACS.DLL.......D:\GAMES\Microsoft Flight Simulator X\PMDG\DLLs\PMDGEvents.dll.....D:\GAMES\Microsoft Flight Simulator X\PMDG\DLLs\PMDGOptions.dll .....D:\GAMES\Microsoft Flight Simulator X\PMDG\DLLs\PMDGSounds.dll .......D:\GAMES\Microsoft Flight Simulator X\GAUGES\PMDG_BAe_JS4100_3.DLL .....D:\GAMES\Microsoft Flight Simulator X\GAUGES\PMDG_BAe_JS4100.DLL .......

best regards,toby ps: Please sign with your real name

I fixed it. In \AppData\Roaming\Microsoft\FSX\SimObjects there's two folders, PMDG_MD11 and PMDG_MD11FDelete those. They will be recreated when the MD11 is loaded, and all is right with the world. As for the other problems I was having, it turns out that when Flight1 products tell you to back up the extracted data, I somehow misinterpreted this to mean that you were to back up the key and exe.I thought they were a pair. This is not true. The exe is specific to the computer it was extracted on, and is useless after the install completes. You're only supposed to back up the key file.Copying the extracted installer is interpreted as violation of the copy protection and is intended to cause problems. You're supposed to use the key file to run the Flight1 wrapper again.

Glad to see, you've fixed it.