BPQ32 Installation

 

 

Usergroup:                  BPQ32

Document Author:       Ron Stordahl, AE5E

Date:                             2014Nov28

 

1.0     DESCRIPTION

 

2.0    Installing/Updating/Configuring BPQ32

2.01 ..\Examples\Minimal

2.02 ..\Examples\APRS

2.03 ..\Examples\Large

            2.04 ..\Examples\Small

 

3.0    BPQ32 Utility Programs

            3.01 BPQ32           

            3.02 BPQTerminal

            3.03 BPQTNC2 / VCOMConfig

            3.04 ClearRegistryPath/SetRegistryPath

            3.05 Uninstall

 

 

4.0    APPLICATIONS

            4.01 AGWPE Interface

            4.02 AR-Cluster

            4.03 CC Cluster

            4.04 DXSpider

            4.05 RMS

            4.06 UI-DX Bridge

            4.07 WinFBB701A

            4.08 WinFBB700I

 

5.0    AUTOMATICALLY STARTING AGWtoBPQ or BPQ32

 

6.0    STARTING BPQ32 and UTILITIES MINIMIZED

 

7.0    CHANGELOG

 

 

1.0   DESCRIPTION

 

BPQ32 software is a product of John Wiseman G8BPQ/GM8BPQ, to whom the amateur radio community owes a debt of gratitude.  BPQ32 is not in the public domain; however it may be freely used by licensed radio amateurs in amateur radio packet applications.  Assistance in using BPQ32 can be obtained through participation in the BPQ32 Yahoo Group.  BPQ32, packaged as an executable NSIS installer, is available in the files section of the BPQ32 Yahoo Group.

 

BPQ32 is an AX.25 NET/ROM switch, running under Microsoft Windows®, which interfaces via standard RS232 com ports to TNC’s supporting KISS, JKISS, multi-drop BPQKISS and NET/ROM interfaces.  It also supports internet connections via AX/IP/UDP and Telnet, as well as interfacing with AGWPE.  This later capability allows BPQ32 to provide AX.25 NET/ROM services via devices connected to AGWPE, most significantly sound card modems.

 

BPQ32 has three application interfaces: DLL, Active-X (OCX) and AGWPE. The DLL is the fundamental interface, the most efficient, and is used by the BPQ32 utilities as well as a number of user applications.  The OCX interface, which is deprecated and should not be used in any new designs, is used only by AR-Cluster Version 4.  The AGWtoBPQ driver emulates the AGWPE interface, permitting existing application programs, which have an AGWPE interface, to readily use BPQ32.  If a user application, interfacing via the AGWPE interface is well written, it will periodically try to reconnect to BPQ32 if it not currently connected.  Once per minute is a reasonable interval.  This will allow BPQ32 to be cancelled to make changes, restarted and then automatically reconnected by the user application.

 

The BPQ32 Console window displays several windows which previously required separate utilities: AXIP Port Resolver, AXIP Port MHeard, Telnet Server Status, Monitor, Stream Status and BPQ32.dll Status.  Options are provided to Close all BPQ32 Programs, Re-read BPQ32.cfg and reconfigure node, Re-read the APRS configuration.  Previously it was necessary to cancel BPQ32 to reconfigure.

 

BPQ32 Console can be started ‘mimimized’ as explained here.

 

Software developers wishing to interface their applications with BPQ32 may obtain interface programming specifications at the G8BPQ website.  The goal is to make BPQ32 compatible with all Microsoft Windows® amateur radio applications which can benefit from AX.25 network software.

 

Section 4.00 Applications describes the configuration of these interface methods with various applications.

  

 2.0   INSTALLING/UPDATING/CONFIGURING BPQ32

 

BPQ32 is supplied as an installer program which may be used to perform a new install, to update or to repair an existing installation.  The installer detects a running instance of BPQ32 during an install, upgrade or uninstall.  It issues a warning and aborts without making any changes.  To continue you must close BPQ32.  If you started BPQ32 by starting a single utility, such as BPQTerminal, closing it will close the BPQ32 system.  With many applications running it is easiest to use ‘Close all BPQ32 Programs’ offered on the BPQ32 Console Windows drop down.

 

The installer complies with Microsoft’s recommendations to separate program files from application data, and install each in the recommended locations.  This standard has been in effect since the introduction of Windows-XP, but a great number of programs failed to observe the standard and instead installed everything in the program files directory.  This was acceptable in XP, but beginning with Vista, failure to follow the standard results in frequent irritation in the form of UAC warnings, to which you must respond before BPQ32 will load.  By performing a compliant install these annoying warnings are avoided.  The installer also provides a procedure to convert an existing non-compliant install into a compliant install, applicable to Win-95 through Win-8, and likely Win-10.  The procedure to convert an existing non-compliant installation into a compliant installation is to perform an uninstall and then run the installer, taking all defaults.  A BPQ32 uninstall retains all of the user’s configuration, and reuses it in the subsequent install.  Finally for those of you who insist upon running with a non-compliant installation, you may simply run the installer.

 

The installer offers options for the folder locations of the program files and application files, should you not want to accept the recommended defaults.  The recommended locations for the program files are %programfiles%\BPQ32 on a 32-bit system and %programfiles (x86)%\BPQ32 on a 64-bit system.  For 32-bit systems these translate to C:\Program Files\BPQ32, for 64-bit systems C:\Program Files (x86)\BPQ32.  The application data files recommended folder is %appdata%\BPQ32 on either 32-bit or 64-bit systems.  On XP this translates as C:\Documents and Settings\”Username”\BPQ32, for Windows-7 C:\Program Files C:\Users\”Username”\AppData\Roaming\BPQ32.  If the system disc is ‘E’ rather and ‘C’, then the preceding will be E:\ rather than C:\ etc.

 

While it might seem awkward to locate the application data in such an obscure location, it is actually easy! Simply click on “Windows Start Button\Start Menu\All Programs\BPQ32”. Click on BPQ32 revealing an extensive list of BPQ32 components including “View Configuration Folder”. Doing so will open Windows Explorer to that folder with BPQ32.cfg already selected.

 

In the same manner you may choose “View Examples Folder” for a number of BPQ32 configuration examples.  Copy an appropriate BPQ32.cfg file to another location to edit it for your use.  Should you in error corrupt any of these and other files, you can simply rerun the Installer taking all the defaults to return to a valid state.

 

A starting point is the minimal BPQ32.cfg described as follows:

 

 2.01    ..\Examples\Minimal

 

A new install makes the BPQ32 minimal configuration the current configuration.  If you have an different existing configuration and you wish to run the minimal configuration test, first save your existing configuration, if any, then copy the contents of ..\Minimal to the Configuration Folder and execute BPQTerminal.exe.  Enter the following in the BPQTerminal data entry field:

 

C 1 MYNODE v MYCALL

 

You should receive the following response:

 

MYNODE:MYCALL} Connected to MYNODE

Minimal BPQ32 installation successful.

MYNODE:MYCALL} CONNECT BYE INFO NODES ROUTES PORTS USERS MHEARD

 

If you get the above response the basic test has succeeded.

 

Descriptions of useful BPQ32 configurations, which can serve as a basis for your configuration follow:

 

 2.02    ..\Examples\APRS

 

This is an example of a BPQ32 node which supports APRS digipeating compliant with the New-N Paradigm Initiative.  It includes one radio port and an internet connection to APRS-IS.  You will need an APRS-IS password which can be obtained by requesting if from G8BPQ.  The configuration includes examples of transmitted object formats compatible with ‘one button qsy’ capable radios, such as the Kenwood D710A and Yaesu FTM-350.

  

2.03     ..\Examples\Large

 

This is similar to the actual configuration I run on my AE5E CC-Cluster v 3.086 production system.  The configuration has 1 AX/IP/UDP, 1 KISS TNC, 1 AGWPE Device and 1 Telnet Port.  Via the internet AX/UPD users from around the world may connect using a combination of radio, telnet and AX/IP/UDP.  This is a busy machine, having up to 1,000 users during DX contests.

 

2.04     ..\Examples\Small

 

This example supports a KISS TNC, an AX/UDP port, BPQChat and the BPQMail BBS.

  

3.0   BPQ32 Utility Programs

 

After executing the installer, a number of utilities will be available which can be located at Start>Programs>BPQ32 or in the folder ..\BPQ32.  These are:

 

3.01     BPQ32   

BPQ32.exe is the background process that runs the Node software. It is loaded automatically when a program that uses BPQ32 is started. If you want to run just the Node without any other BPQ programs you can run BPQ32.exe.

 3.02     BPQTerminal

 

BPQTerminal allows terminal access to the BPQ32 system.

 

BPQTerminal.jpg 

 

The upper window allows monitoring of traffic, as selected by the Monitor drop down box. The middle window displays connected output, while the bottom windows is used to enter commands.  Starting BPQTerminal will bring up BPQ32 if it is not already running.  Multiple copies of BPQTerminal may be run at the same time.

 

3.03    VCOMConfig

VCOMConfig is used to generate a virtual com port.  An application designed to interface via a serial port to a TNC device can connect via a virtual port to BPQ32 through the BPQ32 TNC emulators, avoiding the need for two real com ports linked by a null modem cable. See here for more information on BPQ32 Virtual serial ports.

  

3.04     ClearRegistryPath/SetRegistryPath

 

ClearRegistryPath.exe and SetRegistryPath.exe either clear or set registry entries which tell BPQ32 where to find its configuration files.  Upon starting BPQ32 first looks in the registry at “HKEY_LOCAL_MACHINE\SOFTWARE\G8BPQ\BPQ32\BPQ Directory”.  If a path to the configuration files is found there it is used.  If it is not found, then “HKEY_LOCAL_MACHINE\SOFTWARE\G8BPQ\BPQ32\Config File Location” is examined and if a path is found, it is used.  If neither is found, then BPQ32 will expect to find its configuration files in the directory from which it is started.

 

Currently only AR-Cluster sets ..\Config File Location, however with the current BPQ32, this is no longer needed or desirable.  Neither ..\BPQ Directory or ..\Config File Location should be set or cleared by application programs.

 

3.05     Uninstall

 

Uninstalls BPQ32, including your configurations.  If you wish to save your configurations you must do so prior to running Uninstall.

 

 

4.0   APPLICATIONS

 

BPQ32 can be used stand alone or interfaced with local or remote user applications.  User applications with which I have tested it include: AGWPE, AR-Cluster, CC-Cluster, DXSpider, RMS, UI-DX Bridge, and WinFBB701A.  There are many other applications, on which I am seeking information for the next installation document, which could benefit from BPQ32 services.

 

4.01     AGWPE Interface

 

BPQ32 includes an interface to AGWPE allowing BPQ32 to access all devices supported by AGWPE.  See ..\Examples\Large\BPQ32.cfg . The main purpose of the AGWPE interface is to allow BPQ32 access to sound card modems supported by AGWPE.  However, it interfaces equally well with any device supported by AGWPE.  Thus you can have AGWPE control all such devices and have BPQ32 access them via BPQ32’s AGWPE interface.

 

4.02     AR-Cluster

 

With BPQ32 v 6.0.9.1 and AR-Cluster v 6, which has replaced AR-Cluster v 4, the use of AGWtoBPQ.exe as a separate program has been deprecated.  Additionally the OCX interface is no longer supported.  AR-Cluster v 6 only supports the AGWPE interface.  The matching BPQ32 interface is now an integral part of BPQ32.  An example configuration, from ..\Examples\Large\BPQ32.cfg is:

 

;AGW Emulator Parameters – Replaces the now deprecated AGWtoBPQ.exe

AGWPORT=8001

AGWSESSIONS=6

AGWMASK=2

 

APPLICATION 2,DXA,,A1ABC-1,ABCDXA,255            ;The ‘2’ in this line corresponds to AGWMASK=2

 

This statement generates a user command DXA, a node entry of ABCDXA:A1ABC-1 transmitted to adjacent nodes with a quality of QUALITY value less 1.

 

Within AR-Cluster a corresponding configuration is made in the AR-Cluster ServerIoCfg Collection Editor.


 

4.03     CC Cluster

 

With BPQ32 v 6.0.9.1 the need for AGW2CCC.exe to interface between BPQ32 and Winsock v 3.24/CC Cluster v 3.086 has been eliminated. Instead within BPQ32.cfg define a Telnet Server Port and include the statement CMDPORT=9002. In Winsock.exe define the AGW/Winsock Port with the corresponding number 9002 and 'check' AGW Enabled. A BPQ32 applications statement is required, thus:

APPLICATION 1,DXC,C 4 HOST 0 K,A1ABC,ABCDXC,255         ; See ..\Examples\Large\BPQ32.cfg

In this example the configured BPQ32 Telnet Port is 4. That port definition contains a single CMDPORT statement, which corresponds to the "0" in the applications statement above.. If there were a second CMDPORT statement, following the first, it would correspond to "1", etc. The "K" enables a keepalive function with a timer equal to 60 seconds less than IDLETIME, the node idle shutdown timer. This APPLICATION statement generates a user command of "DXC", a node entry of ABCDX:A1ABC which is transmitted to adjacent nodes with a quality of QUALITY less 1. For example with a receiving node QUALITY of 192, the application, with an internal quality of 255, the receiving node would show this application with a quality of 255(192/256) = 191. A connection to this port via BPQ32 will forward your callsign to CC-Cluster automatically, thus no sign on is required.

CC Cluster allows you to define logon messages depending upon the port on which the user connects. For telnet users multiple ports can be defined, as shown in the following example: 23 and 7000. These would correspond to ports 1 and 2 on the Logon & Logout Message window of CC-Cluster. The AGW/Winsock port would follow as port 3. When connecting on the AGW/Winsock port much of the welcome text is skipped, reducing radio traffic. Only the text below the port number listing, in the Logon & Logout Message window of CC-Cluster, is sent plus any optional cluster commands you choose to set for automatic execution.

 

4.04     DXSpider

 

DXSpider can utilize either the BPQ32 DLL or AGWtoBPQ interface.  I have tested DXSpider V1.55 build 0.26 with ActivePerl-5.8.8.822-MSWin32-x86-280952.msi.  I was unsuccessful with ActivePerl-5.10.0.1003-MSWin32-x86-285500.  The DXSpider Wiki provides installation information for MSWindows®.  In the install document the paragraph Additional Packages describes how to add net.telnet, timedate and db_file to Perl.  In order to use BPQ32 with the DLL interface you must also add Win32-api.  You may do this from a DOS box thus:

 

cd \

ppm install Win32-api

 

This will download and install the appropriate additional components.  The additional components may also be added via the Perl Package Manager.

 

With BPQ32 installed in C:\Program Files\BPQ32 to use the DLL interface copy as follows:

 

copy c:\spider\perl\BPQConnect.pm

c:\spider\local\BPQConnect.pm

 

In the ..\local folder edit BPQConnect.pm.  There are three parameters to edit:  $enable = 1 enables the DLL interface, $Applmask = 1 sets the applications mask to a decimal 1, you may have to change this if DXSpider is other than the first positional parameter in bpqcfg.txt’s APPLICATIONS string, and  $BPQStreams = 10, which should be adequate.

 

Alternately you may choose the AGWtoBPQ interface, instead:

 

copy c:\spider\perl\AGWConnect.pm

c:\spider\local\AGWConnect.pm

 

In the ..\local folder edit AGWConnect.pm.  There are three parameters to edit:  $enable = 1 enables the AGWtoBPQ interface, $addr = “localhost” and $port = 8000 are the defaults, which are likely to be correct.  The applications mask is set in AGWtoBPQ as described in AGWtoBPQ, with 0x1 being the correct value if DXSpider corresponds to the first positional parameter in bpqcfg.txt’s APPLICATIONS string.

 

If using the DLL interface, upon starting DXSpider, BPQ32 will automatically start. If using the AGW interface it is up to the user to start AGWtoBPQDXSpider’s AGWtoBPQ’s interface is well designed, allowing AGWtoBPQ to be cancelled, reconfigured and restarted without effecting DXSpider’s telnet users.

 

4.05     RMS

 

RMS Packet has a direct BPQ32.DLL interface. Select "Use BPQ32 to access TNC" on the Site Properties Dialog. 

 

4.06     UI-DX Bridge

 

UI-DX Bridge setup with AGWtoBPQ is exactly the same as with AGWPE.  Surprisingly the TX Radio Port must be entered as one less than the actual AGWPE or AGWtoBPQ port number.  Thus if your AGWPE or AGWtoBPQ desired port is 2, you must set the ‘TX Radio Port” in UI-DX Bridge to 1, if the AGWPE or AGWtoBPQ port is 1, then you must set this field to 0.  This anomaly lies with UI-DX Bridge not with AGWPE or AWGtoBPQ.

 

4.07     WinFBB701A

 

The install documentation and file set for WinFbb701-35A is in the files section of the BPQ32 Yahoo Group.  This includes the bpq.dll version 1.0.0.1 and tln.dll version 1.6.1.0 included in that set.  The updated tln.dll corrects a problem in WinFBB701-35A which caused corruption of the callsign of the connecting station, resulting in corrupt entries being sent to the WP database.  Note that versions 1.7.0.0 and 1.8.0.0 tln.dll from May 2001 exist, however they are not to be used.  John was able to get source code for version 1.6.0.0 and he corrected that code resulting in version 1.6.1.0.

 

In the example file. ..\Examples\Small\bpqcfg.txt, FBB is the first positional parameter in the bpqcfg.txt APPLICATIONS string thus the Appl Mask needed is 0x1.  You must set this in the registry as HKEY_LOCAL_MACHINE\SOFTWARE\G8BPQ\BPQ32\FBBAPPL REG_DWORD 0x00000001 (1).

 

With this completed, starting WinFBB701A will, using the bpq.dll interface, bring up the needed BPQ32 modules.

 

4.08     WinFBB700I

 

The install documentation and file set for WinFBB700I is in the files section of the BPQ32 Yahoo Group.  That set includes TFWIN.DLL Version 1.2.0.1 which resolves a 100% CPU utilization issue.

 

5.0   AUTOMATICALLY STARTING AGWtoBPQ or BPQ32

 

If you will be using BPQ32 standalone, then BPQ32.exe, or more likely BPQTerminal.exe, may be started by adding an appropriate shortcut to..\Start Menu\Programs\Startup\.  A quick way to get to this directory is to right click on the Windows® Start button and select Explore.  Windows® Explorer will begin at the Start Menu directory, and you can then drill your way down to two levels to the Startup directory, and there add the desired shortcut.

 

A better alternative to using Windows® Explorer is to use a utility such as R2 Studio’s Startup Delayer.  That program will allow you to control the sequence and delay for each program you wish to start at boot time.  In addition you can impose a fixed delay before the process starts, giving you time to abort the process should you wish.

 

6.0   STARTING BPQ32 and UTILITIES MINIMIZED

 

The BPQ32 Console offers, in the “Action” drop down list, “Start Minimized” and “Minimize to Notification Area (System Tray).

 

Prebuilt shortcuts are provided from the BPQ32 program drop down list in “View Shortcuts Folder” in both Normal and Minimized formats.

 

R2 Studio’s Startup Delayer also provides for selection of Normal and Minimized windows for the programs it starts.

 

7.0 CHANGELOG

 

BPQ32_6.0.9.1_2014Nov28:


BPQ32.dll Updated to Version 6.0.8.1. Changes Since 6.0.8.1

BPQMail updated to Version 1.4.62.1 Changes since Version 1.4.61.1

BPQChat updated to Version 1.0.5.1 Changes since Version 1.0.4.1

Support Program Changes.

  BPQAPRS updated to Version 1.1.8.1
  BPQTerminal updated to Version 2.2.2.1
  BPQTermTCP updated to Version 1.0.10.1


BPQ32_6.0.8.1_2014Aug17:


BPQ32.dll Updated to Version 6.0.8.1. Changes Since 6.0.7.1

BPQMail updated to Version 1.4.61.1 Changes since Version 1.4.60.1

Support Program Changes.

  BPQAPRS updated to Version 1.1.8.1
  BPQTermTCP updated to Version 1.0.9.1


BPQ32_6.0.7.1_2014Apr13:


BPQ32.dll Updated to Version 6.0.7.1. Changes Since 6.0.6.1

BPQMail updated to Version 1.4.60.1 Changes since Version 1.4.59.1

BPQ32_6.0.6.1_2014Apr06:


BPQ32.dll Updated to Version 6.0.6.1. Changes Since 6.0.5.1

BPQMail updated to Version 1.4.59.1 Changes since Version 1.4.58.1

BPQChat updated to Version 1.0.4.1 Changes since Version 1.0.3.1

Support Program Changes.

  BPQAPRS updated to Version 1.1.7.1
  BPQUIUtil.exe is withdrawn. It has been replaced by similar facilities in BPQ32.

BPQ32_6.0.5.1_2014Jan15:


BPQ32.dll Updated to Version 6.0.5.1. Changes Since 6.0.4.1

BPQMail updated to Version 1.4.58.1 Changes since Version 1.4.57.1

BPQChat updated to Version 1.0.3.1 Changes since Version 1.0.2.1

Support Program Changes.

  BPQAPRS updated to Version 1.1.6.1
  BPQTermTCP updated to Version 1.0.7.1

BPQ32_6.0.4.1_2013Oct06:


BPQ32.dll Updated to Version 6.0.4.1. Changes Since 6.0.3.1

BPQMail updated to Version 1.4.57.1 Changes since Version 1.4.56.1

BPQChat updated to Version 1.0.2.1 Changes since Version 1.0.1.1

BPQTermTCP updated to Version 1.0.8.1


BPQ32_6.0.3.1_2013Jul20:


BPQ32.dll Updated to Version 6.0.3.1. Changes Since 6.0.2.1

BPQMail updated to Version 1.4.56.1 Changes since Version 1.4.5.1

Support Program Changes.

  BPQAPRS updated to Version 1.1.5.1
  WinmorControl New Program

BPQ32_6.0.2.1_2013Jun08:


BPQ32.dll Updated to Version 6.0.2.1. Changes Since 6.0.1.1

BPQMailChat updated to Version 1.4.55.1 Changes since Version 1.4.54.1

Support Program Changes.

  AGWtoBPQ updated to Version 1.2.5.1

BPQ32_6.0.1.1_2013Mar22:


BPQ32.dll Updated to Version 6.0.1.1. Changes Since 5.2.9.1

BPQMailChat updated to Version 1.4.54.1 Changes since Version 1.4.53.1

BPQChat updated to Version 1.0.1.1

Support Program Changes.

  BPQAPRS updated to Version 1.1.4.1
  BPQTermTCP updated to Version 1.0.5.1
  BPQUIUtil updated to Version 0.1.3.1


BPQ32_5.2.9.1_2012Sep25:


BPQ32.dll Updated to Version 5.2.9.1. Changes Since 5.2.8.1

BPQMailChat updated to Version 1.4.53.1 Changes since Version 1.4.52.1

BPQ32_5.2.8.1_2012Aug08:


BPQ32.dll Updated to Version 5.2.8.1. Changes Since 5.2.7.1

BPQMailChat updated to Version 1.4.52.1 Changes since Version 1.4.51.1

Support Program Changes.

  BPQAPRS updated to Version 1.1.3.1


BPQ32_5.2.7.1_2012Jun08:


BPQ32.dll Updated to Version 5.2.7.1. Changes Since 5.2.6.1

BPQMailChat updated to Version 1.4.51.1 Changes since Version 1.4.50.1

BPQAPRS.exe Updated to Version 1.1.2.1

Support Program Changes.

  BPQTerminal updated to Version 2.2.1.1
  BPQTermTCP updated to Version 1.0.4.1


Although the BPQDED drivers haven't been updated, a error was found in the released bpqded.zip, so the zip file has been updated.

BPQ32_5.2.6.1_2012Apr04:


BPQ32.dll Updated to Version 5.2.6.1. Changes Since 5.2.5.1

BPQMailChat updated to Version 1.4.50.1 Changes since Version 1.4.49.1

New program BPQChat.exe Version 1.0.0.1. This is the Chat part of BPQMailChat as a separate program.

BPQAPRS.exe Updated to Version 1.1.1.1

Support Program Changes.

  BPQHostModes updated to Version 1.1.8.1


BPQ32_5.2.5.1_2012Feb20:


BPQ32.dll Updated to Version 5.2.5.1. Changes Since 5.2.4.1

BPQMailChat updated to Version 1.4.49.1 Changes since Version 1.4.48.1

BPQAPRS.exe Updated to Version 1.1.0.1

BPQ32_5.2.4.1_2012Jan30:


BPQ32.dll Updated to Version 5.2.4.1. Changes Since 5.2.3.1

BPQMailChat updated to Version 1.4.48.1 Changes since Version 1.4.47.1

New program BPQAPRS.exe Version 1.0.0.0


BPQ32_5.2.3.1_2012Jan06:


BPQ32.dll Updated to Version 5.2.3.1. Changes Since 5.2.1.3

BPQMailChat updated to Version 1.4.47.1 Changes since Version 1.0.4.46:

Support Program Changes.

  AGWtoBPQ updated to Version 1.2.3.1
  BPQHostModes updated to Version 1.1.7.1
  BPQTerminal updated to Version 2.1.2.1
  BPQTNC2 updated to Version 1.1.5.1
  BPQUIUtil updated to Version 0.1.1.0

BPQ32_5.2.1.3_2011Oct18:


BPQMailChat updated to Version 1.0.4.45. Changes since Version 1.0.4.45:

BPQ32_5.2.1.3_2011Oct17:


BPQ32.dll Updated to Version 5.2.1.3. Changes Since 5.0.0.1

BPQMailChat updated to Version 1.0.4.45. Changes since Version 1.0.4.40:

Support Program Changes.

  BPQAuth New Program
  BPQTerminal updated to Version 2.1.1.2
  BPQTermTCP updated to Version 1.0.3.1
  BPQUIUtil New Program

The following have been updated to use HKEY_CURRENT_USER when running on Vista or above

  BPQ1632.dll
  AGWtoBPQ updated to Version 1.2.2.1
  BPQDED32.dll
  BPQHostModes updated to Version 1.1.6.1
  BPQTNC2 updated to Version 1.1.2.1


BPQ32_5.0.0.1_2011Apr11:


BPQ32.dll Updated to Version 5.0.0.1. Changes Since 4.10.16.15

BPQMailChat updated to Version 1.0.4.40. Changes since Version 1.0.4.38:

Support Program Changes.

    BPQHostModes updated to Version 1.1.5.1
    BPQStatus updated to Version 1.0.6.1


BPQ32_410p_2011Feb14:


BPQ32.dll Updated to Version 4.10.16.15. Changes Since 4.10.16.13

BPQMailChat updated to Version 1.0.4.38. Changes since Version 1.0.4.35:

New Program BPQTermTCP which provides remote access to a BPQ32 Node over the Internet

BPQ32_410p_2011Jan20:


BPQ32.dll Updated to Version 4.10.16.13. Changes Since 4.10.16.12

BPQMailChat updated to Version 1.0.4.35. Changes since Version 1.0.4.33:

BPQ32_410p_2011Jan14:


BPQMailChat updated to Version 1.0.4.33. Changes since Version 1.0.4.32:

BPQ32_410p_2011Jan13:


BPQ32.dll Updated to Version 4.10.16.12. Changes Since 4.10.16.11

BPQMailChat updated to Version 1.0.4.32. Changes since Version 1.0.4.30:

BPQTNC2.exe code re-arranged to stop various anti-virus programs reporting it as a virus.

BPQDED32.dll updated to support application numbers above 8

BPQ32_410p_2010Dec20:


BPQ32.dll Updated to Version 4.10.16.10. Changes Since 4.10.16.8

BPQMailChat updated to Version 1.0.4.28. Changes since Version 1.0.4.25:

BPQ32_410p_2010Dec08:


Installer reissued with a recompiled bpqtnc2.exe to stop AVAST reporting it as a virus.

BPQ32_410p_2010Nov16:


BPQ32.dll Updated to Version 4.10.16.8. Changes Since 4.10.16.5

BPQMailChat updated to Version 1.0.4.25. Changes since Version 1.0.4.23:

Support Program Changes.

    BPQHostModes updated to Version 1.1.4.1
    BPQTerminal updated to Version 2.0.10.1


BPQ32_410p_2010ct15:


BPQ32.dll Updated to Version 4.10.16.5. Changes Since 4.10.16.3

VCOMConfig.exe updated to Version 1.0.1.1
BPQVirtualCOM.sys updated to Version 1.0.2.1
    These together increase the number of Virtual COM Ports from 10 to 20.

BPQTelnetServer is withdrawn - the same functions are now built into BPQ32.dll


BPQ32_410p_2010ct07:


BPQMailChat updated to Version 1.0.4.23. Changes since Version 1.0.4.22:

BPQ32.dll Updated to Version 4.10.16.3. Changes Since 4.10.15.4

BPQHostModes and BPQTelnetServer updated see Changelog for details


BPQ32_410o_2010Sep22:


BPQMailChat updated to Version 1.0.4.22. Changes since Version 1.0.4.15:


BPQ32_410o_2010Aug16:



BPQMailChat updated to Version 1.0.4.15. Changes since Version 1.0.4.10:

BPQ32.dll Updated to Version 4.10.15.4. Changes Since 4.10.14.3

KAMPactor.dll updated to 1.2.1.4:

    Send Change to ISS before each transmission
    Support up to 32 BPQ Ports
    Drop RTS as well as DTR on close
    Save Minimized State on exit and restore on restart

SCSPactor.dll updated to 1.2.1.1

    Support up to 32 BPQ Ports
    Drop RTS as well as DTR on close
    Save Minimized State on exit and restore on restart

Winmor.dll Updated to Version 1.2.1.2

    Support up to 32 BPQ Ports
    Support up to 32 BPQ Applications
    Save Minimized State on exit and restore on restart
    Handle new "BLOCKED by Busy channel" message from WINMOR TNC Version 1.1.8.0


BPQ32_410n_2010Jul02:



BPQMailChat updated to Version 1.0.4.10. Changes since Version 1.0.4.8:


BPQ32_410n_2010Jun06:

 

BPQ32.dll Updated to Version 4.10.14.3:

    Add option to prevent node trying to keep link to a neighbours open.

BPQCfg.exe Updated to Version 1.0.10.1:

    Added Supress Keepalives Option

BPQTelnetServer Updated to Version 2.1.9.1

    Fix problem with input lines longer than 256 chars.

BPQTNC2 Updated to Version 1.1.2.0

    Implement MYCALL command.

BPQMailChat updated to Version 1.0.4.8. Changes since Version 1.0.4.4:


BPQ32_410n_2010Apr19:

 

BPQ32.dll Updated to Version 4.10.14.2:

    No longer flips SSID bits on Downlink Connect if uplink is Pactor/WINMOR
    Fix resetting IDLE Timer on Pactor/WINMOR sessions. This was preventing transfers lasting longer than IDLETIME
    Add KISS OPTION "D700" which removes risk of accidentally taking D700/D710 radios out of KISS Mode
    Send L3 Keepalive messages (KEEPLI) based on IDLETIME

BPQCfg.exe Updated to Version 1.0.9.2:

    Added KISS "D700" Option

BPQMailChat updated to Version 1.0.4.4. Changes since Version 1.0.4.1:


BPQ32_410n_2010Mar20:

 

BPQ32.dll Updated to Version 4.10.14.1:

    Rig Control is now build in to bpq32.dll. Rigcontrol.dll is no longer used.
    Adds control of Kenwood Rigs
    Adds option to combine Attach and Call commands for Pactor and WINMOR

Winmor.dll Updated to Version 1.1.1.10

    Minor Changes to window layout

RigControl.dll Withdrawn - now in bpq32.dll

KAMPactor.dll updated to 1.1.1.12:

    Add option to set make ax.25 calls on HF port.

BPQCfg.exe Updated to Version 1.0.9.1:

    Added SIMPLE config mode for basic configurations. See here for details.

BPQMailChat updated to Version 1.0.4.1. Changes since Version 1.0.3.38:

BPQTerminal to 2.0.9.2

    Adds optional use of colour for Chat Mode and Monitor output



BPQ32_410m_2010Feb28:

 

Winmor.dll Updated to Version 1.1.1.9

     Changes to improve reliablity
     Added FEC mode for realtime QSOs
     See here for details.

RigControl.dll updated to Version 1.1.1.7

    Time Based Scanning added
    Interlock added to facilitate operating Winmor and Pactor on same radio

SCSPactor.dll updated to 1.1.1.12

    Interlock added to facilitate operating Winmor and Pactor on same radio
    Fix crash if port is not defined in the config file

KAMPactor.dll updated to 1.1.1.12:

    Interlock added to facilitate operating Winmor and Pactor on same radio
    Fix crash if port is not defined in the config file
    Add option to set to PACTOR mode (instead of TOR mode) for older KAM versions.

BPQTerminal to 2.0.8.1

    Fix use of numeric keybad in Num Lock mode (was interpreted as cursor control)



BPQMailChat updated to Version 1.0.3.38. Changes since Version 1.0.3.37:

 

BPQ32_410m_2010Mar05:

 

BPQ32.dll Updated to Version 4.10.13.12:

    Supports APPLCALL feature of the new winmor.dll
    Accepts commands terminated by CR/LF

Winmor.dll Updated to Version 1.1.1.10

    Now accepts connections to any APPLnCALL
    Adds a display of messages received from the Winmor TNC
    Is compatible with WINMOR TNC Version 1.0.1.0
    See here for details.

RigControl.dll updated to Version 1.1.1.8

    Adds option to control PTT for two Winmor ports, one using RTS and the other DTR

BPQ32_410m_2010Feb28:

 

Winmor.dll Updated to Version 1.1.1.9

     Changes to improve reliablity
     Added FEC mode for realtime QSOs
     See here for details.

RigControl.dll updated to Version 1.1.1.7

    Time Based Scanning added
    Interlock added to facilitate operating Winmor and Pactor on same radio

SCSPactor.dll updated to 1.1.1.12

    Interlock added to facilitate operating Winmor and Pactor on same radio
    Fix crash if port is not defined in the config file

KAMPactor.dll updated to 1.1.1.12:

    Interlock added to facilitate operating Winmor and Pactor on same radio
    Fix crash if port is not defined in the config file
    Add option to set to PACTOR mode (instead of TOR mode) for older KAM versions.

BPQTerminal to 2.0.8.1

    Fix use of numeric keybad in Num Lock mode (was interpreted as cursor control)



BPQMailChat updated to Version 1.0.3.38. Changes since Version 1.0.3.37:

 

BPQ32_410m_2010Feb12:

 

BPQ32.dll Updated to Version 4.10.13.11:

    Fix handling commands split over more that one packet. Mainly affects Pactor connections.
    Attach Command changes to handle Winmor disconnecting state
    Interlock Winmor/Pactor ports using the same radio

Winmor.dll Version 1.0.0.1 New Module to support the Winmor soundcard-based HF protocol. See here for details.

Driver .dll files recomplied for compatibility with new bpq32.dll, but without any functional changes:

    Bpqaxip.dll to 1.15.2.9
    Bpqether.dll to 1.3.0.5
    BPQtoAGW.dll to 1.5.0.5
    Bpqvkiss.dll to 1.3.1.5
    RigControl.dll to 1.1.1.4
    SCSPactor.dll to 1.1.1.11
    KAMPactor.dll to 1.1.1.11
    BPQIPModule.dll to to 1.2.1.5

BPQMailChat updated to Version 1.0.3.37. Changes since Version 1.0.3.29:

 

BPQ32_410m_2010Jan19:


BPQ32.dll Updated to Version 4.10.13.9:

    Fix occasional deletion of your applications from the NODES table when running INP3
    Fix GETCALLSIGN for Pactor Sessions. The affected the BPQStatus.exe display
    Add N Call* to display all SSID's of a call
    Fix flow control on Pactor sessions.
    HDLC cards are now supported on W2K/XP systems
    Add AUTH routines to provide a reasonably secure One Time Password system. Initially for use by RigCOntrol

RigControl.dll updated to Version 1.1.1.3

    Fix crash if configured to use a KISS or HDLC port. (Should only be used for Pactor)
    Add AUTH command to allow frequency control of a remote system

SCSPactor.dll updated to 1.1.1.10

    Add Scan Control using %W Hostmode Command. This stops the frequency being changed if an incoming call is being set up.
    Map Rig control port to a Virtual Serial Port.
    Add Support for packet port(s).

KAMPactor.dll updated to 1.1.1.10: Fix to flow control on Packet Sessions.

BPQIPModule.dll updated to to 1.2.1.4: Fix recently introduced fault which stopped the gateway from functioning.

Driver .dll files recomplied for compatibility with new bpq32.dll, but without any functional changes:

    Bpqaxip.dll to 1.15.2.8
    Bpqether.dll to 1.3.0.4
    BPQtoAGW.dll to 1.5.0.4
    Bpqvkiss.dll to 1.3.1.4

 

BPQTelnetServer.exe to 2.1.8.1:   Removes the Session number from the *** Connected message, to simplifiy parsing for software that needs a connect script (eg Outpost).

 

BPQMailChat updated to Version 1.0.3.29. Changes since Version 1.0.3.24:

 

BPQ32_410m_2009Dec25:

 

BPQ32.dll Updated to Version 4.10.13.7:

    Add Rig Control Interface.
    Limit KAM VHF attach and RADIO commands to authorised programs (MailChat and BPQTerminal).
    Fix reading INP3 Flag from BPQNODES.
    Add MAXHOPS and MAXRTT config options for INP3.

BPQCfg.exe Updated to Version 1.0.8.2:

    Add MAXHOPS and MAXRTT config options for INP3.

New Driver RigControl.dll Version 1.1.1.0

Pactor Driver .dll files updated to use RigControl:

    KAMPactor.dll to 1.1.1.5
    SCSPactor.dll to 1.1.1.6

Driver .dll files recomplied for compatibility with new bpq32.dll, but without any functional changes:

    Bpqaxip.dll to 1.15.2.7
    Bpqether.dll to 1.3.0.3
    BPQIPModule.dll to 1.2.1.3
    BPQtoAGW.dll to 1.5.0.3
    Bpqvkiss.dll to 1.3.1.3

Changes to BPQMailChat - Version 1.0.3.24:

 

BPQ32_410m_2009Dec10:

 

BPQ32.dll Updated to Version 4.10.13.4:

    Changes for PACTOR and WINMOR to support the ATTACH command.
    Enable INP3 if configured on a route.
    Fix count of nodes in Stats display
    Overwrite the worst quality unused node if a call is received from a node not in your table when the table is full

BPQCfg.exe Updated to Version 1.0.8.2:

    Add MAXRTT and MAXHOPS configuration options for .

Driver .dll files recomplied for compatibility with new bpq32.dll, but without any functional changes:

    Bpqaxip.dll to 1.15.2.6
    Bpqether.dll to 1.3.0.2
    BPQIPModule.dll to 1.2.1.2
    BPQtoAGW.dll to 1.5.0.2
    Bpqvkiss.dll to 1.3.1.2

Changes to BPQMailChat - Version 1.0.3.21:

 

 

BPQ32_410l_2009Nov22:

 

The only change is to BPQMailChat.

 

Changes to BPQMailChat - Version 1.0.3.17:

 

BPQ32_410l_2009Nov06:

 

The only change is to BPQMailChat.

 

Changes to BPQMailChat - Version 1.0.3.12:

 

BPQ32_410l_2009Oct28:

 

BPQTerminal.exe to 2.0.7.2  Added input buffer scrollback.  Fixed monitoring when PORTNUM is specified.

 

BPQ32.dll to 4.10.12.2.  Added a GetVersionString API call enabling the V command on the BBS to show both BBS and Node Versions.  Added a GetPortTableEntry API call used by the BBS to determine if any external drivers are loaded.  The code will not attempt to keep links to each neighbouring node open.  If the connection fails the obs count on each node is decremented.  Thus if a neighbor does down, node entries via it will be removed after about 5 minutes.

 

Changes to BPQMailChat - Version 1.0.3.11:

 

 

 BPQ32_410k_2009Sep24:

 

BPQTelnetServer.exe to 2.1.7.1:   Supporting changes required by BPQMailChat for forwarding to FBB via tcp.

 

Bpqaxip.dll 1.15.2.5:  Properly clears the MH window and adds a new AX/TCP access method. See example bpqaxip.cfg’s in folder ...\examples.

 

Bpq32.dll  4.10k Ver 4.10.11.4:  Adds a new  user command “NRR ‘node’”, which may be entered from BPQTerminal,  sending a netrom record route packet to the specified node.  The return results show the actual path taken to and from said node.

 

 

BPQ32+BPQMailChat_Beta_2009Sep24:  Includes the changes listed above for BPQ32_410k_2009Sep24 plus BPQMailChat Beta – Version 1.0.2.9:

 

Changes to BPQMailChat - Version 1.0.2.9:

 

BPQ32_410j_2009Aug03:

 

BPQTelnetServer.exe to 2.1.6.2:  Remove entry from Disconnect User Dialog when session closes.  Fix reception of multiple backspaces in the same packet.

 

BPQAxip.dll to 1.15.1.2:  Corrected time display in AXIP MHeard window.

 

BPQTerminal.exe to 2.0.6.3:  Added option to send “*** Disconnected” upon disconnect.  Added linewrap code.  Added option to disable monitoring of NODES broadcasts.

 

BPQ32.dll to 4.10.10.5:  Fix tidying of window list when program crashed.  Added Max Nodes to Stats display.  Don’t update APPLnALIAS with received NODES info.  Fix MHeard display in other timezones.  Fixed possible crash when processing NETROM type Zero frames (e.g. NRR).  Basic IMP3 Stuff.  Added extra diagnostics to Lost Process detection.  Process Netrom Record Route Frames.

 

The installer now adds the folder c:\ProgramFiles\BPQ32\BPQMailChat.  This will be the future location for BPQMailChat, John Wiseman’s new BBS system which is still in beta.  Beta testers should ensure that they have installed the beta test software in that directory. 

 

BPQ32_410i_2009May09:

 

BPQTelnetServer to 2.1.5.1 raising the number of users as defined in BPQTelnetServer.cfg which was previously limited to 249.

 

BPQCfg.exe to 1.0.6.2 by adding a ‘C’ style multiline comment feature to bpqcfg.txt thus:

 

            /*         This begins a multi-line comment

            Statement (1 or more lines)

            */         ;This ends a multi-line comment

            This is useful in commenting out a range of lines in bpqcfg.txt.  Refer to the examples in the \Examples folders.

 

BPQAXIP.dll to 1.14.1.1 by adding two new options to the BPQAXIP.cfg file and changing the default behavior to NOT add information to BPQ32’s nodes table for  AX/IP/UDP nodes which are not explicitly listed in the bpqaxip.cfg file.  The default behavior can be modified with these commands:

 

            DONTCHECKSOURCECALL        ;This option allows entries in the NODES table from

                                                                        ;stations sending you nodes broadcasts without the

                                                                        ;corresponding node being configured in bpqaxip.cfg.

 

            AUTOADDMAP                               ;This option automatically adds the node call and

                                                                        ;address of a node for which you do not have a

                                                                        ;pre-arranged fixed entry in bpqaxip.cfg.  If the

                                                                        ;option DONTCHECKSOURCECALL is specified then the

                                                                        ;AUTOADDMAP option is ignored.

 

BPQ32_410i_2009Apr01:

 

AGWtoBPQ.exe to 1.2.1.1 correcting a buffer overflow problem that can arise when using UIDX Bridge to transmit dx beacons.

 

BPQAXIP.dll to 1.13.4.1 correcting a problem where a syntax error in a MAP record could cause a loop.

 

BPQTelnetServer.exe to 2.1.4.1 adds an option “DisconnectOnClose=1” to close the telnet session when the user disconnects from the switch.

 

BPQ1632.dll to 1.1.2.1 and BPQ1632.exe updated to correct a problem when used with JNOS.

 

BPQ32_410i_2009Feb07:

 

BPQ32_410h_2009Feb04 is withdrawn due to a problem with the KISS interface which is corrected in this release.

 

BPQ32.dll to 4.10.9.1 corrects a problem with the KISS interface.  Window position and size are saved and restored.

 

Bpqaxip.dll to 1.13.3.1.  Window position and size are saved and restored.

 

..\RelatedFiles\CC_Cluster folder removed.  Needed CC_Cluster files should be obtained instead from the CC_Cluster Yahoo Group.

 

..\RelatedFiles\BPQ_WinFbb701-35A folder removed.  Needed WinFbb701-35A files should be obtained instead from the files section of the BPQ32 Yahoo Group.

 

..\RelatedFiles\BPQHostModes folder removed.  Updated contents moved to main files and docs section.

 

TLN.dll to 1.6.1.0 corrects a problem in WinFBB701-35A which caused corruption of the callsign of the connecting station, resulting in corrupt entries being sent to the WP database.  The updated DLL is included in WinFbb701-35A-Accumulated.zip in the BPQ32 Yahoo Group files section.  The updated DLL should be placed in “C:\Program Files\WinFbb\Drivers\”.

 

BPQVirtualCOM.sys to version 1.0.1.1.  resolving a CPU utilization issue with WinLink Classic.

 

TFWIN.DLL to 1.2.0.1 corrects 100% CPU utilization problem in WinFBB700i.  The updated file is included in FBB-Win700i.zip in the BPQ32 Yahoo Group file section.

 

The following updates are related to running BPQ32 minimized to the task bar or to the notification area (system tray):

 

            AGWtoBPQ.exe to 1.1.0.1

            BPQ32.dll to 4.10.8.1

            BPQ32.exe to 1.1.0.1

            Bpqaxip.dll to 1.13.2.1

            Bpqether.dll to 1.3.0.1

            BPQHostModes.exe to 1.1.0.1

            BPQIPModule.dll to 1.2.1.1

            Bpqstatus.exe to 1.0.5.1

            BPQTelnetServer.exe to 2.1.3.1

            BPQTNC2.exe to 1.1.0.1

            BPQTerminal to 2.0.5.1

            BPQtoAGW.dll to 1.5.0.1

            Bpqvkiss.dll to 1.3.1.1           

 

BPQ32_410g_2008Dec25:

 

Bpq32.dll to 4.10.7.5

 

            Corrected a failure with Win98 when using the ‘re-configure’ option.

            Corrected the nodes count in the Stats display.

 

BPQHostModes added to the RelatedFiles folder allowing software which expects to see a real TNC in either Kantronics or WA8DED Host Mode connected to a serial port to be used with BPQ32.

 

BPQ32_410g_2008Dec09:

 

The installer now detects a running instance of BPQ32 during an install, upgrade or uninstall.  It issues a warning and aborts without making any changes.

                       

Bpq32.dll to 4.10.7.3

 

bpqvkiss.dll to 1.2.1.1

 

BPQtoAGW.dll to 1.5.0.1

 

Bpqether.dll to 1.3.0.1

 

Bpqaxip.dll to 1.13.1.1

 

BPQIPModule.dll to 1.1.0.1

 

            Corrected a failure which could occur depending upon the order in which programs were started.

            Corrected a failure to detect a crashed BPQ32 process.

            Corrected a TNC2 usage problem.

            Node commands enhanced to request a list of nodes sorted by callsign.  Commands available are:

                        N         Displays nodes sorted by alias

                        N T      Displays nodes by alias with non-zero frame counts

                        N *      Includes nodes with a # alias prefix

                        N C     Displays nodes sorted by call sign rather than alias

                        N C T  Same as N T but sorted by call sign

                        N C *  Same as N * but sorted by call sign

            BPQ32.dll Console Window now offers the following action drop down list:

                        Save Nodes to file BPQNODES.DAT

                        Save Nodes, Re-read bpqcfg.bin and reconfigure node

                        Clear Nodes, Re-read bpqcfg.bin and reconfigure node

                        Diagnostic Dump to file BPQDUMP.

 

BPQ32_410f_2008Nov17:

 

Bpq32.dll to 4.10.6.7

 

            Add IP Gateway

            Add Multiport DIGI capability

            Fix potential hangs if RNR is lost

            Fix problem if external driver fails to load

            Put pushad/popad round _INITIALIZEPORTS (main.asm)

            Add APIs GetApplCallVB and GetPortDescription (mainly for RMS)

            Route quality is updated if Port quality is changed

            Add Reload Options, plus menu items for DUMP and SAVENODES

 

BpqCfg.exe to 1.0.3.1

 

            New System Param in bpqcfg.txt:

            IPGATEWAY=1        ; Enables IP over ax.25 <> IP over Ethernet Gateway

            New Port Param in bpqcfg.txt:

            DIGIMASK=65535   ;Digi UI Frames to all ports.  DIGIMASK overrides DIGIPORT

            Configuration line length limit increased from 100 bytes to 250 bytes

 

Bpqaxip.dll to 1.13.1.1

            Add Linux-style config of broadcast addresses:

                        ; Config file for BPQAXIP

MHEARD ON

                        UDP 10093

                        BROADCAST NODES

                        BROADCAST QST

                        MAP BPQ 127.0.0.1

                        MAP AE5E example.com UDP 10093 B

                        MAP G8BPQ-2 example.net UDP 10094 B

                        MAP GM8BPQ-2 example.net UDP 10094

                        MAP N9PMO-2 example.org UDP 10093 B

            Any message address to a call defined in a BROADCAST line will be sent to each map

            Entry with a ‘B’ parameter.

 

            The example configurations have all been converted to the new format, however the previous

bpqaxip.cfg style will continue to work (for now).

 

            The AXIP MHEARD window generated by Bpqaxip.dll now includes in its final column a ‘K’

            if you are receiving ‘keepalive’ packets from the particular node heard.  In most cases keepalive

            is unneeded traffic.  You may care to contact the sender about possibly turning it off.  The AXIP

            MHEARD window displays a maximum of 40 entries, with the oldest ones dropping out.

 

            The AXIP Resolver window generated by Bpqaxip.dll provides an Update drop down list with

            the option to ‘ReRead bpqaxip.cfg’ (ideal after you have edited that file) or to temporarily add

            an entry (it does not get added to bpqaxip.cfg).

 

BpqTelnetServer to 2.1.2.1

            A new configuration parameter:

            LOGGING=1

            Will enable logging on startup, which will include the IP address.  Logging can

            also be toggled via the Actions drop down menu.

 

BPQStatus.exe to 1.0.3.1

                        Added an option to display IPGateway ARP table.

 

BPQTerminal to 2.0.4.1

                        Added an option to strip or not strip Linefeeds to deal with ill behaved applications

 

Bpqether.dll to 1.1.0.1

                        To support changes described above

 

BPQIPModule.dll to 1.1.0.1

                        To support changes described above

 

BPQtoAGW.dll to 1.5.0.1

                        To support changes described above

 

Bpqvkiss.dll to 1.2.1.1

                        To support changes described above

 

BPQ32_409e_2008Jul27:

BPQTerminal.exe to 2.0.3.1.  Lines not terminated with a newline were not displayed.

BPQVirtualCOM to 5.0.2195.6717.  Update pertaining to MSYS.

BPQtoAGW.dll to 1.5.0.1

bpqvkiss.dll to 1.2.1.1.  Update pertaining to MSYS

bpqether.dll to 1.3.0.1

bpqaxip.dll to 1.12.1.1

bpq32.dll to 4.10.5.4.  Fix for a missing SSID on an unproto packet as well as a possible crash if a Netrom “Disconnect ACK” is received when not expected.

 

::: Made with CoffeeCup : Web Design Software & Website Hosting :::