ON HOLD: Option 1 below is not working for me now for some reason. Please ignore it until or if I find the problem.In playing around with the combinations possible I have discovered the following. I thought possibly this might be of some use to someone else.The following is applicable assuming that the DF737-400/FFX merge has been installed and is working properly as per the installation Mr. Peter McLeland has been kind enough to offer:The one limitation to this installation has been that when the required line item, "MakeItVersionFS2002=Yes" is inserted into the FSUIPC.ini file, some other FS9 addon's will not function (i.e. fsmeteo). I have discovered that after you have started up FS9 and selected the DF737-400, that you can go back into the FSUIPC.ini file and remove "MakeItVersionFS2002=Yes" (WITHOUT SHUTTING FS9 DOWN). The aircraft continues to work properly (including course selection, heading selection etc.). FSmeteo then also works correctly, and I am assuming the other third party programs dependant upon FS9 configuration do also. The only liability I have discovered is that after you shut FS9 down, restart it and select the DF737 again you will get the age old series of error messages. What this amounts to is that every time you want to select this bird, you must go back and add"MakeItVersionFS2002=Yes" and go through the same sequence again in order for EVERYTHING to work correctly.To me personally it is a very slight nusiance which I am tickled to live with in order to be able to fly this great bird and still have everything else working properly as well.The following are the options as I see them:1. Operate the DF737-400 as described above. After removing "MakeItVersionFS2002=Yes" all other aircraft and third party programs useing FSUIPC will be back in their standard configuration and should work properly. In order to fly the DF737-400 the next time you startup FS9, you will have to add "MakeItVersionFS2002=Yes" again. In order for everything else to work normally in FS9 you may then remove it (WITHOUT SHUTTING DOWN FS9) if you want to fly the DF737 with everything else working properly.2. You may choose not to use FSUIPC at all. If you do so, everything can work properly in the DF737 with the exception of course selection which will be limited to 10 degree increments. In order for me (and I assume everybody else) to select the DF737 without FS9 crashing to the desktop, you must disable the "DF734Nj6!IPCI" gauge in your panel.cfg (ONLY FOR THIS OPTION)A liability to disabling or operating without FSUIPC is that some of your other aircraft may not work without another crash to the desktop if they have panel gauges dependant upon that program (i.e. My "RKG_Speed!TAS_GS_S" gauge which I add to all of my panels). I am sure there are others, but I don't know which they are.3. Operate without adding "MakeItVersionFS2002=Yes" to the FSUIPC.ini file and retain FSUIPC. The DF737 will operate normally with the exception that the course selection is inoperative and heading select on the autopilot is extremely sluggish relative to banking to a new heading. You can add a VOR for course selection, and simply help the bank manually with your yoke or Joystick. She will roll out on the selected heading. This is what I have been doing for what seems like forever, and is a bit of a Micky Mouse operation IMHO. The upside to this choice was that all items dependant on FSUIPC were still operable.I am sure there are probably other combinations, and someone smarter than I which doesn't take much doing may have discovered a better mouse trap, but I believe the first option above will work for me. Hope this is of some help to somebody!Happy flyingRTH

"In order for me (and I assume everybody else) to select the DF737 without FS9 crashing, you must disable the "DF734Nj6!IPCI" gauge in your panel.cfg"This is what I have done, and that is in FS2004.If there is another way, I'd love to know what it is.I have a registered copy of FSUIPC and it sure does not likethe above gauge...

Bert:You are 100% correct. Form your quote I was not fast enough I am afraid. I edited option two to include that this was true only if one did not use FSUIPC. Sorry if I mislead you. That statement was only meant for those conditions. If FSUIPC is implemented, you are right that this gauge is necessary. Without it, it must be disabled.Good luck:RTH