Version 2.6:  Added support for the keyword DOWN in the twit file to temporarily disable the door without reconfiguring all the door control files for the BBS. Example twit file useage: XWAR DOWN where XWAR is the door name and flagging it as down. An errorlevel of 5 will indicate the 'down' status. Add to your batch files if you use this. Fixed a bug where /N1 properly limit the number of times per day to 1.  Increased the limit of the door's name from 4 characters to 8. This can now be the same name as the batch file that runs that door, it might make things a little less confusing. Version 2.5: Fixed a problem where users in the Twit file not being detected. Version 2.4: Problem reading in some of PcBoard.sys data on some conversion routines. Fixed. Version 2.3: Fixed a problem when the conversion routine was selected and alternate commands lines were entered via the config file, the conversion file was not being created and would exit with an error. In laymans terms, the programmer screwed up. Fixed a problem in the converted file when callers (sysops mostly) had a large amount of time left and was giving a negative number of minutes left. (Prototype your variables Wayne! -5 points.) Version 2.2: Was not including the callers birthday in the door.sys file. Fixed. Added support to read Door.sys and create Dorinfox.def, Chain.txt Callinfo.bbs and PcBoard.sys. Aborted Conversion routine will now (U)nlock the door if previously (L)ocked. Some changes and additions to the doc file. Version 2.1:  Door.sys format to include the new expanded form of that file. Version 2.0:  We have begun writting a built in conversion routines. I am/was sick and tired of the other 'converters' that just decided to 'ad-lib' so much data. Most or all of them required a config file and still can't even come close to creating a proper file of another BBS's type. Well.....NO MORE!....... Version 2.0 is basically geared to PcBoard based systems such as Pcboard 14.x and FeatherNet amoung others. We create from your pcboard.sys file the following formats: Dorinfox.Def, Callinfo.bbs, Chain.txt and Door.sys as good or better than your own system could have if it would. The only exceptions to this being the Conference scans/joined, etc, then again, how many PcBoard/Fnet systems use a Mail Reading doors anyway? Best of all, NO CONFIG file is required for this routine! All 2.xx versions of DoorMan will be Beta versions as we add these routines. We hope to carry this utility to the point to where it is the very last management utility you will ever need to run doors. We hope to add other BBS types real soon. Due the the Major expense trying to track down these formats and the major time it took to impletement these routines, this feature will be available to registered users of the program only. Version 1.1 Maintanence release only. Optimized the code some for speed, minor changes here and there. What??? No bug reports? Version 1.0 Initial release. áeta tested on several systems, all was well. Amazing....huh... Released á version as 1.0.