FolksAfter a year of not being able to run FlightGear on Win XP,I decided that instead of just going off in a huff when told FG would not copme up because of 1) my hardware 2) my drivers (video and/or sound)that I would abide by my determination to ignore such advice, however well-intended, and just get it to run ( I came to programming from philosophy and have had many years to learn to handle engineers with kid gloves and free beer. Civil engineers are expected to buy beer, natch; no beer for landscape architects - I have my standards ;-)My unflappable approach: i)let fgrun mangle the system.fgfsrc file to its heart's content ii) quit fgrun iii) correct obvious errors to system.fgfsrc iv) start fgfs in with my own bat file in command sessionAnd after some exaspperation, I am flying. Hooray! And what an admirable great deal of progress has been made! I hope Ilan Papini has also been able to get this sim to run.And I am flying even with Apache Tomacat and Cocoon running and my web pages up - and without any hardware or driver change that could undermine my own add-on development for FS9 or beta-testing of x-plane 8.03 RC1a. Whew!Nothing in the docs was decisive in resolving this XP SP2 issue, nor was any post on this forum. Which is fine. But I wonder that any novice or non-programmer would have long-endured unless they had no other sim available or loathe Microscoff or are offended by a rude developer of another sim whom I need not mention by name: great guy, just rude, or blunt or somehow vexing. I for one had ignored a whole FG release and lost a year. Only learning that Megginson had some involvement here (and loyalty to Minneapolis) brought me back.Through the year I did leave a link to FG up at my website thinking that my issue was something idiosyncratic.What i would like to contribute to this Forum is:setting a DME for NAV1 using fsrun writes a bogus line to the config thus: -dme=nav1which should be, of course (no pun) --dme=nav1ThanksRobert

I'm glad you didn't give up. Most people (especially the developers) use fgfs under some kind of Unix and without fgrun, and the typical Windows user doesn't seem to be interested in debugging or capable of programming. That's why bugs persist longer in Windows ports. I've submitted your --dme fix to the fgrun author. Thanks for reporting, and for your patience! :-)