The only reason to use the AGWPE program would be if you are using sound
card modems. BPQ32 has an interface to AGWPE for that very reason
If instead you use a TNC in KISS mode, then BPQ32 will drive it directly
without any need for AGWPE.
To do this you need to start AGWtoBPQ.exe, it will bring up everything
it needs to do the job. Of course you do need to properly configure
bpqcfg.txt (and then compile it with bpqcfg.exe) as well as create
bpqaxip.cfg (but this only if you intend to use AX/IP/UDP for Internet
connections to other machines).
The documentation is not as good as it should be, but you still should
read it. I would say, knowing little or nothing about WinFBB, that the
usage and configuration is likely to be very similar to AR-Cluster,
which I tried to explain in detail.
> > I think BPQtoAGW.EXE is not intend for BPQ32 to interface with
> WinFBB7.01.35 as Ron has mentioned before. The easy way to interface
> WinFBB7.01.35 is to configure the port to use AGW interface (this will
> use the AGW.DLL from WinFBB7.01.35) then your WinFBB can interface
> with AGW Engine. If you wish you can interface both of AGW Engine and
> BPQ32 in the same time which I have tried out b4.
> Hello Sunan.
> Just to clarify, do you mean you need to load the AGW software to have
> it drive the serial port instead of having BPQ32 drive the serial
> port, for the port/tnc that WinFBB32 is going to use?
> I haven't used AGW before, so I am a bit unclear here.
> Lane, VE7IHL