but why? i've downloaded the latest setup (0.9.8) for windows and installed it.everytime i want to start FG my pc resets (sometimes i get a bsod "Page_Fault_in_Non_Paged_Area" without a driver or dll name).it's a almost fresh xp sp2, amd64, 6800gt and audigy2.edit: FG is working under linux (same pc), and i got newest drivers for my graphic and my soundcard

Does the System Log in the Event Viewer give any clues to this problem? You might try running 'Chkdsk /f /r' in case somehow a fault in the file system is causing FG to tear up the system. I have seen Page_Fault_in_Non_Paged_Area BSOD's caused by bad memory chips, software, and even bios problems. But, if everything else is acting right... it must be something about FG. Perhaps someone out there knows if there are any AMD64 vs. FlightGear compatibility issues?

BSOD have always their cause in faulty drivers or faulty hardware, not in faulty user programs that just crash without compromising the system.And there is no problem with amd64 in itself. Win32 0.9.8 version was compiled with such a system and works every day. But my earlier bsod ( not cause by fg btw ) were triggered by a faulty bit in a faulty memory module detected by memtest86.I advise you to download UltimateBoot and check your hardware, or change your drivers.

the hardware has no problems.it's running 24/7 with every other program/game (prime95, 3dmark03 and 05 in loop, memtest86)and i've got no problems with FG in linux, so it is a compability problem with XP SP2 and Amd64, or a driver problem

>Does the System Log in the Event Viewer give any clues to>this problem? You might try running 'Chkdsk /f /r' in case>somehow a fault in the file system is causing FG to tear up>the system. I have seen Page_Fault_in_Non_Paged_Area BSOD's>caused by bad memory chips, software, and even bios problems.>But, if everything else is acting right... it must be>something about FG. Perhaps someone out there knows if there>are any AMD64 vs. FlightGear compatibility issues?there is nothing in the application log, and only the savedump message in the system log :(

No compatibility problem with XP SP2 and amd64. If you are so sure that your hardware is ok, there is only the drivers.

'Bug check 0x50 (AKA Page_Fault_in_Non_Paged_Area) usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).Another common cause is the installation of a faulty system service.Antivirus software can also trigger this error, as can a corrupted NTFS volume.'Above is from http://msdn.microsoft.com/library/default....a4f1498.xml.asp which might give you some ammo to throw at the problem.What I was saying before, 'something about FG'... could FlightGear be using some resource that your other Win programs aren't using? How you would go about figuring this out, I have no idea.Be nice for you if it was as easy as reinstalling the video driver for that 6800.Anyway, good (bug) hunting.P.S. Just remember to double-check that MD5 sum on FG if you decide to troubleshoot as per that MSDN article and try turning the antivirus off! Oh wait, you're a *NIXster... you knew that already :-)

ROARi installed #### XPSP2 on a old hdd and installed the latest official drivers for the chipset/graphiccard/soundcard/X45 and now it's working ... i hate windows, but the X45 isn't working since 2.6.5 :(

Well, congrats. After I posted that last, it occurred to me that the only difference, on my XP box, between FG and my other games is that most everything else tends to use DirectX instead of OpenGL. The important thing is that you have it working, though, even if you never figure out exactly why it wasn't!Huh... tried replacing FlightGeardataInputJoysticksDefaultjoystick.xml with the FlightGeardataInputJoysticksSaitekX45.xml ? No reason that would work, looks like the X45 is included with the joystick #includes anyway, so it should install/detect that X45 automatically :-/