Jim has right. CS737 seems to be the problem. If CS737 is default flight and the plane has become corrupted, fsx cannot see it anymore, and becouse of that fsx cannot load default flight. This is what i would do:

 

 - reset FSX default flight. Here is the link how to do that, by PMDG: http://support.precisionmanuals.com/KB/a90/j41-default-flight-related-issues.aspx

 

You can see there some more info about default flight

 

 - uninstall CS737 completely 

 

 - run CCleaner to remove all temp files and unused registry keys(this will remove CS737 from registry too)

 

I see you have tried install/re-install CS737, but you need to do that again and to reset default flight

Edited August 20, 201312 yr by B247NG

I think you and Jim are showing me signs of hope. However, I had not or never used cs as my default at start up. I use the baron 55 by Miltvz. I was in the process of changing the baron to the CS737 but when there were no 737-200 in the airplane hanger I proceeding back to free flight with the baron but that is when FSX locked up. I have downloaded CCleaner and now cleaning up all the junk stuff that was placed on my home page do to ads. I just didn't catch it in time. Finally back to my home page and will run the cleaner. I analyzed the registry but didn't see any real thing that stood out to be a problem like a 737 etc. There were several items in the registry that may need fixing but was mainly MS office and other software outdated.

I really thank you guys trying to get me back into the air. I am very grateful for your time and assistance. I am gradually losing most what little hair I had before this started.(LOL)

 

Will check the PMDG and see if I can check out the default.

Yah I have had a few heart attacks myself not fun Carl, maybe you could try this uninstall addons one by one and check your simulator after each uninstall you might get lucky then you would not have to install all of it again - just a thought

 

Make sure this file (uiautomationcore.dll) is not in your main folder until you figure this out please 

Trying to avoid a complete reinstall or removing other addons, this is what I would do:
 
1.- Uninstall or move the CS 737 Aircraft folder to another location. Plus whatever files (gauges) you recently added.
2.- Delete or rename fsx.cfg (Re Tweak later)
3.- Make a copy of your dll.xml somewhere else and create a clean dll.xml

Here is a clean dll.xml with only FSUIPC added. (Assuming you have the SDK installed)
Note: FSUIPC must be the latest version, because of some registration changes/problems as Pete recently stated.
 

<?xml version="1.0" encoding="Windows-1252"?>

<SimBase.Document Type="Launch" version="1,0">
  <Descr>Launch</Descr>
  <Filename>dll.xml</Filename>
  <Disabled>False</Disabled>
  <Launch.ManualLoad>False</Launch.ManualLoad>
  <Launch.Addon>
    <Name>Object Placement Tool</Name>
    <Disabled>True</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>Traffic Toolbox</Name>
    <Disabled>True</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>Visual Effects Tool</Name>
    <Disabled>True</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
        <Name>FSUIPC 4</Name>
        <Disabled>False</Disabled>
        <Path>Modules\FSUIPC4.dll</Path>
    </Launch.Addon>
</SimBase.Document>

 
 EDIT: If I recall correctly CS also adds info to the exe.xml file, make sure that file is correct or just rename it while testing.(Might not exist on some installations)
 
4.- Delete or move all files from -> C:\Users\<Your Name>\Documents\Flight Simulator X Files (the log will be recreated by FSX later)
 
5-  Download Flight1’s safe startup flight from here: Important Start Up Flight For Complex Aircraft, the link to the file is right there. 
Download and run it. It is a small exe that will place 2 files on your C:\Users\<Your Name>\Documents\Flight Simulator X Files folder namely SafeFSX.FLT and SafeFSX.WX.
 
6.- Double click on SafeFSX.FLT. Doing so will force FSX to start and use that saved flight.
 
Hopefully that fixes whatever is keeping FSX from starting up. If so, then later we can start rebuilding your dll.xml.

Rich,I have just about tried everything that has been suggested with no success, so it is now getting very gloomy at the home front. I thought Zeljko and Jim gave me hope with their last posts but it didn't. After the uninstall of the 737, cleaning, removing the situation statement in the config and finding other 737-200 files in my fsx cfg to remove,I almost thought FSX might get me to the startup. There is one other item that not sure if it matters but I do run with DX10. Been using it all year with great success. Is there a way to go back to DX9 by changing the fsx.cfg. I guess as a final resort as you suggested is start to delete some planes one at a time. Would just cut and paste each aircraft one at time to desktop folder prove any benefit? That would save some time. Would plugging in an older fsx.cfg which was used with DX9 be worth a try?

Ramon,Thanks for your help. I will sure give it a try.

Carl

Yes you can enable DX9 via fsx.cfg, just change  D3D10=1 to D3D10=0 under graphics.

 

But First thing that needs to go while you get FSX running is a tweaked fsx.cfg. (Need to remove all the [Trusted] section, all tweaks and at the same time will take care of the Situation parameter). FSX will rebuild it and then You can tweak it later, when FSX works again.

 

Cheers.

Carl yes go back to dx9 and delete your fsx.cfg file let it build a new one.

Ramon,

Thanks for your help. You have really done some background work. Certainly appreciate all the efforts you guys have been doing for me. As you may have noticed I did try to rebuild the fsx.cfg but it only took about 5-10 seconds before windows stated "fatal error will try to find problem then fsx not starting".

I have tried item 1 and 2, not sure about 3. Do you mean dll.xml? Is there a difference

 

 

I have tried item 1 and 2, not sure about 3. Do you mean dll.xml? Is there a difference

Yes, the file is dll.xml. Just make a copy of it, then open dll.xml with Notepad++ and copy paste what I quoted on the previous post. (Sorry I mispelled it on my previous post, I corrected it now. :wacko: )

 

Don't forget steps 4-6 plus if you have an exe.xml file also rename it while you get FSX up and running.

Ramón's suggestion with clean DLL.XML is good. Starting with clean DLL.XML and adding addons one by one(if fsx starts). If not, try with clean fsx.cfg too.

Fsx should start with clean DLL.XML and clean fsx.CFG. I'm going to sleep and i'll check tomorow this thread again - i hoppe problem will be solved

 

Carl yes go back to dx9 and delete your fsx.cfg file let it build a new one.

 

 

Rich, That is one of my problems it will not let a rebuild of new fsx.cfg. It always stops within a few seconds on start up. Was thinking about just renaming one of my older config files and see what would happen. It is getting to the point I have little to lose.

   

 

Rich, That is one of my problems it will not let a rebuild of new fsx.cfg. It always stops within a few seconds on start up.

I have read about that problem, where FSX won't even create a fsx.cfg, it always seems to be related to a corrupt save/startup file.

 

Delete fsx.cfg, make a clean dll.xml, try steps 4-6 and FSX should start.

 

Cheers.

Ouch got yah Carl, yah good idea if you have an older cfg file give it a go to get you in change the dx9 switch in the external menu before you launch a flight

 

Thinking one of his addons got tweaked some how so an uninstall of payware staring with aircraft is the way to go also with your idea of fresh XML file

 

Uninstalling addons is lot easier than a rebuild - give that a try

 

 

but I do run with DX10. Been using it all year with great success.

 

DX10 should have no affect whatsoever (plus I knew you used DX10 as you were one of the first to get on board with it when Steve released the DX10 Shader fix).

 

 

 

make a clean dll.xml

 

There should be some older versions in the folder where the fsx.cfg is located.  Most addon developers save the old one and issue a new one (like dll.xml before addon manager, etc.).

 

Look in your main FSX folder too and see if there are any remnants of that special gauge you installed for the CS737.  Sometimes there's an initiator file (*.ini) placed in there that is loaded when FSX is loaded.  Gee, I thought this would be a simple fix.

 

Best regards,

Jim

Gosh Jim,

 

I never thought I would still be here at 9pm trying to get any kind of airplane in the air. I have some of the best minds at AVSIM working with me ....and still I can't even get 20 seconds of start up before I get fatal error. I know I must be doing something wrong with all the help I have received. I just finished using the 6 step program that Ramón gave me. All went well until I clicked the SafeFSX.FLT exe file. It took me to a folder but not FSX so I assumed I would have to browse to the desktop and click the FSX icon. Of course it gave me the same old message. The only question I may have on Ramón's post I put his copy shown inhis message into the clean dll.xml file, in other words the dll had his writeup.

I do have several old dll files that might could be used. The only new gauge that I placed in the Gauge folder was "dsd_fsx_xml_sound.gau", which has been deleted.

 

Well maybe tomorrow will be a brighter day.

 

Thanks everyone for your help..