Just loaded v1.0 and have 2 issues: No landing gear is visible and front cargo compartment door open light will not extinguish when door closed.

Firecapt_32 wrote on Apr 22^nd, 2012 at 1:47am:

Just loaded v1.0 and have 2 issues: No landing gear is visible and front cargo compartment door open light will not extinguish when door closed.

Did you do a complete fresh install on the -200? Make sure the all the expansion packs are removed before you install the full version.

Yup.... uninstalled .9 and installed 1.0 from scratch. Maybe I'll have to try it again.

Since i went from V 9 to V 1.00 The 737 has default engine jet sound for FSX and the Yoke does not dissapeer when yoy click on it

Try to unstall all and reinstall a proper 1.0 version

I don't have this problem

Mine works fine.

This is what I did:

1) Uninstall the 737-200 v0.9
2) Make sure the [FSX]\SimObjects\Airplanes\CS_B737-200 folder has been removed. If it hasn't, delete it.
2a) Do the above for any Expansion Models you have installed (CS_B737-200ADV and CS_B737-100).
3) Make sure the  [FSX]\Captain_Sim\737 folder has been removed. If it hasn't, delete it.
4) Reboot your computer.
5) Install the 737-200 Base Pack v1.0, then the Expansion Models in any order (737-200ADV, 737-100 and 737-200C\F)
6) Reboot your computer.
7) Start FSX, select one of the CS 737's and go for a flight. It should be working fine.

Something to consider. I use Avast Antivirus (free) and something changed recently. Every time I tried to install the aircraft a window popped up say it was a high risk file and asked if I wanted the file terminated. No matter what I did, it terminated the file so I could not install it.
There was a simple way around this that required me to stop the "Shields" for 10 minutes while I installed the 737 and after ten minutes they would automatically start again, but I was finished installing the 737's by then.
The more difficult one to do was to add the folder where I downloaded the files to the "excluded" list so they were not going to be terminated by Avast and I did not have to turn the "shields" of any more. I had to add the FSX folder to the "Excluded" list as well because it was terminating the uninstall programs for the 737's, just like it did to the installation files!

Mark

Reinstalled it again and all works fine now.