TeleShare DOS Remote Access XM or XMODEM Page 1 Updated: December, 1994 This Product is Shareware, if you continue to use it Please Legalise your usage through Registration. _______ ____|__ | (R) --| | |------------------- | ____|__ | Association of | | |_| Shareware |__| o | Professionals -----| | |--------------------- |___|___| Member Table of Contents 1. File Transfer 2. Automatic File Transfer 3. Creating Batch File(s) for Automatic Transfer(s) FILE TRANSFER TeleShare primarily uses a stand-alone DOS program called XM.EXE (indicating the XModem protocol) to perform file transfers. This is in keeping with maintaining a small memory footprint in the PCs' limited available RAM. You can also use other external file transfer programs as described elsewhere in this distribution. XM.EXE is run from the DOS command line and runs as dependent child process of the TeleShare Host/Remote modules. XM.EXE will ONLY transfer files between 2 TeleShare systems. It is written specifically to get along with the TeleShare TSR's. It is small, simple, reliable, and uses the most widely used file transfer protocol to get the job done with minimal fuss. You can use DSZ, PCZ, and HYDRA with TeleShare if you wish. They provide a variety of external protocols. Using XM.EXE, with the XModem protocol, is akin to the DOS COPY command but differs in important ways as follows: Let's say that you are using TeleShare on two PCs and would TeleShare DOS Remote Access XM or XMODEM Page 2 like to transfer a file called RESULTS.TXT from the Host PC to your local machine. 1. While accessing the REMOTE HOST change to the area on that machine where XM.EXE is located. This is not necessary if XM.EXE is in a sub-directory listed in the current PATH or environment statement(s) on the HOST PC where the system can easily find it for you. 2. Enter 'XM S RESULTS.TXT' at the DOS prompt. Add any PATH characters necessary if RESULTS.TXT is not in the default sub-directory. If XM.EXE is in the \TELE subdirectory, you can use '\TELE\XM S RESULTS.TXT' The 'S' stands for 'SEND'. 3. If the file is found then the screen will clear and you will be informed that you have a certain amount of time to exit to your LOCAL DOS and run your own XM.EXE to receive the file. 4. When the message appears that the HOST is ready to SEND press ALT-L ( or whatever you have set the hotkey to) and exit to your own local DOS. Change to the area on your LOCAL PC where XM.EXE is located and enter 'XM R'. This will allow the file to be RECEIVED into the default sub-directory with the same name as the file being sent. (You can change the name during the transfer. See below). 5. The Transfer progress screen will appear and show the progress of the file transfer. Once back at your own local DOS prompt when the transfer is finished. 6. When the transfer is completed then simply press ALT-R ( or whatever you have set the hotkey to ) and return to the REMOTE HOST session. You will see the same transfer screen you saw locally on the REMOTE HOST. It will say 'SEND' instead of 'RECV' in the upper left corner of the screen. This allows you to discover what the other side had to say about the progress of the transfer (just in case gremlins attacked). Simply clear the screen (CLS) and continue your session normally. How to use the XM.EXE Command format XM [R or S] [ somefile ] [@filelist] XM This is the transfer program itself, unless you have renamed it. R or S The first parameter should be 'S' if XM is to SEND TeleShare DOS Remote Access XM or XMODEM Page 3 files. The first parameter should be 'R' if XM is to RECEIVE files. somefile File(s) to be transferred. Wildcards are OK when 'S' is used to SEND files. '*.DBF' is a wildcard for all the dBase files ending in .DBF in the current directory. @filelist The @filelist is a response file containing a list of files to be transferred in the following file format: anyfile C:\SOMEDIR\FILE1 C:\OTHERDIR\FILE2 D:\DOS\OTHER\FILE3 # a comment ; another comment You will notice that there is one file per line, and that the format is simple enough for various kinds of software to be programmed to produce such a file for your specific needs. You can include blank lines and add comments with a ; or a # symbol to the left of any comment. The @ can be used in place of the 'S', as in "XM @filelist". Such a filelist can be of any length, and is a good way to backup or update specific files to another (off-site) location for security. However, you should consider using an archiver like lha or pkzip if you need to minimise transfer times and/or add security. Other Teleshare tools produce files with this format, and some add commands such as [transfer],[copy], [move], and [erase]. The lines following a [transfer] command are for file transfer to another computer. Normally, xm will bypass portions of a response file that are not for file transfer. You can create such files for use with the GATHER program, and gather will automatically follow the commands and will pass them to XM when the [transfer] is included. If you are RECEIVING files then this parameter is optional. You can simply enter 'XM R' and all files will be received using the SAME name as the one sent. This works whether it's 1 or 100 files being sent. If you are RECEIVING one file only and you wish to change its name on your side then go ahead and enter the desired new_filename after the 'R' parameter. When the name arrives from the HOST the transfer box will tell you that it's 'Receiving ORIGINAL_NAME as NEW_NAME'. 'NEW_NAME' will appear in your local directory. If you are receiving more than 1 file then you cannot enter an alternate filename after the 'R' parameter. You must receive ALL the files using the names sent. TeleShare DOS Remote Access XM or XMODEM Page 4 Some important reminders... - You MUST separate the XM parameters with SPACES, so it will not become confused trying to find 'Ssomefile' when it should just be using the Send command to send the 'somefile'. - You cannot enter a LIST of different filenames one after the other in this version. Groups of files can only be sent if they can be distinguished with any normal DOS wildcard directory command. Use a response file. - If your LOG files option is ON then the progress and results of each 'XM' request will be appended to either XMSEND.LOG or XMRECV.LOG. - You cannot access the remote PC while transferring files. XM is a stand-alone DOS program ( non- multitasking ) and it must be terminated before you can have a HOTSCREEN session with the HOST. The HOTKEY will work but you will NOT establish contact with the remote HOST while a transfer is in progress! Other similar software will let you do both at the cost of slowing down the transfer, the normal session, and both computers. If your personal time or toll charges are important consider separating the sessions in some way. You can put file transfers at the beginning or the end of the session while you do something else, or you can setup an automatic tranfer when the toll charges are lower. Aborting the File Transfer You can ABORT the transfer(s) at any time by pressing the ESC key. The standard xmodem CANCEL signal will be sent to the other system and you will return to your own local DOS. Automatic File Transfer With the proper batch file and the use of TSWAIT.EXE or a similar task suspension program you can use XM.EXE to transfer files when nobody is around and toll/billing charges are possibly lower. Use the normal XM R and XM S commands but you need to add the letter 'A' after the 'R' or 'S' to indicate this is an Automatic transfer. Example: XM SA *.DAT - Send ALL .DAT files automatically! TeleShare DOS Remote Access XM or XMODEM Page 5 Why the 'A'? The normal transfer start timeouts are set for manual operation and are based on seconds. The 'A' causes these timeouts to be based on minutes so that the PC's involved have a longer chance to establish the connection. This allows the transfer to be set for a specific time of day and it won't matter if the P.C.'s clock times do not match. The default WAIT is 2 minutes when 'A' is added to 'R' or 'S'. You can increase or decrease the number of minutes by adding the desired number following the letter 'A'. Do NOT separate the number from the letters with a space, unless you really want to send a file called 2. Example command line entries... XM SA RESULTS.TXT - Send the file automatically and wait 2 minutes (default) before giving up. XM SA5 RESULTS.TXT - Send the file automatically and wait 5 minutes before giving up. XM S @filelist - Send the files listed in the 'filelist XM @filelist file. The '@' can be considered a replacement for the S when using a response file list. XM RA - Wait 2 minutes to start receiving all files being sent by the other side. XM RA10 - Wait 10 minutes to start receiving all files being sent by the other side. XM SA 8 RESULTS.TXT - WRONG!! This will NOT wait 8 minutes before giving up... it will wait only 2 minutes and will try to send a file called '8'! The minimum value you can specify after the 'A' is '1' (1 minute). If you are using the transfer LOG files then a special entry will be made whenever an automatic transfer is initiated to inform you that that's how the transfer was made. Creating batch files to perform automatic transfers If the TeleShare TSRs are loaded and running on BOTH PC's and the current PATH includes both XM.EXE and the files to be transferred then the following 2 batch files will perform an automatic transfer at 11:00 pm. TeleShare DOS Remote Access XM or XMODEM Page 6 Both sides will wait 5 minutes for the transfer to kick off before giving up in case the clocks are a little off, as 'cheap insurance'. NOTE: See the documentation concerning WAIT, RUNT, or the particular timer command that you will use for more information about timing the transfer. Sender Explanations Receiver ------------ ----------------------------- --------- cls <-Clear the screen ---------> cls wait 11 PM <-Wait until 11:00 PM ------> wait 11 PM XM SA5 *.DAT <-Wait 5 mins then transfer-> XM RA5 If the TeleShare programs are NOT loaded on the 2 PC's then the batch file can be sure they are before performing transfer. Assuming the files are in a sub-directory called \TELE on the C: drive. Sender Explanations Receiver ------------ --------------------------------- --------- wait 11 PM <-Wait until 11:00 PM ----------> wait 11 PM cls <-Clear the screen -------------> cls c: <-Be sure we are on drive C: ---> c: cd\TELE <-Change to TeleShare directory-> cd\TELE call TSHOST <-Call batch files for the TSR's> call TSREM cd\transfer <-dir holding SEND/RECV files---> cd\transfer XM SA5 *.DAT <-Wait 5 mins then transfer -> XM RA5 cd\TELE <-Return to TeleShare directory-> cd\TELE TSH U <-Unload the TSR's from RAM ----> TSR U Remember to use the batch file 'call' command if you are loading the programs with the normal batch files or batch file execution will stop after the TSHOST or TSREM batch file is run. Run 'TSH' or 'TSR' directly in the same batch file if you don't want to use CALL in batch files to load the programs. You can put multiple 'XM' commands in the batch file(s) to send groups of files and switch between xmodem sender and receiver. Examples: Assuming the TeleShare programs are already loaded. Sender Explanations Receiver TeleShare DOS Remote Access XM or XMODEM Page 7 -------------- ------------------------------ ---------- cls <-Clear the screen ----------> cls wait 11 PM <-Wait until 11:00 PM -------> wait 11 PM XM SA5 *.DAT <-Send all *.DAT to receiver-> XM RA5 XM SA5 *.TXT <-Send all *.TXT to receiver-> XM RA5 XM SA5 *.TXT <-Send all *.TXT to receiver-> XM RA5 XM SA5 TEST.EXE <-Send TEST.EXE to receiver-> XM RA5 XM RA5 <----- Send *.COM to sender--> XM SA5 *.COM XM RA5 <----- Send *.BAK to sender--> XM SA5 *.BAK XM SA5 *.DBF <-Send all *.DBF to receiver-> XM RA5 XM @SENDFILES <-Send the files listed to -> XM R Faster Protocols If you need faster protocols pcz provides the ymodem and zmodem options. DSZ is the industry standard zmodem tool. Our tests show the the hydracom protocol is as fast as DSZ, is bi-directional, and has some other features, such as a chat. Support and the ASP Please consider reporting the circumstances, preferably in written form, to technical support when you discover problems with the software. For technical support, either call (604) 433-5189, write, or email. Both registered and soon to be registered users currently get the same support without any arbitrary time limit. You may try leaving a Compuserve message at 75020, 2664, but be aware that messages rapidly 'scroll off' Compuserve. The best electronic message area (also available from Compuserve) is via the internet at: INTERNET:vic_williams@mindlink.bc.ca. P. C. Softsmith Suite 606 6455 Willingdon Ave Burnaby, B. C., Canada V5H 4E4 ASP Introduction: Please also carefully read the accompanying SHR_WARE.TXT document. "This program is produced by a member of the Association of Shareware Professionals (ASP). ASP wants to make sure that the shareware principle works for you. If you are unable to TeleShare DOS Remote Access XM or XMODEM Page 8 resolve a shareware-related problem with an ASP member by contacting the member directly, ASP may be able to help. The ASP Ombudsman can help you resolve a dispute or problem with an ASP member, but does not provide technical support for members' products. Please write to the ASP Ombudsman at 545 Grover Road, Muskegon, MI 49442 or send a CompuServe message via CompuServe Mail to ASP Ombudsman 70007,3536." Please read the TELE.TXT file for more information, including contact and support information. This document and associated TeleShare documents and software are Copyright (C)1992-4 P. C. Softsmith All Rights Reserved. THE DOCUMENTATION AND ASSOCIATED SOFTWARE ARE DISTRIBUTED AND SOLD WITH NO WARRANTIES, EITHER EXPRESS OR IMPLIED, REGARDING ITS MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE. THE INFORMATION IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE AND DOES NOT REPRESENT A COMMITTMENT ON THE PART OF THE VENDOR. OTHER PRODUCT AND BRAND NAMES MENTIONED ARE TRADEMARKS OR REGISTERED TRADEMARKS OF THEIR RESPECTIVE HOLDERS.