ftp.wwiv.com

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

/ ftp.wwiv.com / ftp.wwiv.com.zip / ftp.wwiv.com / pub / UTILITY / MTS_V701.ARJ / MTSDOCEN.DOC < prev next >

Wrap

Text File | 1991-04-01 | 66KB | 1,274 lines

╔══════════════════════════════ ┌─────────────────┐ ║ MTS Make Them │ D.I.S.P. │────┐ ║ (Your)Self │ │░░░░│ ╟────────────────────────────── │ │░░░░│ ║ (c) 1991 Robert W.van Hoeven │ Dutch │░░░░│ ╟────────────────────────────── │ Independent │░░░░│ ║ Release : 7.01 │ ShareWare │░░░░│ ║ Rel.Date: 1th April 1991 │ Programmer│░░░░│ ╠══════════════════════════════ └─────────────────┘░░░░│ ║ | │░░░░░░░░░░░░░░░░░│ ║ │ MTS.EXE | └─────────────────┘ ║ │ MTSCFG.EXE | ┌─────┐ | ║ │ | │░░░░░│ | ║ │ | └──┬──┘ | ║ │ Lines starting with '|' are | ┌────┴────┐ | ║ │ changes to release 6.04 !! ------││││││ ═══│------- ║ └─────────┘ ╠═══════════════════════════════ ║ Address: Robert W. van Hoeven ║ PO. Box 131 ║ 1170 AC Badhoevedorp ║ Nederland / Holland ╚═══════════════════════════════ ┌───────┬─────────────────────────────────────────────────────────────┐ │ 0 │ Table of contents │ └───────┴─────────────────────────────────────────────────────────────┘ 1 ---- General information 1.1 Copyrights and License Agreement 1.2 Newer versions and contacting the author 2 ---- Package description and requirements 2.1 Preface 2.2 Requirements 2.3 Included files 2.4 History 2.5 Introduction & specs 3 ---- Installation description 3.1 Installation 3.2 MTSCFG.EXE 3.3 The MTS HELP-files 4 ---- Runtime information 4.1 Calling MTS 4.2 Memory 4.3 Recursive support 4.4 Log file(s) 4.5 The (de)compressors 4.6 Working with MTS 4.7 Baud rates 4.8 FileDoor/DISP-compatible tag-file <tm> 4.9 Errors 4.10 Specials 5 ---- Version information and credits 5.1 The BETA-team 5.2 Credits 5.3 Version history 5.4 Copyright, Trademarks ┌───────┬─────────────────────────────────────────────────────────────┐ │ 1 │ General information │ └───────┴─────────────────────────────────────────────────────────────┘ │1.1 Copyrights and License Agreement │──────────────────────────────────── │- Users of the MTS-package must accept this disclaimer of warranty: │ │- The MTS-package is supplied as is. The author disclaims all │ warranties, expressed or implied, including, without limitation, │ the warranties of merchantability and of fitness for any purpose. │ The author assumes no liability for damages, direct or consequential, │ which may result from the use of the MTS-package; │ │- The MTS-package is a "shareware program" and is provided at no charge │ to the user for evaluation. Feel free to share it with your friends, │ but please do not give it away altered or as part of another system. │ The essence of "user-supported" software is to provide personal │ computer users with quality software without high prices, and yet to │ provide incentive for programmers to continue to develop new products. │ │- If you find this program useful and find that you are using and │ continue the use of the MTS-package after a 30 days trial period, │ you must register the MTS-package as described below; │ │- Non-commercial users will get a license for the usage of MTS by │ sending a postcard or letter as registration. Non-commercial users │ are FREE to use MTS on their system(s) without paying any fee. A │ 'closed BBS' (a BBS where users have to pay for using the BBS) is │ NOT a non-commercial user; │ │- Closed BBS's (a BBS where you have to pay to get access to the │ BBS) can get a Closed-BBS license for a small amount of money. │ All users that are registered before April 1th 1991 (postcards, │ letters or NetMail received by me before April 1th 1991) and that │ run a Closed BBS, get their license for free. See REGISTER.MTS │ for details; │ │- Commercial usage of MTS will cost somewhat more. A company using │ MTS needs a commercial license. See REGISTER.MTS for details; │ │- The registration of the MTS-package will license ONE copy for use on │ any computer at any one time, as long as the usage confirms to the │ type of registration you have done (so NON-commercial usage when you │ have a non-commercial license); │ │- Anyone distributing the MTS-package for any kind of remuneration must │ first contact the Author at the address above for authorization. │ │- You are encouraged to pass a copy of the MTS-package along to your │ friends for evaluation. Please encourage them to register their │ copy if they find that they can use it; │ │- Support on MTS, is available by means of written letters or by │ entering the international echomail area DISP; │ │- Problems and suggestions can be entered in the FidoNet <tm> Echomail │ conference <tm> called DISP (international). Entering this echo does │ not exclude you of the duty to register the MTS-package, though users │ who evaluate the product can enter the echo for questions; │ │- The MTS-package, all programs, the documentation and support-files is │ copyrighted 1991 by Robert W. van Hoeven, PO. Box 131, Badhoevedorp │ 1170AC, Holland. All rights are reserved. You may copy this package │ for backup purposes. Also you may copy and share unmodified copies of │ the whole package, providing that the copyright notice is reproduced │ and included on all copies. │ Excluded from this statement are the support-files written by other │ authors. Please refer to the documentation of these programs for │ copyrights and license agreements; │ │- It is forbidden to modify, adapt, translate, reverse engineer, de- │ compile and/or disassemble the software in the MTS-package. Patching │ the medium at places that carry the software is seen as a program │ change and is also forbidden; │ │- Performing any of the illegal actions as stated in the previous │ lines, is a theft and no fair play to the author and, more important, │ to the registered users; │ │- Bulletin Board Systems that distribute the MTS package can convert │ the WHOLE package to any archive-system they like but all original │ files must be included in the new archive. The MTS-package on the │ Bulletin Board can contain at the most 2 extra files. These files │ can only be a commercial for that Bulletin Board and/or validation │ data that is presented as a service to all users and shall have no │ other functions; │ │- After the normal trial period of 30 days, you must register the soft- │ ware (see REGISTER.MTS) or you must remove it from your PC; │ │- Comments, suggestions and bug reports are welcome and will be answered │ as soon I have the time to do so. You can send me a letter of leave a │ NetMail <tm> message named to Rob Van.hoeven (mind the point) on node │ 2:512/100 (RA Support, Monster, Holland, SysOp is Reinier de Groot). │ When you want to send me normal mail, address it to: │ Robert W. van Hoeven, PO. Box 131, 1171 AC Badhoevedorp, Holland; │ Also you can enter messages in the FidoNet <tm> DISP Echomail <tm> │ area; │ │ │1.2 Newer versions and contacting the author │──────────────────────────────────────────────────────────────────────── │The newest version of MTS is always available at the DISP-HQ on node │2:512/100. MTS is also distributed thru a number of DISP support nodes. │You can obtain MTS in four different ways: │ │- Logging on at DISP-HQ or a support node │ │ All zones : 2:512/100 (Multiline Paradise NL ) DISP-HQ │ (Sysop: Reinier de Groot) │ │ For zone 1: 1:203/988 (Amber Shadow USA ) Support & beta │ (Sysop: Dave Overton ) │ │ For zone 2: 2:280/216 (Sirex NL ) Support & beta │ (Sysop: Gerry Ulrich ) │ 2:242/4 (GOLEM Meerbusch FRG ) Support & beta │ (Sysop: Hanstheo Wolf ) │ 2:244/12 (FunBoard Felbert FRG ) Support & beta │ (Sysop: Dirk Astrath ) │ │ The BBS's above will always have the most current version of MTS │ available. Also, in some cases, it is possible to request the │ newest MTS with a standard file-request (ask the SysOp in question). │ On 2:512/100 you can use MTSNEW as magical name to Freq. the newest │ version. │ The actual DISP-HQ is point 2:512/100.5, but this is a closed system │ and can not be accessed from the 'outside'). You CAN address netmail │ to this point though ! │ │- Logging on to a SDS node │ MTA is distributed thru SDS/SDN, but only big minors (x.10, x.20 and │ so on) and majors (14.01, 15.01 and so on) are submitted to the SDS │ distribution point in Holland; │ │- Logging on to your own BBS; │ Chances are, that you will find an older version (international │ users) because it will take some time for the new version to │ 'bleed' thru the net; │ │- Update service; │ You can enter a special update service (read REGISTER.MTS). │ │ │If you think you have found problems in MTS, or in any other case, │you wish to contact the author, you can send me: │ │- A letter to the address you can find in the header of this file; │- A NetMail <tm> message to Rob Van.hoeven (please mind the point │ between Van and Hoeven) at 2:512/100 or (better) 2:512/100.5; │- A Message in the FidoNet <tm> DISP echomail <tm> area; ┌───────┬─────────────────────────────────────────────────────────────┐ │ 2 │ Package description and requirements │ └───────┴─────────────────────────────────────────────────────────────┘ 2.1 Preface ──────────────────────────────────────────────────────────────────────── Please notice the following: - MTS is a ShareWare product in every right way, this means that this software is not crippled in any way; - This program only works when you have the right compressors available on your PC. It does not do any compression of it's own ! The program only interprets all the supported formats. I can not think of any problem with that, but if any of the authors/companies of the supported products has problems with this program, I will remove that piece of coding at once (although I could not find any quote like 'You may NOT call our program in program's of your own' in any of the doc's); 2.2 Requirements ──────────────────────────────────────────────────────────────────────── MTS requires: - PC XT/AT/386/486 - At least 300K free memory but it depends on the archiver(s) you use; - DOS 3.xx and higher; (tested with 4Dos 3.02, should work with lower versions); - HDU optional - The archives you support; - A Bulletin Board System. Directly supported are the QuickBBS, SBBS and Remote Access types; 2.3 Included files ──────────────────────────────────────────────────────────────────────── The package includes : MTS.EXE The main program MTSHLP.ANS Example help-file for ANSI users MTSHLP.ASC Example help-file for ASCII users MTSCFG.EXE Configuration program 2.4 History ──────────────────────────────────────────────────────────────────────── At this moment it is still 'compression war'. All BBS systems will know already. There are as many 'View/Extract' programs as there are compression programs and this is another one. But please read the remainder of this documentation, because this one brings you the best of all compression worlds..... This program actually is a small version of my compression convertor MTA (up from release 14.40 for the version lovers...). It has added fossil routines and some BBS-tricks and also misses some features found in MTS. Where MTA can be used by the SysOp to convert all incoming files to her/his own compression scheme, MTS is written from the point of the BBS user. It carries all the possible features to minimize the users frustration when he sees that he has to download yet another compres- sion program to extract your famous collection for files. Also this program tries to eliminate the need for a large collection of viewer and extractors for BBS usage and gives you as Sysop and 'them' as the users the highest form of service. │In general, MTS can be used to view and COLLECT any number of files │inside any number of archives. The collected files can be converted │to a new archive of any of the supported types and later it can be │downloaded by the user. MTS is multiline aware and supports the │SBBS <tm>, QuickBBS <tm> and Remote Access <tm> BBS programs. 2.5 Introduction & specs ──────────────────────────────────────────────────────────────────────── Those who took the time to read the history (and I know of at least one, beside myself who hasn't done this) will have a general picture of MTS's functions. For those who didn't, a brief review and some general specs: MTS can do one or more of the following: - Viewing of files inside archives; │- Combine files from several archives to one new archive; │- Create the new archive in any installed type of archive │ (when all are installed you can create ARC, PAK, ZIP, ZOO, HYP, │ LZH, LZS, ARJ, DWC); - Easy to use; - Simulated full-screen support; - Look in and extract from SFX files (if supported by archive); Beside the interface to most compression files, the view SFX and extract from SFX make MTS special. Most viewers can only view (and some extract) more than one compression type, but almost none can view and extract from SFX files. If you want this features offline, you should look for MTA (the big- ger brother of MTS) release 14.30 and up. │MTS was designed with Remote Access, QBBS or SBBS in mind but can work with every BBS program that can work with doors and creates a DORINFO1.DEF when going thru the door. When you use QuickBBS <tm> conversion is simple. The same goes for Remote Access. In the generic mode you must try to emulate QuickBBS <tm>. This is the easiest of the two, because the 'area-file' (the file containing the file-area's) is a straight forward text-file. In RA it isn't. To use MTS, you must install the program first. To minimize file access at startup, the MTS.EXE program is self-contained. This means that you must patch the installation values with a support program (MTSCFG.EXE). ┌───────┬─────────────────────────────────────────────────────────────┐ │ 3 │ Installation description │ └───────┴─────────────────────────────────────────────────────────────┘ 3.1 Installation ──────────────────────────────────────────────────────────────────────── This installation takes Remote Access <tm> as an example. For other BBS programs you have to adapt the installation to your own needs. WARNING: After installation you can only run MTS from within a BBS (local or remote) or place a DORINFO1.DEF and EXITINFO.BBS in the BBS (current) directory before you run MTS from the command-line; - Place MTS.EXE in a directory. - Also place MTSCFG.EXE in the directory you placed MTS.EXE in; │- Also place the MTSHLP.ANS and MTSHLP.ASC files in the same │ directory as MTS.EXE OR in the directory that will be CURRENT │ when MTS starts OR somewhere in the DOS PATH; - ChDir to this directory (make it current); - Start MTSCFG and answer the questions (see below); - Create a menu option (somewhere in your main menu or in the area change or file-menu). Remember that MTS works global 'over' all download directories so placing the menu option everywhere is overhead, but it's your choice... The menu option can be a Type 15 (exit to DOS function) for the QuickBBS system or a type 7 (with *M set to on) for Remote Access. MTS can internally swap itself out of memory before a compressor is executed, so you can also use type 7 (in QuickBBS) or type 7 without *M in a Remote Access environment and still keep enough memory to execute the archiver(s); - Optionally update your text-files (when you work with the type 40 auto-display option) with the MTS function; For QuickBBS/SBBS only: - If you don't work with a file called FLSEARCH.CTL you have to create one in the QuickBBS directory. The file contains a line for every file area you have in the format: path security-level name-of-the-area MTS looks if the user-security matches the level in the lines in FLSEARCH.CTL. If the user-security is equal or higher than the one in the line, the user may select files from this area. For Remote Access only: - Remote Access can run in Single line and multi-line environment. MTS is DesqView aware, so that deals with the first problem. But there is an other thing to consider. You can setup MTS in a multi- line environment in two ways: - Set the BBS path in MTS to the original BBS System-path (first line), also use the FILES.RA in THIS directory (see later). MTS will only open FILES.RA in READ-ONLY mode so this is no problem; - You can configure 1 copy of MTS for up to 8 lines. These 8 lines can all use the same MTS. If you run more than 8 lines (and still want MTS to log for every line), you must create multiple copies of MTS of each bundle of 8 lines; There is really (I hope) no need for the second option. Try the first mode first. If you have trouble, 'gimme a message' and switch to the second option. 3.2 MTSCFG.EXE ──────────────────────────────────────────────────────────────────────── To patch the installation options in MTS, you must use MTSCFG.EXE. MTSCFG.EXE reads the MTS.EXE file and alters some data area's de- pending on the answers. You can expect the following questions: ╒══════════════════════════════════════════════════════════════════════════════╕ │Found : MTS.CFG │ │Use this CFG to load old configuration [Y/N] : Y │ │ │ │Old configuration file used for default settings │ ╘══════════════════════════════════════════════════════════════════════════════╛ Function: When you get a new version of MTS, you can first run the previous version of MTS with the option /CFG to create a file called MTS.CFG. This file (if in the current directory or somewhere in the path) can be used to setup the newer version of MTS. Be warned however that some options could be added or changed, so revise all questions again. If no MTS.CFG file is found, this message will not be displayed; │ WARNING : MTS 7.01 can NOT read MTS.CFG files from older │ versions. Only 7.xx type of CFG-files can be │ read ! ╒══════════════════════════════════════════════════════════════════════════════╕ │You can now select the type of BBS you run MTS on. Currently there │ │are three types supported, Generic, QuickBBS <tm> and the Remote │ │Access type. When choosing <Generic>, you are on your own ! │ │NOTE : Use <ESC> to abort installation and read documentation !! │ │ │ │You can enter the following types: 0 - Generic BBS type │ │ 1 - QuickBBS <tm> │ │ 2 - Remote Access <tm> Rel 0.xx │ ││ 3 - Remote Access <tm> Rel 1.xx │ ││ 4 - SBBS <tm> │ ││ │ ││Type of BBS MTS will assume : 3 │ ╘══════════════════════════════════════════════════════════════════════════════╛ Function: Now is the moment to select your own type of BBS system. This question will also rule some of the next questions, │ so please take the right BBS system. Type 0 is simple a │ QuickBBS <tm> generic type where you can select the type │ of logging by yourself. │ Please make sure to choose between the Remote Access 0.xx │ and 1.xx releases. There are several rules involved to any │ of the types so pick the right one (the one you currently │ use). │ SBBS users will get the same options as the QuickBBS users. ╒══════════════════════════════════════════════════════════════════════════════╕ │BBS system directory (containing config files) : D:\BBS\RA\ │ ╘══════════════════════════════════════════════════════════════════════════════╛ Function: This entry must point to the BBS system directory. For a QuickBBS <tm> BBS this must point to the directory containing CONFIG.BBS. For Remote Access this must point to the path where CONFIG.RA is found. This path is only used in BBS types 0 and 1. For a Remote Access system this entries is superfluous, but I advise you to enter the right path over here; ╒══════════════════════════════════════════════════════════════════════════════╕ │Directory where MTS places its downloadable file : D:\BBS\RA\FILES\VIR\ │ ╘══════════════════════════════════════════════════════════════════════════════╛ Function: This must point to one of the common area's that all users can access. MTS places its DOWNLOAx.fff file over here, so the user can download the file. The 'x' depends on the line-number (1 by default) that you supply with the /L option, the 'fff' depends on the type of target-file, the user has selected (f.i. ZIP or ARJ). In a multi-line environment, you MUST assign the /Lline value to MTS, otherwise sharing problems (or worse) can be the case. Every time MTS is entered, MTS will delete all files with the name DOWNLOAx.fff in this area before any questions are asked to the user. For a multi-line environment, only the DOWNLOAx.fff files for THAT line are deleted (not the other lines); ╒══════════════════════════════════════════════════════════════════════════════╕ │Decription of this area : Virtual Area │ ╘══════════════════════════════════════════════════════════════════════════════╛ Function: You can enter the name of the area you supplied in the pre- vious question (e.g. something like 'Common download files'). You can insert spaces at any place; │╒══════════════════════════════════════════════════════════════════════════════╕ ││Directory MTS will put the FileDoor tag-file : D:\BBS\RAX │ │╘══════════════════════════════════════════════════════════════════════════════╛ │Function: FileDoor 2.xx (and higher) can use a so called FileDoor/DISP │ compatible tag-file. This file can be created by programs │ like RFW and can be used by FileDoor 2.xx. │ The tag-file will have the name BBSTAGFl.n (where 'n' is the │ number of the line). Look into the documentation of FileDoor │ (2.xx or higher) to see a description of the format of this │ file. │ │ When tagging is enabled in FileDoor, the user can give /TAG │ on the file-selection line. A standard file (the tag-file) │ is loaded (when available) and the filenames inside this │ file are carried over into FileDoor <tm>, working as a kind │ of note-pad. When you use tagging in FileDoor you must let │ this option point to the same directory as FileDoor will use │ to find the tag-file. Only the directory has to be included. │ MTS will create the filename (and the file itself) depending │ on the line it is running. ╒══════════════════════════════════════════════════════════════════════════════╕ │Directory where MTS places its in-between files : E:\ZIP │ ╘══════════════════════════════════════════════════════════════════════════════╛ Function: MTS creates some in-between files when the user wants to view or combine some files from an archive. This entry must point to a valid directory. MTS will create another sub-directories UNDER this directory. These special directories are generated by MTS and have a unique name, so sharing problems are not possible in a multiline environment. │ MTS will generate the following directories UNDER the direc- │ tory you supply over here (where [dddddddd] is the hex-decimal │ representation of the current date/time and [ll] is the num- │ ber of the current BBS-line (01-08): │ │ dddddddd.All : This directory contains the files that will │ make up the private collection of the current │ user; │ dddddddd.Vll : This directory contains the extracted files │ that the user is currently viewing; │ │ The following option in MTSCFG can be set to a certain num- │ ber of bytes that will limit the disk-usage for these two │ directories. You must assign a directory on a drive that │ can contain (at least) this number of bytes; │ │╒══════════════════════════════════════════════════════════════════════════════╕ ││Maximum bytes allowed in private collection : 512000 │ │╘══════════════════════════════════════════════════════════════════════════════╛ │Function: The user can create a private collection of files that are │ extracted from one or several source-archives. This option │ will set the maximum number of UNCOMPRESSED bytes that can │ be in the user's private collection. This figure, plus the │ amount of uncompressed bytes for the largest file to be │ viewed, must be available on the drive where the in-between │ files are stored (previous option); ╒══════════════════════════════════════════════════════════════════════════════╕ │Directory for temp. archive files or empty : E:\ZIP │ ╘══════════════════════════════════════════════════════════════════════════════╛ Function: Some archivers (ZIP, ARJ and more) can use a temporary direc- tory for their in-between files. Best way, is to use a RAM- drive for this directory if you have enough storage on such │ a drive. A RAM-disk of 128K or less will, in general, give │ more problems benefit to this option. │ If you leave this entry empty, MTS will not pass a temporary │ directories to the archivers. ╒══════════════════════════════════════════════════════════════════════════════╕ │Directory for swap-files or empty (current) : E:\ZIP │ ╘══════════════════════════════════════════════════════════════════════════════╛ Function: MTS can swap itself out of memory BEFORE any archiver is called. When memory is low and/or when you use large programs like ARJ and the new LHA, you should set swapping for these archivers to ON. If you do so, MTS will look at this option. │ If a directory is present, MTS will use it for the swap-file │ (if created, see later). If no directory is present (you have │ left the option empty), MTS will use the current directory. │ │ The swap routines will look for EMS first. If enough of this │ type of memory is available, MTS will use it. Otherwise MTS │ will look for XMS memory. Again, when not enough XMS memory │ is available, MTS will look for EXTENDED memory. If there is │ not enough of this memory also, MTS will use a disk-file to │ store the swap-data. This can even be the case on a big AT- │ class type machine with lots of memory. It could be the case │ that you used all extended/EMS/XMS memory for a RAM-disk. If │ you did so, you can let this option point to that drive. In │ all other cases, this directory is used for the swap-file. │ Use the fastest drive that is available and eligible. │ │ Swapping will ONLY occur when for those archives that are │ installed with swapping set to ON. ╒══════════════════════════════════════════════════════════════════════════════╕ │File used as area-file (FLSEARCH.CTL/FILES.RA) : D:\BBS\RA\FILES.RA │ ╘══════════════════════════════════════════════════════════════════════════════╛ Function: This must point to a file describing all area's and their security levels (and area names). The file FLSEARCH.CTL (or its name-like) should be used over here when running a QuickBBS <tm> system (also an alternate name can be used). The file FILES.RA (with the path) MUST be used for a Remote Access System (you can however, create an optional FILES.MY as a stripped copy of FILES.RA and let MTS use this one); │╒══════════════════════════════════════════════════════════════════════════════╕ ││Path and name of ARC.EXE or empty string : C:\SYS\ARC\ARC.EXE │ ││Swap memory before calling this program [y/n] : N │ ││ │ ││Path and name of PKZIP.EXE or empty string : C:\SYS\ARC\PKZIP.EXE │ ││Swap memory before calling this program [y/n] : N │ ││ │ ││Path and name of PKUNZIP.EXE or empty string : C:\SYS\ARC\PKUNZIP.EXE │ ││Swap memory before calling this program [y/n] : N │ ││ │ ││Path and name of PAK.EXE or empty string : C:\SYS\ARC\PAK.EXE │ ││Swap memory before calling this program [y/n] : N │ ││ │ ││Path and name of PKUNPAK.EXE or empty string : C:\SYS\ARC\PKUNPAK.EXE │ ││Swap memory before calling this program [y/n] : N │ ││ │ ││Path and name of ZOO.EXE or empty string : C:\SYS\ARC\ZOO.EXE │ ││Swap memory before calling this program [y/n] : N │ ││ │ ││Path and name of LHARC.EXE or empty string : C:\SYS\ARC\LHARC.EXE │ ││Swap memory before calling this program [y/n] : N │ ││ │ ││Path and name of LARC.EXE or empty string : C:\SYS\ARC\LARC.EXE │ ││Swap memory before calling this program [y/n] : N │ ││ │ ││Path and name of DWC.EXE or empty string : C:\SYS\ARC\DWC.EXE │ ││Swap memory before calling this program [y/n] : N │ ││ │ ││Path and name of ARJ.EXE or empty string : C:\SYS\ARC\ARJ.EXE │ ││Swap memory before calling this program [y/n] : N │ │╘══════════════════════════════════════════════════════════════════════════════╛ │Function: This cluster of questions will decide which compressors are │ available for selection by the user. Obvious, the archivers │ that you use on your BBS-files must be available. All other │ archivers are a service to the user. The more archivers you │ supply, the more users can be satisfied. If you want certain │ archivers to be left out, you must supply an EMPTY string ! │ │ Some archivers will use much (VERY MUCH) memory. LHA and the │ ARJ and HYPER are some obvious examples. If memory is low, │ you can select to use swapping for these archivers. For ANY │ archiver you supply (compressors AND decompressors) you can │ select to use swapping or not. It will take more time when │ swapping is on, so select the swappable archivers with care. │ │ Because of the old 'compression war', I have left out the │ PKPAK/PKARC options. Only the PKUNPAK/PKXARC can be used. │ If you want to be able to create old ARC files with MTS, │ you MUST supply ARC.EXE (S.E.A.). Also ZIP'ing is only │ possible with PKZIP and not with PAK.EXE ! ╒══════════════════════════════════════════════════════════════════════════════╕ │Path and name include file Nr.1 (or empty string): │ │Path and name include file Nr.2 (or empty string): │ │Path and name include file Nr.3 (or empty string): │ ╘══════════════════════════════════════════════════════════════════════════════╛ Function: Up to 3 entries can be entered. If you include a filename (with path) in one or more of the entries, MTS will add these files to the DOWNLOAx.fff file when it is created. │ The user won't like it, but if you always add some advertise- │ ment file inside your archives, it is a good idea to include │ it in the DOWNLOAx.fff files also. Users won't like to get │ files like PKZ110.EXE or 640x480x256 DAISY.GIF as 'bonus' │ files, so use this option with care ! ╒══════════════════════════════════════════════════════════════════════════════╕ │Alternate fossil port, 999 lets MTS sort it out : 999 │ ╘══════════════════════════════════════════════════════════════════════════════╛ Function: If you do NOT use a standard FOSSIL-port scheme, you must insert the FOSSIL-port to use over here. If you run a multi- line BBS with a non-standard scheme, there is no other way than to create multiple copies of MTS. Under normal con- ditions this should not be the case. When MTS must use the FOSSIL port-number equal to the COM port-number (taken from DORINFOx.DEF) minus 1 (the default situation), you must enter a 999 over here; ╒══════════════════════════════════════════════════════════════════════════════╕ │Locked baudrate (0 to let MTS sort out baudrate) : 0 │ ╘══════════════════════════════════════════════════════════════════════════════╛ Function: Independent of the baud-rate supplied in DORINFOx.DEF, you can instruct MTS to lock itself on a baud-rate. This should only be done when you use a locked-baudrate on your whole system ! ╒══════════════════════════════════════════════════════════════════════════════╕ │Type of LOG, F=Frontdoor, O=Opus style [F/O] : F │ ╘══════════════════════════════════════════════════════════════════════════════╛ Function: When MTS must create a LOG-file, you can select the type of │ log to create. QBBS/SBBS systems have no choice. Generic systems can choose 'FrontDoor-style', 'Opus-Style' or 'QuickBBS-style'. Remote Access systems can only choose between 'Frontdoor- style' and 'Opus-Style'. IF MTS will create a log, depends on the next entries ! ╒══════════════════════════════════════════════════════════════════════════════╕ │Name of the logfile for line x, or empty (nolog) : D:\LOG\LINE01.LOG ││ ╘══════════════════════════════════════════════════════════════════════════════╛ Function: You will get this question for 8 lines. If you leave the entry empty, MTS will not log on that line. If you want to create a log, you can point to a special log-file OR you can let MTS append the log-records to the BBS log. MTS will create compatible logs (depending on the previous question) so log-analyze programs can still access the log. │3.3 The MTS HELP-file │──────────────────────────────────────────────────────────────────────── │You can change the MTSHLP.Axx files to any format you like. You can use │a special ANSI-editor to create a new MTSHLP.ANS file and a normal text │editor (that can create flat ASCII files) to change the MTSHLP.ASC │file. │ │MTS will look for a CTRL-A (). If this character is found, MTS will │wait for a keystroke from the local or remote keyboard. Look into the │supplied examples for the usage of this characters ! │ │The supplied examples contain almost ALL information for this release. ┌───────┬─────────────────────────────────────────────────────────────┐ │ 4 │ Runtime information │ └───────┴─────────────────────────────────────────────────────────────┘ 4.1 Calling MTS ──────────────────────────────────────────────────────────────────────── MTS (under normal conditions) is called from a menutype 7 or 15 (depending on the BBS type and version you use. MTS carries only two (optional) command-line parameters. The first must NEVER be used when MTS is called from a menu. This is /CFG; /CFG will create a MTS.CFG in the current directory. You can use this file to reinstall MTS again or to install a newer version. The other optional command-line parameter can be used from the menu call. This is /Lx. /Lx must contain the BBS-line number (1,2,3,4,5,6,7,8) for a multi- line environment. You can use the *N option in type 7 (Remote Access) to auto-detect the line-number. The call should be: drive:path\MTS.EXE /L*N 4.2 Memory ──────────────────────────────────────────────────────────────────────── MTS will consume a nice amount of memory (100K by itself). Also, when MTS calls a (de)compressor, the memory this program uses must be added to the amount you already use. In a non-overlay/non-swapping BBS of around 250K this could cause memory problems. There are some options to deal with this problem: - Use a build-in swapper in the type 7, like the *M in Remote Access (nice feature and fast too). You should always do so if you have the type of memory (EMS/Extended) available; - Use a type 15 option; - Use an overlay-version of the BBS to reduce memory usage by the BBS itself (QuickBBS overlayed version); - Use MTS's internal swap ! NEVER use a batch-file with a stand-alone swap to call MTS. Stand-alone swap's will refuse to work or will make a mess of your interrupt list. Under normal conditions everything is recovered but when using asynch communication, this WILL cause a problem. 4.3 Recursive support ──────────────────────────────────────────────────────────────────────── Unlike MTA, MTS does not carry a recursive support (yet). This should be no problem because when the user extracts some files from an existing compression-file, directories inside the original compressed file will have no meaning anymore. When time, MTS is converted to support recursive support. All compressed files with directory names inside the file, can be converted with MTS, but the directory-name is lost when you convert the extraction to an- other method of compression. 4.4 Log file(s) ──────────────────────────────────────────────────────────────────────── MTS can append the log-records to any file. MTS always tries to append │if the file is already present, otherwise the file is created. The for- │mat of the log is the same as the format of the BBS's log-file. Please │notice that you use different log-files for different lines. MTS will │not try to serialize the log-file so cross-linked files can be the re- │sult of multiple accesses to the same log-file from different lines. 4.5 The (de)compressors ──────────────────────────────────────────────────────────────────────── As already stated, MTS depends on the ORIGINAL compression/decompression programs. As you have seen, you must instruct MTS to look for these pro- grams in fixed directories. There is one little trick you should know of. Of course you know that there was a 'war' going on between SEA and PKWare. NoGate's PAK (also a very nice program) can do best of both worlds and more. I am no judge, and I will not make any judgments but I find that I should respect the results of the 'war'. I can imagine that some (or many) of you have always used PKWare's program's and don't own a copy of ARC (not even a evaluation copy), but others have both programs. PAK.EXE is downward compatible with (old) PKWare and PKWare is downward compatible with ARC.EXE. Depending on the internal structure of the source file, MTS will take ARC.EXE first, then PKWare and then PAK.EXE. Concerning the destination options. When you ask for a destination of ARC, MTS will only work when you own a copy of ARC.EXE. It is NOT possible to create a destination of ARC with the PKWare (old) and │Nogate programs (NoGate can be created with the PAK option). The same │goes for ZIP. ZIP can only be created with the original PKZIP.EXE and │not the NoGate PAK.EXE. 4.6 Working with MTS ──────────────────────────────────────────────────────────────────────── MTS is full-screen driven. This means that working with MTS under the BBS (or local) is ease. When in doubt, display the help in- │formation that is supplied. We will walk thru a typpical session: │ │The user wants to look inside MTS_V701.ZIP to view the MTS.NEW and │(optionally) wants to extract only the documentation to download it: │ │- Entering MTS; │- On the question, the user answers MTS*.*; │- He gets back MTS_V604.ZIP. Knowing this old buggy version, he will │ answer NO and MTS will now return MTS_V701.ZIP. So a Y is given; │- He gets a screen with all the files inside the archive. Setting │ the NUM-LOCK to on, the user is now able to scroll thru the files; │- The user selects (tag) MTS.NEW and presses <V>iew. The information │ is displayed; │- Now the user tagges MTS.NEW and MTSDOCEN.DOC and uses <A>dd to add │ these files to his own collection. But Argg! the MTSDOCEN.DOC was │ not needed. So <F>lush will empty the private collection again ! │ Now MTS.NEW and REGISTER.MTS are selected (tagged) and <A>dded to │ the private collection; │- Now the user remembers the new MTA. The users enters <N>ew and │ selects MTA_VE40.ZIP. MTS will return this name and the user │ will select it; │- MTA.NEW is tagged and <A>dded to the private collection; │- Now <C>ombine is used to create a new archive, containing the files │ MTS.NEW, REGISTER.MTS and MTA.NEW; │- The user selects ARJ and MTS will create the new archive under the │ name DOWNLOA2.ARJ (did I forget to mention that we are busy on the │ second line ?); │- Also a DISP-compatible tag-file <tm> is created. The user enters │ FileDoor <tm> and enters /TAG after selecting a protocol. The │ DOWNLOA2.ARJ is selected and download can start; │ │Simple isn't it. 4.7 Baud rates ──────────────────────────────────────────────────────────────────────── Baud-rates (even locked) can be as high as your fossil (BBS) supports. Use 999 in MTS.CFG to let MTS sort out the baud-rate. If you want to force a locked rate, you can enter the locked baud-rate over there ! │4.8 FileDoor/DISP-compatible tag-file <tm> │──────────────────────────────────────────────────────────────────────── │MTS can create a so called FileDoor/DISP-compatible tag-file in the │directory you supply in MTSCFG.EXE. This tag-file will contain all │the information for FileDoor <tm> to access the newly created file │DOWNLOAx.fff in an easy way. │ │FileDoor <tm> 2.xx (when released) can use two kinds of tag-files. │The first one is normal tag-file. The user MUST enter /TAG on the │FileDoor selection question. The second one is a so called AUTOLOAD │tag-file. When the user selects the download-menu, FileDoor will │load the tag-file without having to enter the /TAG on the selection │line. The user is still able to select or deny the tagged files. MTS │will create a tag-file of the SECOND (so AUTOLOAD) type. │ │When you don't work with FileDoor (2.xx and up), you can disable the │creation of tag-files by giving an empty string to the tag-file op- │tion in MTS.CFG. │ │When there is still a FileDoor/DISP compatible TAG-file, MTS will │give a warning to the user and the user gets the choice to terminate │MTS (and go to FileDoor) or to overwrite the tag-file. 4.9 Errors ──────────────────────────────────────────────────────────────────────── When errors occur, MTS aborts and the user gets back to the BBS. If the error was detected by MTS itself, you can find the error in the log-file for that line. If the user hangs the phone while in MTS, MTS will terminate with the next INPUT-loop. If you are not sure, use a watchdog like WATCHCD or WAKA to watch the carrier. Routines are tested but you never know, all previous versions had no problems at all; 4.10 Specials ──────────────────────────────────────────────────────────────────────── MTS has 3 ways of running: -1) Under a BBS with a remote user logged on. In this case MTS uses both FOSSIL and local keyboard routines, so you as sysop can 'guide' your remote user local; -2) Under a BBS in local operation. In this case MTS uses only the local keyboard routines; -3) Stand alone You must capture a DORINFO1.DEF file (Remote Access leaves one for you after termination) and run MTS as a stand-alone program. Also from release 5.05 and up, a EXITINFO.BBS file is needed; MTS needs ANSI.SYS to be active in your local system, but that's no problem because your BBS needs it too (in most cases). On the remote side, MTS will use ASCII or ANSI. When the user is working with the AVATAR emulation, MTS will use normal ANSI. A special note about DORINFO1.DEF. Under types 0 and 1, DORINFO1.DEF is opened in the BBS system directory (this could also be the cur- rent directory, but just in case of). Under Remote Access, MTS will open the DORINFO1.DEF file in the CURRENT directory. This could well be the BBS System directory too, but in multi-line environments it could also be another directory. The same goes for EXITINFO.BBS; │MTS will try to clean all temporary directories when the termination │is not abnormal (e.g. a run-time error). If this is not possible, │the directories and files will stay on disk, but the next user won't │have any problems with them, because MTS creates new directories for │every new user; When converting TO the ZIP system, you should know that you need at least Version 0.92 (-ex option) or higher. Version 0.90 is, beside the fact that it contains some bugs, not supported ! MTS is implemented to run under DesqView <tm>. I see no reason why MTS would not run under DoubleDos <tm> or TopView <tm>, but having only an old 4.xx version of DoubleDos and no version of TopView, I │can not test this. This also goes for other multitasking software. │Windows 3.0 <tm> will also work OK, because some users of MTS run │their BBS under Windows and have not complained about it at all. For the DesqView <tm> users the following information: - All the MTS output (in user ANSI-mode) is done in ANSI, so if you did not do so at the start of your DV window, you have to include DVANSI before starting MTS; - MTS uses own colors and does not write directly to the screen; - MTS looks for multitaskers and if multitasking is present, it will use virtual window pages (local); - MTS is a non-critical task; ┌───────┬─────────────────────────────────────────────────────────────┐ │ 5 │ Version information and credits │ └───────┴─────────────────────────────────────────────────────────────┘ 5.1 The BETA-team ──────────────────────────────────────────────────────────────────────── The following Sysop's and their CoSysop's (only if they use the same BBS or a NON-user (closed) shadow BBS) are allowed to make use of the BETA-releases on their own risk: - Remote Access Multiline/Multiport Paradise 2:512/100 (*) Sysop: Reinier De Groot - GOLEM Service BBS 2:242/4 Sysop: Hanstheo Wolf - Sirex BBS 2:280/4 (HUB) Sysop: Gerry Ulrich 2:280/401 - Funboard BBS Sysop: Dirk Astrath 2:244/12 - Amber Shadow Sysop: Dave Overton 1:203/988 The BBS marked with (*) will always test the newest version and is also the main distribution node for the MT-series. Also mail to me can be send to this system. The other BBS's are asked, if they like, to test the new versions, but if there is no time, or if they find the risk to high I don't mind. I would be pleased though, if these BBS's would like to look into the new BETA version. 5.2 Credits ──────────────────────────────────────────────────────────────────────── Thanks to the following people: - All registered users. You make it possible to enhance MTS with nice features; - All users who did write me a message and/or sent me a postcard; - The BETA-team; - A special 'thanks' to Reinier de Groot, Hanstheo Wolf and Dirk Astrath. They keep coming with nice suggestions; - A big thanks to Dave Overton who is doing the USA support; 5.3 Version history ──────────────────────────────────────────────────────────────────────── ┌───────┬─────────────────────────────────────────────────────────────┐ │ 1.xx │ Sample release information │ └───────┴─────────────────────────────────────────────────────────────┘ ■ What ever did version 1.xx ?? ┌───────┬─────────────────────────────────────────────────────────────┐ │ 2.xx │ Sample release information │ └───────┴─────────────────────────────────────────────────────────────┘ ■ View added, DV aware; ┌───────┬─────────────────────────────────────────────────────────────┐ │ 3.xx │ Sample release information │ └───────┴─────────────────────────────────────────────────────────────┘ ■ FOSSIL support, full-screen version, added LHARC, ZIP and PAK; ┌───────┬─────────────────────────────────────────────────────────────┐ │ 4.xx │ Sample release information │ └───────┴─────────────────────────────────────────────────────────────┘ ■ An ALL-beta release; ┌───────┬─────────────────────────────────────────────────────────────┐ │ 5.01 │ Major release │ └───────┴─────────────────────────────────────────────────────────────┘ ■ Added support for generic and Remote Access BBS types; ■ Reworked to TurboPower Object Professional; ■ Changed MTSCFG to be somewhat smarter than previous versions; ■ Fixed large number of flaws (only internal); ■ Installation configuration can now be saved and carried to a newer version; ■ Extra speed on some routines; ■ Reworked FOSSIL support a bit; ┌───────┬─────────────────────────────────────────────────────────────┐ │ 5.02 │ Bug release │ └───────┴─────────────────────────────────────────────────────────────┘ ■ A few critical routines removed. As it went, MTS would always take ALL (or as many) ticks from other tasks; ■ The backspacing (local and remote) was in error. This has been fixed; ■ MTS would (running in Remote Access mode) display empty paths and would then start using them. This caused MTS to 'hang'. Pressing the CTRL-Z local would 'resurrect' MTS again. Fixed; 'resurrect' MTS again. Fixed; ■ After termination MTS will now clear the screen; ┌───────┬─────────────────────────────────────────────────────────────┐ │ 5.05 │ Bug release │ └───────┴─────────────────────────────────────────────────────────────┘ ■ Fixed a problem with the /CFG option. When no DORINFO1.DEF was present, MTS would abort before a MTS.CFG was created; ■ Fixed a problem with the log-file. Only the last line in the log- file was present. This is fixed; ■ Included an exit-procedure, so MTS will always try to remove the temporary files and path; ■ When a user selected '*.*' it was possible that MTS would display FILES.BBS (or BAK) or DIR.BBS (or BAK). This is fixed. These files are always skipped by MTS; ■ When MTS was searching on large (slow) drives or special media (like CD-rom), waiting could be very long and users could drop the carrier in panic (thinking the BBS did hang). MTS will now display a kind of windmill (I'm dutch you know) running on the screen (after change in path); ■ Display is somewhat changed. Fixed some flaws in the questions (default options are now in caps on and [ENTER] can be used to select the default), the help-bar is now more colorful and the NUM-LOCK warning is now flashing red; ■ Added support for security flags (only in the Remote Access mode). MTS now uses EXITINFO.BBS (both QuickBBS and RA). Under RA, MTS will compare the user flags to the flags in the file-area's. If flags don't match, MTS will skip that area. Flags work the same way as they work in RA (so when a user has security 100 without flags and an area has security 50 with flags, the area is skipped although users security is higher); ┌───────┬─────────────────────────────────────────────────────────────┐ │ 5.06 │ Bug release │ └───────┴─────────────────────────────────────────────────────────────┘ ■ Fixed a bug that could cause directories to be cleaned from any (wanted or unwanted) file. This could happen at random but only when MTS had an error before the main-screen is presented (not installed, not DORINFO1 or something like that). ┌───────┬─────────────────────────────────────────────────────────────┐ │ 5.07 │ Bug release │ └───────┴─────────────────────────────────────────────────────────────┘ ■ When running under RA <tm>, MTS will also ask the user if he/she wants to skip or process any special (slow) drives like a CD-rom. If there are no FILES.RA area's with a different list- and filepath, this question has no meaning at all. If you have installed such area's, a 'Y' to the question (default) will mean that MTS will search thru this area's. A 'N' will cause MTS to skip these area's ! ┌───────┬─────────────────────────────────────────────────────────────┐ │ 5.08 │ Minor and Bug release │ └───────┴─────────────────────────────────────────────────────────────┘ ■ Changed the version documentation. ■ MTS caused a 'file not found' situation when the user replied a 'N' to the slow-drive question and the FILES.RA contained empty paths in the List-path field. This is fixed. Reported by Reinier de Groot; ■ MTS now only asks for the slow-drive search if running under RA AND when you have answered 'Y' to the installation question about slow-drives. This question will only be asked when you installed MTS as running under a RA system. When you answer NO to the installation question, the user never gets the slow-drive question; ┌───────┬─────────────────────────────────────────────────────────────┐ │ 5.09 │ Bug release │ └───────┴─────────────────────────────────────────────────────────────┘ ■ Changed MTSCFG to OPRO; ■ MTS contained bug when archives with more than 100 files were processed. This is fixed; Reported by Various users; ■ MTS contained bug when running in RA-mode and when BBS used security levels greater than 32767 (QuickBBS). This is fixed; Reported by John Barton; ┌───────┬─────────────────────────────────────────────────────────────┐ │ 5.10 │ Minor Release │ └───────┴─────────────────────────────────────────────────────────────┘ ■ Added support for ARJ files; Reported by Various users; ■ Changed some displays in NON-ANSI mode to keep the ASCII users happy; Reported by: Eddy Emck ┌───────┬─────────────────────────────────────────────────────────────┐ │ 6.01 │ Minor Release │ └───────┴─────────────────────────────────────────────────────────────┘ ■ Added support for LHA (LHARC 2.05 and up). I suggest that you use the new 2.05 as a replacement of LHARC 1.13 because MTS will NOT test if the file can be converted with older LHARC versions (e.g. LH 2.05 files and conversion with 1.13); ■ Fixed a problem with ARJ. ARJ would ask, 'OK to delete files'. This is fixed. Reported by: Many ■ MTS would ask for a new mask when the user entered no to the sug- gested file. This is changed. MTS will now search for the next file that validates the filemask until all files (area's) are searched. Suggested by: Many ■ Fixed the under-score in FLSEARCH.CTL area names. These are now displayed as spaces. Suggested by: Saar Blitz ■ Changed logging again. MTS can now log in different files for different lines. Suggested by: Saar Blitz ■ Questions (and variables) for various temporary directories are reinstated again. Suggested by: Saar Blitz ■ Fixed some flaws in MTSCFG.EXE. Suggested by: Saar Blitz ┌───────┬─────────────────────────────────────────────────────────────┐ │ 6.02 │ Bug release │ └───────┴─────────────────────────────────────────────────────────────┘ ■ Sorry to all users who used MTS /CFG. This would cause a directory to be flushed (files and directory). ┌───────┬─────────────────────────────────────────────────────────────┐ │ 6.03 │ Bug release │ └───────┴─────────────────────────────────────────────────────────────┘ ■ Removed the exit-routine. All problems with the temporary directory should be gone now but already 99.9999999% of the users would not have problems with 6.02 already; ┌───────┬─────────────────────────────────────────────────────────────┐ │ 6.04 │ MAJOR Bug release │ └───────┴─────────────────────────────────────────────────────────────┘ ■ Thanks to Henny Kohler (dutch user) I have found a nasty bug in MTS. Under certain conditions (and locally for sure) drives (even non- network drives) could be 'lost'. MTS was trashing memory because of an internal error (the current-drive list could get corrupted, not the drives themselfs but DOS had to rebooted to get them back). This is now fixed; Reported by : Henny Kohler ■ Many users complained about the fact that MTS would leave the temporary directory on disk. This has either to do something with the DOS-release or TP6 (or both) but is fixed now. Reported by : Many users ┌───────┬─────────────────────────────────────────────────────────────┐ │ 7.01 │ Major release │ └───────┴─────────────────────────────────────────────────────────────┘ ■ OK, I know, MTS was becoming a mess. I agree. It has always been a pain in the head (MTS I mean) and now I decided to rewrite it from almost scratch. From the users point of view, only a few op- tions are added, from the inside everything works different than before. This also gave me the chance to add some new features and to take away some of the painful routines. This will also fix some bugs that I have found; ■ MTS would still remove files and directories when using /CFG. This is now fixed (again); Reported by : Many users; ■ MTS would delete the log-file if it was called MTS.LOG and in the current directory. This is fixed. Log will stay on disk; ■ MTS would deny some view operations. MTS was not closing some file handles in certain cases. This is fixed; ■ MTS can now combine files from several archives. The user can now make his/her own private collection of files, before combine has to be started. Also flushing of the private collection is imple- mented; Suggested by : Many users ■ Added support for SBBS and RA 0.xx/1.xx operations; ■ Fixed a problem where MTS could not run multi-line with QBBS; ■ MTS can now work on HYPER (25 and up) and MDCD files; ■ The help-information is now contained in normal ASCII (ASC) and ANSI (ANS) files. You can alter the contents; Suggested by : Many users ■ Added FileDoor/DISP-compatible tag-file <tm> so users can use /TAG when FileDoor 2.xx (or higher) is used; ■ MTS is reduced in size. Optimized many routines. Removed the dummy header for ARJ files. ■ Routines for ARJ 1.10 and LHA 2.11 are implemented; ■ Many cosmetic changes to all the screens; MTS is tested with PKWare PKPAK release 3.61, PKWare ZIP release 1.10, NoGate release 2.51, ARC release 6.02 and ZOO release 2.01, DWC 5.10, LHarc 2.11 and LARC 3.33, ARJ 1.10 and on a running Remote Access BBS system 1.00 and 1.01betaB. Also execution under DesqView is tested with version 2.31 and QEMM version 5.11 (plus fix). 5.4 Copyright, Trademarks ──────────────────────────────────────────────────────────────────────── PKPAK, PKUNPAK, PKZIP and PKUNZIP are trademarks of PKWare Inc. PKLITE is a trademark of PKWare Inc. PAK is a trademark of NoGate Consulting. ARC is a trademark of SEA inc. ZOO is a trademark of R. Dhesi. DWC is a trademark of Dean W. Cooper LZH and LHarc are trademarks of Yoshi; LZS and LARC are trademarks of K.Miki H.Okumura and K.Masuyama MD is a trademark of Michael Davenport ARJ is a trademark of Robert K. Jung HYPER is a trademark of Peter Sawatzki and Klaus Peter Nischke CRA is a trademark of DISP and donated to public domain Windows is a trademark of The Microsoft Corporation 4Dos is a trademark of J.P. Software / R.C. Conn and T. Rawson FrontDoor is a trademark of J. Homrichhausen SWAP is a trademark of Nico Mak / Mansfield Software Group SCAN is a trademark of McAfee Associates VIRSCAN is a trademark of J.P. van der Landen TBSCAN is a trademark of Frans Veldman / ESaSS B.V. VALIDATE is a trademark of McAfee Associates CRC.EXE is copyrighted by Howard Vigorita but seems to be public domain; CRC32.EXE is copyrighted by Barry Geller but seems to be public domain; QuickBBS is a trademark of the QuickBBS group Inc. QuickBBS is a trademark of The QuickBBS Team, Inc Remote Access is a trademark of Continental Software DoubleDos is a trademark of SoftLogic Solutions DesqView is a trademark of QuarterDeck Office Systems. Windows is a trademark of Microsoft X00 is a trademark of Ray Gwinn MTS is written in Turbo Pascal 6.0, with help of the Turbo Debugger 2.0 and makes extensive use of Object Professional 1.10 and OPCFI V 9.06. Turbo Pascal is a trademark of Borland International Turbo Debugger is a trademark of Borland International Object Professional is a trademark of TurboPower Inc. OPCFI is a trademark of Robert W. van Hoeven ==================== END OF DOCUMENT ==================================