Drag-and-drop behavior in Windows10 x64 system

[litbear]

I can not open text file such as *.txt, *.html via drag & drop on text editor such as notepad.exe, notepad++, Sublime Text just after I update my OS to Windows 10 x64 .

It worked well in Total Commander 8.5 x32 + Windows 7 x64

It can't open file in following cases:

• Total Commander 8.5 x32 + Windows 10 x64

• Total Commander 9.0 x32 + Windows 10 x64

But work fine under Total Commander 9.0 x64 + Windows 10 x64

and ,i'm pretty sure all cases NOT in the administrator mode

[petermad]

In order to be able to drag and drop from 32bit TC under Windows 8 and 10 to for example notepad.exe, you have to make sure you are running the 32bit version of notepad.exe.

Assuming that you have NOT disabled redirecting og the system32 folder (default), and you are running 32bit TC, then you can find the 32bit versions of notepad.exe here:
C:\Windows\System32\notepad.exe
C:\Windows\SysWOW54\notepad.exe

Whereas the 64bit versions of notepad.exe are found here:
C:\Windows\notepad.exe
C:\Windows\Sysnative\notepad.exe

So in stead of just starting Notepad by writing notepad.exe, start it by writing C:\Windows\SysWOW54\notepad.exe - then you should be able to drag files fron TC 32bit to Notepad.

[litbear]

In order to be able to drag and drop from 32bit TC under Windows 8 and 10 to for example notepad.exe, you have to make sure you are running the 32bit version of notepad.exe.

Assuming that you have NOT disabled redirecting og the system32 folder (default), and you are running 32bit TC, then you can find the 32bit versions of notepad.exe here:
C:\Windows\System32\notepad.exe
C:\Windows\SysWOW54\notepad.exe

Whereas the 64bit versions of notepad.exe are found here:
C:\Windows\notepad.exe
C:\Windows\Sysnative\notepad.exe

So in stead of just starting Notepad by writing notepad.exe, start it by writing C:\Windows\SysWOW54\notepad.exe - then you should be able to drag files fron TC 32bit to Notepad.

I tried to launch the following program, and all of them can not work.
"C:\Windows\notepad.exe"
"C:\Windows\System32\notepad.exe"
"C:\Windows\SysWOW64\notepad.exe"

[MVV]

In order to be able to drag and drop from 32bit TC under Windows 8 and 10 to for example notepad.exe, you have to make sure you are running the 32bit version of notepad.exe.

Are they dumb enough to break drag-n-drop between x86 and x64 applications in Windows 8/10??? Sounds completely weird!
I have no Windows 8/10 in touch but it is a very questionable reason that breaks compatibility with all old apps a lot.

[hlloyge]

It's really years old, you can't start 64 bit app from within 32 bit app.
Just use 64 bit Total Commander.

[MVV]

It's really years old, you can't start 64 bit app from within 32 bit app.
Just use 64 bit Total Commander.

That's an absolute nonsense! You can start 64-bit apps from 32-bit apps, the only thing to keep in mind is the redirection (if you want to start something from C:\Windows\System32 dir, you have to start it from C:\Windows\Sysnative dir instead, e.g. C:\Windows\Sysnative\notepad.exe).

[petermad]

Well, I tested it yesterday before I wrote my previous posting.

Under 64 bit Windows 7 using TC 9.0a 32bit, it doesn't matter whether I start the 64bit notepad (C:\Windows\notepad.exe or
C:\Windows\Sysnative\notepad.exe) or the 32bit notepad (C:\Windows\SysWOW54\notepad.exe) - I can still drag&drop from TC to that notepad.

But under 64bit Windows 8.1 and 10 I can only drag&drop from 32bit TC to 32bit notepad (C:\Windows\SysWOW54\notepad.exe)

Using 64bit TC I can always drag&drop no matter which notepad.exe I am running and no matter which Windows version I am using.

[hlloyge]

That's an absolute nonsense! You can start 64-bit apps from 32-bit apps, the only thing to keep in mind is the redirection (if you want to start something from C:\Windows\System32 dir, you have to start it from C:\Windows\Sysnative dir instead, e.g. C:\Windows\Sysnative\notepad.exe).

Could be just for programming, that you can't call 64 bit library from 32 bit program.

[MVV]

You can't load 32-bit libraries to 64-bit processes and vice versa, that's correct. But you can start 32-bit or 64-bit processes from both 32-bit and 64-bit ones.

[hlloyge]

I misunderstood what I read, then. Thanks for explanation.

[litbear]

Well, I tested it yesterday before I wrote my previous posting.

Under 64 bit Windows 7 using TC 9.0a 32bit, it doesn't matter whether I start the 64bit notepad (C:\Windows\notepad.exe or
C:\Windows\Sysnative\notepad.exe) or the 32bit notepad (C:\Windows\SysWOW54\notepad.exe) - I can still drag&drop from TC to that notepad.

But under 64bit Windows 8.1 and 10 I can only drag&drop from 32bit TC to 32bit notepad (C:\Windows\SysWOW54\notepad.exe)

Using 64bit TC I can always drag&drop no matter which notepad.exe I am running and no matter which Windows version I am using.

firstly, the path of notepad.exe x32 is "C:\Windows\System32\notepad.exe". and the path of notepad.exe x64 is "C:\Windows\SysWOW64\notepad.exe".

secondly, when I worked under windows 10 x64. neither notepad.exe x 32 nor notepad.exe x64 could work well with TC x32. not only notepad.exe but also notepad++ and sublime text

[Lefteous]

firstly, the path of notepad.exe x32 is "C:\Windows\System32\notepad.exe". and the path of notepad.exe x64 is "C:\Windows\SysWOW64\notepad.exe".

No it's the other way round.

[Dalai]

No it's the other way round.

Uh, no. Actually both paths point to the very same file when looking from a 32-bit perspective, because access to files in \Windows\system32 will get redirected to \Windows\SysWOW64. The 64-bit executables are available in \Windows\SysNative, or, in case of notepad.exe, directly in \Windows.

BTT: I can confirm petermad's findings. Win8.1 somehow broke drag'n'drop from 32 bit applications to 64 bit applications. This is not limited to TC but also affects (all) other programs.

Regards
Dalai

[Lefteous]

2Dalai

Uh, no. Actually both paths point to the very same file when looking from a 32-bit perspective

I had a 64 bit perspective.

There is also the x64DisableRedirection setting to consider.

[MVV]

There is also the x64DisableRedirection setting to consider.

... and leave in default state to get rid of strange troubles.