Beijing Paradise BBS Backup

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

/ Beijing Paradise BBS Backup / PARADISE.ISO / software / BBSDOORW / MTS_V764.ZIP / MTSDOCEN.DOC < prev next >

Wrap

Text File | 1993-05-30 | 69.9 KB | 1,462 lines

╔══════════════════════════════ ┌─────────────────┐ ║ MTS Make Them │ D.I.S.P. │────┐ ║ (Your)Self │ │░░░░│ ╟────────────────────────────── │ │░░░░│ ║ (c) 1993 Robert W.van Hoeven │ Dutch │░░░░│ ╟────────────────────────────── │ Independent │░░░░│ ║ Release : 7.64 Pre-Release │ ShareWare │░░░░│ ║ Rel.Date: May, 31th, 1993 │ Programmer│░░░░│ ╠══════════════════════════════ └─────────────────┘░░░░│ ║ | │░░░░░░░░░░░░░░░░░│ ║ │ MTS.EXE | └─────────────────┘ ║ │ MTSCFG.EXE | ┌─────┐ | ║ │ | │░░░░░│ | ║ │ | └──┬──┘ | ║ │ Lines starting with '│' are | ┌────┴────┐ | ║ │ changes to release 7.63 !! ------││││││ ═══│------- ║ └─────────┘ ╠═══════════════════════════════ ║ Address: Robert W. van Hoeven ║ PO. Box 131 ║ 1170 AC Badhoevedorp ║ Nederland / Holland ╚═══════════════════════════════ *********************************************************************** *********************************************************************** ** W A R N I N G : This is a pre-release, meaning that this version** ** is *close* to 'the real' 8.01, but some options ** ** will not work (yet). ** *********************************************************************** *********************************************************************** ┌───────┬─────────────────────────────────────────────────────────────┐ │ 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 4.11 FILES.CTL 4.12 Security 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, Closed BBS and Commercial users can obtain a license by following the procedures described in the file REGISTER.MTS which must be inside this distribution archive; - 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 1993 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 software (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:281/904 (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:281/904. 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 Look into the file SUPPORT.MTS for a full list of support nodes; - Logging on to a SDS node MTS is distributed thru SDS/SDN, but only big minors (x.10, x.20 and so on) and majors (8.01, 9.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:281/904 or (better) 2:281/904.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 MTSCFG.EXE Configuration program MTS_ANSI.ZIP The ANSI help-files (examples) MTS_ASCI.ZIP The ASCII help-files (examples) 2.4 History ──────────────────────────────────────────────────────────────────────── At this moment it is still 'compression war'. All BBS systems will know already. The number of door-type 'view/extract' programs is somewhat more limited than before, mainly because MTS can do just that what you want (in most cases). This does not mean that there will be no development to MTS in the future. New archivers will hit the marked (or newer, sometimes better, versions of current archivers) and the average user of today is more demanding than in the past. This program actually is a small version of my compression convertor MTA (up from release 15.10 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 compression 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 multi-line aware and supports the SBBS <tm>, QuickBBS <tm> and Remote Access <tm> BBS programs. In the past, MTS was for free and, because there are no drawbacks on the shareware version, some users will continue to use it for free. From version 7.59, you are encouraged to pay a little fee for MTS. Users of 7.59 can pre-register for the 8.01 release for a price that is very low (see REGISTER.MTS). The reason for the pre-release is the FileDoor <tm> 3.01 support that is not available in all previous versions. Also you will be able to have a 'glance' at what is to come (because a number of features are present in the configuration program but don't work). Because of this 7.59 you can have the FileDoor <tm> features working without having to wait for the 8.01 release (which will take a couple of weeks). The actual testing is still a job of the beta-team, but if you encounter any problems, feel free to inform me about them ! 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; - Archive of non-archived files, so smaller files are created for download; - 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, SQZ); - 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. Also, most are not able to extract (and combine) files from VARIOUS archives into one archive. If you want these features offline, you should look for MTA (the bigger brother of MTS) release 15.10 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 and QuickBBS 2.75+ 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; Installation will go as follows: - If you upgrade from a previous version of MTS, you should do the following: - Run the old MTS.EXE with only /CFG on the command-line (so MTS /CFG), it doesn't need BBS files in this mode; - Remove ALL old MTS.EXE and MTSCFG.EXE versions from your hard-disk; - Continue the installation; - Place MTS.EXE in a directory (preferred in the DOS path); - 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 the directory containing MTS.EXE and MTSCFG.EXE; - Start MTSCFG.EXE and start filling in all the screen. The MTSCFG program works with pull-down menus to ease the installation; - 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 (2.74 and lower): - 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 (all versions) only and partially for SBBS; - 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; - For SBBS you must assume FLSEARCH.BBS (not CTL) for the options above. Also MTS can work with both DORINFOx.DEF (x is the BBS line) and DORINFO1.DEF options in SBBS; There is really no need for the second option (I hope). 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. I will describe most of the fields in the pull-down menus: ╒═════════════════════════════════════════════════════════════════════╕ │Startup │ ╘═════════════════════════════════════════════════════════════════════╛ When MTSCFG.EXE is started, it will first search for MTS.EXE (in the current directory, the DOS-path or in the same directory where MTSCFG was started from). Then it will search for a file called MTS.CFG. If this file is present, MTSCFG will ask you if you want to use it (you should do so when you upgrade from a previous version). It is possible that MTSCFG will warn you that there are new features that must be installed first. ╒═════════════════════════════════════════════════════════════════════╕ │BBS-Type │ │Paths │ │Miscellaneous │ │General │ ╘═════════════════════════════════════════════════════════════════════╛ These are the 4 main menus that are present within MTSCFG. You should go from left to right when you start updating all fields, but you can change single fields in specific menus also; ╒═════════════════════════════════════════════════════════════════════╕ │BBS-Type │ │ Generic BBS type │ │ QuickBBS <tm> 2.74 down │ │ QuickBBS <tm> 2.75 up │ │ Remote Access <tm> 0.xx │ │ Remote Access <tm> 1.xx │ │ Remote Access <tm> 1.1x │ │ SuperBBS <tm> 1.xx │ ╘═════════════════════════════════════════════════════════════════════╛ When you enter the 'BBS-type' menu, you can select ONE of the BBS types that is listed. When you select on (scroll to it and press ENTER) 'ON' will be shown and all others will be off. ╒═════════════════════════════════════════════════════════════════════╕ │Paths │ │ Path to archivers │ ╘═════════════════════════════════════════════════════════════════════╛ This menu will present you a sub-menu. In this sub-menu you must supply all drive, directory and filenames of the archivers that you are going to support. If you leave one or more paths empty, the user will not be able to use that archiver (not for the source-archive nor for the target-archive). 7.62 special : The paths to OWN (compress and decompress), GIF2JPG and GIFLITE can be set, but will not function in 7.62. They will in 8.01; ╒═════════════════════════════════════════════════════════════════════╕ │Paths │ │ Path to include-files │ ╘═════════════════════════════════════════════════════════════════════╛ This menu will present you a sub-menu. In this sub-menu you can set up to 3 files that are included to the archive when a user creates a new archive of her/his own. If you leave the field empty, no file will be included. You must supply the drive, directory and filename. ╒═════════════════════════════════════════════════════════════════════╕ │Paths │ │ Path to logfiles │ ╘═════════════════════════════════════════════════════════════════════╛ This menu will present you a sub-menu. In this sub-menu you can set up to 8 log-files for each line you are going to run MTS for. Include the drive, directory and filename. Also there is a sub-menu present. In this sub-menu you can supply the type of logging (OPUS, Frodo or QuickBBS style) you would like. ╒═════════════════════════════════════════════════════════════════════╕ │Paths │ │ BBS-system directory │ ╘═════════════════════════════════════════════════════════════════════╛ This directory must point to the BBS-system directory. It must contain a drive and directory (no filename). ╒═════════════════════════════════════════════════════════════════════╕ │Paths │ │ Download directory │ ╘═════════════════════════════════════════════════════════════════════╛ This field must point to the directory from where the user can later download the file that she/he has generated with MTS. All users must be able to access this download-area. ╒═════════════════════════════════════════════════════════════════════╕ │Paths │ │ Area name of DL directory │ ╘═════════════════════════════════════════════════════════════════════╛ This field must contain the NAME of the area where MTS will place the created files (the name of the area that is pointed to by the previous option). ╒═════════════════════════════════════════════════════════════════════╕ │Paths │ │ Temporary directory │ ╘═════════════════════════════════════════════════════════════════════╛ This field must point to a directory where MTS can place some temporary files and directories. There must be enough room on this drive. ╒═════════════════════════════════════════════════════════════════════╕ │Paths │ │ In-between directory │ ╘═════════════════════════════════════════════════════════════════════╛ This field must point to a directory where MTS can store the un-archived files that the user collects while working inside MTS. There must be enough space to contain a couple of large files (you can limit the amount with one of the other options below). ╒═════════════════════════════════════════════════════════════════════╕ │Paths │ │ Swap directory │ ╘═════════════════════════════════════════════════════════════════════╛ This field must point to a directory where MTS can place its internal swap files. MTS needs around 300K for each swap-file (so there must be enough space for one or more swap-files). ╒═════════════════════════════════════════════════════════════════════╕ │Paths │ │ Path to area-file │ ╘═════════════════════════════════════════════════════════════════════╛ This field must point to the correct file that contains the areas that your BBS manages. For old QuickBBS and SBBS BBS-types, you must point to a FLSEARCH.CTL (alike) file. For Remote Access you must point to the correct FILES.RA file. The field must contain drive, directory and name of the file. ╒═════════════════════════════════════════════════════════════════════╕ │Paths │ │ Alternate FILES.BBS directory │ ╘═════════════════════════════════════════════════════════════════════╛ This field is only needed for Remote Access 1.0x and 1.1x versions. It must point to the directory that contains the FILES.n files for offline devices like CD-ROM. ╒═════════════════════════════════════════════════════════════════════╕ │Paths │ │ DISP tag-file directory │ ╘═════════════════════════════════════════════════════════════════════╛ This directory must be set when you use FileDoor 2.xx or 3.xx. This is the location where FIleDoor will search for DISP/FileDoor-compatible tag-files. For SBBS, use the *CUR option in this field, because SBBS itself will look for the tag-file in the 'current' directory. When you don't want tag-files to be created, use NONE as a value overhere; ╒═════════════════════════════════════════════════════════════════════╕ │Paths │ │ ANS/ASC text-directory │ ╘═════════════════════════════════════════════════════════════════════╛ This directory must be set to the directory that can (optionally) contain the special ANS/ASC files that MTS can use (some examples are included in the release archive ! ╒═════════════════════════════════════════════════════════════════════╕ │Miscellaneous │ │ Max. disk-space to use │ ╘═════════════════════════════════════════════════════════════════════╛ This field must contain the maximum disk-space a single user can use for uncompressed files. In the process, the user can select one or more files from one or more archives. These files will combine into a new archive (with the output format the user likes and you support). The value over here will govern the number of bytes the user can set aside before she/he is forced to combine the files and download the result. If you supply 0, MTS will allow all the space that is available at the moment the user is working on the file. ╒═════════════════════════════════════════════════════════════════════╕ │Miscellaneous │ │ Alternate FOSSIL port │ ╘═════════════════════════════════════════════════════════════════════╛ Normally MTS will sort out itself which FOSSIL-port is must access. If the BBS runs on COM1, the port will be 0, on COM2 1 and so on. If you use a different setup, you must set the port number over here. Normally you supply 999 as the default, so MTS will test itself ! ╒═════════════════════════════════════════════════════════════════════╕ │Miscellaneous │ │ Swapping toggles │ ╘═════════════════════════════════════════════════════════════════════╛ This is a sub-menu. For each archiver you can toggle swapping to ON or OFF. When ON, MTS will swap from memory before the archive-program is called. It is advised to use swapping on most of the archive programs unless you know what you do. ╒═════════════════════════════════════════════════════════════════════╕ │Miscellaneous │ │ Locked baudrate │ ╘═════════════════════════════════════════════════════════════════════╛ If you run a BBS on a modem with locked baudrate, you must supply the rate over here. Normally (when you supply 0), MTS will use the baudrate that is found in DORINFO1.DEF. ╒═════════════════════════════════════════════════════════════════════╕ │Miscellaneous │ │ Update FILES.BBS │ ╘═════════════════════════════════════════════════════════════════════╛ MTS can update the FILES.BBS of the area where it places its file that can be downloaded by the user. If you set this option to ON, MTS will add and delete entries in FILES.BBS itself (in a fixed format). If you dislike these updates, you can switch this option to OFF. ╒═════════════════════════════════════════════════════════════════════╕ │Miscellaneous │ │ Default extension │ ╘═════════════════════════════════════════════════════════════════════╛ Normally the user will supply a file-mask. If she/he does not supply an extension, MTS will add .* to the extension unless you set a default extension over here. In that case, MTS will add the extension you supply (only supply the extension, not the point). If you dislike the default extension, you can leave this field empty. ╒═════════════════════════════════════════════════════════════════════╕ │Miscellaneous │ │ Ignore hidden │ ╘═════════════════════════════════════════════════════════════════════╛ Normally the user can select any file that is available inside the area (or areas) that can be access with his/her security level(s). This will also include those files that are in these directories but are not registered inside the FILES.BBS. If you would like that your users can NOT select files that are not described in FILES.BBS, you should set this option to [ON], otherwise leave it to [OFF]. ╒═════════════════════════════════════════════════════════════════════╕ │Miscellaneous │ │ Date format │ ╘═════════════════════════════════════════════════════════════════════╛ You can use an alternate date format in MTS. You must always use 8 bytes, so combinations like dd/mm/yy and mm-dd-yy are allowed (as is ddmmyyyy) but dd yyyy is not allowed ! ╒═════════════════════════════════════════════════════════════════════╕ │Miscellaneous │ │ Registered MTS │ ╘═════════════════════════════════════════════════════════════════════╛ You should leave this field blank when you did not receive a registered copy of MTS. If you do, you should follow the instructions in the supplied documentation-files that come with the diskette when you register. ╒═════════════════════════════════════════════════════════════════════╕ │General │ │ Help │ ╘═════════════════════════════════════════════════════════════════════╛ Help will (at this moment) not give you much help. Only a few rules about the usage. ╒═════════════════════════════════════════════════════════════════════╕ │General │ │ Version info │ ╘═════════════════════════════════════════════════════════════════════╛ Used only once (or never). ╒═════════════════════════════════════════════════════════════════════╕ │General │ │ Quit MTSCFG │ ╘═════════════════════════════════════════════════════════════════════╛ When you quit MTSCFG, it will ask if the updates must be written to the MTS.EXE program. If you enter N, all changes are lost ! 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 menu-type 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 /F[path] can contain a drive, directory and name of a file that must be viewed or worked on. This option can be used in combination with FileDoor <tm> version 3.0x to use MTS as an external viewer. With this option set, the user can NOT change to another file. If /VIEW is not supplied, she/he IS able to create a DOWNLOAx.xxx file ! /VIEW can be used to run MTS in view-only mode. If present, MTS will only allow viewing of files and will not allow the creation of new (personal) archives. It is the suggested way of calling MTS under FileDoor 3.0x. 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 format 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 result 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 and 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 information that is supplied. We will walk thru a typical 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 tags 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 but it works. Under VIEW-ONLY mode (you have supplied the /VIEW command-line option) you can not add or combine. Also, in this special case, the DISP-compatible tag-file <tm> will be left alone, even if it is available. 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> 3.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 (3.xx and up), you can disable the creation of tag-files by giving an empty string to the tag-file option 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. This is not the case when a user enters MTS in VIEW-ONLY mode (/VIEW), as would be the case when MTS is called from FileDoor <tm>. 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 multi-taskers and if multitasking is present, it will use virtual window pages (local); - MTS is a non-critical task; 4.11 FILES.CTL ──────────────────────────────────────────────────────────────────────── From this release (and up), MTS will support the FILES.CTL file that can be used by the BBS to implement unwanted, free and special password protected files. Obvious, MTS will only use the /PWD (files protected with a password) options from FILES.CTL. Up to 100 password protected files can be supported. MTS will look for a FILES.CTL file as follows: - Inside the directory pointed to by the SYSTEM-directory (supplied in MTSCFG.EXE). Obvious this is the BBS SYSTEM-directory; - Inside the CURRENT directory; - Inside the directory that contains MTS.EXE; - Inside the DOS-path; If no FILES.CTL is found, MTS will not mark files as password protected and will work as normal. If found, MTS will abort if the syntax of the FILES.CTL file is incorrect. If it is correct, MTS will store all the passwords for the password protected files. If a user selects such a file, MTS will ask for the password (up to 3 times). If no (valid) password can be supplied, MTS will search for the next file. Special formats of FILES.CTL, where only files are entered without any /PWD, /FREE or other extra parameter, are accepted but will not result in a different behaviour of MTS. 4.12 Security ──────────────────────────────────────────────────────────────────────── Various BBS programs use various types of security. MTS will look for the 'normal' security order (level and flags). In special cases (in the case of Remote Access), MTS will also look if the user can 'LIST' files (the LIST security). Security (where LIST and DOWNLOAD security can be different values) is implemented as follows: - If the LIST-security (in combination with the LIST-security-flags) is is too high, the user will not be able to select the files from this area at all; - If the LIST-security is OK for the user (in combination with the LIST-security-flags), files from this area can be selected in two different ways: - If the DOWNLOAD-security (in combination with the DOWNLOAD-security flags) is to high for the user, MTS will only allow VIEW and ADD and/or COMBINE is impossible. VIEW is impossible when the file is a non-archived file; - If the DOWNLOAD-security (in combination with the DOWNLOAD-security flags) is to OK for the user, MTS will allow VIEW and ADD/COMBINE (full functional); If there is no separation between LIST and DOWNLOAD security, MTS will only look at the normal security level (and flags). ┌───────┬─────────────────────────────────────────────────────────────┐ │ 5 │ Version information and credits │ └───────┴─────────────────────────────────────────────────────────────┘ 5.1 The BETA-team ──────────────────────────────────────────────────────────────────────── See SUPPORT.MTS for a list of beta-team members. 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; - This pre-release is dedicated to our friend Saar who kept pressing for changes and fixes for the better (keep up the good work); 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.xx │ Sample release information │ └───────┴─────────────────────────────────────────────────────────────┘ ■ Complete rewrite; ┌───────┬─────────────────────────────────────────────────────────────┐ │ 6.xx │ Sample release information │ └───────┴─────────────────────────────────────────────────────────────┘ ■ LHA support. ┌───────┬─────────────────────────────────────────────────────────────┐ │ 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 options 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); ■ 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 implemented; ■ 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; ■ 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; ┌───────┬─────────────────────────────────────────────────────────────┐ │ 7.05 │ Bug-release │ └───────┴─────────────────────────────────────────────────────────────┘ ■ When you pressed 'N' to all suggested files, MTS would report 'Invalid compression file [name]'. This is a wrong error message and is fixed; ■ A screwup in the ASCII tag-menu is fixed; ■ The layout of the FileDoor/Disp-compatible tag-file is changed. MTS now used the new format; ■ There are some new options pending but not YET implemented in this version. This is a bug-release and does not contain new features. ┌───────┬─────────────────────────────────────────────────────────────┐ │ 7.59 │ Pre-release │ └───────┴─────────────────────────────────────────────────────────────┘ ■ There is now an entry for both LHA (2.xx format) and LHARC (1.13 format); ■ There were some small errors with line-checking and carrier checks which are fixed; ■ Fixed some bugs in the log-entries; ■ When N was used, MTS would go back to the BBS if the user entered only a CRLF on the filename question. Fixed; ■ MTS can now update the FILES.BBS by itself (add and delete of the created DOWNLOAx.XXX file in FILES.BBS); ■ Sharing on FILES.RA would fail sometimes. Fixed; ■ Added a small status line (not nice, but it is there); ■ Remote Access 1.11 support is added (just a small part, the difference between view/download security will be added in the 8.01 release); ■ User can now give ESC or 'S' when viewing the help information; ■ It is now possible to assign a default extension; ■ MTS has now a 'single-file' option which can be supplied on the command-line (FileDoor 3.xx support); ■ MTS has now a 'view-only' option which can be supplied on the command-line (FileDoor 3.xx support); ■ The returning message (Returning to BBS) has been altered; ■ Added (NOT activated) coding for conversion of GIFS, flat-files, several exits and extended help-files. All to come with the actual 8.01 release; ┌───────┬─────────────────────────────────────────────────────────────┐ │ 7.60 │ Pre-release │ └───────┴─────────────────────────────────────────────────────────────┘ ■ Fixed a nasty bug where users could enter file-masks like ..\*.* or ../*.* (or any other mask with relative paths, as long as the limit of 12 characters was not reached). Paths (relative and absolute) are now stripped from selection; ■ Under rare circumstances, MTS would report 'Unregistered' even if it was registered or would report run-time errors. This was caused by a sharing problem on the key-file. Fixed; ■ Under RA (1.1x), MTS would allow work on files that had a security for list (not normal or download-security) that was higher than the user-security. In fact, when the normal security was matched, MTS would not look at the list-security. This has been added to MTS; ■ Added support for a FILES.CTL file. Files (inside FILES.CTL) marked as password-protected will now force MTS to ask for the password if the user selects such a file; ■ Added support for the *MT*.* (4DOS) and =MT (DISP alike) wildcards. *MT*.* or =MT (which does the same) will force a shifted search, so kMTA.zip, MTA_v145.arj and coMTAsk.hyp will all match; ■ Changed the name of the MTSHLP.A?? file into MTS_HLPx.A?? (where x can be 1, 2 or 3). You can have 0 up to 3 HLP-files which all can be interrupted while they display on screen; ■ Added support for MTS_WELC.A?? which will be displayed just after the start of MTS and BEFORE the file-selection; ■ Added support for MTS_GBYE.A?? which will be displayed just before termination of MTS; ┌───────┬─────────────────────────────────────────────────────────────┐ │ 7.61 │ Pre-release │ └───────┴─────────────────────────────────────────────────────────────┘ ■ Fixed a bug where MTS would fail while reading FILES.CTL. This was caused by FILES.CTL entries without secondary parameters. Now these entries are left alone and MTS will continue; ■ Fixed a problem with the LIST/DOWNLOAD security. MTS will now look at both levels in ALL circumstances; ■ Fixed a major problem with the tag-file. If a user REentered MTS, MTS could report that there was still a tag-file. After that message the user could choose to terminate MTS to download the previous file (DOWNLOAx.xxx) first, but when the user did so, MTS had already removed that DOWNLOAx.xxx file. Now, the DOWNLOAx.xxx file will not be removed when the user terminates at this question, so both tagfile and DOWNLOAx.xxx will be present for download; ■ Enhanced the tag-file detection. If MTS is called with /VIEW (as will be the case under FileDoor), it will not look for, nor do anything with, the tag-file (if present) and the previous DOWNLOAx.xxx (if present). This makes it possible to create a user-archive while still viewing files under FileDoor <tm>; ■ Fixed a bug where the tag-file was left in the directory. When the user answered to continue MTS (even with the tag-file still present), MTS would leave the old tag-file (but would delete the previous file) when the user did not (re)create a new user-archive. When the user entered FileDoor <tm>, the auto-tag was started but the DOWNLOAx.xxx file was already gone. MTS will now delete a previous tag-file when the user ignores the warning and starts MTS when there is still a tag-file around; ■ MTS was sometimes unable to view GIF and JPEG files. This was cause by a bug in the archive-detection routines and is now fixed; ■ When MTS asked for a password, the password was shown on the local screen (not remote). Now MTS will show a number of '#' characters when the password is entered (both local and remote); ■ Removed some duplicate coding. This should make the remote/local output somewhat faster; ■ At the local screen there would be trash-screens when no GOODBYE file was present. MTS will now display a clear-screen in these cases to preserve the screen for any task that follows; ■ GIF/JPEG files were marked as archives without any file inside. Now MTS will display the type of file and (in case of GIF) the type of GIF-file (XXXxYYYxCCC). The user can still view the contense of this file; ■ While searching for files, you can now supply Y (yes), N (no) and Q (Quit). Q(uit) will terminate the search and will jump back to the initial file-selection screen. Overhere the user can hit [ENTER] to terminate MTS; ■ Added 'Ignore hidden' option to make MTS not select any file that is not inside the FILES.BBS file; ┌───────┬─────────────────────────────────────────────────────────────┐ │ 7.62 │ Pre-release │ └───────┴─────────────────────────────────────────────────────────────┘ ■ Fixed various problems that have to do with SBBS and QBBS (2.75+) that run Multi-line. Previous versions of MTS would look for the EXITINFO.BBS and DORINFO1.DEF files in the BBS-system directory, but now MTS will look in the current directory. The BBS system directory is now only used to search for the FILES.CTL file (if any); ■ Fixed a problem with /F. /F would not allow a tag-file to be made in the tag-file directory; ■ Fixed various problems in the archive detection routines; ■ Fixed problems with ZOO (high compression) and PKZIP (2.xx). These formats are now supported but you need to install the correct program versions (ZOO 2.10 and PKZIP 1.93) yourself. If you don't extraction *could* be impossible when you support such files on your BBS; ■ Added coding for SBBS CDROm files which were not detected by the previous versions of MTS; ■ Added coding to support various date formats in MTS and MTSCFG; ■ Non-archived files can not be viewed when the download-security is not of the right level; ■ Non-archived can now be viewed and/or added to the personal buffer in which case they can be compressed into the DOWNLOAx.XXX file; ■ SBBS implementations can now work with either DORINFO1.DEF as the default or with DORINFOx.DEF files (x is line-number). MTS will first look for the DORINFOx.DEF file. If it is not found, MTS will continue to search for DORINFO1.DEF; ■ If you press [ENTER] (without a filename) on the file-selection question AND you still have files in your personal buffer (to create a DOWNLOAx.XXX file), MTS will now display a question where you can select to 'Q'uit, 'C'ombine or 'S'elect another file again. You don't have to go into the menue anymore. This is done, because the view/add of a non-archived file will not force MTS into the primary Otherwise the user should have to select a bugus file to enter the menue; ■ Added coding to support the fine SQZ compression program, made by Jonas I Hammarberg; ■ Changed all coding to Borland Pascal 7.0, which could result in a little gain in speed; ┌───────┬─────────────────────────────────────────────────────────────┐ │ 7.63 │ Pre-release │ └───────┴─────────────────────────────────────────────────────────────┘ ■ This is a fast (Q&D) release to support RA 2.00 gamma which has seen the light; ■ Fixed a problem where MTS could not extract files with relative directories from a ZIP-file. The file will still be stored without the directory (e.g. there is not yet directory support in MTS). Only PKUNZIP has problems with extractions from the archive when there are directories included inside the archive; ■ Fixed some problems with PKZIP 2.xx; ■ Fixed a problem with archives that contained files that are larger than 999.999 bytes. The screen overflow is now suppressed by placing a 'k' (KB) after these files. All files with sizes under 1.000.000 bytes are still displayed as normal; ■ Fixed a problem with DORINFOx.DEF support under SuperBBS, please let me know if this still causes problems; ■ Fixed a problem with the FILES.BBS entries. This was the result of an internal overflow. This should not occur anymore. Again let me know; ■ Added support for SQZ 1083 releases (and higher); ■ Added support for Remote Access 2.00 (gamma) and the new structures (again <sigh>). Yet ALL versions of Remote Access are still supported by MTS; ┌───────┬─────────────────────────────────────────────────────────────┐ │ 7.64 │ Pre-release │ └───────┴─────────────────────────────────────────────────────────────┘ ■ DON'T BE DISAPPOINTED IF THE OPTIONS YOU ASKED ARE NOT INCLUDED. There will be a new version very soon. Some questions you asked for (like the optional ENTER for the log-out screen, the -README problems and so on), WILL be included, but this version needed to be quick (and dirty); ■ Due to a 'change' in the structures for ARJ 2.39e (and higher), MTS would not report any files. This has been fixed, until the moment the structures for ARJ change again; ■ Fixed a nasty numeric overflow situation. This could cause some invalid scrolls in the PGUP function. Fixed; MTS is tested with PKWare PKPAK release 3.61, PKWare ZIP release 2.04g, NoGate release 2.51, ARC release 6.02 and ZOO release 2.10, DWC 5.10, │LHarc 2.13 and LARC 3.33, ARJ 2.39f and on a running Remote Access BBS │system 2.00 or SuperBBS 1.17gamma2. Also SQZ 10.83 is used for testing │of MTS. 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. SQZ is a trademark of Jonas I. Hammarberg 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 Pegasus Software Remote Access is a trademark of Continental Software SuperBBS is a trademark of Aki Antman and Risto Virkkala 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 MTA is a trademark of Robert W. van Hoeven / DISP FileDoor is a trademark of Robert W. van Hoeven / DISP MTS is written in Borland Pascal 7.0, with help of the Turbo Debugger 3.5 and makes extensive use of Object Professional 1.20 and OPCFI V 16.30. Borland 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 ==================================