LANXCOPY

LANXCOPY Version 1.00 Chris Ahl RTP, N.C. 03/17/94 LANXCOPY is similar to the DOS and OS/2 XCOPY command. However, LANXCOPY allows the transfer of files between two machines on the same LAN without the need to have PCLP or LAN Requester/LAN Server running in either machine. Instead, LANXCOPY uses the NETBIOS interface to transfer the files. The main reason for developing LANXCOPY was to eliminate the Sneaker Network that many of us use daily to get files from one machine to another. How many times have you searched for a diskette so that you could copy files from one machine to another machine even though the machines were on the same LAN? It's even worse if you have to convert between 5 1/4" and 3 1/2" diskettes. Not to mention what you go through if the files fill up more than one diskette. So the next time you need to copy files from one machine to another and they are on the same LAN, give LANXCOPY a try. The time and effort saved may be worth the couple of minutes it takes to learn to use LANXCOPY. -------- Features -------- - Bound executable - runs under DOS or OS/2. - Uses Netbios - PCLP and/or LAN Requester/LAN Server are not needed. - Ability to copy subdirectories. - Ability to copy Hidden files. - Ability to copy System files. - Maintains a log file containing details of each transfer. - Saves time and effort compared to using diskettes. - Saves wear and tear on your shoes! ----- SetUp ----- Before you use LANXCOPY you need to: - Add the environment variable LANXCOPY_ID=<name>. Where <name> is the name you want to be known by on the LAN when using LANXCOPY. Do this in one of two ways: - Do a SET LANXCOPY_ID=<name> on the command line. - Add SET LANXCOPY_ID=<name> to your CONFIG.SYS for OS/2 or AUTOEXEC.BAT for DOS. This is the preferred way. Every time you reboot your machine, this environment variable will be set. If you just edited CONFIG.SYS and added this variable, it will not take effect until you reboot your machine. - Copy LANXCOPY.EXE to your utilities directory or any other directory that is in your PATH= statement. - Make sure that you have NETBIOS installed on your LAN attached machine. -------------- Using LANXCOPY -------------- LANXCOPY has been run through the IBM C/2 BIND utility. This will allow LANXCOPY to run on both DOS and OS/2. So whether you use DOS or OS/2 you only need to remember and use one program, LANXCOPY. Since LANXCOPY operates over a LAN, it requires that both machines run LANXCOPY. The machine which will be the RECEIVER should be the one started first. After the RECEIVER machine is running and waiting to receive files, the SENDER machine is started. The SENDER machine will attempt to locate the RECEIVER machine. If successful, file transfer will be attempted. LANXCOPY will display the current file being copied and the result of the copy operation. This allows both the SENDER and RECEIVER to know exactly what files have been processed. After all the files specified by the SENDER have been processed, the SENDER application will terminate. The RECEIVER has the option of terminating or remaining active and waiting for more files from another SENDER. To aid the user in keeping track of file transfers, LANXCOPY maintains a log. The log file is LANXCOPY.LOG and it resides in the same directory as the LANXCOPY executable. For more information on this, look under Log File For details on invoking LANXCOPY to receive and send files, please refer to the next two sections. --------------- Receiving Files --------------- -The RECEIVER side of LANXCOPY must be started first. -LANXCOPY <from> <to> (optional) -Required Parameters: <from> Receive files from this LANXCOPY_ID. Prefix with FROM:. You may use an asterisk (*) to specify that you wish to receive files from whoever sends them to you. <to> An existing directory where all received files will be copied to or under. Optional Parameters: /A Use the alternate LAN adapter /B Emit a beep when the program ends /C Allow creation of subdirectories if required. The subdirectories will be created under the directory specified in the <to> parameter. /H Accept files even if they have the Hidden attribute bit turned on. /L Don't create a LOG file on the disk /R Replace files if they already exist under the directory specified in the <to> parameter. NOTE: Use this parameter with caution since even files with the read only bit turned on will be replaced. /X Exit after transfer of files. After the SENDER side has transferred all files specified, it will terminate. If you wish for the RECEIVER to terminate after the transfer of files, specify this parameter. /Y Accept files even if they have the System attribute bit turned on. Receive Example Receive files from JACK into directory C:\TEMP. LANXCOPY FROM:JACK C:\TEMP ------------- Sending Files ------------- -The SENDER is started after the RECEIVER is up and running. LANXCOPY <from> <to> (optional) Required Parameters: <from> Send these files. Wildcards are supported. <to> Send files to this LANXCOPY_ID. Prefix with TO: Optional Parameters: /A Use the alternate LAN adapter /B Emit a beep when the program ends /F The file specified contains a list of files to send. The file names need to be separated by blanks or place each file name on a separate line. Wildcards are allowed. /H Copy Hidden files. (NOTE: The RECEIVER must use the /H switch also in order for the files to be copied) /L Don't create a LOG file on the disk /S Search all subdirectories under the directory specified in the <from> parameter for matching files. /T=n Timed retries, 1 minute apart, will be performed in an attempt to locate the receiver. Useful if you have many senders trying to get to one receiver. n is the number of retries from 1 to 65000. The default is 0. /Y Copy System files. (NOTE: The RECEIVER must use the /Y switch also in order for the files to be copied) Send Example Copy all files in the current directory to JOE. LANXCOPY *.* TO:JOE -------- Examples -------- NOTE: All of the following examples assume that the SETUP has been performed. - Send C:\CONFIG.SYS from A to B. B will receive files from anyone and place them in C:\LANXCOPY. After B has received the files, it will terminate LANXCOPY. B types: LANXCOPY FROM:* C:\LANXCOPY /X After LANXCOPY displays a message that it is waiting to receive files A types: LANXCOPY C:\CONFIG.SYS TO:B - Send all the files in C:\UTILITY from A to B. B wants to receive the files in D:\TEMP and only receive files from A. B types: LANXCOPY FROM:A D:\TEMP After LANXCOPY displays a message that it is waiting to receive files A types: LANXCOPY C:\UTILITY TO:B - Send every file on C: including subdirectories, system, and hidden files from A to B. B will receive the files in C:\BAK and will allow the creation of subdirectories and copying of system and hidden files. B types: LANXCOPY FROM:A C:\BAK /C /H /Y After LANXCOPY displays a message that it is waiting to receive files A types: LANXCOPY C:\*.* TO:B /S /H /Y ------------ Restrictions ------------ -Only 8.3 filenames are supported. -Only file attributes supported by DOS are supported. -Attributes of directories such as hidden and system are not copied. -------- Log File -------- A log file, LANXCOPY.LOG, is used to keep track of all file transfers that occur. The file resides in the same directory as the LANXCOPY executable and is appended each time LANXCOPY is started. This file may be deleted or edited if you wish so that it does not get too large. With each invocation of LANXCOPY, a header will be printed displaying the LANXCOPY version along with the date and time the program was started. All the information which appears on the screen during the execution of the program will also be put in the log file. It is up to the user of the program to occasionally prune or delete the LANXCOPY.LOG if it becomes too large. -------- Security -------- Since LANXCOPY operates over a LAN, it is necessary to provide some basic security measures to protect both the SENDER and the RECEIVER of the files. SENDER security is provided in two ways: - The SENDER explicitly specifies where the files are going to be sent. This keeps files from inadvertently going to a machine other than the one expected. - The SENDER specifies what files are to be sent to the RECEIVER. This keeps the RECEIVER from gaining access to any files which the SENDER does not want the RECEIVER to see. RECEIVER security is provided in six ways: - The RECEIVER specifies the directory where LANXCOPY will base all copied files. All files will be copied in or under this directory. - The RECEIVER can explicitly specify who files are to be received from. Only a specific SENDER can send files to this RECEIVER. - The RECEIVER controls the replacement of files which already exist. The RECEIVER may or may not allow the SENDER to replace a file. - The RECEIVER controls the creation of subdirectories under the base directory described in the first RECEIVER security measure. - The RECEIVER can deny the copying of Hidden files. - The RECEIVER can deny the copying of System files. --------------- Common Problems --------------- -NETBIOS AddName or NETBIOS Reset failed. This usually occurs when there are not enough NAMES, SESSIONS, or NCBS defined for the NETBIOS interface. For OS/2, use Comm Mgr to increase NAMES by 1, SESSIONS by 2, and NCBs by 4. -NETBIOS Reset failed. Make sure adapter is operational. This means that the adapter you are trying to run LANXCOPY on - Is not present in your machine. - Is not operational. You may not have the proper device drivers loaded for the adapter to work properly. If you are using DOS, make sure the LAN Support Program is installed properly. For OS/2, make sure that Communication Manager is installed properly. -You have not installed NETBIOS support for this adapter. You can check to see if you have NETBIOS installed on DOS by looking for the statement DEVICE=<path>DXMT0MOD.SYS in CONFIG.SYS. For OS/2 1.2 and 1.3, look at the \CMLIB\ACSLAN.LOG. For OS/2 2.0, look at \IBMCOM\LANTRAN.LOG. If the OS/2 logs have a message that says NETBIOS is installed, then you do have NETBIOS. Note to OS/2 2.0 Users: NETBIOS is not automatically installed during installation of Extended Services. Be sure to use Communication Manager to add NETBIOS support to the adapter you want to run LANXCOPY on. -Environment variable LANXCOPY_ID not found Before you use LANXCOPY, you must specify this environment variable which lets LANXCOPY know what you userid will be for the LANXCOPY program. See the SETUP section for more information. -Unable To Open The File On RECEIVER The file may already exist on the RECEIVER and have the READ ONLY bit turned on. You need to change the READ ONLY bit of this file before LANXCOPY will replace it.