can't find wcx_ftp.ini in order to remove the write prote

[hagita]

Hi,
While configuring TC on a new computer, windows 7 64 bit, I can't find
wcx_ftp.ini in order to remove the write protection.
I have searched for the file all over, it seems that it does not exist.
The TC is installed on c:\Program Files\totalcmd\.
In the Help window, it says that the wcx_ftp.ini is located in the c:\Program
Files\totalcmd\ directory, but I don't see it although I can view hidden files.
Where can I find it or maybe create it?
I am using Total Commander 8.52 32+64 bit.
Thanks

[sqa_wizard]

In the Help window, it says that the wcx_ftp.ini is located in the c:\Program Files\totalcmd\ directory...
Where can I find it or maybe create it?

Well, you got it right:
Create a wcx_ftp.ini at c:\Program Files\totalcmd\ directory and add for it permissions for everybody write.

[Dalai]

The better solution would be to create TC's settings on a writeable location, e.g. the default location %AppData%\Ghisler, either during setup or afterwards using IniReloc (available via www.ghisler.com).

And, again, this issue has been discussed a couple of times.

Regards
Dalai

[hagita]

Thank you,
I copied a wcx_ftp.ini file from my other computer, put it in c:\Program Files\totalcmd\, this even transferred my FTP configured.
Problem solved.

[MVV]

If you can't find some configuration file (because program or any of its plugins can't create it) it is good to start TC elevated and let it create that file, and then change its permissions.

[umbra]

BTW
Non-elevated programs running from Program Files, that try to write into their own directory, are sometimes silently redirected into "c:\Users\<username>\AppData\Local\VirtualStore\". If you have an old program, that doesn't support UAC, yet it still happily stores its settings into its own folder, that's where the ini files are really stored.

[Dalai]

2umbra
That's not entirely correct. The virtualization applies when a program doesn't include any manifest (IIRC specifying compatibility with Vista). In that case, the program just writes its files and everything works; no "access denied" or something like that. The system virtualizes access to these files and redirects them to the virtual store.

But that doesn't apply to TC since it has been including a manifest for many years.

Regards
Dalai

[MVV]

From my experience, when a program have no manifest, Windows still tries to detect if it is an old one and sometimes applies such redirection and sometimes not. I don't exactly know how it detects it (perhaps it has some list of popular old programs and maybe some other heuristics). My little tools w/o any manifests (both old and new ones) aren't redirected.

BTW sometimes Windows applies such redirection when __COMPAT_LAYER=RunAsInvoker envvar is used (I use it to disable elevation requests from non-trusted software).

[umbra]

2Dalai
Yes, I know that.

an old program, that doesn't support UAC

I didn't want to go into technical details, but instead give a simple generic hint for future reference. But maybe I have chosen my words poorly.

[Dalai]

2MVV
Windows uses a special compatibility database (%SystemRoot%\AppPatch\sysmain.sdb) which lists some programs - mainly old ones - that are treated in a special way. Maybe this database has something to do with it. Unfortunately, I don't remember which parameters can be applied to the listed programs, but you can take a look at the database using Compatibility Administrator (IIRC it can be found in some MS SDK).

2umbra: OK, never mind .

Regards
Dalai