Latley I've been having this anoying problem with my keybord in FS9. The 2 won't work. For example, the other day I was preflighting the Project Open Sky 757 and the cargo doors wouldn't shut when I hit Shift+E+2. They eventualy shut after pressing those keys repeatedly. Also when I switch engines to control I can never get engine 2 linked with 1 when I press E+1+2 and can never push back pressing Shift+P+2. I want to know if this can be fix and how. I would appreciate it. Thanks.

Please pardon me if I am misunderstanding what you said here but here goes. You said:"... the cargo doors wouldn't shut when I hit Shift+E+2."It appears to me that you are saying that you hit Shift and E and 2 all at the same time. If this is so, then I believe that you are doing it wrong. The proper procedure is Shift+E, 2. That is to say, the Shift and E keys simultaneously, then the 2 key by itself.Likewise, to enable two engines the keystrokes are e, 1, 2. Each key individually and one right after the other.Finally, to push back, press the Shift and P keys together, then press the 1 or 2 key by itselt to determine which way the tail will turn (Shift+P, 2). (after pressing the 1 or 2 key, the plane will move straight back for a ways before it turns.)I hope that I have understood the problem and helped you to solve it. R-

If it's a keyboard problem then you would have had trouble typing the "2" in your post. If that's so you'll probably want to pick up a new keyboard. It's not really worth fixing a keyboard anymore. They are pretty cheap nowdays (around $10-40).

I made the mistake on how I hit the keys in my first post. I hit them Shift+E, 2 ,not Shift+E+2, sorry about that. The 2 on my keyboard works, and in FS9 works for a little while then stops and then after a little bit it works again. When I hit Shift+E, 2 the main door closes as I hit 2. Hopefully this will carify my problem.

>I made the mistake on how I hit the keys in my first post. I>hit them Shift+E, 2 ,not Shift+E+2, sorry about that. The 2>on my keyboard works, and in FS9 works for a little while then>stops and then after a little bit it works again. When I hit>Shift+E, 2 the main door closes as I hit 2. Hopefully this>will carify my problem.If the aircraft you are having trouble with has it's own add-on panel then you may be experiencing what I have found to be an all to common problem.This sounds like a mis-behaving gauge. One that is sendingKEYcommands on every simulation cycle. If so, what happensis that after you send yourfirst keystroke, the offending gauge sends a KEYcommand, breaking up the sequence.When you enter your 2nd keystroke, FS9 sees it as the firstkeystroke of a new command.There is a nice little utility gauge by Doug Dawson calledEVENT LOGGER that you could use to determine if this isindeed what is causing your problem. You might then be ableto delete/replace the offending gauge with another one thatworks as it should, sending "KEY" events only once per triggeringevent. Paul

Wow Paul, that's good information. I have fought this problem on several panels and usually just quit using those panels. Perhaps now I can fix them. Thanks. R-

>Wow Paul, that's good information. I have fought this>problem on several panels and usually just quit using those>panels. Perhaps now I can fix them. Thanks. R-After I posted I was checking out a panel that wasjust released and discovered I had lost control of the throttles ( stuck on Engine 1 ).I used the utility to isolate the problem to the cowel flapsgauge. At cowel flap settings of 0 and 100% everything was finebut at other increments of the cowel flaps a continuos KEY command was being generated. The code LOOKED logically OK but apparently rounding errorsin the math operations of one statement caused the problem.Turns out this gauge is originally from another well designedpanel on a widely distributed aircraft which I checked and italso has the problem.I won't say what aircraft/panel it is as I intend to contactthe original panel designer to make him aware of the problem.If you suspect a problem of this sort just stick the event loggerin the panel.cfg temporarily and check the results.If the KEY statement that's repeating doesn't point to aspecific gauge you may have to go in and comment out groupsof gauges until you isolate the offending one. Paul