A
Antoine
omega said:I downloaded what should be the same file you did:
fc_setup_200410.zip.
It is indeed the same file I downloaded.
I used InnoUnp (Inno Setup Unpacker,
http://innounp.sourceforge.net/) to extract setup.exe, bypassing
the installer. Then I monitored my first run of it.
I didn't know there existed an Inno setup Unpacker. Thanks.
[...]
You want to get TUN configured so that it does not tell you about
normal Windows activity in its installation reports. The standard
approach for this is to run TUN for a snapshot; do some of your
normal Windows things; then when it gives you a report from that,
set the keys shown in that report into its TUN's Ignore settings.
Thank you for this tutorial and pieces of advice about TUN.
IMO, it should not have been distributed in installer form in the
first place. It runs totally green. And user has only to delete
its folder from drive for uninstall.
I second this suggestion, all the more as the registry entries I
evoked seem to be generic entries produced by Inno setup.
It uses a local ini. Some programs have got mad at me when I was
too lazy to not do an S&R in their ini to change referenced files
paths, prior to moving them. But with Free Commander, I did a lazy
move just now, and it gave no complaint, coping easily.
The second one: path_to_the_free_commander_folder.
As I played a little with free commander, I confirm this. FYI, the
actual .ini that is used is indicated through Help > Info.
Thank you Karen for your help.