GMark

Airforce2, Thanks for posting the item regarding Remove ATC. Resolved my CTD issue as well. :D GMark

Pete, The culprit is a file for a Kensington mouse which I use. The filename is kmu_run.exe. I don't know what it does (it has a companion called kmw_show). But the kmu_run was the one that freed-up FS9 (which now overall loads faster to the initial configuration screen as well). I think I'll send a note to Kensington support and find out what the file does and how to prevent it from loading. The mouse works fine without the process running. Cheers! GMark@KCVG

Pete, I went through the list of active processes and removed a number of them. And Voila! FS9 loaded without failure. So the culprit is one of those processes. I will try and narrow it down to the specific process and see where that leads. By the way, I did get my FSUIPC registration in my email as well.

Pete, I will zip the file and send straightaway. I did the windows thing but there are no error messages. The situation is more of a program loop situation which is taking up all of the CPU resources. In the Task Manager you can see that FS9 is working feverishly along with a "tmp" process. Overall, FS9 is getting about 50%, the tmp process about 10% and the system idle at about 45-50%. All of this varies up and down to a degree. I found that if I raised the iexplore priority to "realtime" and open and closed the FS9 window (maximize/minimize) a thousand times or so, whatever is getting hung up would get terminated long enough to slooooowly get the percentage of loading (fly now - 172/KSEA) to reach 100%. However, even when that was done, the sim was obviously degraded to a framerate of between 3.5 to 4.0 frames/second. Let me send the modules file now.

FS9 created a new FS9.cfg. I have a list of the installed modules in a .jpg file but the forum will not permit me to post an attachment.

So positively aggravating! Removed the .cfg file and when FS9 was reloaded it brought up the base 800x600 or 640x480 window (hard to tell anymore). Selected Fly Now for the basic 172/KSEA configuration and obtained the same result - hung on loading scenery objects. This is truly bizarre.

Pete, here is the short story... ********* FSUIPC, Version 3.41 by Pete Dowson ********* Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL) User Name="" User Addr="" FSUIPC not user registered WIDEFS not user registered, or expired Module base=61000000 ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E WeatherOptions(Orig)=0000B027[0000B027] InitDelay: 0 seconds WeatherReadInterval=4 LogOptions=00000001 DebugStatus=0 3391 System time = 18:56:05 3391 C:\Program Files\Microsoft Games\Flight Simulator 9\ 3391 System time = 18:56:05, FS2004 time = 12:00:00 (00:00Z) 5391 FLIGHTS\OTHER\FLTSIM.flt 5500 AIRCRAFT\c172\Cessna172SP.air 6031 Aircraft="Cessna Skyhawk 172SP" 52016 C:\Documents and Settings\GMark\My Documents\Flight Simulator Files\UI generated flight.flt 53406 Clear All Weather requested: external weather discarded And just for the record, I have applied for the license to FSUIPC (well at least I spent my money but do not yet have confirmation... not sure what I would do with it... but I have taken advantage of the FSUIPC interface over the years and it's probably time to pay a few dues). GMark@KCVG

I encountered something similar to the crashing issue but instead FS9 just hangs at 0%-1% when "Loading Scenery Objects". This showed up when I licensed the new ATR from Flight 1. Prior to this my FS9 did not have any FSUIPC in the Modules folder and everything was working fine. They bring FSUIPC along when the ATR is installed - current version is 3.4.1.1. The long and short is that with FSUIPC in the modules folder, FS9 hangs every time. If I remove it, the FS9 is happy, but I'm not since I can't use the new ATR. I have a similar system to Peteflyers: P4/HT 3.0 Ghz, 1 gig DDR, Nvidia 4400 (64mb), XP Home with patch, FS9.1. I did have a mix/match of 9.0 and 9.1 but now all modules are at 9.1 except for the few modules that the ATR brought along. I do not have FSAdventures.dll on my machine. I am not presently licensed for the FSUIPC but that may have to change - no problem.