--- Jim A <[EMAIL PROTECTED]> wrote:
> ---- Don Oliver <[EMAIL PROTECTED]> wrote: > > Thanks for the suggestion. I tried it, but no > change > > here. > > > > I did solve it by deleting the flightgear entry in > > Documents and Settings,all flightgear folders and > > re-installing. > > > > So, the problem appears to have been the Documents > and > > Settings entry. > > > > Don > > > > Glad you're up and running, Don. > > Here's an earlier reply from me that got rejected as > spam for some reason. (maybe spam assassin is > smarter than I thought!) :-D > > ........................................................................................... > > -----Original Message----- > > From: Ron Jensen [EMAIL PROTECTED] > > Sent: Wednesday, May 31, 2006 11:54 PM > > > > Now fails with only the following errors: > > > Error reading properties: > > > Failed to open file at C:/Documents and > > Settings/Don.ANTEC/Application > > > Data/flightgear.org/autosave.xml (reported by > SimGear XML Parser) > > > > This is not a problem. The file autosave.xml will > be created > > for you the first time FGFS successfully exits. > It will > > update itself every time you quit FGFS. > > In theory, maybe.... :-) > > FWIW, my first try at 9.10 required me to have an > "autosave.xml" file. Else, > FGFS would immediately abort. That may be fixed > now. If not, try creating an > autosave.xml file manually, put in one line "<?xml > version="1.0"?>, and save the > file to the appropriate place (maybe an empty file > would work, too?). Also, > check any pre-exsiting fgrun.prefs file while you're > there to make sure all the > paths are correct (this is for the FGRUN wizard, if > you ever use that). > Finally, I commented out the <presets> section in > the preferences.xml, because > I was getting aborts due to not having loaded > scenery matching what was in > <presets>. (I'm sure I could have also changed the > values there, also). > > There may have been a fiew other tricks, too, to get > started. Once you get > through them all, you're all set. > > Jim > > ..................................................................................... > ADDENDUM: I tested today without an autosave.xml > file, and no abort....just a warning. > Jim, Thanks for your response. It appears that there are several things that can trip up an installation, and the uninstall program that comes with flightgear does not deal with these. The safest procedure seems to be to remove all references to FlightGear. Well, maybe not *all* - I found a lot of entries in the registry, and decided not to try anything there. :-) Don __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
