Hi folks,Here's the synopsis: Scenery conflict-> FS9 crashed to desktop-> comp. unresponsive-> blue screen error message -> reboot-> Most Keyboard Commands NOT Working in FS9Scenery conflict: Sandmann's Columbia River Gorge and Taburet's St. Helens.I had just installed Columbia River addon, flew from an airport in the gorge, beautiful!, turned north toward Mt. St. Helens, maybe 10 miles from the mountain -> crash to desktop, completely unresponsive-> a minute later, Error Message: "A problem has been detected and windows has been shutdown to prevent damage to your computer. The problem seems to be caused by the following file: ialmrnt5.dll. If this is the first time you've seen this stop error message, restart your computer. If this screen appears again, follow these steps. The device driver got stuck in an infinite loop. This usually indicates a problem with the device itself or with the device driver programming the hardware incorrectly. Please check with your hardware device vendor for any driver updates. Tech. Info. STOP 0x000000EA (0x87c7020, 0x86978E68, 0xF79BECB4, 0x00000001) ialmrnt5 Beginning dump of physical memory. Physical memory dump complete. Contact Tech. Support for further assistance." I rebooted, no error message, no problems, started FS9 at same airport in the gorge, looked OK except rudder was stuck left and direction gauge incorrect, several other similar problems, screen prompts told me to hit some keys to reset stuff and it worked, except the rudder didn't work (didn't work from yoke either) and most keyboard commands didn't work. After several more tries with other planes at other locations, the rudder straightened out and worked using yoke toggle, everything works from yoke now, still few keyboard commands work. Rudder and others controlled by yoke don't work from keyboard. But can now fly. Flew back to St. Helens. DUMB. Same crash to desktop. same error. Then I started thinking.... Sandmann's readme for the gorge addon mentioned conflicts with other addons. So I got rid of Taburet's St. Helens addon. Flew->NO CRASH. Beautiful scenery. Still few keyboard commands working. Tried several other locations. No change. FRAPS works, shows 25-30 fps; frame rate max is set at 20 in fs9.cfg. ??, Interesting. As with most key commands, frame rate does not display with key command. I don't think its a device or driver problem. Just the addon conflict. I have all the current driver updates, and all other updates I could find as well. The file ialmrnt5.dll is in the i386 folder, the system32 folder and the C:driversvideoonboard folder. It's the controller hub for the graphics driver. OK, I could go on, but bottom line, the keyboard commands aren't working in FS9. I suppose the first question is, What happened? The important question is, How do I fix it? Help.Rob

I'm a little bit confused. You went into an awful lot of detail on the crash, but your question seems to only be asking why your keyboard commands are no longer working.This has happened to me before. The keyboard commands are stored in fs9.cfg. A CTD often causes the fs9.cfg file to be only partially written to disk, meaning much of its content does not get written, including the keyboard commands at the end of the file. If you have a backup fs9.cfg, just copy your backup over the current version. If not, you'll probably want to just delete the current fs9.cfg, and restart FS9 and let it write a new one (then edit it to what you like).Thomas[a href=http://www.flyingscool.com] http://www.flyingscool.com/images/Signature.jpg [/a]I like using VC's :-)

Thomas said, "You went into an awful lot of detail on the crash..." I'm fairly new to FS9 and here as well. My experience from previous posts is that giving as much info as possible is better. I try to anticipate others' questions about what, when , how, etc. Perhaps i put more than needed in my post. Thomas said, "your question seems to only be asking why your keyboard commands are no longer working." Actually my FIRST question was, "What happened?" I want to know so I don't do it again. I'm assuming it was the scenery conflict, but maybe not. So I asked, "What (people with more experience think) happened?" based on my description. Perhaps I don't know enough to even ask the right question(s). What would have been a better question?To the point. I did what Thomas suggested, I deleted the fs9.cfg. I thought I had a copy, but when I tried to copy it over the current version, a message appeared saying it couldn't do it with a text file, or doing that would change the file somehow. (I made the backup by creating a new word document and pasting the contents of original fs9.cfg into it. Apparently that isn't the way its done. Now, thinking about it, I could have just copied the original and pasted it back next to the original with a different name, like xfs9.cfg. Is that correct?)So then I did the second thing Thomas suggested. I deleted the fs9.cfg and started FS9. The splash screen has been looking at me now for 30 minutes, nothing is happening. I apologize if I missed something. What next?Rob

Hi,Bearing in mind that I really know nothing about computers.Each time you start FS9 the cfg is rewritten.What seems to be happening to you is that the conflicting sceneries are stopping FS9 getting going.Because I generally panic when things go pear shaped I would delete the sceneries and any other bits and then try to restart FS9.Apologies if you are way ahead of me!Andy.

Hi Rob,I'm sorry. Now that I've gotten you further into this mess of trouble, I'm not sure if you'll want to take any further advice from me, but, hopefully, I can help get you out of this mess.I still stand by what I said, when you CTD, FS9 can end up only writing a partial FS9.cfg. That is most likely why your keyboard commands stopped working, because the keyboard mapping is at the end of the FS9.cfg file. Doing what I said has fixed things for me in the past when I have had crashes similar to yours.Based on your comments, I am working under the assumption you have knowledge of working with files in Windows.Could you say exactly what the error message was that you got when you tried to copy your backup over the original? From your description, it sounds like it was telling you that you were changing the type of file that it was from a .txt file to a .cfg file. Scary, perhaps, but this is exactly what you wanted to do.Did you keep backups of any of the files you were working with? In the future, before you delete anything, always back it up. I'm sorry I didn't say this earlier.At this point, bring up the Windows task manager and kill fs9.exe. Look to see if a new FS9.cfg file was created. If so, check it out and see if it looks normal to you. Compare it to the fs9.cfg.txt file, the two should be very similar. If it does, try to start FS9 again. If you still have a problem, delete the new FS9.cfg file. Copy the FS9.cfg.txt file and rename the copy to FS9.cfg. Ignore the warning that you are changing the type of file it is.Start FS9 again. Did it start ok?If this doesn't work, it could be that your Scenery.cfg file got corrupted as well. If that is the case, download a file called Flightsim manager http://library.avsim.net/esearch.php?CatID...util&DLID=76742This program has many tools for fixing issues with FS9, and I believe is an essential tool for keeping a healthy installation. Go to the button with the fisher price doctor on it and have it check your scenery.cfg file and then have it fix it. Let me know how you do.Thomas[a href=http://www.flyingscool.com] http://www.flyingscool.com/images/Signature.jpg [/a]I like using VC's :-)

Whoah, slow down. Don't delete them yet. As I noted below, first lets make sure your FS9.cfg file is ok using the steps outlined below. Then, if that doesn't work, use Flightsim Manager to check your scenery.cfg file. Then write back and lets move from there.Let me know if you need instruction on how to work with files and FSM.Thomas[a href=http://www.flyingscool.com] http://www.flyingscool.com/images/Signature.jpg [/a]I like using VC's :-)

BTW, if you click on my site below, and go to the menu item "Microsoft Flight Simulator" on the left, I have some instructions you may want to read on installing and organizing your scenery files, as well as lists/links of what I think are essential downloads for FS9 for scenery, utilities, and aircraft freeware and payware.Thomas[a href=http://www.flyingscool.com] http://www.flyingscool.com/images/Signature.jpg [/a]I like using VC's :-)

Were you able to fix your problem?Thomas[a href=http://www.flyingscool.com] http://www.flyingscool.com/images/Signature.jpg [/a]I like using VC's :-)