64 bits WinSCP version
Does exists a 64 bits WinSCP version?
If not, any prevision?
TIA
Advertisement
Advertisement
What for?I need the 64 bit also
Advertisement
What for?I need the 64 bit also
It should be enough to make 64-bit drag&drop shell extension. It is planned. TortoiseSNV is Explorer-plugin not a regular application.Drag and drop from 32-bit apps into Windows Explorer doesn't work properly under 64-bit XP. There's something about the 64-bit explorer such that when the item is dragged from WinSCP to an explorer window, a folder entitled (for instance) scp51328 is created in the explorer, and then WinSCP itself complains with the "WinSCP was not able to detect folder, where the dragged file(s) was dropped. Either ...".
I think that's the reason that the TortoiseSVN guys have an x64 version as well as an x86 version.
Thanks. I will do once I have anything to test.Anyhow, if you need access or work done on a 64-bit platform, you can get to me from the contact links at www.pagaros.com.au.
Advertisement
Thanks for your post. This issue has been added to tracker.I'm using WinSCP 4.1.8 on Windows Vista x64, and I get this same error:
"WinSCP was not able to detect folder, where the dragged files(s) was dropped. etc."
It appears to work just fine when I drag files from WinSCP to the desktop (a 64-bit process) or to Windows Explorer x64, but when I try to drag files to the 32-bit Windows Explorer (which I use sometimes for compatibility with certain 32-bit Explorer extensions), I get this error.
Is it possible to install both the 32-bit and 64-bit WinSCP Explorer extensions on x64 Windows? (Many other apps do this.)
You do not have that amount ;-)How big a donation would it take to get you to build a 64 bit version that handles SMB shares??
Advertisement
There are no plans for that.
Advertisement
We cannot make 64 bit version of WinSCP in near future due to technical constraints.
Anyway, what advantage would 64 bit version bring to you?
"Technical contraints" means that the first stable version of 64 bit C++ Builder was released only a month ago."Technical constraints" usually means there isn't a programmer that uses the required platform, nor has the expertise to optimize for 64 bit. Since that expertise doesn't exist here, I suppose I'll keep looking.
Advertisement
It's not as trivial as to just compile it.Any plans to compile under x64 ? compiler is out.
We cannot make 64 bit version of WinSCP in near future due to technical constraints.
Anyway, what advantage would 64 bit version bring to you?
I suppose you are referring to WinSCP .NET assembly, not WinSCP itself.We use WinSCP with SSIS, since SSIS does not have a Secute FTP component. Since WinSCP is a 32bit app, we need to run the whole SSIS in 32 bit and loads suffer from teh performance. It would be beneficial if we could run the whole project in 64bit.
Advertisement
We are going to release stable version of 5.2.x branch in new few days/weeks. Than we will start working on a new branch, for which we plan to upgrade to the latest version of C++ Builder with x64 support. Then we will be able to assess a feasibility of implementing support for x64.The technical constrains mentioned on the Altap website were that the 64bit compiler was not available. This has change some month ago, didn't it ?
When will a 64bit version of the plugin for Altap Salamander available ?
Actually, I do not get this. WinSCP .NET assembly has platform set to AnyCPU, so it can load as 64-bit into 64-bit process. What particular problems are you having with this?I suppose you are referring to WinSCP .NET assembly, not WinSCP itself.We use WinSCP with SSIS, since SSIS does not have a Secute FTP component. Since WinSCP is a 32bit app, we need to run the whole SSIS in 32 bit and loads suffer from teh performance. It would be beneficial if we could run the whole project in 64bit.
While the assembly is made available in binary form for 32 bit only, it should be trivial to download the source code and compile it for 64 bit yourself. But I admit I haven't tested it. Will do.
Added to tracker:
https://winscp.net/tracker/1016
Advertisement
We are going to release stable version of 5.2.x branch in new few days/weeks. Than we will start working on a new branch, for which we plan to upgrade to the latest version of C++ Builder with x64 support. Then we will be able to assess a feasibility of implementing support for x64.The technical constrains mentioned on the Altap website were that the 64bit compiler was not available. This has change some month ago, didn't it ?
When will a 64bit version of the plugin for Altap Salamander available ?
Not yet.any news reagrding Slamander 64 bit version?
Is there anyting new regarding 64bit Salamander plugin?Not yet.any news reagrding Slamander 64 bit version?
Not yet.Is there anyting new regarding 64bit Salamander plugin?
Advertisement
What? WinSCP 64-bit or Salamander 64-bit WinSCP plugin? Both are planned, in a (rather long) term. In this order. No news yet. It's not a priority. Why do you need it?no news? Is it planned actually?
Advertisement
Why do you need 64-bit Salamander?"Salamander 64-bit WinSCP plugin"
From salamander web siteWhy do you need 64-bit Salamander?"Salamander 64-bit WinSCP plugin"
Sure, I'm aware of these limitations. I believe this is very specific problem that very few users actually face.Modern Windows are all 64-bit.
32-bit version of Altap Salamander has a number of limitation when running on 64-bit Windows. Mostly because of these 2:
1. https://docs.microsoft.com/en-us/windows/win32/winprog64/registry-redirector
2. https://docs.microsoft.com/en-us/windows/win32/winprog64/file-system-redirector
Specially when you're a software developer. I have to keep both version of AS. Very inconvenient.
Advertisement
Sure, I'm aware of these limitations. I believe this is very specific problem that very few users actually face.
I was just wondering, if a new user case emerged that I'm not aware of. Apparently not. Thanks anyway.
Thanks for this information.Well, a good use case for me would be using 64bit GSSAPI for login. This is not possible with 32bit application.
Advertisement
TheI am working on a 64bit Windows 2012 R2 server and converting old VBS scripts that use the WINSCPNet.dll to transfer files. The issue I come across is that the DLL is 32bit making it impossible to run the converted script outside of C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe. It would really be helpful if this interface was 64bit.
winscpnet.dll
assembly targets "AnyCPU". So you can use it both in 32-bit and 64-bit environments. We will need more details about your problem to help you.Thanks for this information!martin, since no one else has mentioned it: I've had good results compiling PuTTY "beta" and snapshot source with both MSVC++ 2015 Community Edition and the RC of MSVC++ 2017.
Advertisement
I do not get this problem. I can load the assembly into 64-bit PowerShell without any problems.This is what happens when I run a powershell script using the native 64bit version of Powershell.exe:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Windows\system32>\\tpa-isl\ftp\budd\aig_autoftp.bat
C:\Windows\system32>PowerShell -NoProfile -ExecutionPolicy Bypass -Command "& '\
\tpa-isl\ftp\budd\WINSCP.ps1'";
Add-Type : Could not load file or assembly
'file:///C:\Windows\system32\WinSCPnet.dll' or one of its dependencies.
Operation is not supported. (Exception from HRESULT: 0x80131515)
Sorry, nothing has changed since you have asked the last time.any progress? Putty is now 64-bit
Advertisement
Martin, is there any chance you'd consider moving to a free-as-in-beer build environment? I pulled down the source to see if I could cajole it into compiling against a Win64 target, but I don't have Embarcadero C++ Builder XE6 Professional. I imagine most people don't. I do have Visual Studio 2015 (because it's free). I didn't bother checking the other requirements.Thanks for this information!martin, since no one else has mentioned it: I've had good results compiling PuTTY "beta" and snapshot source with both MSVC++ 2015 Community Edition and the RC of MSVC++ 2017.
It's unlikely. I do not have a time to reimplement WinSCP using a different toolkit.Martin, is there any chance you'd consider moving to a free-as-in-beer build environment? I pulled down the source to see if I could cajole it into compiling against a Win64 target, but I don't have Embarcadero C++ Builder XE6 Professional. I imagine most people don't. I do have Visual Studio 2015 (because it's free). I didn't bother checking the other requirements.
Thanks for this information.Also, in response to your note above about there not being a good reason to make an x64 build of WinSCP available - Microsoft have been providing Server (optionally) without WoW64 since at least Server 2008 R2. Leaving out WoW64 means significantly lower memory and disk requirements. I would absolutely install Windows without WoW64 if I could get away with it... but I can't, because I need tools like WinSCP that haven't made x64 builds available.
There are some other very good reasons; too many to go into here, but one is that ASLR is crippled on 32-bit systems, in 32-bit subsystems, and in 32-bit binaries. It's not a Windows-only problem, either.
Aw, man. Well, I had to ask. I'd like to help move WinSCP forward; I really prefer it to the other SFTP solutions I have available.It's unlikely. I do not have a time to reimplement WinSCP using a different toolkit.Martin, is there any chance you'd consider moving to a free-as-in-beer build environment? I pulled down the source to see if I could cajole it into compiling against a Win64 target, but I don't have Embarcadero C++ Builder XE6 Professional. I imagine most people don't. I do have Visual Studio 2015 (because it's free). I didn't bother checking the other requirements.
Advertisement
You can post new topics in this forum