fsxNet Wiki

BBS Development & Resources

User Tools

Site Tools


dropfiles

BBS Dropfile

A dropfile in a BBS (Bulletin Board System) is an interface between the BBS software and an external application. It is used to pass current/active data from the BBS to the external application, this allows the external applications to be compatible with multiple BBS software packages.

List

Created by Maarten Bekers, author of EleBBS, and James Coyle, author of Mystic BBS. This dropfile is able to handle TELNET connections created by newer BBS software (EleBBS, Mystic BBS, Synchronet, and PRoBBS) and certain old BBS applications (mostly OS/2 native: Maximus, Telegard, AdeptXBBS).

This format originated in the GAP BBS application and quickly became a de facto standard. The original DOOR.SYS contained 52 lines. Nearly all modern BBS applications support this format.

Created by Mark Goodwin, original author of the TriBBS Bulletin Board System.

  • 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.

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.

This was created by Wayne Bell, the author of WWIV BBS, and contains 32 lines.

To be defined.

To be defined.

  • SFDOORS.DAT

Created by Mike Woltz, the author of Spitfire BBS.

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.

dropfiles.txt · Last modified: 2019/11/16 17:52 by ozz