When running the ftp executable for Windows via a PROCESS START request, why aren I getting the remote server responses in stdout?
When using the PROCESS service to run command “ftp -s:C:/temp/stdin.txt” on a Windows machine, where C:/temp/stdin.txt is a text file that contains the FTP commands to run after FTP starts, if you don’t specify the SAMECONSOLE option (e.g. if you use the NEWCONSOLE option which is the default),, the remote server responses are not written to stdout. However, if you can specify the -v option for the ftp executable when using new console, then the remote server response are written to stdout. For example: “ftp -v -s:C:/temp/stdin.txt”. When you specify the SAMECONSOLE option, the remote server responses are written to stdout when you don’t use the -v option for the ftp executable. For example, say file C:\temp\stdin.
Related Questions
- How do I install the PowerEdge Expandable RAID Controllers Power Console remote client utility on a console server running Windows NT?
- When running the ftp executable for Windows via a PROCESS START request, why aren I getting the remote server responses in stdout?
- Cannot use smart card credentials to logon when running Remote Desktop on Windows XP or Windows Server 2003?
