Differences

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

--- supported_drop_file_information [2023/07/18 01:32] – massacre
+++ supported_drop_file_information [2023/07/18 01:36] (current) – massacre
@@ Line 6: / Line 6: @@
 When configuring menu's for DOORS, you have parameters <command line> that need the full path and filename (.COM or .EXE extension included), and may contain some special codes.  These codes will (at run-time) be replaced by a value or a string.
-Special codes:
+  Special codes:
-  **D      Writes a full 52-line DOOR.SYS drop file to the current directory before shelling.
+    *D      Writes a full 52-line DOOR.SYS drop file to the current directory before shelling.
-  **E      Writes an RA 1.1x EXITINFO.BBS to the current directory before shelling and reads it back afterwards.  ProBoard creates an RA 2.xx by default so if you need the older EXITINFO.BBS format be sure to specify the *E Parameter.
+    *E      Writes an RA 1.1x EXITINFO.BBS to the current directory before shelling and reads it back afterwards.  ProBoard creates an RA 2.xx by default so if you need the older EXITINFO.BBS format be sure to specify the *E Parameter.
-  **M      ProBoard's start-up directory (including trailing '\')
+    *M      ProBoard's start-up directory (including trailing '\')
-  **P      Com-port used by ProBoard (1-8).
+    *P      Com-port used by ProBoard (1-8).
-  **0      (zero) ProBoard will write a DORINFO1.DEF instead of a  DORINFO<node>.DEF - great for running doors which require a DORINFO1.DEF file on a multi node ProBoard system.
+    *0      (zero) ProBoard will write a DORINFO1.DEF instead of a  DORINFO<node>.DEF - great for running doors which require a DORINFO1.DEF file on a multi node ProBoard system.
 ProBoard will soon support other Drop File formats like:
   PCBOARD.SYS
   DOOR32.SYS

ProBoard BBS Documentation

User Tools

Site Tools

Differences

Page Tools