RE: [BPQ32] BPQ32 and Winpack 
Ok I can do 40 30 and 17 let me know where you want me….. 73 jerry
I cannot do 80 metres, not enough room on the lot, and no tower it is a rental house. I could linear load the radiator and reduce the length
to around 90 feet, but the trees height is just at 40 feet or so.
Linear loading of 20-30% will reduce the radiator efficiency of only 2-5%, I usually use 3" spaced ladder line..
I have antennas on 40, 30, and 17.
I swept the antenna with a Rhode and Schwartz FSH spectrum analyser;it has about a -20 db return loss on 20 (low vswr),
but I am not sure it would be efficient on that band it is a parallel dipole with 3 wires, closely spaced, I am sure there is some mutual inductance.
3.5 would not be usable, I do not use an antenna tuner.
----- Original Message -----
Sent: Thursday, October 06, 2011 3:58 AM
Subject: RE: [BPQ32] BPQ32 and Winpack 
Jim… Let me know when you want me on 3580 on Pactor… 73 jerry
John does the switch support the dragon modem? I just received mine from Martin. Pity our regs do not all that on ham bands but it is ok on MARS.
Your tracker code works great at my station. I like their stuff
Sent from my iPhone
On Oct 5, 2011, at 2:47 PM, "John Wiseman" <john.wiseman@...> wrote:
APPLMASK is used by nearly all BPQ32 programs, not just HostModes, so it is worth getting to grips with it. APPLMASK has a bit set for the Application number(s) the program supports. Written in Binary, the Masks are 00000001 00000010 00000100 00001000 etc. This may seem a convoluted way of doing it, but a program can support more than one application. For example BPQMailChat supports both a BBS and a Chat Server. So if the BBS was APPL1 and CHAT APPL 4, the applmask would by 00001001 = 9.
BPQMail could be used instead of WINPack, but people often like to stick with programs they are familiar with. All have their advantages and disadvantages.
The sample AXIP config is a section of the bpq32.cfg file. The DLLNAME parameter refers to the AXIP driver, even though it is part of BPQ32.dll and not a separate file. It would work just as well with DLLNAME=BPQAXIP, but it accepts either for backward compatibility with old config files. I see that is can be confusing, and maybe I should change it to something like DRIVER=.
Thanks John for the latest assistance....
(further comments between your reply)
--- John wrote:
> 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..
** Initially, I was confused by the above but then found the APPLMASK part of the main BPQ Host screen. 'Luckily', my PMS application is still the default nr 1, so the mask setting was the same 'figure'. Not sure about the words 'APPLMASK is a bit map' and then showing that the next required figure increases by double the previous. No doubt there is something in some of the recent documentation that I have still to read! [Should I wish to add anything else of a 16 bit nature!]
Suppose that BPQmail will do the job of a Winpack PMS.....
= = = == = =
> Having a separate bpqaxip.cfg and bpqaxip.dll is obsolete. All the .dll
> drivers are linked 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
** Hmm, thanks John and will study hard!
[However, I notice that your document above points towards a
Sample Config file for BPQAXIP
... and also refers to a missing BPQAXIP.DLL, so might have to look elsewhere in the documentation for info/solution.
= = = =
> 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.
Now that Winpack16, BPQ32 and UIView32 are all working over the radio TNC, I will progress much more cautiously!
= = = = =
Until the next time, with many thanks
- 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