Am Mittwoch, den 22.02.2012, 08:51 +0100 schrieb Frederic Bouvier: > 1. did these problem occurs in the release candidates or are specific > to the final version ?
b89717f9acf01d154c868afadf39b89f Setup FlightGear 2.6.0.exe > 2. We know that you didn't install in "Program Files" but we don't > know where exactly. Could there be a special german character in the > path, or any non purely ascii character ? E:\Games\FlightGear > 3. what happen if you install in "Program Files" as suggested by the > installer ? Don't know, didn't try that. > 4. Did you install the 64bit binaries or have forced the 32bit > install ? This was another confusing thing in the installer. There was no help given and i wondered why i should force the installer to install the 32 Bit version on a 64 Bit system. So i decided to take the default setting and because the "force installer to install the 32 Bit version" was marked i took the 32 Bit version. I suggest to split the windows version in a 32 Bit and 64 Bit installerpackage or give more detailed information why a 32 Bit version should make sense on a 64 Bit system. > 5. Can you find the "flightgear.org" directory in \Users and check > that fgrun.prefs has write privileges ? This directory was created after i started FlightGear first time in the users: %APPDATA%\Roaming\flightgear.org Keep in mind, that i installed as admin but didn't start FlightGear as admin! So the installer put the files in Users\Administrator\AppData\Roaming\flightgear.org but this is useless for other user accounts, it's not used by them. For things like that i suggest do put a default config file created by the installer as read only in the directory where fgrun is. And when fgrun ist started it should check if there is already a user config file in %APPDATA%\Roaming\flightgear.org available. If not, then it should read the default config files set by the installer that were installed in fgrun's directory like i suggested and then create a new one in %APPDATA%\Roaming\flightgear.org I also want to mention, never use direct addressing instead always use Environment variables to check the locations of Programm files, Windows or Users. Wrong (direct addressing): C:\Program files C:\Windows C:\Users Correct (indirect addressing via Environment variables): %PROGRAMFILES% %WINDIR% %HOMEPATH% Read here for more informations: http://en.wikipedia.org/wiki/Environment_variable#Default_Values_on_Microsoft_Windows You can't expect to have the users data in: C:\users\username\ My users directory is for example called "home", not "users" and it is in: F:\home\myusername\ So the only correct way to get there is via: %HOMEPATH% > The save button is only there to save another set of options and it's > normal that a file name is requested. For the current set of options, > it goes to flightgear.org\fgrun.prefs but this file should be > writable. It is created at install and contains the default path that > you shouldn't have to set by hand. The default path is the admins user directory when installed as admin. It shouldn't belong there if other users should be able to read these config files! So put them in the program directory of fgrun as mentioned before or in a shared user config directory and then check at start if a user has its own config files, and if not, read them from the programm directory or the shared user config directory like mentioned before. And after that, create one in the user's directory and use this for writing new settings data to it. Never write the data for daily use to somewhere else, only in the users's directory, never the programm directory. Best Regards, Oliver C. ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
