Otherware

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

/ Otherware / Otherware_1_SB_Development.iso / cdrom / viewers / megadoor.doc < prev next >

Wrap

Text File | 1993-01-25 | 32.1 KB | 659 lines

╔═══════════════════════════════════════════════════════════════════════════╕ ║ MegaDOOR version 3.56S (C) 1991-1992 SB Development │ ╙───────────────────────────────────────────────────────────────────────────┘ TABLE OF CONTENTS Section 1 MegaDOOR License Agreement 2 About MegaDOOR 3 Where to get help and updates 4 Single node quick start 5 System requirements 6 Features list 7 Network/DesqView support 8 BBS support 9 Protocol support 10 Security options 11 Look and feel 12 Enhancing performance 13 Forced COM ports 14 Command line parameters 15 Sysop keys 16 Updating MegaDOOR 17 MegaTERM 18 Bad Words/Filenames 19 Version history from 2.00 20 Program status indicators ╔═══════════════════════════════════════════════════════════════════════════╕ ║ Section 1: MegaDOOR License Agreement │ ╙───────────────────────────────────────────────────────────────────────────┘ MegaDOOR, MegaSearch (DOS + Windows), MegaTERM, MSETUP, MegaINSTALL, and MegaFILE are Copyright (C) 1991-1992 by SB Development. The right to use and/or distribute any of the above mentioned products is granted if the conditions below are met. 1. The software may only be used on SB Development or Profit Press label CD-ROM discs. 2. The software may not be represented as a product of any person or business entity other than Profit Press or SB Development. 3. The floppy disk based support software and it's updates may not be distributed for more than $5.00 per disk plus exact shipping. 4. SB Development support disks included with any CD-ROM must be given to the purchaser as a bundle free of charge. 5. If updates are available for distribution from a BBS or other online service no access fee may be charged. 6. Any sysop or other online service manager is granted the right to restrict the use of MegaDOOR and MegaTERM to specific users. 7. None of the software or support files may be disassembled or modified. This includes, but is not limited to, modifying SB Development software to work with CD-ROM products not published by Profit Press or SB Development. 8. All other rights reserved, including the right to change the above license agreement at any time. ╔═══════════════════════════════════════════════════════════════════════════╕ ║ Section 2: About MegaDOOR │ ╙───────────────────────────────────────────────────────────────────────────┘ MegaDOOR is a DORINFO/DOOR.SYS compatible door. It assists in file searches and downloading on supported CD-ROMs. It is included free with all supported CD-ROMs. MegaDOOR comes with a remote user interface called MegaTERM. This interface caches CD-ROM listings and gives users nearly complete MegaSearch for DOS functionality. MegaTERM abides by all MegaDOOR security level restrictions. Also included with MegaDOOR is MSETUP. MSETUP allows the sysop to configure MegaDOOR for nearly any system. Online context sensitive help is provided for all menus (just hit F1). MSETUP may be incompatible with DesqView on certain systems. ╔═══════════════════════════════════════════════════════════════════════════╕ ║ Section 3: Where to get help and updates │ ╙───────────────────────────────────────────────────────────────────────────┘ If you have any problems with MegaDOOR or have a bug to report call us at (602)293-0770. We do ask that you review this entire document AND the online help in MSETUP before making the phone call. New features are being added to MegaDOOR constantly. Updates are free and only cost you a phone call. Please call if you feel a feature or support for a BBS package is missing. New versions of MegaDOOR will be made available to first time callers on the Not-Yet-Named BBS (602)577-3650 [v.32bis] (602)577-3419 [v.32bis,HST]. ╔═══════════════════════════════════════════════════════════════════════════╕ ║ Section 4: Single node quick start │ ╙───────────────────────────────────────────────────────────────────────────┘ Unzip the MegaDOOR distribution file (usually MDORxxxS.ZIP) and the appropriate CD-ROM support file (usually the name of the disc). This is done automatically by the INSTALL program. Run MSETUP (may not work with DesqView). Full mouse and keyboard support is included. Keyboard commands are: F1 for help (at any time). F10 to access the menu. TAB switches between entry fields. SPACE executes a button. ENTER executes the menu or the default button. If you are using a high speed modem, adjust the locked baud rate in Standard│Comm. Set the DORINFO/DOOR.SYS path and CD-ROM drive letter in Standard│Paths. (optional) Set up your systems security in the Standard│Other menu, the Restrictions menu, and the Protocol│Ratios menu. Exit MSETUP. (Quit/Exit in Standard│Other or Alt-X). Run "MEGADOOR LOCAL" to make sure the paths were setup correctly. Add MegaDOOR to your BBS menus and make sure to set it up as a DORINFO or DOOR.SYS compatible door. Have someone log on at your systems minimum and maximum supported speed to ensure that the locked baud rate is set correctly and that your BBS is passing the proper information to MegaDOOR. Please see Section 8: BBS support for more information on getting specific BBS software to work with MegaDOOR. ╔═══════════════════════════════════════════════════════════════════════════╕ ║ Section 5: System requirements │ ╙───────────────────────────────────────────────────────────────────────────┘ - 256K of free RAM (less when EMS is available) - 300K of disk space - DOOR.SYS or DORINFO.DEF compatible BBS software - Any supported CD-ROM disc and a CD-ROM drive - The appropriate CD-ROM support files ╔═══════════════════════════════════════════════════════════════════════════╕ ║ Section 6: Features list │ ╙───────────────────────────────────────────────────────────────────────────┘ ■ Quick and easy installation with MSETUP.EXE ■ Directly supports: WildCat! 3.0, Remote Access 1.11, QuickBBS 2.75, SuperBBS 1.17, Maximus 2.0, and GAP ■ Batch downloads with Ymodem, Zmodem and Kermit ■ Single file downloads with Xmodem, Ymodem, Zmodem and Kermit ■ Batched files may be marked from file lists or at the menu ■ ZIP view / ZIP read (including string search) ■ *Virus report for each ZIP file ■ Sysop definable main menu and colors ■ Sysop definable security includes: Level to view and/or download files, Ratios for UL/DL and daily K limits. ■ Network/DesqView support [9 nodes DORINFO.DEF, 127 DOOR.SYS] ■ Description search ■ File find ■ *Hyper search (for words 3 or more characters in length) ■ Locked COM ports ■ Support for non-standard comm ports ■ *Sysop may define their own CD-ROM order form ■ DigiBoard general interface support * Not available on some CD-ROM discs. ╔═══════════════════════════════════════════════════════════════════════════╕ ║ Section 7: Network/DesqView support │ ╙───────────────────────────────────────────────────────────────────────────┘ Different copies of MegaDOOR may be run for each node of a multi-node system, however, this is wasteful of disk space. Proper setup of MegaDOOR for a Network or DesqView system will yield better system performance. To set MegaDOOR up for your multinode environment, load MSETUP. For each node in your system enter the appropriate Network│Node x menu and set the DORINFO/DOOR.SYS path, the node's locked baud rate (if any), and the CD-ROM drive letter. (optional) Set up your systems security in the Standard│Other menu, the Restrictions menu, and the Protocol│Ratios menu. Most multinode systems should set "Copy dload to HD" on in the Protocol│Internal menu. MegaDOOR will copy all files in a single or batch download to the hard drive before the transfer. Most CD-ROM drives can not keep up with more than one user at a time. Exit MSETUP. (Quit/Exit in Standard│Other or Alt-X). Run "MEGADOOR x LOCAL" to make sure the paths were setup correctly. (where x is the node number representing the keyboard/window you are using) Add MegaDOOR to your BBS menus and make sure to set it up as a DORINFO or DOOR.SYS compatible door. Please see Section 14: Command line parameters for instructions on passing the node number to MegaDOOR. Have someone log on at your systems minimum and maximum supported speed to ensure that the locked baud rate is set correctly and that your BBS is passing the proper information to MegaDOOR. Please do this for each node. NOTE: If you would like to use more than the 16 nodes supported by MSETUP you will have to edit the MEGADOOR.SET file with a text editor. Find the NODExxx entries, copy, and edit for your setup. WARNING(DesqView): Some versions of DesqView can not handle direct screen writes. If necessary set Direct Video to No in Standard│Other. Please see Section 8: BBS support for more information on getting specific BBS software to work with MegaDOOR. ╔═══════════════════════════════════════════════════════════════════════════╕ ║ Section 8: BBS support │ ╙───────────────────────────────────────────────────────────────────────────┘ MegaDOOR includes directly support for WildCat! 3.0, Remote Access 1.11, QuickBBS 2.75, SuperBBS 1.17, Maximus 2.0, and GAP. This means that MegaDOOR (if the option is activated) will update user daily and total download information for each of the packages above. Two steps are required to activate this support. Turn on K Limit checking in MSETUP's Standard│Other menu. Define *"Transfer Data for MegaDOOR" in MSETUP: Single node system: In the Standard│Paths menu. Network/DV systems: In every Network│Node x that you are using * refer to the online help (F1) on information for adding your particular BBS software into this field. MegaDOOR does not directly support any package's file ratio setup. It does support 16 different file ratio access levels in the Protocol│File Ratios menu. Use these to inform MegaDOOR of the file ratios that you would like to keep. MSETUP's online help explains how to edit the file ratios. ╔═══════════════════════════════════════════════════════════════════════════╕ ║ Section 9: Protocol support │ ╙───────────────────────────────────────────────────────────────────────────┘ MegaDOOR includes Xmodem, Ymodem, Zmodem and Kermit. You may disable any internal protocol in the MSETUP Protocol│Internal menu. In this menu you may also enable downloads being copied to the hard drive before a transfer. Up to six external protocols may be added to MegaDOOR in the Protocol│External x menus. Please see the online help in MSETUP for complete instructions (including batch file parameters). ╔═══════════════════════════════════════════════════════════════════════════╕ ║ Section 10: Security options │ ╙───────────────────────────────────────────────────────────────────────────┘ MegaDOOR includes many options for user security. In MSETUP, the Standard│Other menu includes a minimum access, download, and zipview level. Also in this menu is a sysop level - this defines the level a local logon will be given. You may also set access and download levels for each file area on a CD-ROM. These individual levels will be overridden by the global levels only if they are LOWER than the appropriate global security level. This helps to avoid unnecessary typing. Each menu option may be hidden or set to sysop in the Standard│Menus menu. Please see Section 8: BBS support for setting up your system's user upload/download ratios. ╔═══════════════════════════════════════════════════════════════════════════╕ ║ Section 11: Look and feel │ ╙───────────────────────────────────────────────────────────────────────────┘ The sysop can control many of the basics attributes of MegaDOOR's user interface. Foremost is color control. The MSETUP menu Standard│Colors allows a sysop to adjust MegaDOOR colors to suit. Online help provides a color chart for reference. Sorry, but at this time no active color demo is available and the sysop will have to log on locally to view the effects. Most menu item names and command letters are also sysop definable. The menu Standard│Menus provides a method of changing menu text. The menu command letter is always the first character of the menu text. A menu attribute exists to hide certain options, or make them sysop only. You may also define your own text files. For a menu create an ASCII and/or ANSI menu in the MegaDOOR directory, and inform MegaDOOR in the MSETUP Standard│Text Files menu. If you would like to sell CD-ROM's on your system you may define your own ASCII order form. Set the order form name in the same menu. Other sysop definable text file names appear below. These files will be used in place of the standard menus if found in the MegaDOOR directory. DLSING.ANS/.TXT Protocol menu for single file transfers. DLBATCH.ANS/.TXT Protocol menu for batch transfers. DIR.ANS/.TXT Primary change directory menu. DIRxx.ANS/.TXT Sub directory cd menu. You may also edit or create a new banner text/ansi file (the file displayed as the user logs into MegaDOOR). ╔═══════════════════════════════════════════════════════════════════════════╕ ║ Section 12: Enhancing performance │ ╙───────────────────────────────────────────────────────────────────────────┘ MegaDOOR's search and change directory functions will operate quite a bit faster if a few files are copied from your CD-ROM into the MegaDOOR directory. They are 0CDDIR.DAT, 0CDSORT.DAT, 0HYPCACH.DAT (if available), and 0CDINDEX.DAT. These files together are found in the CD-ROM \00INDEX directory and should total less than one megabyte. More speed during zipview and hypersearch operations may be gained by copying 0HYPERIN.DEX from the same directory. This file can be 15+ megabytes and will not speed MegaDOOR to any degree justifying it's hard drive space usage. ╔═══════════════════════════════════════════════════════════════════════════╕ ║ Section 13: Forced COM ports │ ╙───────────────────────────────────────────────────────────────────────────┘ In the Standard│Comm and Network│Node x appear three options that are not usually used in a MegaDOOR setup. They only need be used if you have a nonstandard communications port setup. If you do need to adjust the IRQ or base address of a com port you should set Forced COM Port, Forced IRQ, and Forced I/O port to the proper values. This has successfully been used to drive a 4 node DesqView BBS using COM 1-4 and IRQs 2,3,4 and 5. ╔═══════════════════════════════════════════════════════════════════════════╕ ║ Section 14: Command line parameters │ ╙───────────────────────────────────────────────────────────────────────────┘ Single node systems: MEGADOOR [local] ---> where local is optional Multi node systems: MEGADOOR x [local] ---> where x is the node number and local is optional. A node number is required for local logons. ╔═══════════════════════════════════════════════════════════════════════════╕ ║ Section 15: Sysop keys │ ╙───────────────────────────────────────────────────────────────────────────┘ The up and down arrows adjust user time F1 will abort file transfers F5 will log a user off and drop DTR to the modem for a hangup. F9 drops the sysop to DOS F10 will engage the user in chat (not available during MegaTERM) ╔═══════════════════════════════════════════════════════════════════════════╕ ║ Section 16: Updating MegaDOOR │ ╙───────────────────────────────────────────────────────────────────────────┘ If you are installing this MegaDOOR as an update, please make sure that you have the appropriate CD-ROM support file. These files are usually an archive carrying the name of the CD-ROM (MEGAROM1.ZIP, FAO3.ZIP, etc). You should make sure to overwrite all files in your directory (including MEGADOOR.SET) with the newer support and MegaDOOR distribution files. ╔═══════════════════════════════════════════════════════════════════════════╕ ║ Section 17: MegaTERM │ ╙───────────────────────────────────────────────────────────────────────────┘ Included with MegaDOOR is the matching version of MegaTERM. Please inform your users that it is available. The interface offered by MegaTERM makes files easier than ever to find. While a user is in MegaTERM the sysop is presented with a packet display. During MegaTERM operations your system is essentially acting as a file server. MegaDOOR still processes all security limits while MegaTERM is active. During a MegaTERM zipread the sysop display will change to reflect the state of the user's screen. ╔═══════════════════════════════════════════════════════════════════════════╕ ║ Section 18: Bad Words/Filenames │ ╙───────────────────────────────────────────────────────────────────────────┘ You may stop a user from performing a hyper-search on a profanity or other word by adding the word with the MSETUP Standard│Bad Words/Filenames menu. A filename added into this list will never be displayed to the users screen, can not be downloaded, and is totally locked out. ╔═══════════════════════════════════════════════════════════════════════════╕ ║ Section 19: Version history from 2.00 │ ╙───────────────────────────────────────────────────────────────────────────┘ 2.00S - MegaDOOR now supports MegaTERM (2.00) with ZIPRead - Bug fixed with text search/file find - MegaDOOR no longer needs to be run from it's own directory - MSETUP.EXE (MegaDOOR setup program) completed 2.02S - Added twirling idle cursor to bottom right of screen - Fixed MegaTERM read-zip related logoff bug - Added a check to see if COM port exists (prevents lock-ups) - Added a ^C abort check during listings - ZIP View and ZIP Read combined into one menu option - ZIP Read by file # instead of file name - ZIP View/Read now on file list more prompt - Fully supports DOOR.SYS daily kilobyte limits - Problems fixed with restricted directories - Minimum MEGADOOR access level added. 2.03S - MEGADOOR is now DesqView aware (will give up time slices) - Fixed bug with fossil and networks (wouldn't use it on LANS) - Supports EXITINFO.BBS from RA (may not quite work/feedback welcome) - Added support for strange comm ports 2.10S - ANSI interpreter built in, MEGADOOR no longer requires ANSI.SYS for ANSI menus/banners. - Xmodem/YModem(G)/Zmodem(8K)/Kermit now internal (no DSZ.EXE or GSZ.EXE required) - Fixed chat/shell to DOS user timeout bug - UNZIP code now internal. PKUNZIP no longer required. - Local copy code now internal. - Overlays added to decrease MegaDOOR memory requirements - Fossil driver support has been removed. USEFOSSIL and NODEFOSSIL settings are ignored. 2.50S - MegaTERM is now being distributed. 2.53S - Network sharing violations fixed on HD based data files. - Single download fixed (OOPS!) - MegaTERM interface now uses the OOXPORT transport layer - Visual quirk found in large zmodem downloads should be fixed - Added error info on status line - Download status bar has less granularity 2.55S - Protocol status spruced up 2.56S - MegaDOOR was crashing when given invalid command line parameters. I've tracked it down and it shouldn't happen again. - ANSI directory menu support added [DIR.ANS, DIRx.ANS, ...] - A little touch of user help added to ? - Zip read now unzips to a temp directory. Users can unzip any file except one with the same name as another user is reading (network or multitasking bbs). 2.57S - MegaTERM maintenance 2.58S - MegaDOOR was logging the user out after downloads. 2.59S - Added Xmodem-CRC, Xmodem-1K, Xmodem-1KG - Added ANSI to download protocol menus (batch and single) [DLSING.ANS, DLBATCH.ANS] - Eliminated the batch download command. MegaDOOR chooses according to the state of the download queue. - .TXT support added for DIR, DIRx, DLSING, DLBATCH - Added "expert mode" change directory. If you enter the cd command twice - like "cc<cr>" it will jump to the sub directory display instead of starting at the main directory. 2.60S - Network support expanded to 127 nodes with DOOR.SYS - Zipview was not working correctly in hyper search, file find and text search. - Internal protocols may now be disabled in MSETUP - External protocol support has been added (again...) - MegaDOOR internal menus (ANSI anyway) are much nicer looking and display faster for 2400 or slower users. - Some default colors have been adjusted. Background colors are now supported. Hit F1 in the Standard|Colors menu of MSETUP - MegaDOOR now has a temp directory for each node - A local login or sysop level has been added as an option in MSETUP. It defaults to 65534. 2.61S - Some changes in MegaTERM. 2.62S - More help added to MSETUP with links between help panes. - External protocol log file support added. - EXITINFO.BBS support has been revamped. (RA & SBBS supported) - Slight visual bug in MegaTERM sysop display fixed. - PS2 detection was messing up forced comm support. 2.63S - QuickBBS support added - Limited hot key support added - Zip read now goes back to the archive instead of the more prompt - Up and down arrows now adjust user time - Xmodem 1k/1kG should be working now. - .SDN archives are supported (PAK.EXE must be present) - K/files ratio support added in MSETUP - WildCat! 3.0 support for USERINFO.DAT added - More DOOR.SYS support added (fully GAP compatible) 2.80S - Official release for the SDN1+ CD-ROM - Maximus 2.00+ support added - Tiny bug fix on hot keys. 2.81S - MegaTERM update (slightly pre-SDN) - Minimum access for zipview added. - Hangup on user timeout added. (optional) 2.82S - MegaTERM downloads now count against the user. - MegaTERM now reports correct zipread fail info. - Some MegaDOOR network setups outputted garbage to the screen. This has been corrected. 2.83S - Bug on text mode autoprompt fixed. 2.84S - MegaTERM zipread in window 3.00S - XModem/YModem transfers fixed - New version of MegaTERM with MkDir/ChDir option 3.10S - Upgraded to Async Pro 1.04 - Fixed external main menu problems - Unzipping ZIP AV files corrected (Async Pro bug) 3.11S - BIOS [optional] video (screen writes) partially implemented 3.20S - EMS/conventional CD-ROM caching modified - Terminal errors now reported in Red at bottom of screen - Exit status reported in Blue at bottom of screen - MegaTERM double click problems repaired - Heap error fixed on early error exit - Fixed logic error in complex hypersearch expressions 3.21S - Added XIDOS5 Digiboard general driver support 3.22S - Eliminated duplicate CD-ROM info code - Modifed CD-ROM data file open 3.50S - Fixed error in EMS exit code (introduced in 3.22) 3.51S - Fixed MEGADOOR exit status inconsistency 3.52S - Sysop may now lock out any filename from the CD-ROM from MSETUP 3.53S - No longer displays file dates on MegaA/V CD-ROM - Added CPS/estimated time to MegaDOOR/MegaTERM dload window - Added BIOS support for saving/restoring screen - BIOS support should be complete now - Added CD-ROM name and current directory name to sysop's MegaTERM display 3.54S - Using Borland Pascal 7.0 3.55S - Added support for Wildcat 3.5 3.56S - WildCat IM bug fix release ╔═══════════════════════════════════════════════════════════════════════════╕ ║ Section 20: Program status indicators │ ╙───────────────────────────────────────────────────────────────────────────┘ Two forms of system status are provided during MegaDOOR operation. A rotating cursor should appear in the bottom right corner while MegaDOOR is idle. Each cursor rotation also denotes a time slice given to DesqView if it is loaded. Also in the bottom right corner is a status number. This is a number reported by the Async Pro serial communications toolkit. Use the information below for reference. If the number reported is larger than 9999 ignore the first digit. ecOk 0 Reset value for AsyncStatus +++General error codes (0-999)+++ DOS errors ecFileNotFound 0002 File not found ecPathNotFound 0003 Path not found ecTooManyFiles 0004 Too many open files ecAccessDenied 0005 File access denied ecInvalidHandle 0006 Invalid file handle ecOutOfMemory 0008 Insufficient memory ecInvalidDrive 0015 Invalid drive ecNoMoreFiles 0018 No more files Turbo Pascal I/O errors ecDiskRead 0100 Attempt to read beyond end of file ecDiskFull 0101 Disk is full ecNotAssigned 0102 File not Assign-ed ecNotOpen 0103 File not open ecNotOpenInput 0104 File not open for input ecNotOpenOutput 0105 File not open for output ecInvalidFormat 0106 Invalid format for packed window DOS critical errors ecWriteProtected 0150 Disk is write-protected ecUnknownUnit 0151 Unknown disk unit ecDriveNotReady 0152 Drive is not ready ecUnknownCommand 0153 Unknown command ecCrcError 0154 Data error ecBadStructLen 0155 Bad request structure length ecSeekError 0156 Seek error ecUnknownMedia 0157 Unknown media type ecSectorNotFound 0158 Disk sector not found ecOutOfPaper 0159 Printer is out of paper ecDeviceWrite 0160 Device write error ecDeviceRead 0161 Device read error ecHardwareFailure 0162 General failure +++Capacity or environmental errors (2900-2999)+++ APUART port errors ecNoMorePorts 2900 Can't open port, no slots available ecOverrunError 2901 UART receiver overrun ecParityError 2902 UART receiver parity error ecFramingError 2903 UART receiver framing error APCOM/OOCOM errors/status ecBlockIncomplete 2920 Block shorter than requested ecBufferIsFull 2921 No room for new char in buffer ecBufferIsEmpty 2922 No characters to get ecTimeout 2923 Timed out waiting for something ecStringIncomplete 2924 String shorter than requested ecStringOverrun 2925 String longer than 255 ecUserAbort 2926 User aborted during "wait" +++Programmer errors (8900-8999)+++ APCOM/OOCOM port errors ecBadPortNumber 8900 Out-of-range port number ecOutofRange 8901 General out-of-range error ecPortNotOpen 8902 Port not open ecInvalidBaudRate 8903 Bad baud rate for this device ecInvalidArgument 8904 General programming error ecNoDevice 8905 No device layer installed ecNotaUart 8906 Couldn't find a uart at this address ecInvalidParity 8907 Bad parity option for this device ecBadFileList 8909 No end of list marker found in file list ecNotBuffered 8910 Operation only allowed on buffered ports ecNotSupported 8911 Function not supported by device-layer +++Status codes (9900-9999)+++ APABSPCL/OOABSPCL status codes ecInitFail 9900 Xmodem init failed ecInitCancel 9901 Xmodem init was canceled on request ecCancelRequested 9902 Cancel requested ecDuplicateBlock 9903 Duplicate block received ecSequenceError 9904 Wrong block number received ecDirNotFound 9905 Directory not found in protocol transmit ecNoMatchingFiles 9906 No matching files in protocol transmit ecLongPacket 9907 Long packet received during protocol ecEndFile 9908 End of transmitted file ecHandshakeInProgress 9909 Initial protocol handshake in progress ecFileRenamed 9910 Incoming file was renamed ecFileAlreadyExists 9911 Incoming file already exists ecInvalidFilesize 9912 Ymodem header has bad file size ecInvalidDateTime 9913 Ymodem header has bad date/time ecUnexpectedChar 9914 Unexpected char during protocol ecBlockCheckError 9915 Incorrect CRC or checksum received ecNoSearchMask 9916 No search mask specified for transmit ecNoFilename 9917 No filename specifed in xmodem download ecAsciiReceiveInProgress 9918 Ascii receive in progress ecFileRejected 9919 Receiver rejected file ecTooManyErrors 9920 Too many errors received during protocol APZMODEM/OOZMODEM status codes ecGotCrcE 9925 Zmodem - got CrcE DataSubpacket ecGotCrcW 9926 Zmodem - got CrcW DataSubpacket ecGotCrcQ 9927 Zmodem - got CrcQ DataSubpacket ecGotCrcG 9928 Zmodem - got CrcG DataSubpacket ecGarbage 9929 Zmodem - got garbage from remote ecSkipFile 9930 Zmodem - skip file ecBadPosition 9931 Zmodem - bad file position ecFileDoesntExist 9932 Zmodem - specified file doesn't exist ecCantWriteFile 9933 Zmodem - not allowed to overwrite file ecFailedToHandshake 9934 Zmodem - never got proper handshake ecNoFilesToReceive 9935 Zmodem - no files to receive ecBuffersTooSmall 9936 ZModem - port buffers too small ecGotHeader 9937 Zmodem - got a complete header ecNoHeader 9938 Zmodem - (internal) no header yet Archive status messages ecUnknownMethod 9960 Unknown compression method ecFileEncrypted 9961 Cannot extract--file is encrypted ecBadFileCRC 9962 Bad CRC--file is probably corrupted ecCannotCreate 9963 Unable to create output file ecBadFileFormat 9964 Bad archive file format ecNotAnLzhFile 9965 Not an LZH file ecNotAZipFile 9966 Not a ZIP file ecEmptyFileMaskList 9967 File mask list is empty