Programmer 7500

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

/ Programmer 7500 / MAX_PROGRAMMERS.iso / PROGRAMS / UTILS / COMMUNIC / EZCOM.ZIP / XYZ.DOC < prev next >

Wrap

Text File | 1990-03-03 | 31.7 KB | 859 lines

XYZ.TTP ======= By Alan Hamilton WHAT IT IS ========== Here it is.... a new ZMODEM program for the Atari ST. I was frustrated by the limitations that the ST version of RZ.TTP had, so I wrote my own, and I'm willing to fix any bugs that turn up in it. Features include: 1. Transfers all files unchanged -- "binary" mode. No more truncated files. 2. Transfers files at the maximum speed the sender can send them. No "wait states." 3. The timestamps on the files are preserved, unless you don't want them to be. You are told, in regular calendar format, what the timestamp is. 4. Interrupted transfers can be restarted where they left off (in ZMODEM). 5. You are kept informed as to how much of the file has actually been received, not how many bytes have been received in the current session. If you tried to restart a transfer with RZ.TTP, you wouldn't know where you were. 6. There is no feature six. 7. Filenames that aren't compatible with the ST are transformed into ones that are, not just truncated at the first illegal character. If they can't be converted, a random filename is chosen. These transformed filenames are unique -- no more losing a file because after being truncated it was the same as a previous filename. 8. Works with all ST/Mega configurations. 9. Includes versions of XMODEM and YMODEM for completeness. 10. It's -*>FREE<*- No vicious licencing agreement or shareware guilt trip here. This program may be copied, given away, folded, spindled, mutilated, or sold into slavery. REVISION HISTORY ================ 10-24-89: v1.41 Lots o' changes this time: 1. If v1.3 of XYZ.TTP was started before the sender started up, XYZ.TTP would bomb. Fixed. 2. A bug in handling of file creation dates in YMODEM has been fixed. 3. XMODEM and YMODEM now use disk buffering. 4. File errors are now more explicit as to what the problem is. 5. ZMODEM now can handle speeds over 9600 baud. 6. XMODEM and YMODEM now indicate how fast the files were transferred. ZMODEM no longer overstates the transfer rate if you are restarting a transfer. 7. Handling of retries is different. In earlier versions, the retry limit (before aborting) was supposed to be ten, but a bug made it only five. This has been fixed, and a new option has been added to let you specify a retry limit. Put -r<n> on the command line, with <n> replaced by the number of retries (up to 1000). For example, -r25 would give you 25 retries. 8. Some messages that were similar in YMODEM and ZMODEM were changed to be exactly the same. 9. Some of the C library code has been replaced with code of my own, making - 1 - XYZ.TTP about 4k smaller. 10-1-89: v1.3 At long last, disk buffering is here! Rather than saving after every packet, XYZ.TTP only does a disk write after all available memory has been filled up. XYZ.TTP now lets you start it before the sender has started. This was attempted in v1.2, but a bug in the code would make XYZ.TTP bomb if you tried it. That has been fixed. A disk full condition is now reported, rather than just a generic "File error" if the disk doesn't have enough room for the file. A new option -p will make XYZ.TTP wait for you to press a key before exiting. This can be handy if you are running XYZ.TTP from the Desktop. 9-19-89: v1.2 Up to now, if XYZ.TTP got five CTRL-X's while waiting for a ZMODEM frame to start, it would abort with a "Sender aborted" error. Now it only aborts if it gets five *consecutive* CTRL-X's. Unexpected aborts most often happened during recovery of CRC errors. Now sends hardware break signal correctly. XYZ.TTP now handles timeout errors better. 9-15-89: v1.1: A rather stupid error regarding filename conversion has been fixed. XYZ.TTP would sometimes insert a '.' in the seventh or eighth position of a filename, regardless of whether it was appropriate or not. The help screen (printed in response to the -h option) has been rearranged. 9-13-89: XYZ.TTP v1.0 released. Implements ZMODEM for the first time. Buffer overflow at high bps rates fixed. Synchronization error in YMODEM fixed (again!). UNDO key handling improved. The documentation file, XYZ.DOC, is totally new. XY.DOC is no longer applicable. 7-2-89: XY.TTP v0.5 released. Handles only XMODEM and YMODEM. Early release to accommodate changes made to GEnie software that Flash(tm) could not handle. DISCLAIMER ========== My obligations to you are exactly the same as your obligations to me: NONE. Although I have tested this program as best I can, you use this program only at your own risk. I will not be responsible for any losses you suffer from using it. ACKNOWLEDGMENTS =============== XMODEM was developed by Ward Christenson. YMODEM and ZMODEM were developed by Chuck Forsberg, Omen Technology. CRC code by Stephen Satchell, Satchell Evaluations and Chuck Forsberg, Omen Technology. Flash is a trademark of Antic Publishing. C library code copyright (C)1988 by the Mark Williams Company. 520ST, 1040ST, and Mega ST are trademarks of Atari, Inc. GEnie is a trademark of GEISCO/General Electric. WHAT IT ISN'T ============= Although XYZ.TTP supports the most useful parts of the ZMODEM protocol, there - 2 - are a few things that aren't. 1. 32 bit CRCs. XYZ.TTP only uses 16 bit CRCs, which should be sufficient unless you are really paranoid about data integrity. 2. Commands. This part of the ZMODEM protocol was intended to allow you to remotely control a system. Since XYZ.TTP is intended to be manually operated, and the ST doesn't have a standard command line interface, commands are not accepted. 3. Compression. Neither run-length encoding (RLE) nor Lempel-Ziv-Welch (LZW) compression is supported. If you use a separate decompression utility, this isn't needed. You can receive files that have already been compressed; you just need to use a separate utility to do the decompression. XYZ.TTP will not do the decompression itself. 4. Challenges. XYZ.TTP does not try to verify that it is connected to a system that is ready for ZMODEM. It assumes that you have already told that system to go to ZMODEM. 5. Pathnames. XYZ.TTP will put all files into the default folder, or one that you specify on the command line. Any path information that is sent with the file is ignored. 6. Selective file replacement. The ZMODEM protocol lets you selectively transfer files based on whether they exist or don't exist at the receiver, or whether they are different in file size, date, or CRC. XYZ.TTP only does one of two things: If a file does not exist, it is transferred in its entirety. If it does exists, it assumes that you are resuming a file transfer that was aborted, and tries to resume at the end of what you have. 7. File transmission resumption. Do not try to download a file that already exists on your disk unless you are trying to recover an aborted transfer. The file will be damaged if it is a different file, despite having the same name. If the file was previously received in its entirety, and you try to restart a download on it, it probably won't be damaged, but this depends on how the sender reacts, so be careful. 8. Disk space check. If the sender tries to check on how much space you have available on your disk, XYZ.TTP will always tell it that you have an unlimited amount. This was done because checking the disk space is a very slow operation on hard drives. Activating this feature might be done in future versions if enough people request it. 9. Encrypting. File encryption is not supported. 10. Seven bit transfers. Transferring eight bit files (non-text files) over lines that only support seven bits per character is not supported. This is something you'd only run into with a mainframe. 11. Sparse files. Transferring selected portions of a file that's mostly zeros is not supported. The entire file must be sent. 12. XYZ.TTP does not contain oat bran. HOW TO USE IT ============= XYZ.TTP is mainly intended to be run from inside a regular telecommunications terminal program. Because of this, it does not alter the settings of your ST's RS232 port from what the terminal program has set them to. For XYZ.TTP the RS232 port should be set as follows: Baud (or bits per second or BPS): This should match what the system you are connecting with requires, and what - 3 - your modem is capable of. Data bits: 8 Parity: None Stop bits: 1 or 2 Flow control: XOFF/XON (also called DC2/DC4): OFF for XMODEM and YMODEM either ON or OFF for ZMODEM RTS/CTS: OFF, unless you are using a high-speed modem that requires it to be on. These settings are very common, so you probably won't have to change them. If you can't run programs from within your terminal program, you will have to exit to the Desktop to run XYZ.TTP. Set the remote system to download ZMODEM, then exit your terminal program. Open XYZ.TTP, and a dialog box will appear. Type in the options (see below for a list), click on OK, and the ZMODEM transfer will start. One of the options you will want to specify is -p which will make XYZ.TTP pause before it returns to the GEM Desktop. If you don't specify a folder to download to, the files will go into the same folder that XYZ.TTP was in. After ZMODEM completes, it will exit back to the Desktop. You may then rerun your terminal program and continue. If you can run programs from within your terminal program, life gets much easier. If, however, your terminal program doesn't let you pass parameters to a .TTP program, you will only be able to download only with ZMODEM and to the default folder. See the manual for your terminal program for directions on running other programs. In Flash, the command is "exec xyz.ttp" (omit the quote marks). Any options go after the program name. If you are keeping XYZ.TTP in a different folder than the default one, you will have to specify it: "exec c:\telecom\xyz.ttp". You can even program a function key to run XYZ.TTP, and download with the push of one button. Program the key you want with ">exec xyz.ttp|", along with any options you want. (See the Flash manual on setting function keys.) After XYZ.TTP completes, you will be returned to Flash. JANE, STOP THIS CRAZY THING! ============================ If you want to abort a transfer before it is complete, press the UNDO key. XYZ.TTP will send an abort sequence to the remote system and terminate. Keep in mind that some mainframes take their own sweet time responding to abort sequences, so you may see a long string of garbage on your screen, or the mainframe may seem to have locked up. If you are using ZMODEM, you can restart the transfer of a partially transferred file later. OPTIONS ======= You should specify any options you want in the GEM dialog box (if running from the Desktop) or after XYZ.TTP's program name if running from a command line like the one in Flash. They should be separated by spaces, and may be in either upper or lower case. Following the options, you may specify a folder to download to. If you don't specify one, the files will go into the default folder. For XMODEM, in addition to the optional folder specification, you - 4 - *must* give a filename, as XMODEM transfers don't send filenames. -x Download XMODEM Downloads using the original XMODEM protocol. You can also specify the -c option if you are dealing with a very old system that does not support CRC error detection. You must specify a filename to download to. Examples: -x foo.txt Download "foo.txt" to the default folder -x -c c:\fold\moby.txt Download "moby.txt" to the "fold" folder on drive C using checksum error detection -y Download YMODEM Downloads using the YMODEM batch protocol. You don't specify a filename with this, just a folder. If you do specify a filename, or a folder that doesn't exist, you will get a file error. Examples: -y Download files to the default folder -y deep Downloads to the "deep" folder that is within the default folder -y e:\ Downloads to the root of drive E -z Download ZMODEM Downloads using the ZMODEM batch protocol. Since ZMODEM is the default protocol, the -z is optional. Again, you don't give a filename, just a folder. If the file that is being received exists in the folder you are downloading to, XYZ.TTP will assume that you are resuming an interrupted file transfer, and will start the transfer at the end of what you've already got. Examples: (no options) Download files to the default folder -z Download files to the default folder lex\grep Download files to the "grep" folder that is within the "lex" folder that is within the default folder -p Pause If you are running XYZ.TTP from the Desktop, you won't be able to see any error messages when it exits, as the Desktop wipes them out. Putting -p on the command line will make XYZ.TTP prompt you to press a key before it exits. -h Help This causes a short description of the available options to print out, along with the current version number. Giving an invalid option gets you this display, too. -t Touch This makes XYZ.TTP "touch" (set the time and date to the current time and date) files that it downloads. If the sender specifies a creation time and date for a file, that is kept. The -t option makes XYZ.TTP use the current time and date instead. If the creation time and date isn't specified by the sender, the current time and date is put on the file. XMODEM will always use the current time and date. -v<file> Verbose mode This causes XYZ.TTP to output special debugging information. If no file is specified, the output goes to the screen. If a file is specified, it should be directly after the "v" (no spaces), and output will go to it, along with any error messages you might get. If you have problems with XYZ.TTP, run it - 5 - with the -v option, and send the file it creates along with any comments to me. Examples: -v Download ZMODEM, sending debug info to screen -ve:\log.txt Download ZMODEM, sending debug info to "log.txt" on drive E: -r<n> Set retry limit Ordinarily, XYZ.TTP will abort a transfer if more than ten errors occur. When you have had that many errors, the chances of an error slipping through undetected become greater. If, however, you want to take your chances, you can set the retry limit with this command. It can be set anywhere from the default 10 up to 1000. Example: -r50 Set XYZ.TTP's retry limit to 50 HE'P ME, HE'P ME, I BE HYP-MO-TIZED =================================== If you have trouble with XYZ.TTP, send a copy of a debug file (see the -v option above) along with your comments to me on the GEnie network at A.HAMILTON1. Be sure to mention the version of XYZ.TTP you are running -- run it with the -h (help) option to check it. ERROR MESSAGES ============== Something that has always ticked me off is getting an error message from the program I'm using, looking it up in the manual, and finding that IT'S NOT THERE! So, what follows is a complete listing, in alphabetical order, of every possible message that XYZ.TTP can produce, along with an explanation. Many of these messages are for debugging purposes, and others you should never under ordinary circumstances run into. Access denied (XMODEM/YMODEM/ZMODEM) >>The ST could not open a file either because the file exists and is set to read only, or a folder exists with that same name. Attn string: <hex bytes> (DEBUGGING/ZMODEM) >>This details the string the sender wants XYZ.TTP to use to interrupt it. Average transfer rate = <number> cps (XMODEM/YMODEM/ZMODEM) >>This gives the average throughput. Bad escape char <hex byte> (ZMODEM/DEBUGGING) >>An invalid escape sequence was received. Probably caused by line noise. Bad escape character (ZMODEM) >>Same as above Bad hexadecimal character (ZMODEM) >>XYZ.TTP was expecting a hexadecimal digit but got an character that wasn't 0-9 or a-f. Probably caused by line noise. Bad or unsupported packet type (ZMODEM) - 6 - >>An unrecognized packet was received. Either caused by line noise, the sender being set to upload instead of download, or using ZMODEM features XYZ.TTP doesn't support. See "WHAT IT ISN'T" section. Bad packet type <byte> (ZMODEM/DEBUGGING) >>Same as above. The type is specified. Bad request (XMODEM/YMODEM/ZMODEM) >>A serious error within either the ST's operating system or within XYZ.TTP has occurred. Bombs (XMODEM/YMODEM/ZMODEM) >>Not the word "Bombs", but the little cartoon bombs on the left side of your screen. The 68000 processor has encountered an instruction that it can't process. This can be caused by a bad copy of XYZ.TTP, an interaction with a desk accessory or program in the AUTO folder, or (most likely) a coding boo-boo of mine. Block #<block number> (XMODEM/YMODEM) >>Number of the block being received. Block resent, but not requested. (XMODEM/YMODEM) >>A block was retransmitted, but XYZ.TTP did not request it. Caused either by line noise, or very slow responses by the sender. <number> bytes transferred (ZMODEM) >>Indicates how much of file has been received. Buffer size = <size> (XMODEM/YMODEM/ZMODEM) >>The number of bytes of memory that XYZ.TTP will use as a buffer. Can't convert filename "<filename>", will use "<filename>" (YMODEM/ZMODEM) >>The sender specified a filename that XYZ.TTP couldn't make compatible with the Atari ST's operating system. A random filename with the extension .XYZ will be used. Can't open error long (XMODEM/YMODEM/ZMODEM) >>The filename specified with the -v (verbose) option can't be opened. The output will go to the screen instead. Checksum error (XMODEM) >>The checksum on the last block was invalid. Probably caused by line noise. Command received, but commands not supported (ZMODEM) >>XYZ.TTP does not accept commands from remote systems. See "WHAT IT ISN'T" section. Command: <command> (ZMODEM) >>Text of command received. See above. CRC error (XMODEM/YMODEM/ZMODEM) >>The CRC on the last block was invalid. Probably caused by line noise. - 7 - Crc error (as part of file error message) >>The ST detected an error while accessing the disk. The disk may be damaged. Disk full! (XMODEM/YMODEM/ZMODEM) >>There isn't enough room on your disk to hold the file. The transfer is aborted, with as much of the file as the disk will hold saved. You can resume the transfer in ZMODEM if you move the partial file to another disk that has more room, or if you delete some files on the disk. Downloading YMODEM (YMODEM) >>A YMODEM session has started. Drive not ready (XMODEM/YMODEM/ZMODEM) >>The disk drive isn't responding. Make sure the drive is attached, turned on, and has a formatted disk in it. Duplicate YMODEM header received. Ignored. (YMODEM) >>A file specification block was retransmitted, but it was not requested. Caused by line noise, very slow responses from the sender, or operating XYZ.TTP in XMODEM mode when the sender is using YMODEM. Error in positioning file pointer: <error type> (ZMODEM) >>XYZ.TTP tries to find the end of the file after it opens it. If it can't, you get this message. Look up the error type that prints out to find out what error occurred. Error in seeking to end of file: <error type> (XMODEM/YMODEM/ZMODEM) >>Same as above. Error opening file: <error type> (XMODEM/YMODEM/ZMODEM) >>XYZ.TTP could not open a file. Look up the error type that prints out to find out what error occurred. Error writing to file: <error type> (XMODEM/YMODEM/ZMODEM) >>An error occurred while XYZ.TTP was trying to write to a file. Look up the error type that prints out to find out what error occurred. File <filename> exists! (XMODEM/YMODEM) >>XMODEM and YMODEM will not overwrite a file that already exists. Specify a different file name (XMODEM) or path (YMODEM), or delete the file that already exists. File created on <time & date> (YMODEM/ZMODEM) >>The time the file being received was created. File created on <time & date>, reset to <time & date> (YMODEM/ZMODEM) >>The time the file being received was created. This will be changed to the current time and date. File creation date not specified, reset to <time & date> (YMODEM/ZMODEM) >>The sender did not specify a creation time; therefore the current time will be put on the file. - 8 - File error (XMODEM/YMODEM/ZMODEM) >>A file error occurred while writing to the disk. Caused by a full disk, a bad filename, specifying a folder that doesn't exist, or a disk error. File error at sender (ZMODEM) >>A file error occurred at the sender, so it is aborting the transfer. File exists -- transfer resuming at offset <offset> (ZMODEM) >>The file that is being transferred already exists, so it is assumed that an aborted transfer is being resumed. File not found (XMODEM/YMODEM/ZMODEM) >>XYZ.TTP tried to read from a file that didn't exist. You should never get this error since XYZ.TTP should not read files. If you do, something is seriously wrong. File pos = <position>, sender = <position> (ZMODEM/DEBUGGING) >>XYZ.TTP and the sender disagree over how much of the file has been sent. The position each claims is specified. File position error (ZMODEM) >>XYZ.TTP and the sender disagree over how much of the file has been sent. Function domain (XMODEM/YMODEM/ZMODEM) Function range Fundamental error General error >>These are all internal errors in the ST's operating system. You should never get them. If you do, you will probably have to reboot the computer. Got a session abort while waiting for ZPAD (DEBUGGING) >>The sender sent a series of CTRL-X's, or "CANcels," while XYZ.TTP was waiting for the start of a ZMODEM frame. Got a GOTCAN (DEBUGGING) >>The sender sent a session abort sequence (a series of CTR-X's, or "CANcels") while XYZ.TTP was waiting for a character Got a ZRPOS! (ZMODEM) >>This packet type is reserved for the receiving side. Make sure the sender is set to download. Got a ZSKIP?!? (ZMODEM) >>This packet type is reserved for the receiving side. Make sure the sender is set to download. Got: <frame type> <header> <hex bytes> CRC <CRC value> (ZMODEM/DEBUGGING) >>This details a ZMODEM packet that was received. Got ZCRC '%c' (ZMODEM) >>This indicates tells the CRC type at the end of the last data subpacket. Insufficient memory (XMODEM/YMODEM/ZMODEM) - 9 - >>Either your computer does not have enough memory for XYZ.TTP to run, or something has gone wrong with the way the memory is being managed. Try removing desk accessories and/or programs in the AUTO folder to free up some memory. Internal error (XMODEM/YMODEM/ZMODEM) >>An error has occurred within the ST's operating system. You will probably have to reboot the computer. Invalid drive specified (XMODEM/YMODEM/ZMODEM) >>You specified a drive in the path name that does not exist. Be sure the drive letter you specified was correct, and the disk is connected and turned on. Invalid function number (XMODEM/YMODEM/ZMODEM) Invalid handle Invalid memory block address >>A serious internal error in XYZ.TTP or the ST's operating system has occurred. <filename> has been renamed to <filename> (YMODEM/ZMODEM) >>A filename was specified by the sender that is incompatible with the Atari ST's operating system. It has been transformed into a valid filename that should still be recognizable, though you may have to manually rename it before using it. Invalid option <option> (XMODEM/YMODEM/ZMODEM) >>You put an option on the command line that XYZ.TTP does not recognize. A list of the valid options is printed out. <filename> is a duplicate filename (XMODEM/YMODEM/ZMODEM) >>You put more than one filename (XMODEM) or more than one path (XMODEM/ YMODEM) on the command line. Only specify one. Media change (XMODEM/YMODEM/ZMODEM) >>You removed the disk from the drive while XYZ.TTP was writing a file to it. NEVER remove a floppy disk until after XYZ.TTP has finished running. Memory free: <# of bytes> (DEBUGGING) >>Shows the amount of memory left free before XYZ.TTP allocates its buffers. Message: <text> (ZMODEM) >>The remote system sent a message. Missing block number (XMODEM/YMODEM) >>A valid block number was not received. Probably caused by line noise. Missing or bad header (XMODEM/YMODEM) >>The block header was not sent completely or was garbled. Probably caused by line noise. No filename (XMODEM) >>You must specify a filename for XMODEM transfers. - 10 - No handles left (XMODEM/YMODEM/ZMODEM) >>The ST has too many files open. If you are running XYZ.TTP from within another program that opens files without closing them, this error might occur. Otherwise, it indicates an internal error in the ST's operating system. Not enough memory to allocate buffers >>There isn't enough free memory to run XYZ.TTP. Remove some of your desk accessories, or run XYZ.TTP from the desktop rather than from within a terminal program. Path not found (XMODEM/YMODEM/ZMODEM) >>The path you specified on the command line does not exist. All the folders in the path must have already been created before you run XYZ.TTP. Press any key to exit.... (XMODEM/YMODEM/ZMODEM) >>The -p option was put on the command line, and XYZ.TTP is about to terminate. Press a key to let it complete its termination. Range error (XMODEM/YMODEM/ZMODEM) >>A serious internal error has occurred within either the ST's operating system or within XYZ.TTP. Read fault (XMODEM/YMODEM/ZMODEM) >>An error occurred while the ST was trying to read from a disk. The disk may be damaged. Receiving file "<filename>", <size> bytes (ZMODEM) >>The transfer of a file has begun. The size is specified by the sender, and may not be the actual size of the file. Receiving file "<filename>", size not specified (ZMODEM) >>The transfer of a file has begun. The size of the file was not specified. Sector not found (XMODEM/YMODEM/ZMODEM) >>Something has gone wrong with the ST's file system. It tried to read a disk sector that does not exist. Seek error (XMODEM/YMODEM/ZMODEM) >>Something went wrong when the ST tried to make the disk go to a specific track. Sender aborted (ZMODEM) >>The sending program is aborting the transfer. Sender indicates end of file, but file length is wrong (ZMODEM) >>The sender has come to the end of the file, but the number of bytes it says it sent does not match the number of bytes XYZ.TTP has received. Sender not ready or set to receive (ZMODEM) >>The sender is echoing back XYZ.TTP's packets, or is set to upload. Make sure it is set to download. Sender requested CRC?!? (ZMODEM) - 11 - >>This packet type is reserved for the receiver. Make sure the sender is set to download Sender requests retransmission (ZMODEM) >>The sender wants XYZ.TTP to resend a packet. Probably due to line noise. Sender sent ZCHALLENGE?!? (ZMODEM) >>This packet type is reserved for the receiver. Make sure the sender is set to download Sender sent ZCOMPL -- ignored (ZMODEM) >>The sender indicates it completed a command, but XYZ.TTP doesn't issue commands. Sent: <header> <hex bytes> CRC <CRC value> (ZMODEM/DEBUGGING) >>Details of a hex-style packet that XYZ.TTP has sent. Setblock failure due to growth restrictions (XMODEM/YMODEM/ZMODEM) >>Something has gone wrong with the ST's memory management. Subpacket bad CRC: <CRC value> (ZMODEM/DEBUGGING) >>An invalid CRC was received at the end of a data subpacket. Probably due to line noise. Subpacket too long (ZMODEM) >>A data subpacket has exceeded 1k in length, or an attention string is over 32 bytes long. Probably due to line noise. Synchronization error (XMODEM/YMODEM) >>The sender is sending the wrong packet. Probably caused by either line line noise or very slow responses from the sender. Timed out (XMODEM/YMODEM/ZMODEM) >>Too much time has passed since the last character was received. Probably caused by line noise, very slow responses from the sender, or failure of the sender. To abort, press UNDO at any time (XMODEM/YMODEM/ZMODEM) >>This just informs you that you can abort a transfer by pressing UNDO. Too many retries (XMODEM/YMODEM/ZMODEM) >>Too many errors have occurred. The session is aborted. Transfer of <filename> complete, <size> bytes (XMODEM/YMODEM) >>Transfer of a file complete successfully. The filename and actual size is indicated. Unexpected ZACK from sender! (ZMODEM) >>This packet type is reserved for the receiver. Make sure the sender is set to download. Unknown device (XMODEM/YMODEM/ZMODEM) >>You didn't specify a valid drive letter in the pathname on the command line. - 12 - Unknown media (XMODEM/YMODEM/ZMODEM) >>The disk you are trying to use is not formatted correctly. Usage: xyz.ttp [options] <path> >>Prints in response to the -h (help) option, or an invalid option. A list of all possible options follows. Use -c (checksum) mode with XMODEM only (YMODEM/ZMODEM) >>Checksum mode is only valid with XMODEM. User aborted (XMODEM/YMODEM/ZMODEM) >>You have pressed the UNDO key, and the session has been aborted. Verbose mode is on! (DEBUGGING) >>The -v option was specified. Special debugging information will be written to the screen or a specified file. Write fault (XMODEM/YMODEM/ZMODEM) >>An error occurred while XYZ.TTP was trying to write to the disk. The disk may be damaged. Write protect (XMODEM/YMODEM/ZMODEM) >>The write protect window on the disk is open. YMODEM complete! (YMODEM) >>YMODEM session has completed. YMODEM packet received, but doing XMODEM. (XMODEM) >>A YMODEM file specification was received, but XYZ.TTP is set to do an XMODEM transfer. Make sure you select the same mode for both XYZ.TTP and the remote system. YMODEM transfer aborted! (YMODEM) >>An error has occurred, and the YMODEM session is being aborted. ZBIN Bad CRC: <CRC value> (ZMODEM/DEBUGGING) >>An invalid CRC was at the end of a binary-style packet. The CRC value is specified. ZEOF = 0x%lx, f_offset = 0x%lx (ZMODEM/DEBUGGING) >>The sender is claiming end-of-file, but XYZ.TTP hasn't received all of it. The file size the sender specifies and the amount XYZ.TTP has received is printed. ZHEX Bad CRC: <CRC value> (ZMODEM/DEBUGGING) >>An invalid CRC was at the end of a hex-style packet. The CRC value is specified. ZMODEM file transfer (ZMODEM) >>A ZMODEM session has started. ZMODEM transfer complete. (ZMODEM) >>A ZMODEM session has completed. - 13 -