executables » Revisions »
Differences
This shows you the differences between the selected revisions of the page.
| 2026-06-02 | 2026-06-03 (current) | ||
| 6.6.2 Issue 2434 – Allow Console interface tool to have .exe extension to avoid false positive detections by some antiviruses (martin) | security_software anchor (martin) | ||
| Line 24: | Line 24: | ||
| * When run from another console application (such as standard Windows console/command-line window, i.e. ''cmd.exe''), it inherits its console.((''winscp.exe /console'' would pop up in new console window.)) | * When run from another console application (such as standard Windows console/command-line window, i.e. ''cmd.exe''), it inherits its console.((''winscp.exe /console'' would pop up in new console window.)) | ||
| - | The ''.com'' executable needs the ''.exe'' one to operate. It looks for it in the same directory where it is located itself. The ''.exe'' must have exactly the same name.((If your security software flags a PE executable file with the ''.com'' extension, you can rename ''winscp.com'' to ''WinSCP-com.exe''. &beta_feature)) | + | The ''.com'' executable needs the ''.exe'' one to operate. It looks for it in the same directory where it is located itself. The ''.exe'' must have exactly the same name.((If your ==security software== flags a PE executable file with the ''.com'' extension, you can rename ''winscp.com'' to ''WinSCP-com.exe''. &beta_feature)) |
| As WinSCP is an Unicode application, you should use a TrueType console font with a full Unicode support, like "Consolas" or "Lucida Console". | As WinSCP is an Unicode application, you should use a TrueType console font with a full Unicode support, like "Consolas" or "Lucida Console". | ||