Hello everyone, I have been having CTD's and now I get the blue screen of death on my Win2000pro system. When this happens, It also says a memory dump has been completed. All of a sudden this has happened everytime on exiting FS9 since yesterday. Also this morning my keyboard was not being seen on bootup, then the next hour on bootup, I got the system hardware unplug device on the taskbar for usb devices. I also got a FSUIPC not accredited message while in the Majestic Dash8 out of nowhere. I don't know what is going on here.My whole system is going crazy out of nowhere!!! All of a sudden the past week since I installed the TNCM scenery and uninstalled it this started happening. I just reinstalled my nforce MB drivers and my display driver. I also noticed a scenery cfg file where the FS9 cfg resides in the documents and settings folder as well as in the main directory for the game. Can either, or both be deleted like the fs9cfg, so they can rebuilt? The contents of both look the same. Why would it be in two places? I also noticed the GDIPlus.dll in my sys32 and in the FS9 main directory. Thanks for your help. I had posted about my CTD problem in another thread, but this might do the trick, I hope. I am at a loss what's going on here.I am getting a new system soon, but can't go one day without a few sim sessions. After several years and everyday simming, I climb the walls without. Best regards, Jeff

You cannot delete the scenery.cfg like the fs9.cfg. It will not rebuild itself like the fs9.cfg and you'll never get your sim started. You should check the scenery.cfg in your main FS9 folder occasionally and make sure the Areas/Layers match and are in sequence. Sometimes it gets corrupted especially when you constantly add/uninstall scenery. Sometimes the sim will start with it corrupted like this, sometimes not. Do not delete the GDIPlus.dll in your system32 folder. Not sure about the FS9 directory. It's in both places on my system too so recommend you do not touch this file.Jim

. . . . . and migrate to Windows XP Pro and update to SP2. . . pj

On CD 4 - the one which should be in your drive - there are two default scenery.cfg files - one for the regular full install and one for the compact install which pulls scenery from CD 4.Copy that to your FS9 folder - but name it NewScenery.cfgWhenever you make changes to the scenery library in FS, it does not record the changes in Scenery.cfg, but it creates a NewScenery.cfg file - which replaces Scenery.cfg when you next start FS.That should put you back to the default setup with no addons installed.But I'd also recommend you review each of the scenery folders under the main scenery folder. Many addon developers have a habit of modifying and distributing the stock APnnnnn.bgl files, and some of the others also. You should restore all the originals until you get FS running, then put those modified files you absolutely must have back.Though my usual practice is to decompile their modified file - extrace the changes and put it into a proper file in the SceneryGenericScenery folder like MS tells us to do in the SDKs.

Thanks everyone for your input. The driver reinstall for my MB and video card seemed to have stopped the blue screen on exiting FS9, but I don't want to say for sure yet. As far as the scenery info, I will look into this. I am going to be extra careful for now on when installing scenery. Valuable lession learned here. Thanks again, I will post any new developments. Best regards, Jeff