BPQ32 allows a computer running under Microsoft Windows® to act as a Node in a NET/ROM compatible AX25
network, and to support a multiuser Mailbox, or other similar applications.
There is now a Linux version called LinBPQ. These documents apply to either version unless stated otherwise.
The software was based on the DOS progam BPQCODE
The switch section of the code allows up to 32 comms ports, supporting a number of radio protocols (see below for supported interfaces) and the application interface supports up to 64 connections.
The software includes an APRS compatible Digipeater and an interface to APRS/IS. A Mapping and Messaging application is available for use in conjunction with the these.
The main interface to radios is via KISS mode TNCs connected to standard RS232 com ports.
Other interfaces are provided, many are built into bpq32.dll, but some are separate .dll files. In either case, they are configured as External drivers.
BPQ32 supports Data over Radio protocols other than ax.25 Packet.
See this document for information on using Pactor with BPQ32.
The following non-x.25 drivers are provided:
BPQ32 supports a 32 bit version of the 'BPQ Host Mode' interface, used by the 16 bit BPQCODE, and defined in file BPQHOST.DOC. However, this was defined for Assembler programs, so other interfaces have been added. The details are really only of interest to application writers.
This is primarily for use by "C" programmers.
This is primarily for use with Visual Basic, and other languages that support Active X (formerly known as OLE) controls.
There are sample programs (C and VB) available here.
This iwas originally written for use with LinBPQ, but is also available in the Windows version.
I've also provided utilities which allow programs written to use a number of other interfaces to use BPQ32.
Most programs written to use the AGWPE TCP interface (not the older AGWPE .dll interface. Although AGWtoBPQ.exe is still available, there is now an AGWPE emulator built in to BPQ32/LinBPQ. See the AGW configuration section of bpq32.cfg
Most 16 bit Programs written for BPQCODE can use BPQ32 using the BPQ1632 subsystem.
Programs expecting to see a TNC2 (or similar) connected to a COM port. See the TNC Emulator section of bpq32.cfg
Programs written to use a Kantronics TNC in Kantronics Host Mode. See the TNC Emulator section of bpq32.cfg.
There are two common interfaces to WA8DED or The Firmware TNCs. One uses a standard serial port, and is supported by bpq32.
See the TNC Emulator section of bpq32.cfg.
The other uses the TFWIN and TFWIN32 interfaces provided by F6FBB for his BBS, but also supported by other programs, (eg TSTHWIN). These programs can interface to BPQ32 using the TFWIN/TFWIN32/TF2AGW Emulator.
The system is designed to be operationally compatible with existing NET/ROM or TheNet nodes, but there are a few minor differences. As it can support an integrated BBS, it has 2 Callsign/Alias pairs, one for accessing the node, and the other the BBS. Note, however, that a multiport node does not need a different callsign for each port. Because of the multiport support, the 'Downlink' connect command needs a port number as the first parameter (eg C 2 G8BPQ). A connect to another Node doesnt need this - the system selects the 'best' port as found from the NODEs and ROUTEs lists.
Up to eight applications are allowed, and each can have its own Callsign/Alias pair. Those without their own call are accessed by connecting to the switch, then entering the application name.
There are extra commands for normal use (BBS, or other application name, to connect to the applications, and PORTS to display available port descriptions), and 2 commands intended primarily for the system operator (STATS and LINKS).
For more information on Node commands, see here
The system is also able to link to the 'back end' async port on a normal NET/ROM or TheNet node.
Some configuration changes can be made while the node is running. See SYSOP Documentation for details.
For LinBPQ, see here . The following instructions are for the Windows version.
I suggest that BPQ32.DLL is placed in the Windows System
directory. On systems prior to Vista, I suggest all the other files are
placed in "Program Files\BPQ32". On Vista and above, there are
restrictions on creating files under "Program Files", so I suggest
software is installed in "Program Files\BPQ32", and data and
configuration files in %APPDATA%/BPQ32.The software uses the following
registry entries to locate configuration files and driver dlls if they
can't be found in the current directory.
HKEY_LOCAL_MACHINE\SOFTWARE\G8BPQ\BPQ32\BPQ Directory and
HKEY_LOCAL_MACHINE\SOFTWARE\G8BPQ\BPQ32\BPQ Program Directory
Vista and above:
HKEY_CURRENT_USER\SOFTWARE\G8BPQ\BPQ32\BPQ Directory and
HKEY_CURRENT_USER\SOFTWARE\G8BPQ\BPQ32\BPQ Program Directory
Program SetRegistryPath can be used to set this up.
The main configuration file is BPQ32.CFG. Edit this file to suit your installation.
The configuration is documented here.
I suggest for initial testing, you run bpq32.exe
BPQ32 now (April 2012) has an MDI (Multiple Document Interface) presentation. This combines all the bpq32 windows (Console, AXIP, telnet, Winmor, Pactor etc) into one frame, along with a monitor and one or more terminal windows, and a Stream Status window, similar to BPQStatus. Terminal windows are created using the Window/New Terminal Window Menu item
With previous versions, most of the background comms processing took place place in the first BPQ32 program to be loaded. Now bpq32.dll will load bpq32.exe to run the background processing (unless the first program you run is bpq32.exe). This should make for a more stable environment.
The code also supports inbound connects to the terminal, so users can connect and talk to you much as was done in thr old days of packet with dumb terminals. To enable this. include an APPLICATION line for Appl 32 in your config - something like:
APPLICATION 32,JOHN,,GM8BPQ-9,0 With this users can connect to GM8BPQ-9, or connect to the node and type JOHN. This will activate a terminal window, and ring a bell.
You can also load the system by running any bpq32 application, such as BPQMailChat. If loaded in this way the node will shut down when all applications are closed (as with the previous version).
If you run bpq32.exe before your applications, the node will keep running when all the applications are closed. As bpq32.exe doesn't have a window of its own, you shut the node down by using the "Close all BPQ32 Programs" item on the Window Menu.