Moving from 32 to 64 bit, keep wincmd.ini and wcx_ftp.ini?

English support forum

Moderators: Hacker, petermad, Stefan2, white

Post Reply
mrboonmee
Junior Member
Junior Member
Posts: 10
Joined: 2011-11-13, 06:09 UTC

Moving from 32 to 64 bit, keep wincmd.ini and wcx_ftp.ini?

Post by *mrboonmee »

I have always stored the wincmd.ini and wcx_ftp.ini in a separate directory.

when going to 64bit version should i use the same .ini files?

I do want to save my FTP sites.

What about noclose.pif?

thanks
User avatar
Flint
Power Member
Power Member
Posts: 3511
Joined: 2003-10-27, 09:25 UTC
Location: Belgrade, Serbia
Contact:

Post by *Flint »

mrboonmee wrote:when going to 64bit version should i use the same .ini files?
Generally, yes; wincmd.ini and wcx_ftp.ini can be shared by the 32- and 64-bit TC versions. The only problem might arise if you start using 64-bit plugins: wincmd.ini must have special section which is added by 64-bit TC when installing the plugin, so it will not "see" the plugin if you just copy a w?x64 plugin file.
mrboonmee wrote:What about noclose.pif?
Starting from version 8.0, there is no more noclose.pif. Instead, TC uses noclose.exe and noclose64.exe located in the TC installation directory.
Flint's Homepage: Full TC Russification Package, VirtualDisk, NTFS Links, NoClose Replacer, and other stuff!
 
Using TC 11.03 / Win10 x64
Post Reply