Is there a way to get rid of the message that comes up when trying to load certain FS2002 aircraft that says "Incompatible Aircraft or Software. Do you want to load this aircraft? Click No to disable this software." If I do click yes, they load fine, so I don't need to see this message every time.

This usually happens with panels that use older versions of fssound.dll. Open your fs9.cfg and add the following entry:[OldModules]FSSound.dll=1Hope this helps,Miltos

It involves an FS9 config adjust, and moving FSSOUND.DLL to your FS9 root, not "modules".FLYing? It's cool. Trillions of birds and insects can't be wrong.

Actually I have version 1.5.2 of FSSound.dll (I believe this is the FS2002 version, correct me if I'm wrong) in my Modules folder and never had to move it to the FS9 root folder. All I did was add the OldModules entry in fs9.cfg.Rgds,Miltos

I already have the fssound.dll entry under oldmodules. I moved the fsssound file to the root directory, but I'm still getting the message. For the Sopwith Camel, it references the MDL file.

>I already have the fssound.dll entry under oldmodules. I>moved the fsssound file to the root directory, but I'm still>getting the message. For the Sopwith Camel, it references the>MDL file. The model itself is incompatible with FS9. You aren't going to get rid to of the message unless you replace the .mdl with a compatible version (which, AFAIK doesn't exist!)...

<<<<<<<<<>>>>>>>Not necessarily so, Bill.scnrfrq (do you have a name?) you haven't said whether or not you are trying to load your FS2002 aircraft in FS9, but I'll presume you are, otherwise you wouldn't have posted.Firstly, FSSound.dll is not the culprit in this case. The 'old modules' section recommended for insertion in your FS9.CFG file is a good thing to do in any case. FSSound.dll should be in your MODULES folder; I don't believe it does a thing if it's in your root FS9 folder.Now, to solve your problem. When you get that message at any time, it will be because it is possible that one or two of the animations in your FS2002 model (which is probably made with FSDS rather than a later modelling version such as FSDS2 or GMAX) may not show in FS9. However, you are ALWAYS safe, in my experience, to say that you do NOT want to disable animations with that model.If you do that, you will not see the message again on subsequent loading.If you say once that you DO want to disable animations, then you will ALWAYS see this message when loading the aircraft. This sounds as if this is what you have done here. To rectify things, open your FS9.CFG file and look for a section called:FrameCallNoWarnwhich will be in square brackets. Under it, look for your rogue aircraft. Let's say it's a DC-3 named as follows:Douglas DC-3 DDA PH-DDZ=0Change it to this:Douglas DC-3 DDA PH-DDZ=1Save the file. Now when you next load the aircraft, you will not see that annoying warning again.Do this for any aircraft that give you the problem that appear in this category in your FS9.CFG.And just to recap, I recommend that you always say NO to disabling animations. Then you will only ever see that message once per aircraft when loading FS2002 aircraft into FS9.Mark Mark "Dark Moment" BeaumontVP Fleet, DC-3 AirwaysTeam Member, MAAM-SIM[a href=http://www.swiremariners.com/cathayhk.html" target="_blank]http://www.paxship.com/maamlogo2.jpg[/a]

The name is Tom. I checked my FS9 .cfg file. Only some of my planes are listed, and they all have an "=1" after them. The Sopwith Camel, which I have the problem with, is not listed at all. What can I do now to fix this?