DoorFix Door Conversion Utility

Version 1.49.01 Beta

Written by Eric Harvey and Donald Huggins

Copyright (c) 1989, 1990 by Eric Harvey and Donald Huggins
All Rights Reserved
DoorFix (tm) is a registered trademark of the above license.


































TABLE OF CONTENTS


What it Does............................................................ 1


How to Use DoorFix...................................................... 2


Setting the TZ Dos Environment Variable................................. 3


Command Line Parameters................................................. 4


Errorlevels Returned for Batch Files.................................... 5


Configuration File...................................................... 6


Help.................................................................... 7


Disclaimer / Bug Reporting.............................................. 8

Note that the '|' character in the first column indicates a change in the
documentation since the last version released.


o DoorFix should run on any IBM (tm) or 100% compatible with at least 200k
free RAM. It is likely to run well in less, but for all modes of operation
200k seems to be a very good number (under 4Dos at least, maybe less under
straight DOS).

o DoorFix is compatible with DESQview, and DoubleDOS. Overlays may be loaded
into EMS for speedier conversions.

o For even faster conversions, turn "Quiet" mode on.















DoorFix Documentation Page 1

What it Does


DoorFix is a utility which reads the Door.sys, Dorinfo1.def, Callinfo.bbs,
Sfdoors.dat, Jumper.dat, System.hst, Exituser.soc, Userinfo.txt, Userinfo,
|Chain.txt, Pcboard.sys, and Lastus##.dat files created by many other BBS
|systems and converts them into a variety of "door support" files.

It is a program which was originally created to run those 'stubborn' doors
on our systems.

Files Included in Original Distribution Archive:

Name of File Description of File

|Doorfix.exe DoorFix Main Executable and Overlay File
|Doorfix.doc DoorFix Main Documentation
Doorfix.cfg Sample DoorFix Configuration File
|Changes.log Changes Made to DoorFix
Readme.1st Last Minute Additions
SharWare.Txt DoorFix Registration Notice
|Sample.Zip Sample Batch files using DoorFix

DoorFix will create data files from information found in the door source
file and data provided by the DoorFix.cfg file. The Following BBS source
files and types are listed with a heading describing if it can also be
used as a source file.

Door Type File Created or Updated Useable as Source

New Door Sys File Door.sys Yes
B.H. Forbes Userfile Yes
Genesis Deluxe Callinfo.bbs Yes
Milton Gameworks Userinfo.txt Yes
RBBS Dorinfo1.def Yes
RBBS Dorinfo1.def Yes
Spitfire Sfdoors.dat Yes
TPBoard Dorinfo1.def Yes
Wildcat 1.12/1.13 Callinfo.bbs Yes
Wildcat 2.0+ Callinfo.bbs Yes
WWIV systems Chain.txt Yes
|PCBoard 12.x/14.x Pcboard.sys Yes
PCBoard.dat N/A
Users N/A
QBBS 2.0x/2.6x Exitinfo.bbs N/A
Dorinfo1.def {new RBBS form} Yes
Remote Access .02 Exitinfo.bbs N/A
Dorinfo1.def {new RBBS form} Yes
Phoenix 1.3 Info.bbs Yes
2AM Jumper.dat Yes
|OPUS CBCS 1.13 Lastus##.Dat Yes
EaziHost System.hst Yes
Socrates Exituser.Soc Yes

DoorFix Documentation Page 2


How to Use DoorFix


DoorFix uses the following command line parameters. These parameters can
be in any order on the command line and any case, provided they are
separated by spaces. Parameters bounded by < >'s are not mandatory.

From DOS:

DoorFix DoorType


NOTE: DoorFix without any parameters will bring up a help screen.

"DoorType" Can be any of the following:

"DoorType" Door Format Created

DsNew New Door.Sys
Forbes B.H. Forbes
Genesis Genesis Deluxe
Mg Milton Gameworks
DoorOld RBBS Old Format
DoorNew RBBS New Format
Spit Spitfire
OldWild Wildcat 1.12/1.13
NewWild Wildcat 2.0+
WWIV WWIV
PCB12 PCBoard 12.1
PCB14 PCBoard 14.x
OLDQBBS QuickBBS 2.01
NEWQBBS QuickBBS 2.61
RA Remote Access 0.02
Phoenix Phoenix 1.3
TPBoard TPBoard
2AM 2AM-BBS
OPUS OPUS CBCS 1.13 **
EaziHost EaziHost
Socrates Socrates
|Install Performs Installation/Modification of DoorFix.Cfg and
| DfSlTime.Dat.

** NOTE: Opus needs to know what time zone you live in. This is set in
your "environment", part of your autoexec.bat file that runs every time
your computer is booted up. For SysOps using Tick and Tick type util-
ities, that environment variable is probably already set correctly.

(For systems not running OPUS doors, the TZ environment variable is not
required for proper operation of DoorFix.)

DoorFix Documentation Page 3

Its put into your AUTOEXEC.BAT file with a line like:

SET TZ=PST08

That setting is for Pacific Standard Time. If it is Daylight Savings Time
the line would be:

SET TZ=PST08PDT

The '08' in the TZ line refers to the fact that Chico, California is 8
hours behind Universal Coordinated Time.

Here are some examples :

USA Pacific Time SET TZ=PST08 SET TZ=PST08PDT
USA Mountain Time SET TZ=MST07 SET TZ=MST07MDT
USA Central Time SET TZ=CST06 SET TZ=CST06CDT
USA Eastern Time SET TZ=EST05 SET TZ=EST05EDT

Bratislava,
Czechoslovakia SET TZ=CET-1 SET TZ=CET-1EET
Sydney, Australia SET TZ=EST-10 SET TZ=EST-11
Perth,
Western Australia SET TZ=WST-8



Command Line Parameters


"/Q" (do not include "s) is an optional parameter. If present, Doorfix
will run in the QUIET mode. This means that NO screen output will be
done when DoorFix is in operation (unless a serious error occurred).
| Note that Unregistered versions still get a notice in both local and
| Remote locations even with Quiet mode on.

"/ND" is an optional Parameter. If present, DoorFix will NOT delete
the source Door.sys file as it normally does.

"/L" is an optional parameter. If present, DoorFix will keep a log
of what it does and when it ran. This switch has several options:

1. /L only to log to DOORFIX.LOG in the current directory.
2. /L with a Dos environment variable named Dfixlog will set the log
file to write to the COMPLETE file and pathname specified by this
variable. Wherever it points, DoorFix will write the log to.
(Environment variables are usually set using
SET DFIXLOG=
from the Autoexec.bat file. See Dos manual for more details.)
3. /L= Doorfix will keep a log to the filename
specified.


DoorFix Documentation Page 4

Command Line Parameters (cont.)


"/DB" is the debug mode. It will display much info about what the
program is doing. If you have a problem, use this option to compile a
good bug report or fix your problem. Use the >> option to
redirect the output to a file if you wish to send us info on bugs.

"/R=PROGRAM.EXE_1_5_3" or "/R==1_5_3" will allow you to shell to another
program from DoorFix and run this program w/ user-definable command line
parameters.
Examples: DOORFIX NEWWILD /R=PROGRAM.EXE_1_5_3
DOORFIX PROGRAM.EXE /R==1_5_3

Here is the table for what the above numbers stand for:
1 : User First Name 6 : ANSI Status (0=off,1=on)
2 : User Last Name 7 : User Record Number
3 : Time Left in Mins. 8 : User Password
4 : Baud Rate 9 : User Security Level
5 : Comm Port (1,2,etc...)

In the First Example, Doorfix would convert source file type to new format
of callinfo.bbs then would shell to run Program.exe with three command line
parameters-#s corresponding to those given above. Up to 9 may be entered
in 1_2_3,etc... fashion on the command line.

In the second Example, Doorfix would only read in the info, not converting
anything, and shell out to run Program.exe w/ same command line (note extra
"=" when ONLY shelling and that PROGRAM.EXE may be any valid complete or
partial path to a program to run).

|"/T=##" is an optional parameter. If used in conjunction with OPUS, and
| Systems using Dorinfo#.def, it will alter the Lastus##.dat or Dorinfo#.def
| file to Lastus00.dat to Lastus99.dat and Dorinfo0.def to Dorinfo9.def.
| If OPUS, DoorNew/DoorOld are called without /T, it defaults to Lastus01.dat,
| and Dorinfo1.def. Also when writing PCBoard 14.x files, the node number
| is set to. When reading PCBoard 14.x PCBoard.sys, the node number is
| ignored and it is up to the sysop to utilize the /T parameter as needed.

"LockedBPS" is another optional parameter. If present, DoorFix will
override the baud rate found in the Door.sys file and replace it with
the one you specify here. This comes in handy for those HST/HAYES, etc.
users who lock their baud rate/com port.

********

Special note about Locked Baud rate when using PCBoard 12.1 doors.
THEY WILL NOT (!!) work above 9600 BPS. The configuration does not allow
more than 4 characters to describe the baud rate. Guess what? 19200 has
more than 4 characters and hence will not work.

********

DoorFix Documentation Page 5

From a Batch File:


In most scenarios, DoorFix will be run from a batch file. We have
setup Errorlevels DoorFix will exit with upon encountering certain
processing errors. You can check these in your calling batch file.
DoorFix Will exit with the following Errorlevels:

Errorlevels Meaning

errorlevel 0 DoorFix ran successfully. No Errors encountered.
errorlevel 1 Source file for conversion not found.
errorlevel 2 DoorFix.Cfg not found.
errorlevel 3 Invalid Command Line.
errorlevel 4 Could not create file.
errorlevel 5 Error in calling routine for PCBoard. (Debugging)
errorlevel 6 Detect attempt to run PCBoard 12.1 at locked baud above 9600.
errorlevel 7 Unknown conversion source file type.
errorlevel 8 Improper usage of /T=## parameter. ## ranges from 00 to 99.
|errorlevel 8 Improper usage of /T=# parameter for Dorinfo#.def, range 0..9.
|errorlevel 9 DOS environment variable TZ not set.


Configuration File


Config File:

To create/modify your DoorFix.Cfg file, type DoorFix Install. Then do
as the prompts ask to update any existing config file, accept the defaults,
or change the displayed values to suit your needs. The Installation Screen
is Window/Menu driven with Context Sensitive Help available at any time by
entering F1 for help with the field the cursor is in or Control-H for help
on help and the Installation Screen itself.

| To create/modify the DoorFix Security Level Time Manager Values, type
| DoorFix Install. Then either hit PgUp/PgDn to modify values per security
| Level. Note that for Opus systems, the security levels predefined such
| as twit and asstsysop are remapped to "appropriate" values for other BBS
| types (SysOp security level for Opus is mapped to 255). From there you
| can enter values, move around using cursor keys, page around using PgUp/
| PgDn keys, assign values for ranges, and modify specific values.

| To modify a range of Security Levels, DoorFix assigns all sec levels
| less than the current one (where the cursor is) to the value you assign.
| You can select the SecLvl of 255 and enter a MaxTime for ALL levels by
| Assigning that value and all others will be defaulted.

| During operation, DoorFix will use the LOWER of the times allowed from
| the BBS source file and the value corresponding to the user's sec level
| the sysop has defined in the DoorFix Security Level Time Manager. This
| is to prevent users from using almost all their time downloading files
| and then playing doors beyond their allowed time. Please note that the
| Time Manager is not required for proper operation of DoorFix. It simply
| operates as before using the BBS data file information.

You must have a file called DoorFix.cfg present in the same directory as
DoorFix to create certain door support files. A sample DoorFix.cfg file has
been included. This file consists of:

Special Note on Registration :
Lines 1-3 are CaSe specific. If you have DoorFix registered with a parti-
cular BBS name, and SysOp's 1st and last names, then DoorFix.cfg MUST use
the same capitalization and spelling or the registration number will NOT
function, and your copy of DoorFix will revert to the Shareware version.


DoorFix Documentation Page 6

Line 1 - Board Name
Line 2 - Sysop First Name
Line 3 - Sysop Last Name
Line 4 - Registration Number or NONE
Line 5 - Path to Main BBS Directory
Line 6 - Path to BBS Gfiles Directory
Line 7 - DoorType - Either DOORSYS, DORINFO, NEWWILD, SPITFIRE, OLDWILD,
| 2AM, EAZIHOST, SOCRATES, MG, FORBES, WWIV, GENESIS, PCB12, PCB14,
| or OPUS. DOORSYS causes Dfix to convert from Door.sys, DORINFO will
| do the same for Dorinfo#.def, NEWWILD/OLDWILD cause Dfix to convert
| from Wildcat Callinfo.bbs 2.0+/1.13 respectively. SPITFIRE causes
| Dfix to convert from Sfdoors.dat. 2AM causes Dfix to convert from
| Jumper.dat. EAZIHOST causes Dfix to convert from System.hst.
| SOCRATES causes Dfix to convert from Exituser.soc. MG causes Dfix
| to use Milton Gameworks' Userinfo.txt file. FORBES causes Dfix to
| use B. H. Forbes' Userfile. WWIV causes Dfix to use Chain.txt.
| GENESIS causes Dfix to use Genesis Deluxe's Callinfo.bbs file.
| PCB12/PCB14 cause Dfix to use PCBoard's 12.x/14.x Pcboard.sys file.
| OPUS causes Dfix to use the Lastus##.dat created by OPUS CBCS 1.13.
Line 8 - Path to Output files to . All converted files will
be written to this directory. Enter NUL here if you wish files to
be output to the current directory.
Line 9 - Path to Input files. Same as above except this is an input path.
Line 10 - Default Quiet mode. Either TRUE or FALSE. If True Dfix will operate
in quiet mode every time it is run, otherwise it will display info.
The command line switch overrides this.
Line 11 - Attempt to Load DoorFix into EMS. Either TRUE or FALSE. This is a
new feature and allows for lower RAM requirements for DoorFix. If
you specify TRUE, then the Overlays inside the DoorFix.exe file
will attempt to load into EMS. In the event that insufficient EMS
is available, DFix will default to reading from disk when needed.
If you do not have EMS or do not wish to utilize this function,
then use FALSE and DoorFix will not attempt to load the overlays in
EMS.
Line 12 - Default Source File Deletion. Either TRUE or FALSE. This is a new
addition to the configuration file since the DoorFix command line
was becoming too cluttered as well as User requests wanting to be
be able to always keep the source door file. If you do not want
to keep the file, enter TRUE. Otherwise, put FALSE here.
Line 13 - Com Port # (1-4)

This config file may now have comments to the right and below the 13 lines
of data. Anything right of the ';' comment character will be ignored. After
the first 13 lines of the file, you may enter as many lines of comments as you
wish. See example Cfg file for additional information.


DoorFix Documentation Page 7

Help


DoorFix has a few help screens which can be accessed via the ? command line
parameter or just running DoorFix w/o any command line parameters.

DoorFix can now automate the installation process for you. To implement
this function, type "DoorFix Install" at the Dos prompt. Then you
are able to modify/create a DoorFix.cfg file that will suit your needs by
very good config file editor with built-in help menus.

The DoorFix Help screen has been revamped. You can hit the key to
exit from the help screen and you can continuously go through the help
pages with either the PgUp/PgDn and the Up/Down arrow keys from both
the keypad and, for extended keyboards, the separate arrow keys.

More pages have been added as well as hopefully made them easier to read
and assist in quickly setting DoorFix parameters without need for reading
this document repeatedly.








Disclaimer


This program is guaranteed to do absolutely nothing except take up
disk space. Use it at your own risk. We don't ask anything for this
program except that you enjoy it. Anyway, if it breaks- don't ask us
to fix it! If you can't agree to these simple terms - do NOT use this
program and DELETE it immediately! Permission is granted to rearchive
this program and reproduce it in any manner provided all the files
listed in the beginning of this file are included.












DoorFix Documentation Page 8


Credits/Bug Reports


If you find any bugs, want another door format added, or have
suggestions on how to improve DoorFix, please let us know about them.
Also, we will be glad to help out with any problems you may have in
setting it up. We may be reached at the following BBS numbers, through
any of the Tag related echoes, or mail on any of the Tag Alpha boards.

Boards to call for support/New Versions:

Name | BBS Number | Fidonet Node # | Desc

Just For Fun BBS 804-793-6094 1:264/610 Development Site
The Hugman's BBS 804-793-0950 1:264/613 Development Site

It has been suggested that we setup an echo for DoorFix support.
If we receive enough support/replies from you, we will setup an echo.
If you desire this, please let us know, that's the only way you'll ever
get it!

Here we give credit where credit is due:

Borland International, for providing Turbo Pascal (r) 5.5.
Robert Jourdain, for Turbo Pascal Express, Revised.
TurboPower Software, for Turbo Professional 5.0.
Michael D. Weaver, Text File door conversion "technique".
Tom Kashuba, Help with OPUS CBCS 1.13.
Mike J., Author of Socrates BBS.
The QuickBBS Group, Authors of QBBS.
ProKIT Developers, for PCBoard structures.
2AM Associates, Authors of 2AM-BBS
SandSoft Software, Authors of EaziHost
|The T.A.G. Team for inspiring the entire process indirectly.

Lastly, we desperately need more up-to-date BBS interface structures
if we are to be able to support more of you, so please send them via
netmail to either Development Site.

Do not feel left out if your BBS type isn't listed or supported, get
involved and send us your structure(s) and we will happily add support
for you. Also, if you are in need of a reverse utility (i.e. one that
doesn't already start with one that is allowed as an input and produces
something that you have structures for), send us the structures and we'll
add it to DoorFix and also provide you with your own personalized utility.

Eric Harvey - and - Donald Huggins
Co-Authors of DoorFix