fsxNet Wiki

BBS Development & Resources

User Tools

Site Tools


doors:dropfiles

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
doors:dropfiles [2017/04/21 20:02]
xqtr
doors:dropfiles [2022/11/11 03:38] (current)
avon
Line 1: Line 1:
-====== Drop Files ====== 
  
-A drop file is a data file generated by the BBS before executing an external program.  ​The drop file contains information about the user and his/her connection, such as the serial port number and security level.  ​The door program will read the drop file and act accordingly (e.gsending output to the correct serial port).  ​In some cases the door will modify the drop file as a means of passing changes back to the BBS.  ​This mechanism allows a door to be used with any BBS software as long as the drop file is generated correctly.+  * [[doors:​dropfiles:​doorfilesr|DOORFILE.SR]] 
 +  * [[doors:​dropfiles:​doorinfoxdef|DORINFOx.DEF]] 
 +  * [[doors:​dropfiles:​exitinfobbs|EXITINFO.BBS]] 
 +  * [[doors:​dropfiles:​pcboardsys|PCBOARD.SYS]] 
 +  * [[[[doors:​dropfiles:​sfdoorsdat|SFDOORS.DAT]] 
 +  * [[doors:​dropfiles:​userssys|USERS.SYS]] 
 +  * [[doors:​dropfiles:​utidoortxt|UTIDOOR.TXT]]
  
  
-===== File Formats ===== 
  
-There are a variety of different drop file formats. ​ The DOOR.SYS format had widespread support among BBS systems ​and door games under MS-DOS systems.  ​Modern systems prefer DOOR32.SYS because the format is simpler and provides information about Telnet connections (something not anticipated when DOOR.SYS was invented).+xxx 
 + 
 +  * DORINFO1.DEF 
 +RBBS-PC, early PCBoard, ​and early QuickBBS software used this format exclusively. This file is 13 lines long. The name os the dropfile never changed, even if it was used in multi-node environments. 
 + 
 +  * [[doors:​dropfiles:​doorinfoxdef|DORINFO#​.DEF]] 
 +Used by v2.0 and later versions of QuickBBS and RemoteAccess,​ this allowed slightly more flexibility for up to 36 nodes. Node 1 through 9 would produce DORINFO1.DEF to DORINFO9.DEF,​ Node 10 produced DORINFO0.DEF,​ and Nodes 11 to 36 would use alphabetic designation from DORINFOA.DEF to DORINFOZ.DEF. The format is exactly the same as DORINFO1.DEF. 
 + 
 +  * [[doors:​dropfiles:​doorfilesr|DOORFILE.SR]] 
 +To be defined.
  
-  * [[doors:​dropfiles:​callinfobbs|CALLINFO.BBS]] 
-  * [[resources:​dropfileformats:​chaintxt|CHAIN.TXT]] 
-  * [[doors:​dropfiles:​doorsys|DOOR.SYS]] 
-  * [[doors:​dropfiles:​door32sys|DOOR32.SYS]] 
-  * DOORFILE.SR 
-  * DORINFOx.DEF 
-  * EXITINFO.BBS 
-  * PCBOARD.SYS 
   * SFDOORS.DAT   * SFDOORS.DAT
-  ​TRIBBS.SYS +Created by Mike Woltz, the author of Spitfire BBS. 
-  * USERS.SYS + 
-  * UTIDOOR.TXT+  ​[[doors:​dropfiles:​pcboardsys|PCBOARD.SYS]] 
 +This is a binary dropfile, was created by PCBoard and used also by FeatherNet Pro and others. 
 + 
 +  * JUMPER.DAT 
 +An uncommon format, created by 2AM-BBS. 
 + 
 +  * USERINFO.DAT 
 +Wilcat! BBS 3.0 and above create this file for addition information not supported by other dropfiles. 
 + 
 +  * EXITINFO.BBS 
 +This was invented by QuickBBS authors, to provide additional information from the BBS to the external application,​ and if existed upon existing the external application,​ the variables would override the existing values in the BBS. Allowing the external application to push changes to the BBS, like additional time left because the user earned it or has withdrew time from a timebank.
  
-==== Sources ==== 
  
-  * http://​thoughtproject.com/​libraries/​bbs/​Sysop/​Doors/​DropFiles/​index.htm 
doors/dropfiles.1492804923.txt.gz · Last modified: 2018/03/29 01:58 (external edit)