Table of Contents

Before you install

Choose the right package

ProBoard v4 comes in two packages. Use the one that matches your copy of Windows:

The package is a zip file named like PBv4-20261102-x64.zip, with a SHA256SUMS.txt file beside it. To check that the download is intact, compare the zip's SHA-256 checksum with the line in that file. Do not mix the two kinds on one system: plug-ins (.P3X files) built for Win32 and for x64 are not interchangeable.

Add the download location for the packages here.

Visual C++ runtime

ProBoard's programs are built to run without extra Microsoft components. If a program does not start on a clean copy of Windows and the message mentions VCRUNTIME140.dll or MSVCP140.dll, install the Microsoft Visual C++ Redistributable (version 14, which covers Visual Studio 2017 through 2026) that matches your package:

Ports and firewall

PBDispatch listens on the ports for every service you turn on. Only the services you enable open a port. Open the matching ports in Windows Firewall, and forward them in your router if callers come from the Internet; those are separate steps from ProBoard's own settings.

Service Port Protocol Notes
Telnet 23 TCP Always on. The in-browser terminal shares this listener.
SSH 22 TCP Off until you enable it in PBConfig. Stop Windows OpenSSH Server first if it owns port 22.
RLogin 513 TCP Optional.
Web (PBWeb) 80 TCP HTTP only for now.
FTP (PBFtp) 21 TCP Plus passive data ports 50100 to 50200.
NNTP 119 TCP Plain or STARTTLS.
NNTP over TLS 563 TCP The simplest choice for PBMessages.
BinkP and EMSI mail 24554 TCP FidoNet-style mail.
Inter-BBS who is online 11 UDP Only if inter-BBS messaging is on.
Inter-BBS messages 18 TCP Same.
Inter-BBS finger 79 TCP Optional, off by default.
PBLink QWK hub 21 and 50000 to 50040 TCP Only if you run a hub. It can share port 21 with PBFtp.

Two services cannot use the same port on the same protocol. PBConfig refuses to save a clash on its Services screen. After you change a port, a session limit or an on/off switch, restart PBDispatch.

To open a port from an administrator command prompt, for example Telnet:

netsh advfirewall firewall add rule name="ProBoard Telnet TCP 23" dir=in action=allow protocol=TCP localport=23

Your board also makes outgoing connections for the features you use, such as program updates and the BBS list (HTTPS to the ProBoard web site), IRC, QWK polling and mail polling. Outgoing connections are normally allowed without any change.

Before you start