Dear all,I finally got my copy of FS2004. When I installed it in my computer, it went fine. However, I cannot run FS2004 because it shows an error during the opening screen, described below:FS9 caused an invalid page fault inmodule FS9.EXE at 0187:004474f4.Registers:EAX=00000000 CS=0187 EIP=004474f4 EFLGS=00210246EBX=7c027075 SS=018f ESP=006beb14 EBP=00000001ECX=81d11bac DS=018f ESI=04edea50 FS=5b4fEDX=00000001 ES=018f EDI=00000000 GS=0000Bytes at CS:EIP:80 38 00 75 03 c6 07 00 56 ff 15 94 81 45 00 83 Stack dump:04edea52 04edea50 00000001 7c027075 0044751f 04edea50 0000001a 04edea50 006beb60 01b59d4f 004478a1 04edea50 00000000 00000005 006bf6cc 00000000I use Win98SE and my PC spec is as follows:AMD AthlonXP 2600+, MSI KT333 Ultra (lates bios and VIA 4in1 drivers), 512Mb PC2700, GF4 Ti 4600 (Driver 44.03). I have tried the suggested solution in Troubleshooting section, but without any result.Can somebody help me with this? Is it a fatal hardware error?Regards,japangg

Fs9 is a very poor written program with many bugs(at least in my belief and experience and reading about the majority of problems such as yourself) my advice--get a hold of MS tech support.

"Fs9 is a very poor written program with many bugs(at least in my belief and experience and reading about the majority of problems such as yourself) my advice--get a hold of MS tech support."What a load of bunk! Anything could be causing the problem, including issues on the system used. But I'm willing to eat crow if you can post the sections of FS9 code you feel are so poorly written. Perhaps your "experience" can enlighten us. I'm running FS9 on a system that has one foot in the "obsolescence" grave. It runs FS9 without issues....and I'd say that's true of most here.Rather than tell someone FS9 is buggy, start with the questions anyone who knows support would ask--system specs? Background apps? O/S?..... Driver versions?

Event Type: ErrorEvent Source: Microsoft Flight Simulator 9.0Event Category: NoneEvent ID: 1000Date: 9/11/2003Time: 5:06:33 PMUser: N/AComputer: *******Description:The description for Event ID ( 1000 ) in Source ( Microsoft Flight Simulator 9.0 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: fs9.exe, 9.0.0.30612, unknown, 0.0.0.0, 04f01a40.Data:0000: 41 70 70 6c 69 63 61 74 Applicat0008: 69 6f 6e 20 46 61 69 6c ion Fail0010: 75 72 65 20 20 66 73 39 ure fs90018: 2e 65 78 65 20 39 2e 30 .exe 9.00020: 2e 30 2e 33 30 36 31 32 .0.306120028: 20 69 6e 20 75 6e 6b 6e in unkn0030: 6f 77 6e 20 30 2e 30 2e own 0.0.0038: 30 2e 30 20 61 74 20 6f 0.0 at o0040: 66 66 73 65 74 20 30 34 ffset 040048: 66 30 31 61 34 30 0d 0a f01a40..

:) You must think I know nothing about coding... My challenge is still the same--show me the buggy code, not a debug excerpt from a system error. You know as well as I do that such errors can be caused from issues on the user system as well as errors in code. Unless you've written the perfect, bulletproof, systemproof code that is.... ;) If you are certain the code is buggy vs. an issue w/the user's system, you must have access to the original source, right? Maybe it's as simple as a semicolon left off of a statement, or a type mismatch? I'd like to know.... Really, I would...

Event Type: ErrorEvent Source: Microsoft Flight Simulator 9.0Event Category: NoneEvent ID: 1000Date: 9/11/2003Time: 5:54:04 PMUser: N/AComputer: *********Description:The description for Event ID ( 1000 ) in Source ( Microsoft Flight Simulator 9.0 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: fs9.exe, 9.0.0.30612, unknown, 0.0.0.0, 04f21a40.Data:0000: 41 70 70 6c 69 63 61 74 Applicat0008: 69 6f 6e 20 46 61 69 6c ion Fail0010: 75 72 65 20 20 66 73 39 ure fs90018: 2e 65 78 65 20 39 2e 30 .exe 9.00020: 2e 30 2e 33 30 36 31 32 .0.306120028: 20 69 6e 20 75 6e 6b 6e in unkn0030: 6f 77 6e 20 30 2e 30 2e own 0.0.0038: 30 2e 30 20 61 74 20 6f 0.0 at o0040: 66 66 73 65 74 20 30 34 ffset 040048: 66 32 31 61 34 30 0d 0a f21a40..Look, im not going to get in a flaming war with you. You must work for MS.In fact for someone to take it personaly like you are proves it to me. And look I know nothing about code, I only know that it crashes 9 out of 10 times. It has serious memory management issues when it comes to autogen of any type. Stutters etc. If you know something about code then team up with the people trying to fix this thing not bash users who report the obvious.My machine funs fs8 at 40fps everything maxed.latest drivers etc. this I get twenty if im lucky. So, if your running this problem free then I would like to know.And if you know about code then tell me how to fix the autogen, memory utilization, cloud, stutter during turns,bridges etc.

No I don't work for Microsoft, and I am not trying to get in a flaming war. But I do feel as a community, we're responsible for what we report to users. Your first reply was so generalized as to suggest you know for a fact that the problem is with the code, vs. your system, your settings, or your style of managing MSFS.I did participate in the beta, so I do take things personally when threads start to suggest we were asleep at the wheel. Your declaration that the code is buggy suggests as much. But everything you cite--Autogen, turns, etc.....if you research it, you'll find it present in FS2002 too. Users of FS2002 reported crashes to the desktop, and some still do. Welcome to the "Babel" that the million or so hardware/software combinations presents to people coding software.As for performance, why does it seem like FS2004 is a problem? Because slider for slider, FS2004 displays more (and thus performs slower) than FS2002. Set your scenery settings to dense, and taxi around an airport in FS2002. Then do the same in FS2004. More is there--taxiway signs, more detail on the tarmac, more buildings. Same is true for Autogen. And weather. You can't gripe about slower performance unless you're comparing apples to apples. No one does--and I'm saying that because I don't want you to feel I'm singling you out. We all had our fps lock set at 20, 25, maybe 30 in FS2002. Perhaps a few had it higher. FS2002 was able to meet that because it has less to do, graphically, than FS2004. The exception was when there's a lot of AI around.... I can't speak for that, as I don't have enough system for it. I'm not happy with all the changes offered in FS2004. Performance into airports seems poorer, but how can I tell if it's the code or the eye candy we all wanted to see in the sim? Even if it isn't displayed, the code is there.As for crashes to the desktop, I think you are in the minority. It must really be rotten to have it happen. But dissin' the sim is no way to solve a problem--who would want to help? When I read your post, it sounded like your mind is made up. Maybe--just maybe--something can be done for you and the thread's author to improve the sim's reliability.Having said all this, if you search on my name you'll know I have my fair share of complaints about FS2004--and considering I was in the beta, I probably didn't win a slot in the next one by voicing them. I mostly stick with FS2002 because I like the sensation of flying, and I can keep the detail high enough in FS2002. Airports kill performance in FS2004, especially on slower systems for someone like me who likes to keep sliders high and still enjoy 25fps. But that's my issue and the consequence of my sticking with such an old system. As for the FDE--I wish that FS2004 would have left what worked well alone. Bridges can be taken from FS2002 and added back into FS2004. The newer features of Autogen which seem to cause problems can be turned off. But in your case, first you have to get rid of the CTD's to enjoy the sim. I bet a number of people here would be willing to help if you give 'em a chance vs. discouraging others who seek the same help...

Thank you for the replies guys. But I don't want this to be something of a discussion about MS or the program itself. I just want somehelp to solve my problem.As an additionalinformation, i usually deactivate any background program before I play FS2004. I do not have this sort of problemwith FS2002 though. I don't know if this is relevant, but I also install FS2002 in the same HD.Regards,japangg

Never mind--missed your specs in your post above... I have 98SE, so I am fairly certain your O/S is OK. I would suggest trying to change to the 30.82 drivers if my suggestion below doesn't work. Off the top of my head, I know of one CTD where users had relocated or renamed the "My Documents" folder. FS2004 now stores settings there. I'll watch the thread for the next hour or two, so if you respond fairly quickly I may be able to help point you in the right direction...Regards,John

Thank you and youre right. If your a beta tester then you know more then us. Im going to shelve the program now and go back to fs8 thanks its what I needed to hear

Sounds like you have an attitude a mile high.... You don't want to listen--thus I suspect the only one who has to be "right" in this thread is you--so whine away regarding COF....Geeesh....

John,Thanks for the advice. Unfortunately, I'am at work now, so I cannot tinker with FS9 as it is installed in my computer at home.I will inform you if your suggestion work okay. I really hope I can cure this problem without having to take drastic measure (e.g. migrating to WinXP or stuff like that).On a side note, I installed FS2004 at E: drive, while My Documents folder are at C: drive, as I isntalled system program and work application at C:drive and installed games in the E: drive. Do you think this may be the cause?japangg

No, my last was not meant to be derogatory in any way.What I meant was you were a beta tester so you had better experience with this than I and from the looks of what you wrote ms ignored the beta tester(maybe? i dont know)But I am tired of all this now being told im a basher oh, well thank you. read my post on going back to fs8, now let us help this guy..

possibly try moving one or the other to the other drive.

I had to step away for dinner--sending this post away from home. 747drvr's idea is a good one to try. Also, (I think you've done this already) turn off all A/V software. If you're using any type of CD cloning software such as that bundled with a CD burner, disable it. Check your system try for icons--if anything other than the volume control is there, that may be enough for the application to fail.As a last resort would I suspect hardware in this case. FS2004 does use more RAM. If you have a faulty chip, it may very well never show up until you have an application that uses is. I doubt this is the case in your situation.I scanned for this error in the forum archives. The My Documents folder issue seemed to be tied to it most often, followed by issues with copy protection and graphics drivers. With Windows 98 and the 4xxx series of Nvidia cards, I've found the 30.82's the most hassle free. That's what I had loaded when I installed FS2004.Last, FS2004 made an entry in your registry on install, pointing to the drive it was installed at. You could try changing this from E: to C: to see if it starts... I can't recall the key, but it is found in HKEY_CURRENT_USER/SOFTWARE.... You should be able to find it either in it's own entry, or one of Microsoft's subkeys. If it doesn't work, you can change it back.In the case of 747drvr's idea, moving the My Documents folder to the E drive is probably the easier of the two things to try...-John