+1 vote from me for keeping 64bit in %programfiles% and 32bit in
%programfiles(x86)% in 64bit systems.
I don't see a problem having both 32-bit and 64-bit FF in same machine
as long as they use same profile. So profile should not care about
bitness of the program (or where it is launched).
Timo Pietilä
On 2.10.2019 12.12, Marco Gaiarin wrote:
Mandi! Klaus Hartnegg
In chel di` si favelave...
You just learned the hard way that not following rules causes problems.
Now instead of fixing the underlying bug you want to break another rule.
Guess what? That will cause more problems.
Every deployment solution, every inventory tool, and Windows itself
assumes everywhere that 64-bit programs are installed in C:\Program Files.
Strictly speaking, 32bit FF/TB in 32bit OS install on %ProgramFiles%,
64bit FF/TB in 64bit OS install again on %ProgramFiles%.
So, the real pain happen for a bitness change, eg if you move from a
32bit FF/TB to a 64bit FF/TB (clearly, on a 64bit OS), because you
change from %ProgramFiles(x86)% to %ProgramFiles%.
Still, PLEASE DON'T DO THAT, thinking to install 32bit software on
%ProgramFiles% on 64bit OS is probably, as Klaus say, worster then the
trouble it (try to) solve.
How about this:
When Firefox is installed in its default directory, it uses the default
name for the profile directory.
Only if somebody installs it in a non-standard directory, it uses a
non-standard name for its profile.
Then all users who use defaults will get what they expect, and those who
do not use defaults will get what they deserve: a surprise.
I agree.
_______________________________________________
Enterprise mailing list
[email protected]
https://mail.mozilla.org/listinfo/enterprise
To unsubscribe from this list, please visit https://mail.mozilla.org/listinfo/enterprise
or send an email to [email protected] with a subject of
"unsubscribe"
