DOS doors (PBLegacy)
- A DOS door block
- Tips

DOS doors (PBLegacy)

16-bit DOS door games cannot run on 64-bit Windows by themselves. PBLegacy bridges them: it starts the door inside DOSBox-X, writes the drop files the door expects, and passes the caller's connection through.

You need DOSBox-X installed on the board's computer. Each DOS door gets a block in DOORS.PRO (edit it in Network > Door Configuration) and a menu item that runs it, just as for a native door.

A DOS door block

door TW2002
   doorexe     TW2002.EXE TWNODE=%NODE%
   doordir     C:\PBDATA\DOORS\TW2002
   dosbox      C:\DOSBox-X\dosbox-x.exe
   fossil      path F:\ADF;ADFCOM1.BAT
   fossildir   C:\PBDATA\DOORS\FOSSIL
   timelimit   60
   nodedir     yes
enddoor

Setting	Meaning
`doorexe`	The door's program and its arguments. `%NODE%` is the node number.
`doordir`	The door's folder.
`dosbox`	Full path of the DOSBox-X program.
`fossil`, `fossildir`	The FOSSIL driver the door needs, and its folder.
`timelimit`	Minutes allowed.
`nodedir yes`	Give each node its own working folder under `NODEDIR\NODE<n>`.

If PBLegacy is not in the same folder as ProBoard.exe, add a global pblegacy line with its path at the top of DOORS.PRO.

Tips

Give every door its own folder, and keep its shared game data there.
If a DOS door has a Windows version, prefer the native door: it is faster and simpler (see Native Windows doors).
Use a separate DOSBox-X configuration only if a door needs special memory or video settings.

This page will grow as more DOS doors are tested with PBLegacy.

Table of Contents

DOS doors (PBLegacy)

A DOS door block

Tips