speller2 wrote:Do you mean event xx.wlx specified in the wincmd.ini TC64 will try to load xx.wlx64?
Yes.
BTW, that's why you can use the same wincmd.ini for both 32- and 64-bit versions of TC: the section contain WLX plugin name, so the 32-bit loads it, and the 64-bit loads wlx64 (if it is present, of course).
Flint's Homepage: Full TC Russification Package, VirtualDisk, NTFS Links, NoClose Replacer, and other stuff!
speller2 wrote:How can I privately clarify reward details
Simply write an email with all informations (plugin, konto, questions) to the standard email address of the Tc (and of ghisler(author)), which is given here: http://ghisler.ch/board/impressum.htm
Oh really you can make a 32Bit dll that is run by a 64 Program without a wrapper? No, and the threads proves my point.
Ofc you can build a wrapper but as Chris pointed out in that thread brings bugs, slowing the thing down - wich is kinda joke if you go for 64Bit for speed and then slow it all down by using a wrapper...
2Sir_SiLvA
rilley was suggesting to create such wrapper ...
And I don't think TCx64 is any faster than TCx32. The only reason I want to use it is a better integration with my OS (context menu, folder redirections, better UI, ...).
I think that it's better to use TC 32-bit if you need to use some unported plugins than to use 32-bit plugins through a wrapper. Such a wrapper would cause a big slowdown because of the constant switching between the 64-bit and 32-bit process.
Now that TC8 final is available, I'm offering the reward for porting to 64-bit also to third party authors. The conditions are:
1. The plugin should support at least the main feature of the 32-bit only plugin.
2. The author needs to put it on Totalcmd.net, give it a similar name as the old unsupported plugin, and send me the link
3. If there is more than one alternative plugin, those coming later will get the reward only if they do significantly more than the first replacement. For example, if the first replacement packer plugin only does unpacking, and the second then also supports packing, or additional formats. We alone decide whether there will be a reward or not. The decision is final.
4. The reward is $100 for plugins where the source is available - then it's often just a question of recompiling with a few minor tweaks. I'm willing to negotiate a higher reward for plugins where no source is available, but please contact me before starting to write the plugin. No higher reward will be available if it isn't negotiated in advance.