Windows 95 Shareware (Platinum Edition)

home *** CD-ROM | disk | FTP | other *** search

/ Windows 95 Shareware (Platinum Edition) / QUEPLAT95.ISO / files / inteutil / rcprsh32 / rcp.doc < prev next >

Wrap

Text File | 1995-06-27 | 17.6 KB | 440 lines

Winsock RCP for Win32 Version 1.7 Copyright 1994 Denicomp Systems All Rights Reserved DESCRIPTION ----------- Winsock RCP ("Remote Copy") for Win32 copies files between a PC and a remote host or between two remote hosts. It is similar to the Unix utility of the same name. There are two versions of Winsock RCP included: a "console" version that is well-suited for use from the Command Prompt (named "RCP") and a windowing version that displays output in a window, allowing you to use the scroll bars to review the output, cut/paste it, or save it to a file. The windowing version is named "WRCP". The "remote host" must be a system running the rshd ("remote shell daemon") server. This can be a Unix system or a Windows-based PC running Denicomp Systems' Winsock RSHD. Please note that if you are using Windows NT, it includes rexec. Since the rexec included in this packages has the same name, you must be sure to put the directory that contains Winsock REXEC at the beginning of your PATH environment variable (or rename NT's rexec command). REQUIREMENTS ------------ Winsock RCP requires a PC running Windows NT, Windows 95, or other Windows operating system that supports WSOCK32.DLL, and a connection via TCP/IP to a host running the rshd server. SYNTAX ------ Console Version: rcp [-abcdhfmprvw] [[User@][Host:]]{File|Dir} ... [[User@][Host:]]{File|[Dir]} Windowing Version: wrcp [-abcdfprw] [[User@][Host:]]{File|Dir} ... [[User@][Host:]]{File|[Dir]} PARAMETERS ---------- User@ (optional) Specifies the user name to be used at the remote host. If this prefixes the Host: parameter, this user name overrides the name of the user currently logged in. Host: Specifies the host name of the remote host. This is not required if the file or directory referenced is on the local system. This host must be a system running the rshd server process. File Specifies the filename of the source or destination file. You may use wildcard characters to copy multiple source files. You may also specify multiple source files individually by separating the names with spaces. If the filename includes embedded spaces, you must enclose it in double quotes. Dir Specifies the name of the source or destination directory. HOST NAMES ---------- The Host: parameter is required for either the source file/directory or the destination file/directory. Copying between two remote hosts is permitted by specifying a Host: for both the source and destination. If a remote host name is not specified for either the source or the destination, you will receive an error. Use the COPY command instead. You should not use the Host: parameter when referencing local files. The local user name determines the file access privileges permitted at the remote host. This name also determines the ownership and access modes of the destination file or files. If the Host is prefixed by the User@ parameter, that name is used as the user name at the remote host. If the User@ parameter is not used, the local user name is used at the remote host. USER NAMES ---------- The local user name is normally the name you used when logging in to Windows NT or Windows 95. For example, if you logged in to Windows as the user "joed", Winsock RCP will use "joed" as the user name at the remote host. Winsock RCP will always convert this name to all lowercase characters. To maintain some compatibility with the 16-bit version, Winsock RCP will also continue to look at the file WIN.INI in the Windows directory (e.g. \WINNT35 or \WINDOWS) for an alternate user name to use as the local user name. If WIN.INI contains a section named "[RCP]" and contains an entry named "User" in that section, the name specified there will be used as the local user name. For example, WIN.INI might contain: [RCP] User=joe If this appeared in WIN.INI, the local user name would be "joe" and Winsock RCP would use this name at the remote host. To support multiple users, Winsock RCP will also look for a section named "[RCP-user]" in WIN.INI first for an alternate user name, where the "user" in the section name is the name used to log in to Windows NT/95. Winsock RCP will look at this section first; if it does not exist, it will then look at the "[RCP]" section (without a user name). For example, if "Mary Jones" and "John Smith" are both users on the Windows PC, but their user names at the remote host are "mary" and "john" respectively, WIN.INI might look like this: [RCP-John Smith] User=john [RCP-Mary Jones] User=mary When the Windows user "John Smith" uses Winsock RCP, "john" will be used at the remote host. When the Windows user "Mary Jones" uses it, "mary" will be used instead. Please note that the use of WIN.INI is supported only to maintain some compatibility with the 16-bit version of Winsock RCP. It is highly recommended that you maintain the same user names across your systems. FILE NAMES ---------- If a full directory path is not specified for a remote host, the path begins at the user's home directory. That is, if the file/directory name specified after the Host: parameter does not begin with a slash (/), it is assumed to reference a file/directory in the user's home directory. For example, the file "joe@remhost:file.txt" refers to the file "file.txt" in the home directory of the user "joe" on the host "remhost". Filenames may contain either slashes (/) or backslashes (\) as directory separators, for either the host file/directory or file/directories on the PC. They will be converted to the appropriate separator. You can copy multiple files by using wildcard characters, such as * or ?. You can also copy multiple source files by separating them with spaces. If the source files reside on the remote host, you must specify the Host: (and optionally the User@) parameter for each file. If you copy multiple source files with wildcard characters or by specifying individual filenames, the destination must be a directory. Note that a colon (:) terminates the host name. This causes a problem when filenames on the PC require a drive letter (e.g. A:). If a file name specification begins with one character between A and Z and is followed by a colon (:), Winsock RCP will interpret this as a drive letter instead of a host name. This means that Winsock RCP cannot handle one character host names. The destination cannot contain only a drive specification (e.g. A:). It must also include a filename or a directory name. If the destination is the current directory on the drive, use "." (e.g. A:.). COMMAND LINE OPTIONS -------------------- -a ASCII conversion. For file(s) transferred to the remote host, all sequences of CR/NL (ASCII 13/10) will be converted to NL (ASCII 10). This is the standard Unix text file format. For file(s) transferred from the remote host to the PC, a CR (ASCII 13) will be added before every NL (ASCII 10) if that NL is not already preceeded by a CR. This is the standard MS-DOS text file format. Without the -a option, files are transferred with no translation. -b Binary transfer. File(s) are transferred with no modifications. This is the default, so this option is not necessary if you want a binary transfer. It is provided for command line compatibility with other RCP commands from other vendors. -c Preserve the case of filenames copied using the recursive option (-r) or wildcards. By default, all filenames are converted to lowercase characters before being sent to the remote host. This is normally useful, especially when copying to case-sensitive systems, such as Unix. However, since Windows NT and Windows 95 can store filenames in mixed case (even though the file system is not case senstive), you can use this option to preserve the case of the names as they appear in the Windows directory. Note that this ONLY affects recursive copies and wildcard copies. If you copy individual files by specifying their names on the command line, the case that you use on the command line will be used at the remote host. For example: rcp xyz unix:/tmp Will create the file "/tmp/xyz" on the "unix" host. The command: rcp XYZ unix:/tmp Will create the file "/tmp/XYZ" on the "unix" host. Note that under Windows NT and Windows 95, "xyz" and "XYZ" represent the SAME file. However, under Unix, these are two different filenames. -d Ignore directories in wildcards. When using wildcards to copy multiple files, normally RCP will attempt to copy any directories that match the wildcard pattern. If you are not using the recursive copy option (-r), you will receive errors on the directory names matched. This option excludes the directories when matched and you will not receive the errors. -f Copy hidden files. Normally, wildcard patterns and recurive copies to not include files with the "hidden" attribute. If you specify this option, wildcard copies and recursive copies will copy hidden files. -h Run Hidden. Like -m, but the window will be completely hidden. Use with caution, since hidden windows cannot be accessed using the Task Manager, so you cannot use it to manually stop a transfer. ** This option is only available in the windowing version (wrcp) ** -m Run Minimized. Normally, Winsock RCP will display a window showing progress and any possible error messages. With -m, Winsock RCP will only display a minimized icon while running. This is useful for software developers who wish to call Winsock RCP transparently from within their software. ** This option is only available in the windowing version (wrcp) ** -p Preserve access and modification times. Normally, when you copy a file to the local system, the files are created with access and modification times of the current date and time. This option will preserve the access and modification time of the file as it was on the remote host. -r Recursively copies, for directories only, each file and subdirectory in the source directory into the destination directory. -v Verbose. In the Console version (rcp), this will display the name of each file as it is copied. Normally, this does not occur. In the windowing version (wrcp), the names of the files display in the window automatically, so this option is not necessary, although specifying it will not cause an error. -w Wait at the end of the command. In the Console version (rcp), it will wait for you to press the Return key after the file(s) are copied so you can view the list of files copied and any error messages from the remote host. In the windowing version (wrcp), it will wait for you to close the RCP window (using File/Exit from the menu, for example). If you are copying multiple files and the list scrolls the window, you can use the scrollbars to review the scrolled information. You can also cut/paste information into other windows or save the information in the window to a file. NOTES FOR OPTIONS ----------------- Specify all options separately; do not combine options. For example, do not use "-amw"; use "-a -m -w" instead. The -a option translates the file regardless of its actual contents. For example, if you transfer a non-text file using -a, it will be modified as if it were a text file. The resulting file will most likely be unusable. If you use the -a option and you transfer multiple files, all files will be translated as ASCII files. Using the -a option to transfer files TO the remote host will slow the operation of Winsock RCP somewhat because it must read each file twice. It reads the file once to calculate the new translated file size, then reads it again to transfer the data. This is because the RCP protocol requires that the exact file size be transmitted before the actual data in the file is sent. Without the -a option, the file size can be found by examining the file's directory entry, but with the -a, the file's contents must be examined to determine the size after CR/NL combinations are replaced with NL. The -a option will also slow Winsock RCP when transferring files FROM the remote host, but only slightly. If transmission speed is critical, consider using utilities to translate the text files after they are transferred. UNIX SECURITY ------------- If the remote host is running the Unix operating system, it allows access if one of the following conditions is satisfied: * The name of the local host (your PC) is listed in the /etc/hosts file on the remote host (Unix) with the proper IP address and as an equivalent host in the /etc/hosts.equiv file on the remote host. * If the name of your PC is not in the /etc/hosts.equiv file, the user's home directory on the remote host must contain a .rhosts file that lists the name of your PC and your user name. The .rhosts file in the user's home directory must be owned by either the user specified or "root", and only the owner should have read and write access. That is, it must have permissions of 0600. * The user's login on the remote host does not require a password. ADDITIONAL OPTIONS ------------------ There are two options you can specify in the [RCP] section of WIN.INI to control the behavior of Winsock RCP. The Minimize entry allows you to control the display of the Winsock RCP window without using the -m or -h command line options. This is useful if you have third party software that calls Winsock RCP and you cannot modify it to run Winsock RCP minimized or hidden through command line options. If you set Minimize to a value of 1 in WIN.INI, Winsock RCP will always run minimized. If you set Minimize to a value of 2, Winsock RCP will always run hidden. For example, to always run Winsock RCP minimized, specify in WIN.INI: [RCP] User=joe Minimize=1 If either the -m or -h options are specified on the command line, these will override the option specified in WIN.INI. However, there is no way to cause Winsock RCP to run with a normal window if the Minimize option is specified in WIN.INI. The other option available is the BlockSize entry. This specifies the number of bytes that will be read from a file and sent over the network connection or the number of bytes read from the network connection and written to a file at one time. Note that this does NOT change any TCP/IP parameters; it is an internal buffer size only. By default, this is set to a value of 512 bytes. Normally, you do not need to change this option. If you set it too high, you may receive "out of memory" errors from Winsock RCP and it may limit you to the number of recursion levels when doing recursive copies. NOTE: Both of these options must be specified in the [RCP] section in WIN.INI. They cannot be specified by user using the [RCP-user] section. Therefore, if specified, they will apply to all users logging on to the PC. EXAMPLES -------- * To copy a file from the PC to a remote host, use: rcp localfile remhost:/u/joe The file localfile is copied from the PC to the remote host remhost and placed in the directory /u/joe. * To copy a file from the remote host to the PC, use: rcp remhost:/u/joe/remfile \lists\remfile The file remfile is copied from the remote host remhost to the file remfile in the directory \lists on the PC. * To copy a remote file from one remote host to another remote host, use: rcp host1:/u/joe/xfile host2:/u/fred/yfile The file /u/joe/xfile on host1 is copied to the file /u/fred/yfile on the remote host host2. * To copy all of the files in the directory \docs to the a remote host: rcp -a -w \docs\*.* remhost:/u/docs All of the files in \docs are copied to the directory /u/docs on the remote host remhost. The files are converted from the MS-DOS text file format to the Unix text file format using the "-a" option. As the files are transferred, their names will display on the screen. The "-w" option tells Winsock RCP to wait for you to press Enter after the files are transferred so you can examine the list. * To copy the file from a remote host to the diskette in drive A: on the PC: rcp mary@remhost:resume.doc a:. This will copy the file resume.doc from the user mary's home directory (since no starting directory was given after the host) to the same name on the diskette in drive A: on the PC. Note the "." after the colon of the drive letter. This refers to the current directory on the A: drive, since a destination filename or directory name is required. * To send the entire directory tree from the PC to a remote host, use: rcp -r \share joe@remhost: The directory \share is copied from the PC to the home directory of joe on the remote host remhost. NOTE: You can subsititue "wrcp" for all of the above examples if you wish to use the windowing version of Winsock RCP. SUPPORT ------- Support is available via U.S. Mail and Compuserve/Internet. Denicomp Systems P.O. Box 731 Exton, PA 19341 Compuserve: 71612,2333 Internet: 71612.2333@compuserve.com