64 bits WinSCP version
Does exists a 64 bits WinSCP version?
If not, any prevision?
TIA
Advertisement
Advertisement
Advertisement
I think that's the reason that the TortoiseSVN guys have an x64 version as well as an x86 version.WinSCP was not able to detect folder, where the dragged file(s) was dropped. Either ...
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
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.WinSCP was not able to detect folder, where the dragged files(s) was dropped. etc.
Advertisement
Has this changed? It would be nice to get a x64 version of this.There are no plans for that.
Advertisement
"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
Advertisement
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe
. It would really be helpful if this interface was 64bit.
Advertisement
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.
Advertisement
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) At \\tpa-isl\ftp\budd\WINSCP.ps1:1 char:1 + Add-Type -Path "WinSCPnet.dll" -ErrorAction Stop + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Add-Type], FileLoadException + FullyQualifiedErrorId : System.IO.FileLoadException,Microsoft.PowerShell .Commands.AddTypeCommand New-Object : A positional parameter cannot be found that accepts argument ' Protocol = [WinSCP.Protocol]::Sftp HostName = "prod-mfttpg01" UserName = "fteadmin" Password = "Qurman98" SshHostKeyFingerprint = "ssh-rsa 2048 1d:fc:6c:2b:a8:89:24:13:9b:95:61:99:47:44:e1:26" '. At \\tpa-isl\ftp\budd\WINSCP.ps1:19 char:19 + $sessionOptions = new-object -ComObject WinSCP.SessionOptions { + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidArgument: (:) [New-Object], ParameterBind ingException + FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.PowerShell .Commands.NewObjectCommand New-Object : Cannot find type [WinSCP.Session]: verify that the assembly containing this type is loaded. At \\tpa-isl\ftp\budd\WINSCP.ps1:29 char:12 + $session = New-Object WinSCP.Session + ~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidType: (:) [New-Object], PSArgumentExcepti on + FullyQualifiedErrorId : TypeNotFound,Microsoft.PowerShell.Commands.NewOb jectCommand You cannot call a method on a null-valued expression. At \\tpa-isl\ftp\budd\WINSCP.ps1:34 char:1 + $session.SessionLogPath($slog) + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidOperation: (:) [], RuntimeException + FullyQualifiedErrorId : InvokeMethodOnNull You cannot call a method on a null-valued expression. At \\tpa-isl\ftp\budd\WINSCP.ps1:38 char:1 + $session.Open($sessionOptions) + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidOperation: (:) [], RuntimeException + FullyQualifiedErrorId : InvokeMethodOnNull New-Object : A positional parameter cannot be found that accepts argument ' TransferMode = [WinSCP.TransferMode]::Binary '. At \\tpa-isl\ftp\budd\WINSCP.ps1:57 char:20 + $transferOptions = new-object -ComObject WinSCP.TransferOptions { + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidArgument: (:) [New-Object], ParameterBind ingException + FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.PowerShell .Commands.NewObjectCommand New-Object : A positional parameter cannot be found that accepts argument ' OtherRead = $True OtherExecute = $True UserRead = $True UserWrite = $True UserExecute = $True GroupRead = $True GroupExecute = $True '. At \\tpa-isl\ftp\budd\WINSCP.ps1:75 char:16 + $permissions = new-object -ComObject WinSCP.FilePermissions { + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidArgument: (:) [New-Object], ParameterBind ingException + FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.PowerShell .Commands.NewObjectCommand You cannot call a method on a null-valued expression. At \\tpa-isl\ftp\budd\WINSCP.ps1:99 char:1 + $transferResult = $session.PutFiles("\\tpa-isl\ftp\save\kaiser\DNC_20170214.log" ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~ + CategoryInfo : InvalidOperation: (:) [], RuntimeException + FullyQualifiedErrorId : InvokeMethodOnNull You cannot call a method on a null-valued expression. At \\tpa-isl\ftp\budd\WINSCP.ps1:100 char:1 + $transferResult.Check() + ~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidOperation: (:) [], RuntimeException + FullyQualifiedErrorId : InvokeMethodOnNull You cannot call a method on a null-valued expression. At \\tpa-isl\ftp\budd\WINSCP.ps1:114 char:5 + $session.Dispose() + ~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidOperation: (:) [], RuntimeException + FullyQualifiedErrorId : InvokeMethodOnNull C:\Windows\system32>
Advertisement
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.
Advertisement
19057016@MAC13DQ05FJEN2 winscp553 % wine WinSCP.exe zsh: bad CPU type in executable: wine
19057016@MAC13DQ05FJEN2 winscp553 % wine64 WinSCP.exe 0024:err:process:exec_process L"Z:\\Users\\XXXXX\\Documents\\zz_simple_script_zz\\winscp553\\WinSCP.exe" not supported on this system
Advertisement
You can post new topics in this forum