Simtel MSDOS 1992 June

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

/ Simtel MSDOS 1992 June / SIMTEL_0692.cdr / msdos / opus / drlk223a.arc / DRLINK.DOC < prev next >

Wrap

Text File | 1989-12-14 | 34.4 KB | 704 lines

DRLINK v2.21 OPUS 1.10 G6 and OPUS 1.03 DOORS Linking Utility July 31, 1989 (C) Copyright 1988, 1989, Chris A. Holten COWBOY Country USA! 4010 Swanton Street Casper Wyoming, 82609 Voice (307) 235-4728 All rights reserved. This is free for the asking, but is *NOT* Public Domain Software. If you paid money for this program, you got screwed. If you sell this program you are in violation of the law. If you are caught selling it you may even get your ass kicked by one tough Cowboy. SPECIAL THANKS: -------------- A -very- special thanks to the people that have helped so much in creating in DRLINK v 2.21. There have been many good Opus Sysops that have given some great ideas, ferreted out bugs, sent file structures and DOORS to test with, and at times put thier BBS's through some pretty crazy things helping me develop DRLINK. These folks did more to make DRLINK work than I did and never flamed me when it crashed thier systems: 303/2 Craig Edwards, Opus 1.03, XT clone, -wierd- DoubleDOS setup 303/5 Thomas Lange, Opus 1.03, Tandy 1000, DoubleDOS 101/200 Cheryl Buzzell, Opus 1.10, 386 DV, Dual Standard HST, 38400 baud 106/131 Danny Wofford, Opus 1.10, AT, HST, 19200 baud 114/7 Michael Malone, Opus 1.03, The only normal one of the bunch... 302/1 Dave Bell, Opus 1.03, AT clone, HST, Flatland cyberpunk, FOSSIL expert NOTICE: ------- This program is released as is only to be used at your own risk. There are no warranties, either expressed or implied that this software, you or anyone in your supervision, sight or hailing will even come close having this software perform in the manner described below. You are only liscensed to use this software if you choose to use it at your own risk. Any damage you may or may not incur with the use of this program is entirly your fault if you try running this software on a computer. Chris Holten, and all users of C's Doghouse will not be responsible for this software working on any other system than the single (1) Epson Equity III AT computer sitting in C's basement at 4010 Swanton ST, Casper WY, 82609. This Software is free for the asking, but DRLINK is *NOT* released into the public domain. The Liscense that you agree to by using DRLINK, is that whatever use you put it to, I ask that you not attempt to make money off it. This is for fun and to help other folks, including BBS Sysops to have fun with. If you can make use of DRLINK please do. Any time you want to show your appreciation for the time and effort I and many others have put into developing drlink, you can do it by sending DOORS to test with or -accurate- BBS file structure documention. I would -greatly- appreciate it. The biggest hassle and expense we have had in developing DRLINK is running down good BBS file structures and DOORS to test it with. Of course, if you must give money, then give it to the OPUS Shanti project. I have put DOORlink together with the goal of providing the OPUS community a utility that will allow them to run most any other BBS DOOR or other external program they want to. It can be run in command line mode, writing the BBS subsystem files that the single DOOR requires. When that one door is completed, exit back to Opus to a .BBS file, or with DRLINK MENU, up to 100 external programs can be set up for a user to choose from. After each DOOR or other external program is completed, DRLINK will be returned to, until the user either runs out of time, or chooses to exit back to OPUS. Both 40 and 80 column mode and ANSI/Non-ANSI graphics are automatically supported with the DRLINK MENU. The amount of time in each individual DOOR and security level for access can be set up when using the DRLINK MENU function. If a user is in NON-ANSI mode, none of the DRLINK screens will contain ASCII characters over 127. In ANSI mode, IBM Graphics are displayed in the opening screen. In menu mode, and with the proper modem (Works with a CPI locked at 38400 baud) it is possible, by setting up LOCKBAUD and MAXDOORBAUD in the DRLINK.CTL file, to run doors that normally won't run at 19200 or 38400 baud. It only works with modems that are capable of having the input baud rate changed while maintaining a constant CONNECT baud rate. The DOOR will run at the CONNECT baud rate, and when the DRLINK MENU is returned to, DRLINK will reset the baud back to the LOCKBAUD rate. See the sample DRLINK.CTL file for a further explanation of making this work. If the MENU system is run from the Opus OUTSIDE EXIT <errorlevel> set up, Drlink will keep track of the time the user was in the external programs, and correct his remaining time in Opus by both/either using the -T switch to pass remaining time back to OPUS or by having DRLINK update the USER.BBS file (Time on today). By exiting OPUS to run DRLINK MENU /B, approximately 140k of memory can be saved as compared to running External programs from the usual OPUS shell via a .BBS file and ^OCexternal.bat command. DRLINK seems to work just fine with PCBoard v 11.8a, 12.1, 14.0, Wildcat, and GAP doors and -most- RBBS doors. I have stuck in routines to write MGW, FORBES, and GT doors. These file structures are very simple, and should work, but due to the paucity of DOOR programs for these lessor known communications packages, those routines haven't been tested <At all>. Most likely you will find some doors that just aren't going to work with DRLINK. If so, help us to fix it by sending the DOOR or decent documention on what the BBS subsystem files is supposed to be that the DOOR is using. This is what drlink does (or attempts to do anyway): 1. It reads the Lastusxx.bbs file, takes most all of the information out of that file (Graphics, Monitor width, length, more?, time-parameters etc), combines that information with the information in the DRLINK.CTL file to accurately pass on user parameters and the remaining time the User has on the System (including time till events that you want to force humans off the system with). It will also allow you to adjust a users DOOR time based on his uploads to your system. I recommend that you set both the privel level times and event times (Only the ones you want to force the user off the system with) to the *exact* times you set them up to in the OPUS.CTL and SCHED.BBS files. You can, however, make them something different if you choose to. You -must- have a DRLINK.CTL file if you are using with a OPUS 1.03 system. Since OPUS 1.10 passes the remaining time to the Lastusex.bbs file (1.03 doesn't) then use of the DRLINK.CTL file is optional with those lucky enough to have OPUS 1.10 systems. 2. Writes the required data files for whatever type DOOR you select. 3. If it is a QuickBBS type Door that requires a QuickBBS command line and you use the /E switch, it will write a spawndor.bat that will run whatever QuickBBS Doors you should want to run. The spawndor.bat file will be written to change drives and directories as necessary to run the door, and then allow a Sysop to add up to 12 command lines to finish the Spawndor.bat file to properly return to OPUS! (Don't forget to add a line in DRLINK.CTL to CD \OPUS (Or whatever the OPUS Default directory is). The command EXIT is automatically appended to the SPAWNDOR.bat file if not run as an outside exit from OPUS and if run with the /boutside.bat file, The last statement in the SPAWNDOR.BAT file will be the name of the Outside.bat file. 4. Automatically supports Baud Rates as high as 38,400 (even with systems running a locked baud, commands to tell DRLINK to lock baud are no longer necessary) or the maximum Door Subsystem is capable of running, and still provide automatic detection of the local mode and write the correct parameters for operation of the DOOR locally. Since OPUS 1.03 sticks a 9600 baud rate in the lastusex.bbs file for local mode, it is necessary to check for carrier to determine if the caller is local or online. Should a 9600 baud caller hangup at just -exactly- the right time, it's entirely possible that DRLINK will assume a local mode and write the DOORS subsystem files for local mode. This can -only- occur with OPUS v1.03 and at a 9600 baud rate. If you lock the baud rate at 19200 for your 9600 baud modem it will be no problem. NOTE: to automatically detect the comport baud rate, DRLINK reads the MSB and LSB values of the selected comport and computes the required baud rate. If the external program you are running screws with those values on exit, then DOORLINK may not compute the baud rate correctly (causing wierd things to happen). If you find an external program that screws up the comport baud rate (MSB and LSB values) on exit, then you won't be able to run that program using drlink. Drlink monitors Carrier, and if the Carrier is lost, will drop DTR for security, and exit with an errorlevel of 1. ERROR Messages: If there is an error in the finding or writing any of the various and sundry subsystem files DRLINK uses, you will get a beep and an error message attempting to help you isolate the problem. DRLINK will then exit with an errorlevel of at least 1. If you have DLOG set up in your .CTL file, then the error exit and possible cause of the error will be noted in the DRLINK.LOG. Drlink will also exit with errorlevel 1 if the user has 0 time or if carrier is dropped. If you have DLOG set up in your DRLINK.CTL file, then the error exit and possible cause of the error will be noted in the DRLINK.LOG. If you are running from command line mode, it would be a good idea to trap this errorlevel in your batch file, and exit with out running the door. In MENU mode, DRLINK writes the SPAWNDOR.BAT file to trap errorlevels and exit back to the BBS. IE: The batch file I run Baystreet Bulls in command line mode: echo off drlink /lE:\opus\lastus01.bbs /pe:\doors\motu\ /Cdrlink.prm /U if errorlevel 1 goto QUIT cd\doors\motu baybull bsb.cfg :QUIT cd \opus EXIT If you are running from MENU mode, DRLINK will trap the Errorlevel in the Spawndor.bat file and return back to OPUS in what ever manner you have told it to your Spawndor setup in the DRLINK.CTL file. DRLINK Command line words (Case insensitive): MENU Will have Drlink present the User a menu selection of the doors available to him, at his security level. MENU will also allow you to set the maximum time allowed in each individual DOOR. A spawndor.bat file is written by DRLINK with the proper commands to execute the DOOR. After each DOOR is completed the Spawndor.bat file will return to DRLINK. When the user runs out of time or chooses to exit DRLINK, he will be returned back to the BBS in what ever manner you have set up in the spawndor commands in the DRLINK.CTL file. If you choose to run DRLINK as an Outside Exit < errorlevel > function of OPUS, using the /BBATNAME.BAT command, DRLINK will pass the users remaining time and the baud rate back to the BATNAME.BAT file. It is up to you to set up your opus batch file to trap the -Bbaudrate (%1) and -Ttimeleft (%2) on your OPUS commandline. (See the /B command below). When You run DRLINK MENU you -must- set your batch file up to invoke the SPAWNDOR.BAT file that DRLINK writes. IE DRLINK MENU /U /lc:\opus\lastuse1.bbs /cc:\opus\drlink.prm IF ERRORLEVEL 1 GOTO QUIT SPAWNDOR.BAT :QUIT EXIT Would invoke DRLINK. After DRLINK is exited, if no errors are encountered, the SPAWNDOR.BAT file that DRLINK writes will be executed. The spawndor.bat file will contain the commands necessary to execute the program the user has chosen, and return to DRLINK with the same command line that it was originally invoked with. Sounds complicated, but run it once and type out the SPAWNDOR.BAT file it writes to see how simple it really is. The F8 key will return the user back to the bbs in MENU mode. The F9 key will toggle QUIET (Snoop) in MENU mode. The F10 key will drop to DOS in MENU mode. If you have DLOG uncommented in the DRLINK.CTL file, when in MENU mode, DRLINK will keep a log of users, errors, and the external programs they executed while in DRLINK. UPDATEUSER This command should -ONLY- be used when you are exiting Opus via the Outside Exit < errorlevel > setup in the OPUS.CTL file. When used in conjunction with the MENU and /B command, the user's record (and just that one record) will be updated in the USER.BBS file with the amount of time the user was outside + his previous time in OPUS. That way when OPUS is ruturned to via the OPUS BBS %1 set in your batch file that is used to return the user to opus, all time parameters will be correct (not necessary to use %2 (-Ttimeleft)). If you screw up and run the UPDATEUSER /Boutside.bat command when shelling from OPUS you will munge your USER.BBS file bigger than hell. If you don't understand the difference between and Outside Exit <errorlevel> command and a shell via an embedded command or the Outside RUN command, then don't use the UPDATEUSER feature. Garanteed -bad- results if run from a shell (even hitting the ESC key at the prompt and running a batch file with the UPDATEUSER could munge the USER.BBS file.) Neat feature, and quite handy, and if used correctly, reasonbly safe, but you've been warned.... HELP Will have drlink give a brief listing of the command line switches. QUIET Will prevent DRLINK from writing to the local screen (Snoop OFF) and with PCBOARD and GAP (Generic) doors, write the subsystem file with the local screen off flag. The door has to be capable of reading this flag and using it to shut the local screen writes and beeping off. System X-10 Canada doors and Camelot doors (PCBoard) correctly go into QUIET mode (keep the screen blank). DRLINK QUIET (Same as SNOOP OFF in OPUS) Will prevent DRLINK from outputting to local screen. In MENU mode F9 will toggle the QUIET on and off (to snoop or not to snoop...that is the question..). COM2 The default comport for DRLINK is Com1. If you put com2 anywhere in the command line, com2 will be used. This overides whatever comport you use in the DRLINK.CTL file. If you are running OPUS 1.10 and choose -not- to use the DRLINK.CTL file, and are running on COM2, you -must- use this switch. COM1 is the default with out a control file. You can overide whatever Comport is in the DRLINK.CTL file by putting COM1 or COM2 on the command line. (Making it possible to run from two comports with the same .CTL file). DRLINK COM2 Will cause DRLINK to use COM2 reguardless of what's in the DRLINK.CTL file. NOTIMER [Command line mode only] DRLINK pauses for 2 seconds before exiting back to the batch file. That is in order for the user to have enough time to read his remaining time and upload adjustment factor. If you have a slow computer/harddisk then you can put NOTIMER on the command line to eliminate the 2 second pause. DRLINK Command Line Switches (Must be preceded with / symbol -- You can write mutiple BBS subsystems in different directories): /B [Use only with MENU combined with Outside EXIT XX in the OPUS.CTL file] This tells DRLINK to pass time and baud rate parameters back to OPUS via the Opus -B and -T switches. You designate the outside.bat file that you want the parameters passed back to by using the command line: /Bc:\opus\Outside.bat Doorlink will then write a spawndor.bat file that will invoke your Outside.bat file with the -Bbaud (%1) and -Ttimeleft (%2) passed back to it. IE: In your RUNOPUS.BAT file :START OPUS BBS IF ERRORLEVEL 99 goto DRLINK other junk :DRLINK DRLINK /l\opus\lastus01.bbs menu /U /boutside.bat IF ERRORLEVEL 1 GOTO START SPAWNDOR.BAT <---Always have a SPAWNDOR.BAT command with MENU When the user selects O)utside (and you have it set up in your BBS.CTL file to cause Opus to exit with an Errorlevel of 99) then DRLINK will be executed. After the user makes a menu selection and drlink is exited, the SPAWNDOR.BAT file that DRLINK writes will be executed. The when the user chooses to return to the bulletin board (or runs out of time) the SPAWNDOR.BAT file will invoke your Outside.BAT file with: c:\opus\Outside.bat -Bbaud -TTimeLeft. If, in your Outside.bat file you have: rem Ron Bemis BAUD program. If carrier, errorlevel is higher than 0 Baud.com If errorlevel 1 goto Board rem if no carrier run your regular runopus.bat file runopus :Board Opus Outside.prm %1 %2 -nf if errorlevel 99 goto DRLINK REM If a lower errorlevel run the regular RUNOPUS.BAT file runopus :DRLINK DRLINK /l\opus\lastus01.bbs menu /U /boutside.bat spawndor.bat REM just for safety runopus Then opus will be invoked with: Opus Outside.prm -Bbaud -Ttimeleft -nf It's not necessary to use the %2 (Remaining time parameter) if you invoke drlink /Boutside.bat UPDATEUSER and have DRLINK update the user.bbs file with time used in O)utside. With OPUS 1.10, you don't need to mess with time at all. 1.10 keeps track of Outside exit time on it's own (the UPDATEUSER will actually mess things up with 1.10). Once a user is in the Outside.bat file, he will stay there until he logs off and OPUS exits. When he exits OPUS, the normal RUNOPUS.BAT file will be executed and wait for another caller. You can set up your outside.bat file to do anything you want it to do, same as having a second RUNOPUS.BAT file to mess with. (Start simple though.) I use Outside as my .PRM file in for the Outside.bat. It does not show the user the LOGO.BBS, Welcome.BBS and Bulletin.BBS files. It is also set up to exit after a caller with an errorlevel of 5. All other parameters and errorlevels are set up identically to my normal BBS.PRM file. That way any errorlevels that the user exits with will be passed back to the runopus.bat file when the user exits OPUS. If you want to you can trap those errorlevels in your RUNOPUS.BAT file and do what ever processing is necessary. /C [Use with both MENU and Command line mode] Tells Drlink which parameter file to read. If left out, it will attempt to read DRLINK.PRM in the default directory. This switch is provided in case you have to do something fancy and need more than just one drlink .prm file or don't want to have your configuration files in the OPUS default directory. If you are running OPUS 1.03, You -must- have a DRLINK.PRM file or DRLINK will give you an error message to that effect, and won't write the subsystem files. If you are running OPUS 1.10, the DRLINK.PRM file is optional in command line mode unless you want to adjust a users time for uploads or don't mind being called "The Sysop" and having your board name as "The BBS". 1.10 Sysops running DRLINK MENU -must- have compiled the drlink.ctl file into a .prm file and use the /C command. /Cc:\opus\drlink.prm or /cf:\contrl\drlinkDD.prm The documentation for setting up the DRLINK.CTL file and compiling it with DRLK_CTL is contained in the sample DRLINK.CTL file. Don't forget to compile the .CTL file into a .PRM file before running DRLINK. /l [MENU and command line mode] Command line switch telling DRLINK where to find the OPUS lastusxx.bbs. If you leave this switch off it will default to lastuser.bbs in the default directory. /Lc:\opus\lastuse1.bbs Tells DRLINK to look for the Lastuser file in c:\opus. The most common problem DRLINK users seem to have is putting the /l in front of the lastuser.bbs. DRLINK goes off into gagaland if the /l isn't there. IE: /lastuse1.bbs --- gagaland /llastuse1.bbs --- drlink is happy as a bug in a rug. /t [Menu and Command line mode] Set time to a maximum limit. This will allow you to limit the users time to a maximum you want to allow him in the door. If the users remaining time on the system is less than the maximum time you want to allow in the Door, then the remaining time on the system will be passed to the door. If you adjust a users time for uploads (/U), then the adjustment ratio will be taken after the time is limited with the /T command. (IE, if the users ratio is .6 and you use /T10, then the user will get .6*10 or 6 minutes in the DOOR. /t10 Will set the maximum time in the door to 10 minutes. /u [Menu and Command line mode] Factor DOORS time based on Quantity of Uploads. You must have the UL time ratios set up in the DRLINK.CTL file if you use this switch. If you use this switch in combination with the /T switch, the ratio you set up in the DRLINK.CTL file will also ratio the time you allow in the door with the /t switch. IE, If you set an UL ratio of .7 up, and use a /T20 then the user will recieve .7*20 or about 14 minutes maximum time in the door. The following subsystem commands can be used in commandline mode. If you are running in MENU mode, then set up these commands in the DRLINK.CTL file under the Subsystem command catagory (Setup for MENU mode is documented in the sample DRLINK.CTL file.) PCBOARD versions 14.0, 12.1 and 11.8a -- DRLINK will write the PCBOARD.SYS, USERS, and PCBOARD.DAT files in the designated directory. The PCBOARD.SYS file is similiar to the OPUS Lastusxx.bbs file, the USERS file will be a 2 record USERS file that the first record will be the Sysop's and the Second Record will be the users. The PCBOARD.DAT file is akin to the OPUS.PRM file (But not hardly). Most PCBoard DOORS only use the PCBOARD.SYS file, however a rare few use the USERS file, and some read the PCBOARD.DAT file to get the version out of it. Since you could be set up with DOORS that need these files and you might have doors for all three versions in the same directory, I set up DRLINK to write each of these files each time. Lots less hassle than screwing around with more command line switches, and it only takes a silly millisecond longer. /p PCBoard doors v 12.1 switch. It should be followed by the full pathname that you want the PCB Door to be run from. Since the PCB v 12.1 file structure only allows the passing of a 4 digit baud rate, unless the DOOR author converts a 1920 baud rate to 19200 and an 3840 baud rate to 38400 baud, you won't be able to run v 12.1 doors over 9600 baud. System X-10 Canada Doors and Camelot Doors were tested at 19200 baud. None would run at 38400 baud. /Pe:\doors\motu Will tell DRLINK to Write the v12.1 PCBOARD.SYS PCBOARD.DAT and USERS files in the e:\doors\motu directory. You must then change to that directory in your batch file and run MOTU. Example Batch file (MOTU.BAT). DRLINK /lc:\opus\lastuse1.bbs /pe:\doors\motu if errorlevel 1 goto QUIT cd \doors\motu motu cd \opus :QUIT EXIT <---Don't forget EXIT or you will cause OPUS to make those ridiculous high messages numbers. /4 PCBoard v 14.0 switch. /4 will work in the same manner as the /p, except that it will write the PCB v14.0 DOORS sybsystem (PCBOARD.SYS, PCBOARD.DAT, USERS) files in the designated directory. Passes a baud rate of up to 38,400. (Turbochess 3.0, Othello and Barons are the only PCB v 14 doors we could get to run at 38400 baud. We tested a few DORPCH35 doors, and none would work at 38400 baud. No doubt somewhere there are DORPCH35 doors working just fine at 38400 baud, but we couldn't find any. The few DORPCH35 doors we did test worked just fine at lower baud rates though. /8 PCBoard v 11.8a switch. /8. Same as /p and /4 but files for PCB v 11.8a PCBOARD.SYS, PCBOARD.DAT and USERS files are written in the designated directory. The file structure only allows for the passing of a 4 digit baud rate, so unless the DOOR author converts a 1920 baud rate to 19200 baud or an 3840 baud rate to 38400 baud, you are stuck at 9600 baud with PCB 11.8 doors. /r RBBS doors switch. it should be followed by the full pathname that you keep your RBBS door in: (Passes up to 38,400 baud but we haven't found an RBBS door that runs that fast.) DRLINK /re:\doors\motu\ <--Trailing Backslashes are not required but shouldn't screw drlink up either. Will write the necessary RBBS files (RBBS-PC.DEF, MESSAGES and DORINFO1.DEF) to run RBBS doors with. In this example the files would be written to drive e:, directory \doors\motu. Use a batch similiar to the Example for the PCBoard /p switch. The following Switches work in the same manner as RBBS and PCBoard Switches. (Including the directory name you want to write the DOOR configuration files to.) /W WILDCAT -- /Wc:\doors\wildcat (Maximum of 9600 baud --Maybe higher) /G GAP -- /Gc:\doors\gap\ (Maximum of 38,400 baud --Maybe) /M MGW -- /M\doors\mgw (Maximum of 38,400 baud) /F FORBES -- /F\doors\forbes (Maximum of 38,400 baud) /X GT -- /X <--- without a drive or pathname files are written in default directory for any of the command line switches to call up the DOOR subsystem. /O OPUS v1.03. /Oc:\opus\ Writes an OPUS v 1.03 LASTUSER.BBS file in the default directory. The Baud rate of the Comport instead of the CONNECT Baud Rate is put into the created lastuser.bbs file. This might be handy if you run a locked baud rate. You can use /o to convert an OPUS 1.10 LASTUSXX.BBS file to an OPUS 1.03 LASTUSER.BBS file or with 1.03 you can use the /o to make a lastuser.bbs file that has the locked baud rate in it. Baud Rates higher than 19200 cannot be passed to the LASTUSER.BBS file. Some utilities that use the FOSSIL -may- leave the COMPORT in better shape when they exit if they are told to use the locked baud rate via the converted LASTUSER.BBS file. If you are having trouble running OPX or some other opus utility from drlink, try running the utility with the converted LASTUSER.BBS file. No garantees, but it -might- work. QUICKBBS doors: /Q QuickBBS doors Switch. It should be followed by the full pathname that you want to Execute your QuickBBS doors from. (Maximum of 38,400 baud) DRLINK /qc:\doors\tw1000 This will write the DORINFO1.DEF file in c:\doors\tw1000 directory. NOTE: DRLINK will also use the pathname to obtain the Drive and Directory information it needs to write the SPAWNDOR.BAT file. The SPAWNDOR.BAT file is necessary for running QuickBBS style doors that require a commandline. Be *SURE* to set up the ending batch file commands you need to have the spawndor.bat file allow a correct return to OPUS in the DRLINK.CTL file. /Efilename Tells Drlink where and what the filename of the QuickBBS Door .exe file is. (This Example is for TW 9.02, written -SPECIFICALLY- for QuickBBS. -- TW 9.03 uses the RBBS style DORINFO1.DEF and if you are running TW 9.03, the /E switch is -not- to be used.) /etwq.exe or something like: /ec:\doors\bin\twq.exe ^ if the Doors .EXE file is kept in a different directory from the directory you want to execute the QuickBBS door from. To run the QuickBBS door, DRLINK will take the information provided by the /Q and /E switches write a SPAWNDOR.BAT file. That spawndor.bat file will contain the following: c: <----This is based on whatever drive and directory cd \doors\tw1000 <----you put with the /Q switch TWQ.EXE baud First Last timeleft graphics <--From /E switch + what ever ending spawndor.bat commands you set up in the DRLINK.CTL file. They could be something like: cd \opus capture on DRLINK automatically adds the EXIT command as the last statement in the batch file. Hence DRLINK would write the Spawndor.bat file as follows: c: cd \doors\tw1000 twq.exe baudrate firstname lastname timeleft graphics cd \opus capture on exit Here is an example batch file (WARQBBS.BAT) that will fire up DRLINK and then invoke the SPAWNDOR.BAT file to run TW1000 (Verson 9.01 and 9.02 only!! --NOT-- 9.03 which needs no QuickBBS commandline): Drlink /lc:\opus\lastuse1.bbs /qc:\doors\tw1000\ /etwq.exe spawndor.bat Drlink will write the spawndor.bat file, and then your WAR.BAT file (Called from OPUS) will invoke it with the spawndor.bat command. ======================================================================== QuickBBS commandline door in MENU mode: If you are running in MENU mode and want to run a quickBBS door that -requires- the quickbbs command line, then you set the /E command up as the execute designator. IE in the MENU portion of the DRLINK.CTL file, you would have: MENU 6, /Qe:\doors\, /Ee:\doors\TWQ.EXE, TW v 9.01, 48, 30 END ========================================================================= If you use DRLINK with the /Q switch, but don't use the /E switch, DRLINK will write the DORINFO1.DEF file in the directory you indicate, but it will not write the SPAWNDOR.BAT file. This command is may be useful for running other door utilities that only require the DORINFO1.DEF file to get it's information (TradeWars v903). DOORlink Control File (Read the Sample DRLINK.CTL file for documention on correct set up also: NOTE! The DRLINK.CTL file -must- be compiled with DRLK_CTL.EXE into a .PRM file for DRLINK's use. You -MUST- have a compiled parameter file when running DRLINK with OPUS v 1.03 or with the MENU system with either OPUS 1.03 or OPUS 1.10. After preparing the drlink.ctl file, use DRLK_CTL to compile it. IE DRLK_CTL DRLINKDD.CTL Will compile the DRLINKDD.CTL file into a DRLINKDD.PRM file. You would then invoke drlink with the command DRLINK /Cdrlinkdd.PRM. As with DRLINK, the default .CTL file is DRLINK.CTL. If you execute DRLINK with no command line, DRLK_CTL will look for a DRLINK.CTL file to compile into a DRLINK.PRM file. KNOWN DRLINK PROBLEMS (That I can't/won't fix). Doorlink does not use the FOSSIL. It makes a vanilla DOS call to open the comport, but like many (most?) external programs, FOSSIL or no FOSSIL, some combinations of FOSSILS, DOS versions, and BIOS versions just cause external programs to go out into gaga land. If you have problems with DRLINK locking up, then try a different fossil. We have found that with an EPSON EQUIII bios 1.10 DRLINK will lock up tighter than a drum with OPUSCOMM 5.30. It works just fine with X00 v 1.10 (far and away the most reliable FOSSIL for OPUS) and BNU. On a Tandy 1000, DRLINK will lock up with BNU, but works just dandy with OPUSCOMM 5.30 and X00. No doubt there are more computer/dos/fossil combinations that just aren't going to get along with DRLINK. Hopefully you will find a FOSSIL that suits your needs, works with your modem and all your external programs. If all else fails try X00 v 1.08 or X00 v 1.10. No garantees, but X00 seems to do best on the widest variety of machine/sofware combinations. As a note, If you think the problem is in DRLINK, then just boot your computer up with out the FOSSIL anywhere in memory and run it. The odds are 999,999 in 1,000,000 that DRLINK will run fine on your IBM or clone computer. The problem is in the FOSSIL and the way Fossils dink up the comports with many clone computers BIOS <Sigh>. Please help me to make this OPUS utility better by giving me some feedback and help with with future revisions. Many Sysops feedback over this past year of developing DRLINK has really improved it over the original program. No way can I run down all the BBS subsystem file structures to program with or adaquately test it with all the various and sundry doors we are trying to get DRLINK to run on OPUS BBS's. I need your help, -especially- in running down well documented BBS subsystem file structures. (Some of mine are hacks, having good structure documentation from the original software authors of the various and sundry BBS's would make DRLINK work better). Chris Holten COWBOY Country USA! E-Mail -- FidoNet 303/2, 303/5 4010 Swanton ST. Casper Wyoming 82609 Voice (307) 234-4728