2Hurdet
To make it clear: When editing wincmd.ini you should know what you are doing!
If you are interested in the technical details:
- The normal plugin section only store paths to 32 bit plugin libs
- There is a corresponding section where information is stored about 64 bit plugin version e.g. [FileSystemPlugins64] but mainly it's not the path which is stored but if such a corresponding 64 bit plugin exists (0/1).
If you are interested in making it work (you only have a few plugins installed):
- Reinstall your plugins by manually adding them in TC.
- If you have messed up the plugin installations by copying files forth and back reinstall them using the normal plugin installation routine.
TC plugins repair
Moderators: Hacker, petermad, Stefan2, white
You're using Windows 64 bit, correct? Are you using TC 64 bit as well? Then you can try to delete the $checksum$ value in [FileSystemPlugins64] section (or remove the entire section if no plugin is listed in there).
However, IIRC, I had to remove the entire [ListerPlugins64] section to make this work.
Regards
Dalai
Are you sure about this? I've been using something like this in TC x64 for years:Lefteous wrote:- The normal plugin section only store paths to 32 bit plugin libs
Code: Select all
[ListerPlugins]
0=%COMMANDER_PATH%\Plugins\Imagine\Imagine.wlx64
Regards
Dalai
#101164 Personal licence
Ryzen 5 2600, 16 GiB RAM, ASUS Prime X370-A, Win7 x64
Plugins: Services2, Startups, CertificateInfo, SignatureInfo, LineBreakInfo - Download-Mirror
Ryzen 5 2600, 16 GiB RAM, ASUS Prime X370-A, Win7 x64
Plugins: Services2, Startups, CertificateInfo, SignatureInfo, LineBreakInfo - Download-Mirror