I bought the 737 on July 9th. Got it to install in 2k2, but not in Fs9... Keep coming up with the attached error, on loading FS9, and then the sim crashes when I try to load the PMDG planes only...Bottom line, it is looking for a 2k2 file in FS9. It is the same in both I know. And it is in my folder, I have checked. I have even made copies and put it in other folders in FS9, to see if it would pick it up.. But, I just realized..before it even gets to the file....BASED ON THE MSG, IT IS LOOKING FOR A FOLDER THAT DOESN'T EXIST!!!! It is not looking for d/msgames/fs9/scenery/base..... it is looking for d/msgames/scenery/base.....your code is looking for the wrong subfolder. EVEN IF YOU HAVE 2k2 installed, which I did on another drive up until yesterday...deleted it, because I wanted to get 737 to work..., pmdg should not be looking for that directory if you are loading the plane up under FS9. Bottom line, after four months and 40-50 installs, I formally request a patch that gets the code to look for FS9 magdec.bgl, not 2k2 magdec, and NOT ing MS GAMES/scenery/base but MSgames/FS9/scenery/base.......!!!I think it will solve my problems and hopefully others perhaps!!!!If not, I am going to be requesting a refund, because it has not worked under the sim I bought it for after 4 months....Please try it... It would be a very small patch, seemingly easy to do, but it would have big consequences I believe.http://forums.avsim.net/user_files/43599.jpg

I made a scenery/BASE/ folder in my MS Games directory, instead of FS9. Still doesn't work.. I think it is still looking for a "2k2" magdec.bgl... Even though the same data is in file in 2k2 and FS9, it might still look different to FS9, which would make your program not work because it is looking for 2k2 magdec.bgljust a thought.. want to use this thing badly

When you run the installer, there are a couple of check boxes that are simulator specific. Did you check/uncheck the appropriate check boxes?VinPMDGwww.precisionmanuals.comhttp://www.vinscimone.com/dancnkid.gif

Yes, I did..Thank you though Vin.Well, I am happy to report that after 4 months, I found the problem. If you look at the error message on the screen that I posted, as I said, it was looking for the file in the wrong folder....If you look at the path that it wanted...there is normally no folder there.. So, I created the folders that it was looking for, and put the magdec in there. WE HAVE A WORKING FMDG now!!!So, off to download liveries....>>Vin>PMDG>www.precisionmanuals.com>>http://www.vinscimone.com/dancnkid.gifP4 2.81024 DDRAM800 Bus36 gig SATA hardrive80 gig harddriveATI Radeon 9700 ProCH yoke/pedalsElite Multi quadrant- serial19" inch monitor-Soundblaster PCI 512Win XPCommercial ASEL- Instrument 285 hoursAOPALawyerPilots Bar Association"Men without dreams are never free, twas thus this way and thus will ever be."

"LawyerPilot" (what's your name, by the way? - it'd be quite nice to put it in your signature, as it would actually go by the forum rules),Can you look into your registry settings and tell me what this key might point to?"HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft GamesFlight Simulator9.0EXE Path"I bet you have a corrupt FS9 installation - this should point to your D:Program FilesMicrosoft GamesFS9. (if that's your correct installation). What the error message actually shows is that your FS9 registry setting is not set properly.(The FS2002 error message is a misnomer - the code actually *IS* looking for an FS2004 folder but the error message doesn't actually convey it - sorry about that, it's fixed for the next patch).Think about it this way too: Had this been an issue in general, every other FS9 customer would have been complaining as well... we've had a couple complaints - all of them turned out to be bad customer installations.In any case, address me privately by email if you wish to look into this further (and if this post doesn't resolve the issue).

That's exactly the problem. The FS9 EXE Path is pointing to FS8 instead of FS9. I've had the same problem here a couple of times. Easy to fix. Just change the value from "FS2002" to "FS2004".Doug