My point of view:
Q1 > A1. Universality.
For those who still have to deal with both 32-bit and 64-bit systems, the combined version provides a uniform working environment.
Q2 > A2. Portability.
Essentially, it's up to the user.
I appreciate the portability and prefer to keep it all within the %commander_path%.
Q3 > A3. Portability (again).
Essentially, it's up to the user again.
For me, regarding portability, in no way I would ever install and keep TotalCommander within the restricted %ProgramFiles% scope, and within the %SystemDrive% at all (excluding the testing purposes of course).
Edit 1,2:
PSFor me, the above is a must.
Otherwise, I can see no valuable point as to why a user decides to utilize such a powerful tool as TotalCommander. Why just not happily keep enjoying Windows Explorer then?
Still, any TotalCommander user is very welcome.
It's OK to begin with the 'defaults', and then proceed to probe in finding your own best practice and ask any actual questions.
Cheers.
Q1 > A1. Universality.
For those who still have to deal with both 32-bit and 64-bit systems, the combined version provides a uniform working environment.
Q2 > A2. Portability.
Essentially, it's up to the user.
I appreciate the portability and prefer to keep it all within the %commander_path%.
Q3 > A3. Portability (again).
Essentially, it's up to the user again.
For me, regarding portability, in no way I would ever install and keep TotalCommander within the restricted %ProgramFiles% scope, and within the %SystemDrive% at all (excluding the testing purposes of course).
Edit 1,2:
PS
Code:
[Configuration]UseIniInProgramDir=7Otherwise, I can see no valuable point as to why a user decides to utilize such a powerful tool as TotalCommander. Why just not happily keep enjoying Windows Explorer then?
Still, any TotalCommander user is very welcome.
It's OK to begin with the 'defaults', and then proceed to probe in finding your own best practice and ask any actual questions.
Cheers.
Statistics: Posted by beb — 2024-01-02, 20:09 UTC