full Win 64bit support to come?

[gigaman]

I think it would be certainly good for testing.
I mean, people would find out what works with the redirection and what doesn't, and report their findings - so the problematic parts could be fixed subsequently (or the redirection would be enabled for them even if disabled overall).
Maybe we'll find out that almost everyting works correctly and the only place to reenable redirection would be before calling the plugin exports (which I hope would not be that much work?) Or, maybe it shows up that the redirection should really be reenabled as soon as the real system32 folder isn't needed (I don't know TC sources of course, so I have no idea how much work would that be, i.e. if there's any "API separation layer", or most of API functions are called from the code directly). Or, maybe everything will work without any problems and without any additional changes...

Just note that the redirection is enabled/disabled for "current" thread, i.e. the .ini file setting should be applied after each thread creation.

[levicki]

I agree with most of what user gigaman writes. One solution would be to allow the user to enable/disable the system32 redirection via a wincmd.ini switch. The user could then choose between using all plugins and system32 pointing to the 32-bit dlls, and using only well behaving/updated plugins and system32 pointing to the 64-bit dlls. What do you think? The current behaviour would remain the default.

I agree with this Christian. When can we expect a beta version for testing?
I will gladly help.

[chrislu]

1st post
i am using totalcommander since version 3.x (when it was still wincmd).

i would also very appreciate a native 64bit version, especially because i do not want to install two versions of shell extensions like for example tortoise svn for 32bit and 64bit versions (explorer is used from time to time).

thx for considering

[rc]

[quote="ghisler(Author)"]Even if they provided a 64-bit version, it wouldn't make much sense, because all plugins are 32-bit DLLs. They would all stop working, except if the plugin writers would write a 64-bit version too.[/quote]

Now replace all "32" and "64" in this text to "16" and "32", respectively, and you will get the same that we saw in mid-1990s. 16-bit program authors spoke the same... and where are now they and their programs?

[Sir_SiLvA]

Even if they provided a 64-bit version, it wouldn't make much sense, because all plugins are 32-bit DLLs. They would all stop working, except if the plugin writers would write a 64-bit version too.

Now replace all "32" and "64" in this text to "16" and "32", respectively, and you will get the same that we saw in mid-1990s. 16-bit program authors spoke the same... and where are now they and their programs?

its not the same - in the 1990s there were no TC Plugins

[Tahattmeruh]

I don't use any plugins because I haven't found anything usefull so far.
So I don't care about the plugin incompatibility. I would prefer to have
a 64bit version of TC.

[Sir_SiLvA]

I don't use any plugins because I haven't found anything usefull so far.
So I don't care about the plugin incompatibility. I would prefer to have
a 64bit version of TC.

There you surly the only one that uses TC WITHOUT plugins

[KyleK]

This might be a bit off-topic, but I've been wondering: Are there any real advantages 64bit provides over 32bit? I mean, for the normal (home) user.
I do know that 32bit systems are limited to 4GB of RAM, but seriously, who has that.

Is there anything else 64bit does that 32bit doesn't?

[rc]

[quote="KyleK"]This might be a bit off-topic, but I've been wondering: Are there any real advantages 64bit provides over 32bit?[/quote]

Simply remember the same discussion about "16 vs 32" in mid-1990s.

[SQUIRE]

2KyleK:

This short article might answer some of your questions in a general way. Do also read the comments.

[KyleK]

This might be a bit off-topic, but I've been wondering: Are there any real advantages 64bit provides over 32bit?

Simply remember the same discussion about "16 vs 32" in mid-1990s.

I was still in school back then, so that didn't really bother me ;)
I also didn't have the knowledge about computers that I have now.

[KyleK]

2KyleK:

This short article might answer some of your questions in a general way. Do also read the comments.

Thanks for the link. That's pretty much what I've assumed about 64bit before. Still, it seems server/industrial systems are fare more affected by this than anything else.

What difference would a 64bit Total Commander make, in particular?

[Elendacil]

I don't use any plugins because I haven't found anything usefull so far.
So I don't care about the plugin incompatibility. I would prefer to have
a 64bit version of TC.

There you surly the only one that uses TC WITHOUT plugins

A lot of people, I think, use TC without any plugins. I'm one of them. And I'm also one of those who'd like a native 64 bit TC. 64 bit is the future, there's no way around that.

[m^2]

Furthermore:
As long as there's no 64bit TC, there will be no 64bit plugins.

[Scyphe]

This might be a bit off-topic, but I've been wondering: Are there any real advantages 64bit provides over 32bit? I mean, for the normal (home) user.
I do know that 32bit systems are limited to 4GB of RAM, but seriously, who has that.

Is there anything else 64bit does that 32bit doesn't?

In 64-bit mode the CPU have twice the size of the registers (64 bits instead of 32 ), there are a few new instructions as well as some other things that can(!) make 64-bit code more efficient and faster than the 32-bit equivalent. The problem is that applications requires Dynamic Link Libraries and other "plugins" to be 64-bit as well since a 64-bit application can't call 32-bit code (if I've understood it correctly).

I would like to see a 64-bit compiled TC to leave the choice to the users. That's when 64-bit plugins can become interesting. Another reason for running native 64-bit code instead of through WoW64 is that WoW64 is an emulating layer translating 32-bit code to 64-bit code (I think).