This airplane flies just fine but it's not dispatchable with the master caution and fire warning lights not working; plus, engine fires simply aren't detected at all, and even if they were, the fire bottle discharge handles are INOP and won't put out the fire!

Here's a download that will fix all this:

http://www.fscaptain.net/downloads/Fix_CS732.zip

The ZIP contains a README explaining how to install and with some notes on the implementation.  I really don't have time to get those lights working with the reset and recall functions, so I've wired them into the various indicator signals so that when any of them are on  the master caution and the category warning lights will be on.

When the light is on you know there's something wrong with your airplane assuming your engines are running.  Start looking for the warning light which will be on somewhere.  The category light will give a hint of where to look, e.g. OVERHEAD or DOORS.

The fire problems are fixed, except the bell doesn't jingle when there's a fire but the lights will light up (master and handle) and pulling the handle will put out the fire.

Now I can fly this wonderful old airplane in the line.

Enjoy!
Dutch

First, important for ALL users of this fix, re-download it if your version is dated before November 28 at 9:30PM.  There was a bug that caused the captain's master caution to come on even when it shouldn't during nighttime.  If this bug shows up, re-download and re-install the two CABs. 

Coolp, if the two cabs aren't there but they've been expanded into folders, just rename your existing folders and expand these, or leave them in the CABs if you want, they work either way.  When I installed the 737 it put CABs into my panel folder, I had to expand them manually to get at the contents to fix them - you are lucky!

It'll be obvious when you have it working - the master caution will be lit when you turn on the battery.

Dutch

Mine is csp732_1000.exe dated 7/9/2012 7:05 PM size 199,533KB.

Okay, I installed to a testbed, and indeed the distribution has folders not CABs.  I got confused with the 727 which has its stuff in CABs and thought I'd expanded the 737 cabs like I had the 727 ones and therefore to be compatible I had to distribute the changes in a CAB.

So, have updated the fix with the folders included instead of the CABs.  You can re-download it or just expand the CABS doesn't make any difference.  Thanks for spotting this...

Entirely my mistake!

Dutch

Sigh.  Let's try this one more time.  Thanks for your patience in beta testing this Coolp.

Download it again and re-install.  The instructions have changed slightly because the structure has changed a little and the line in your panel.cfg has too.  This one should work.  One hopes

Dutch

Hello Dutch and CoolP,
gave it a try and have exactly the same result as CoolP described.
Downloaded the latest file version as you say.
Followed your instructions from Readme. (no CAB files here by the way)
in my case the next gauge number in [VCockpit01] is 18.
Tried almost every possible electrical config e.g. Ext pwr, gen1, gen2 but none of the MC annunciators showed up when supposed to (tried almost all amber ovhd caution lights by switching systems on and off.)
cheers, Lex

Well, it's working for me but I've tinkered with things here.  So I'll do a clean install on a test system and see what little tiny detail is missing.  Coding can drive you nuts, but we'll get it to work.

Dutch

Now it works. Thanks!   Looks very nice. Yes, cancelling the warnings would be nice too.  

See? We always want more. 

I restructured the contents of the zip file to make it so that following the instructions should result in everything falling into place.

Glad it's working!  I've been enjoying flying the 200 around for fun and familiarization but now I want to use it "for real" and I can't chance something going wrong and me just sailing blissfully along.   So, had to have this minimal warning system.

Hopefully CS will fix this properly in 1.1 and we can ditch this fix.  If not, maybe I can revisit it and put in the reset function.  Until then, at least a mech failure should be obvious, or if we start to push with a door open

Dutch

It's possible but I'm very busy getting an FSCaptain release out and already feel a bit guilty over the time I've spent on this.  Maybe after the next release is out some time will open up.

Dutch