Sorry everyone for another "Can't start..." problem but this is getting really fustrating now :-grr I've installed V0.9.5a from the fgsetup-0.9.5a.exe on WinXP.When I start FlightGear with the command (created by fgrun.exe)...D:GamesFlightGearbinWin32fgfs.exe --fg-root=D:GamesFlightGeardata --fg-scenery=D:GamesFlightGeardataScenery;D:GamesFlightGearscenery --airport-id=KSFO --aircraft=c172-610x-jsbsim --control=joystick --disable-splash-screen --enable-mouse-pointer --disable-random-objects --disable-ai-models --log-level=info...the program fails to start. Unfortunately the command window doesn't stay open after the failure so I can't read what the failure is and redirecting stdout doesn't seem to work. Is there a way I can inspect the content of the debug? Operating system: WinXP Pro V2002 SP2Computer: Dell OptiPlex GX270 Intel P4, 2.8GHz, 384Mb RAMGraphics board/chip: NVidia GeForce4 MS440 AGP8X 64MbDriver: nv4_mini.sys (6.14.10.6177, 2.35 MB (2,459,712 bytes), 6/30/2004 19:26)

Hi!It is my opinion that the 0.9.5a build simply does not work on Windows and there does not seem to be enough interest in Windows to find and correct the problem. Hopefully, the next release will be better.Redirecting output does not work because, even if you start it from a console window and redirect the output, it always starts in a separate console window. There is thus no output to the process that has its output redirected.The only way I have found to capture the debug output is to use CTRL-S to control the scrolling of the debug output and to try to capture the last bit of debugging information before it shuts down.If you bump up the log level and manage to capture the last bit of debug information, I am fairly sure you will find the same problem that I have:Refreshing timestamps for -999.938 0.0625updateLocal(-2.13597, 0.656401, c:/programfiles/flightgear/data/Timezone)In memory sounds sampleinterpolate(): lookup error, x to small = -10012In memory sounds sampleIn memory sounds sampleUnknown exception in the main loop. Aborting...FlightGear is interesting and encouraging, but for now, if you run Windows, it seems Microsoft Flight Simulator is your best bet.regards,Alan.

Thanks AlanI've got 0.9.5a running on Linux but it's only an 800MHz with a cr*ppy graphics card so ultimately it's, to borrow a phrase from the FAQ, "So sloooow!".Does anyone know if you can still get the win32 binaries for 0.9.4?

Hi Alan, hi Mike,just to correct an error - I never had any problems with FlightGear running on my Windows system (it ran "out of the box", the only manual work was to adapt the configure files for joystick/pedals and config screen resolution):FlightGear 0.9.5aWindows XP HomeDirect X Version 9Service Pack 1 (*NOT 2!*)AMD Barton 2500768 MB system RAMNvidea 5600 128 MB RAMMight be it is a question of your special Windows (Servicepack 2???) or hardware configuration, but it is *NOT* a generell Windows XP (Home) problem.Best regardsGeorg "HeliFLYer" EDDW

I want to add:when I looked back through the posts I found that nearly all problems with Windows are related to *XP PRO!!!* - I use *XP HOME!!!*If so, where is the difference between PRO and HOME which causes the problems?RegardsGeorg "HeliFLYer" EDDW

>If so, where is the difference between PRO and HOME which>causes the problems?Fundamentally, I think the difference between HOME and PRO is that PRO can participate in Windows networks. There is obviously some difference in some DLLs but I thought FlightGear was built as un-windowsised [!] as possible hence it's enphasis on OpenGL rather than porting to DirectX. (I haven't had more than a cursory glance at the code, though - I'm still trying to get Cygwin to run!)

Hi!It is good to know that it does run on a Windows machine other than the one it was built on. I always assumed that it did run there.You may be correct about the difference between Home and Pro, though this would be the first software I have found that runs on Home, but not Pro. I don't know all the differences, but I do no that Pro has access to finer grained security settings, can join domains and runs more Microsoft servers. I had assumed though, that they had essentially the same functionality internally, but the UI on Home was different for some tools and hid some features. When it comes to servers, it seems clear that Microsoft checks the Operating System version from some of their servers and shut down in the case of home, because servers from other companies run fine on Home.It seems to me that all, or at least most, of the Windows problems are related to sound and the OpenAL library. I downloaded and installed the latest version, but it is the same as the one supplied with FlightGear. It also seems like OpenAL is built with support for specific devices on Windows. If so, it would seem like this is a step backwards from Windows' device independence. It could also explain why it works on some machines, but not on several others.In any event though, it would be nice if FlightGear made a few older builds available so we could at least fall back to a version that works.regards,Alan

After a suggestion from Francisco, I ran several copies of fgfs.exe to load the CPU and managed to catch the tail of the output...-----------------Initializing Tile Manager subsystem.Initializing the tile cache. max cache size = 100 current cache size = 0 done with init()Tile not found (Ok if initializing)State == Start || Inited JSBSim Flight Dynamics Model v0.9.5 [cfg file spec v1.65]JSBSim startup beginning ... aero does not exist (you may have mis-typed the name).FlightGear aborting-------------------Ah-ha - a clue. So I selected 747-100(JSBSim) and it worked :-beerchug I'm flying!

0.9.6 is out, but for those who don't know how to compile, they may have to wait a few more days.Get the source code here:http://flightgear.org/Downloads/source.htmlGet the binary here:http://flightgear.org/Downloads/binary.html