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.
The software was based on the DOS progam
BPQCODE
The switch section of the code supports up to 16 AX25 ports, and the application interface supports up to 64 connections.
Note the software is NOT Public Domain. It may be used only by licenced Radio Amateurs in Amateur Packet Radio systems.
The main built-in interface to radios is via KISS mode TNCs connected to standard RS232 com ports.
The following External driver .dlls are provided:
BPQ32 supports Data over Radio protocols other than ax.25 Packet. These are implemented as External driver .dlls.
See this document for information on using Pactor with BPQ32. There is also a driver available for the WINMOR Virtual TNC.
The following non-x.25 External driver .dlls 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.
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. Use AGWtoBPQ.exe
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. Use BPQTNC2.exe.
Programs written to use a Kantronics TNC in Kantronics Host Mode. Use BPQHostModes.exe.
There are two common interfaces to WA8DED or The Firmware TNCs. One uses a standard serial port, and can
interface to bpq32 using BPQHostModes.exe.
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.
I suggest that BPQ32.DLL is placed in the Windows directory, and all the other files are placed in
BPQ's own directory. Other options are possible - for example AR-Cluster installs BPQ in a
subdirectory of it's application directory. This will work ok, but will cause problems if you want
to add another application. The normal Windows convention would be to put it under Program Files,
eg \Program Files\bpq32, although I use c:\bpq32. The software uses a registry entry
HKEY_LOCAL_MACHINE\SOFTWARE\G8BPQ\BPQ32\BPQ Directory
to locate configuration files and driver dlls if they can't be found in the current directory. I suggest that this is always set to point to your BPQ32 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 you test the system first using a simple terminal program, before trying it with the BBS (if required). I have included a suitable terminal program (BPQTerminal), which may be used with the system.
John Wiseman G8BPQ
December 2008