How to make 32 bit plugins to work in TC 8 64 bit?

[ghisler(Author)]

Unfortunately at the moment such a wrapper plugin would be very counter-productive: Plugin authors would have little reason to port their plugins to 64-bit once there is such a plugin. The cases where real 64-bit plugins are needed are still very rare: For example, a Windows PE 64-bit run from CD or USB-Stick cannot run 32-bit programs or use 32-bit dlls at all.

[Merix]

OK, I sort of see your point...

Well I'm almost done with the wrapper for packer plugins. I made it because I needed it myself - so I'm not really in it for the reward no matter what.

Anyway, now that I have made it (and it really works beautifully), am I to understand that you disapprove of me releasing it to the public?

[Sir_SiLvA]

2Merix
No he didnt said THAT! thats the beauty of TC - everyone is allowed to write and release plugins for it

[Hacker]

Christian,

such a wrapper plugin would be very counter-productive: Plugin authors would have little reason to port their plugins to 64-bit once there is such a plugin.

I don't really get that. Are you saying that it's bad to have a working way to use all existing plugins under TC 64-bit and instead it's better to be at the plugin writers' mercy to port their plugins to 64-bit (if their development environment supports it at all)?

Roman

[Sob]

It seems to me that words "at the moment" are very important part of that sentence. :)

[nsp]

It seems to me that words "at the moment" are very important part of that sentence.

For me the most important part is saying that if such wrapper exist, plugin author will support 32bit plugin. I suspect Mr Ghisler to push plug-in developer to port to 64bit.
So please Merix release as many wrapper as you can even in beta stage for wcx, wdx, wfx but wlx would be really great

[umbra]

I suspect Mr Ghisler to push plug-in developer to port to 64bit.

Maybe. But for many authors the new 64b version is also a sign/opportunity to finally update their abandoned plugins - fix a longstanding bugs, add new features or support some improvements introduced in recent TC versions. Just check the already converted plugins - some of them weren't updated in years. Plus a native plugin can be optimized for the new platform.

[nsp]

Maybe. But for many authors the new 64b version is also a sign/opportunity to finally update their abandoned plugins - fix a longstanding bugs, add new features or support some improvements introduced in recent TC versions. Just check the already converted plugins - some of them weren't updated in years. Plus a native plugin can be optimized for the new platform.

I do not see any advantage in signing anything for community usage... My main point is that without any effort from a plugin author the plugin is not working in 64bit. I use 32bit TC in 64Bit OS because some free plugin are not ported in 64bit. Some author first develop plugin for internal usage and deliver for free to the community and after maintain or not... Some old plugin are not maintained anymore by the author but are useful to some user. So yes it is frustrating from a user point of view of not being able to have both 64 and 32bit plugin working with TC8 64bit if a technical solution exists that do not force people to maintain or port a plugin for free and fun !

[ghisler(Author)]

Yes, "at the moment" is very important - currently it would be better to have some big incentive to port plugins. This could be done either by the author, or by someone else.

[Merix]

-- WCX to WCX64 Wrapper v0.10 BETA --
Enabling 32-bit packer plugins to work with Total Commander 64-bit.

The wrapper for packer plugins is now ready for beta-testing. Anyone interested may apply - Just send me an e-mail or a PM, then I'll e-mail the wrapper back to you.

For now, anyone who requests the plugin will get it - but I will wait for "the moment" to be right before releasing it for general public consumption :-)

- Rico

Web: www.tcmdplugins.com
E-mail: info@tcmdplugins.com

[deus-ex]

Yes, "at the moment" is very important - currently it would be better to have some big incentive to port plugins.

Hi Christian,

I fully support your decision to give plugin authors time and motivation to migrate from 32 bit to 64 bit environment, but I think the time frame of that precious "moment" has past meanwhile.
I would welcome if you could provide a 32 to 64 bit plugin wrapper as there a quite a few packer plugins I'd rather like to be able to use with a wrapper than to abandon them completely. For example the MSI-plus plugin is a very important one that I miss in my daily work.

[ghisler(Author)]

I would prefer to wait at least until the end of the year. For example, if you use 64-bit Windows from a CD or USB stick, it doesn't support any 32-bit programs or dlls at all, so a wrapper wouldn't help.

[nsp]

I would prefer to wait at least until the end of the year. For example, if you use 64-bit Windows from a CD or USB stick, it doesn't support any 32-bit programs or dlls at all, so a wrapper wouldn't help.

Do you really know a lot of people that use a maintenance toolkit CD or USB booting in 64bit ?

[MVV]

nsp, actually Windows Vista/7 x64 DVD contains 64-bit only PE system. If we're talking about USB - I agree that it is much easier to install 32-bit PE on it.

[csmarshall]

I would prefer to wait at least until the end of the year. For example, if you use 64-bit Windows from a CD or USB stick, it doesn't support any 32-bit programs or dlls at all, so a wrapper wouldn't help.

Do you really know a lot of people that use a maintenance toolkit CD or USB booting in 64bit ?

With all due respect - I know more people doing maintenance work as described than users that use a 64bit OS but still use old-school 32bit plugins instead of using 64bit tools that are specialized for their job. 32bit was YESTERDAY and trying to cling on to old plugins is just as pathetic as still wanting to use Internet Explorer 5 simply because you are "used to the interface".

I do understand that some people don't want a bunch of programs on their machine and prefer to use ONE central tool, TC in this case. However, as you can see on every building site, people simply can not do their work if they are restricted to the use of a Swiss Army knife as tool. Double the effect if folks try to use an old flint knife (32bit) instead of the newest version of the Swiss Army knife (64bit).

But there are perfect (free) solutions for most applications (mp3tagging, (my)sql databases, image format exchange) around that LONG have become 64bit applications - why bother hunting down 32bit museum junk and writing workarounds when I can get hold of 64bit applications easier and learn to use them even faster than sitting around and waiting for a revival of old-school tools? People claim that they NEED the 32bit plugins to "get things done" - how VITAL are those things if you can allow yourself to WAIT for ages in hope of a 32bit solution?

In my eyes, you should respect Christian's point of view; he simply wants to wait a bit, probably pondering over a solution or hoping that some users will finally 'see the light' - I don't know.

My opinion however is that all users demanding a workaround for 32bit plugin use should slowly adapt the thought of becoming extinct. For ages, people shunned everything else but MS Office - how many users today (even businesses) use OOffice or LibreOffice? People preferred a pirated copy of Photoshop instead of using the free GiMP (v2.8 with fullscreen option instead of windowed clutter).

But all of them in the end changed their mind and moved their butts instead of whining for a 32bit code "revival". If you believe that you really need the darned 32bit stuff because your life depends on it, reinstall WinXP and TC 7.56 32bit ... and then SHUT UP. There is absolutely *no* excuse for *not* using your 64bit machine in 64bit mode - it is not a software problem, but rather your own incompetence and unwillingness to adapt.

Where are all the 16bit users that predicted worldwide doom years ago because "nobody wants 32bit" ? Q.E.D.