QtTermTCP is a multi-platform version of BPQTermTCP. There are versions for Windows, Linux and Android.
It supports TCP access to a bpq32 node either over a local LAN or the Internet. It connects to the BPQ32 TelnetServer in FBB mode, so you must define an FBBPORT in the BPQ32 Telnet Configuration. It also supports the AGWPE interface. This is primarily to allow it to be used as a terminal for programs like UZ7HO's Soundmodem that support the AGW API. It can be used with the AGWPE emulator in BPQ32/LinBPQ though that has no significant advantages over the normal TCP interface. It supports the YAPP protocol to allow you to send and receive files.
The program can be download from:
http://www.cantab.net/users/john.wiseman/Downloads/QtTermTCP Binary for x86 Linux systems
http://www.cantab.net/users/john.wiseman/Downloads/piQtTermTCP Binary for Raspberry Pi
http://www.cantab.net/users/john.wiseman/Downloads/QtTermTCP.zip Program and Qt runtime for 32 bit Windows.
http://www.cantab.net/users/john.wiseman/Downloads/QtTermTCP64.zip Program and Qt runtime for 64 bit Windows. You can also run the 32 bit version on 64 bit systems.
http://www.cantab.net/users/john.wiseman/Downloads/QtTermTCP.apk Android Version. Should run on Android 7 and above
If you need to run on other Linux or similar systems you may be able to compile from source. Download http://www.cantab.net/users/john.wiseman/Downloads/QtTermSource.zip, unzip and run qmake then make
The program uses the Qt Framework, so needs some runtime files.
The Windows .zip file contains all the needed Qt Files, so you just need to unzip to an appropriate place. It is possible on some older versions of Windows that you may need some compiler runtime files, eg MSVCP140.dll. If you get a message about these being missing when you run the program download and run either
On Linux you may need to install the Qt5 package if you don't already have any other Qt5 programs on your machine:
sudo apt-get install qt5-default
On Android you just need to download and install the .apk file.
On Windows and Linux QtTermTCP keeps it's configuration information in a .ini file, which is saved in the directory QtTermTCP is started from.
QTTermTCP can be set to accept incoming connections. This allows uses on the BPQ node to connect to you.
The program can connect to IPv6 addresses if running on a machine with an IPv6 stack.
The program can run in three display modes - Single Window, MDI or Tabbed. In Single mode the screen can have both Monitor and Interactive windows which is similar to BPQTermTCP and is the default, or Interactive Only. In Tabbed or MDI mode each window can be Terminal Only, Monitor Only or combined Monitor and Terminal. When running is dual Terminal/Monitor mode the split between the two can be changed by right clicking at the point where you want the split and selecting "Set Monitor/Output Split".
QtTermTCP operates internally in UTF-8 so naturally handles different languages. There are a number of options to convert non UTF-8 input into UTF-8. The default is AUTO, where it will examine the input an try to guess what encoding it is using. This works reasonably well with characters using CP1252 (Western Europe), CP1251 (Cyrillic) or CP437 (the original IBM PC font, often used for displaying simple graphics), but sometimes it will guess the wrong set and you can then force the program to use the appropriate set. You can also set to not convert input which may be necessary if the program mis-interprets valid UTF-8.
In MDI mode the Window Menu allows you to create, rearrange, close and select subwindows.
In Tabbed mode it allows you to change the type of the current Tab.
Connect to a host. You can define up to 16 hosts to connect to.
If you are using the AGW interface there will be an entry for AGW Connect.
If using Tabbed or MDI you can have TCP session(s) at the same time as AGW Sessions.
Disconnect from the current host.
Configure HostName/IP Address, Port, Username and Password.
This brings up the AGW Interface configuration dialog
These allow you to choose the fonts to be used for output and menu entries
The next four lines allow you to set the terminal mode (Single, Tabbed, MDI)
Causes a "Keep alive" message to be sent every 11 minutes to stop Chat sessions closing.
Causes the program to sound a tone when a "Bell" character is received.
Removes Line Feeds. Most packet programs just use Carriage Return (Ascii 0x0d) to mark the end of a line, but some use Carriage Return plus Line Feed.
By default the program will beep when something is received after being idle for 5 minutes or when an inbound connect is accepted. These options allow these to be disabled.
The next few lines control how the program handles non UTF-8 input. See above paragraph on Character Sets for details.
Enables monitoring of transmitted frames.
Selects whether to monitor supervisory frames, or just I frames.
If set only UI frames will be displayed.
Controls whether "NODES" broadcasts are displayed.
Causes sent and received messages to be displayed in different colours.
Allows BPQTermTCP to accept incoming connections. You can set a port to listen on (default is 8515). You can also specify a CTEXT to be sent to a user when they connect to you.
The terminal is sent the list of ports from the Node you have connected to so you can choose which to monitor.
Here you can set the directory for received YAPP files and start a YAPP transfer