Winsock RCP/RSH Version History ------------------------------- Version 1.0 - Initial Release Version 1.1 - Added -r option to RSH for redirection of output Added -a and -b option to RCP for ASCII conversion Version 1.2 - Corrected problem in RCP that would not allow recursive copies from a drive other than the current drive. RCP would find the filenames from the specified drive, but would try to read the data from the current drive, causing "File Not Found" errors. For example, the following would not work if the current drive was the C: drive: rcp -r a:\doc remhost:/usr/doc - RCP and RSH would only allow a host name to be used, not an IP address (i.e., a dotted-decimal address of the host). For example, the following would result in a "Record Not Found" error from Windows Sockets: rsh 89.0.0.8 ls -x or rcp 192.15.32.1:/usr/joe/file \doc For the technically curious, this occurred because the Windows Sockets "gethostbyname()" function only allows host names to be specified, unlike Unix, which allows both IP addresses and host names. RCP and RSH now determine whether or not you have specified a host name or IP address and adjusts accordingly. Version 1.3 - Corrected a problem with wildcards. Sometimes the last character of the directory name prefixing the wilcard was being thrown into the name, causing it to not find the files. - Corrected a memory leak. Version 1.4 - Will retry up to ten times when a Connection Refused error occurs. Version 1.42 - Added retry on Shutdown and Timeout errors. Added two options that can be placed in the [RCMD] section of WIN.INI: (The setting in the [RCMD] section sets the option for BOTH Winsock RCP and RSH) RetryError: Set this to the Windows Socket error number (usually between 10000 and 11000) that you want Winsock RCP/RSH to retry on when received when trying to connect to the remote host. This number should be POSITIVE, even though the Winsock RCP/RSH error window shows it as negative. RetryCount: The number of times Winsock RCP/RSH should retry when the Connection Refused, Shutdown, Timeout, or the error specified in the RetryError configuration option is received. The default is ten (10) times. Version 1.43 - Corrected problem with recursive copies. Version 1.50 - Correct problem with error handling in RCP. Add additional retries for Trumpet in RSH and RCP. Added 800 number for orders through PsL. Version 1.60 - Added REXEC utility. - Allows host name to appear before or after flags to be compatible with Unix syntax. - Officially added -h (hidden) option to RSH, REXEC, and RCP. - Added -t option to allow redirection and display of data in RSH and REXEC. - Speeded up display of RSH by reading in blocks of 512 bytes. - Allow Minimize option in WIN.INI to externally control window display. - Allow BufSize option in WIN.INI to control number of characters in each block of data read in RSH and REXEC. Version 1.62 - Added better handling of window close during an operation. - Added -q option (for "quiet" - no error messages displayed) to RCP. - Added -l option (for "log file") to RCP. Specifying "-l filename" on the command line will write all error messages to "filename". They will not be displayed on the screen (i.e. the "quiet" option is also enabled). Version 1.63 - Changed to write redirected output (using -f or -t) in binary mode (no end-of-line conversion). If end-of-line conversion is desired, place the line "ASCII=1" in the [RSH] or [REXEC] section of WIN.INI. Version 1.64 - Would not allow a command to be sent to the host through RSH or REXEC if it began with an at-sign (@). This is because it used that to determine whether or not the command was actually a macro file. Now, you can specify two at-signs (@@) as the first two characters of a command and only one will be sent as the first character. Note that this is ONLY required when the @ should appear as the FIRST character of the command. For example, if the command for the remote host is "@mycmd", use "@@mycmd". Also, you can disable the macro capability altogether by adding "Macros=0" to the [RSH] or [REXEC] sections of WIN.INI (depending on whether you are using RSH or REXEC). This would then remove the requirement of placing @@ at the beginning of commands that begin with @. All commands will be sent unmodified.