RE: [BPQ32] BPQ32 and Winpack 
To connect from the node/bpqterminal to WInpack you need to set an APPLMASK in the BPQHostModes config, corresponding to the APPL number in the APPLICATION definition for PMS. Remember that the APPLMASK is a bit map, so APPL 1 = ApplMask 1, APPL2 = 2, APPL3 = 4 , APPL4 = 8, etc..
Having a separate bpqaxip.cfg and bpqaxip.dll is obsolete. All the .dll drivers are lijnked into bpq32.dll rather than being separate files, and all the driver config is in bpq32.cfg. I suspect the comments in some of the sample configs need updating. The latest docs are online - http://www.cantab.net/users/john.wiseman/Documents/BPQAXIP.htm for the axip info.
I don’t think it will help to run AGWPE. Danny was suggesting to you could run AGWtoBPQ.exe, which allows you to use programs written for AGWPE to be used with BPQ32. But as you have UIView32 going, you probably don’t need that either.
From: BPQ32@yahoogroups.com [mailto: BPQ32@yahoogroups.com ] On Behalf Of g4fvg
Sent: 04 October 2011 21:30
Subject: [BPQ32] BPQ32 and Winpack 
Thanks John and Danny for your updates.
Rebooting XP either side of clearing the registry entry:
has solved the Vcomm driver problem and I have now got Winpack16, Uiview 32 and BPQ32 working all at the same time by using BPQHostmodes.exe.
[My original understanding of BPQ1632 was that this allowed Windows16 programs to talk to BPQ32, rather than only just DOS programs. Sorry John and thanks for correcting me].
I have still to get the bpq terminal to work via the virtual port onto my Winpack pms, when typing 'pms' into the node.
(It comes up with Sorry, Application PMS is not running; even though I can see BPQ received packets on the winpack screen.)
After that, the next thing to get going is to get BPQ32 talking via the network card to the internet... however, I have already spotted a slight problem in that the 4th line of BPQ32.cfg refers to a file bpqaxip.cfg which I cannot find.... :-(
I also cannot find the BPQAXIP.DLL file on the installer setup (or anywhere else on my C: drive for that matter) that the bpq32.cfg port 1 (that I have changed to port 9 in my case) refers to.....
[I've basically added my callsign and two additional KISS TNC ports to the Large without AGWPE example....)
However, I might try getting my head around the 'WITH' agwpe example as suggested by Danny... :-). It might save having to use virtual ports altogether and allow the BPQ32 terminal to talk 'internally' to the winpack program via the bpq32 node.
Oh well, a bit more downloading and reading of documents is probably required. Hopefully, there won't be too many questions afterwards!!
--- In BPQ32@yahoogroups.com, "Danny PD0SNK" <pd0snk@...> wrote:
> Hi all..
> When i wrote to use agw i ment use agwtobpq instead of agw.
> this way you can use all fine options of bpq and use the agw option in
> winpack and ui-view16 to interface to the rs232 kiss ports.
> for ar-cluster i use agwtobpq and it works great this way i can set the
> appl number to 2.
> this is decsribed in the bpq doc by John.
> 73 Danny PD0SNK
- Thanks John for the further info and I will have a go at updating my BPQ32 after sending this!
For Ed: Back on 7th November 2014, I tried the emulator but found the separate PMS program for Winpack did not work... quote:
An external user has now found that, when I use the TNCport emulator in the bpq32.cfg file for Winpack on comport 8, when they connect and type FVG, Winpack [in TF2.7b mode] replies that no PMS facilities are present on that channel [and it opens up a separate terminal screen]. However, if I use BPQHostmode, they can connect to my Winpack pms!
- - -
As a result, I have remained with BPQhostModes [as long as John keeps it working with new BPQ32 versions... :-)
Of course, if you don't use the separate PMS program within Winpack, then you should have no problems....
Any more updates Ed?
---In BPQ32@yahoogroups.com, <john.wiseman@...> wrote :
The latest code still supports TF2.7b Host Mode, but it is via a TNC emulator built into bpq32, not a separate program. BPQHostModes still works, but is no longer actively supported.
The BPQ interface in Winpack is to the DOS BPQCode, not BPQ32. You need to use the DED emulator in BPQ to ruin Winpack. My Config is