FsPassengers Forums
Installation directory - Printable Version

+- FsPassengers Forums (http://www.fspassengers.com/forum)
+-- Forum: FsPassengers (http://www.fspassengers.com/forum/forumdisplay.php?fid=3)
+--- Forum: FsPassengers Support (http://www.fspassengers.com/forum/forumdisplay.php?fid=5)
+--- Thread: Installation directory (/showthread.php?tid=17719)



Installation directory - Redglyph - 04-06-2016

Hello,

I just bought and installed FS Passengers.

However, by looking for the *.ini payload model files, I realized the program installed itself in c:\Users\Public\Documents\FsPassengersP3D, of all places!

How can I force it to install correctly in an appropriate directory, or by default of a user choice, at least %ProgramFiles%?
Installing a program in the document directory is bad, installing it in another user's document directory is even worse, not sure where it's coming from.

Thanks


RE: Installation directory - Joeflyer - 05-06-2016

Why is it so bad? Many users don't seem to have a issue with it. Also, you may want to go over the various change logs and threads that Dan provided for everyone. Your question will be answered Smile If you are having a issue with accessing a payload model within FsP, that's a different story.


RE: Installation directory - Redglyph - 05-06-2016

It's quite bad because of the access rights, and the size it takes in a place that is not designed for this. Those directories are for documents (and public documents), not executables.

Another problem is that if programs starts installing themselves at fancy places, without at least letting the user choose another possibility, the disk will quickly become a mess. I'm not even talking about anti-virus software (for my part, when I find an executable in a document structure, I just assume it's a malware and remove it).

There is a structure in place for a good reason, the correct place for programs is %ProgramFiles%, not %PUBLIC%\documents, believe me on that.

I hope this can be fixed at some point, because it's really messing with my settings.


RE: Installation directory - SamTDS - 05-06-2016

(05-06-2016, 09:56 AM)Redglyph Wrote: It's quite bad because of the access rights, and the size it takes in a place that is not designed for this. Those directories are for documents (and public documents), not executables.

Another problem is that if programs starts installing themselves at fancy places, without at least letting the user choose another possibility, the disk will quickly become a mess. I'm not even talking about anti-virus software (for my part, when I find an executable in a document structure, I just assume it's a malware and remove it).

There is a structure in place for a good reason, the correct place for programs is %ProgramFiles%, not %PUBLIC%\documents, believe me on that.

I hope this can be fixed at some point, because it's really messing with my settings.

Fspassengers installs there so every user is able to use it and access the files to edit the configs or add payload files.


RE: Installation directory - Redglyph - 05-06-2016

And if there are several users on the same computer, how does it separate the databases?

The correct way to do is to install the program in the program directory, and the user files in the user directory, that's what it's made for Smile


RE: Installation directory - SamTDS - 05-06-2016

(05-06-2016, 07:42 PM)Redglyph Wrote: And if there are several users on the same computer, how does it separate the databases?

The correct way to do is to install the program in the program directory, and the user files in the user directory, that's what it's made for Smile

The databases are shared throughout the system, this way can have people with custom settings for FSX but can work in the same company as the same or a different pilot.imagine a set of friends who use FSX on the same computernt accounts, this allows them to be in the same company and work as one pilot or be as separate pilots within the company


RE: Installation directory - Redglyph - 05-06-2016

Ah, I see, thanks for the explanation. There's indeed a whole set of use cases.

Still, we'll have to agree to disagree on the program location Wink