¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Vintage Packet and BPQ-KISS


 

I am having a blast with old dos/win packet apps. I feel like we have
lost so many powerful pieces of software due to "progress". There
were some really phenomenal packet terminals and BBS programs that
have been abandoned. They were not inferior, but just waning interest
meant that the code base was not kept up with so that they run on
modern systems.

I would like to try to get old BPQ working with DOSFBB. I have DOSFBB
running 100%, but
would like to add NETROM. I have been having issues with getting old
BPQ playing with KISS
TNC's. On a real machine I was able to get the TNC to transmit, but
not receive. On a virtual machine I did not get either TX or RX.

However, I was able to get some error message from direwolf about mal
formed KISS frames.
I could not get BPQ code to work with a real TNC or direwolf, but I
think this info can help:

#################### DIREWOLF ERROR OUTPUT #####################

<<< Data frame from KISS client application, port 15, total length = 16
000: f0 ae 82 6c a8 94 a2 ea 96 a2 6c aa a0 40 6d 3f ...l......l..@m?
Invalid transmit channel 15 from KISS client app.

Are you using AX.25 for Linux? It might be trying to use a modified
version of KISS which uses the port (channel) field differently than the
original KISS protocol specification. The solution might be to use
a command like "kissparms -c 1 -p radio" to set CRC none mode.
Another way of doing this is pre-loading the "kiss" kernel module with
CRC disabled:
sudo /sbin/modprobe -q mkiss crc_force=1

################################################################

Also, I am wondering if BPQCODE needs another COMBIOS type COM port
driver loaded
before running BPQCODE -- that may be the issue as I am running BPQCODE to
bear iron.


--
Thanks,
Chris Maness


 

BPQCODE accesses the KISS serial port by directly accessing the hardware and using interrupts, not via any BIOS or OS interface. If your DOS emulator can map hardware I/O on the client side to software access to a COM port on the host side then it should work.

The top 4 bits of the KISS control byte is the channel number on multichannel TNCs. So the displayed frame is either corrupt or is from BPQ configured to use channel 15.

73, John

On 06/06/2024 18:37, Christopher Maness wrote:
I am having a blast with old dos/win packet apps. I feel like we have
lost so many powerful pieces of software due to "progress". There
were some really phenomenal packet terminals and BBS programs that
have been abandoned. They were not inferior, but just waning interest
meant that the code base was not kept up with so that they run on
modern systems.

I would like to try to get old BPQ working with DOSFBB. I have DOSFBB
running 100%, but
would like to add NETROM. I have been having issues with getting old
BPQ playing with KISS
TNC's. On a real machine I was able to get the TNC to transmit, but
not receive. On a virtual machine I did not get either TX or RX.

However, I was able to get some error message from direwolf about mal
formed KISS frames.
I could not get BPQ code to work with a real TNC or direwolf, but I
think this info can help:

#################### DIREWOLF ERROR OUTPUT #####################

<<< Data frame from KISS client application, port 15, total length = 16
000: f0 ae 82 6c a8 94 a2 ea 96 a2 6c aa a0 40 6d 3f ...l......l..@m?
Invalid transmit channel 15 from KISS client app.

Are you using AX.25 for Linux? It might be trying to use a modified
version of KISS which uses the port (channel) field differently than the
original KISS protocol specification. The solution might be to use
a command like "kissparms -c 1 -p radio" to set CRC none mode.
Another way of doing this is pre-loading the "kiss" kernel module with
CRC disabled:
sudo /sbin/modprobe -q mkiss crc_force=1

################################################################

Also, I am wondering if BPQCODE needs another COMBIOS type COM port
driver loaded
before running BPQCODE -- that may be the issue as I am running BPQCODE to
bear iron.


 

On Thu, Jun 6, 2024 at 12:36?PM John G8BPQ via groups.io
<john.wiseman@...> wrote:

BPQCODE accesses the KISS serial port by directly accessing the hardware
and using interrupts, not via any BIOS or OS interface. If your DOS
emulator can map hardware I/O on the client side to software access to a
COM port on the host side then it should work.
Good to know. In this same setup FBB and TSTHOST works just fine with my real
KISS TNC, so that is what has me scratching my head.



The top 4 bits of the KISS control byte is the channel number on
multichannel TNCs. So the displayed frame is either corrupt or is from
BPQ configured to use channel 15.

73, John
What is the default? Here is my port settings:

PORT
ID=KISS
TYPE=ASYNC
PROTOCOL=KISS
IOADDR=3F8H
INTLEVEL=4
SPEED=9600
QUALITY=192
MAXFRAME=5
FULLDUP=0
FRACK=7000
RESPTIME=2000
RETRIES=10
PACLEN=235
MHEARD=Y
PORTALIAS=DIGI
DIGIFLAG=1
MINQUAL=162
UNPROTO=QST-1
UNPROTO=MAIL-1,XXXX,YYYY-4 ; DEFAULT UNPROTO ADDR
ENDPORT

Also, I read in the docs that PAC2 should work with a COMBIOS driver,
so trieed ESS 1
and I just get garbage, but I am thinking it may be looking for 7bit
TNC or a different baudrate.

My TNC is set for 9k6b and is a KPC-2 that works just fine with these
other apps.

-Chris KQ6UP


 

With BPQ32 the default is CHANNEL=A but I'm not sure if that is the case with BPQCODE. I'm away sailing at the moment so can't easily check so I suggest you explicitly set CHANNEL=A

What DOS emulator are you using? My recollection is that I got serial ports working with BPQCODE/DOSBOX but again as I'm away from home I can't check, and it is a while since I tried on it.

73, John

On 06/06/2024 21:14, Christopher Maness wrote:
On Thu, Jun 6, 2024 at 12:36?PM John G8BPQ via groups.io
<john.wiseman@...> wrote:
BPQCODE accesses the KISS serial port by directly accessing the hardware
and using interrupts, not via any BIOS or OS interface. If your DOS
emulator can map hardware I/O on the client side to software access to a
COM port on the host side then it should work.
Good to know. In this same setup FBB and TSTHOST works just fine with my real
KISS TNC, so that is what has me scratching my head.


The top 4 bits of the KISS control byte is the channel number on
multichannel TNCs. So the displayed frame is either corrupt or is from
BPQ configured to use channel 15.

73, John
What is the default? Here is my port settings:

PORT
ID=KISS
TYPE=ASYNC
PROTOCOL=KISS
IOADDR=3F8H
INTLEVEL=4
SPEED=9600
QUALITY=192
MAXFRAME=5
FULLDUP=0
FRACK=7000
RESPTIME=2000
RETRIES=10
PACLEN=235
MHEARD=Y
PORTALIAS=DIGI
DIGIFLAG=1
MINQUAL=162
UNPROTO=QST-1
UNPROTO=MAIL-1,XXXX,YYYY-4 ; DEFAULT UNPROTO ADDR
ENDPORT

Also, I read in the docs that PAC2 should work with a COMBIOS driver,
so trieed ESS 1
and I just get garbage, but I am thinking it may be looking for 7bit
TNC or a different baudrate.

My TNC is set for 9k6b and is a KPC-2 that works just fine with these
other apps.

-Chris KQ6UP




 

I am using Qemu. I will set this explicitly and see what happens. I
have it running on a Raspberry Pi now too. DOSFBB is too much for
full emulation on a Raspberry Pi, but no problem to use mubay terminal
to connect through direwolf.

Enjoy your sailing trip.

-VY 73 de Chris KQ6UP

On Thu, Jun 6, 2024 at 11:10?PM John G8BPQ via groups.io
<john.wiseman@...> wrote:

With BPQ32 the default is CHANNEL=A but I'm not sure if that is the case
with BPQCODE. I'm away sailing at the moment so can't easily check so I
suggest you explicitly set CHANNEL=A

What DOS emulator are you using? My recollection is that I got serial
ports working with BPQCODE/DOSBOX but again as I'm away from home I
can't check, and it is a while since I tried on it.

73, John

On 06/06/2024 21:14, Christopher Maness wrote:
On Thu, Jun 6, 2024 at 12:36?PM John G8BPQ via groups.io
<john.wiseman@...> wrote:
BPQCODE accesses the KISS serial port by directly accessing the hardware
and using interrupts, not via any BIOS or OS interface. If your DOS
emulator can map hardware I/O on the client side to software access to a
COM port on the host side then it should work.
Good to know. In this same setup FBB and TSTHOST works just fine with my real
KISS TNC, so that is what has me scratching my head.


The top 4 bits of the KISS control byte is the channel number on
multichannel TNCs. So the displayed frame is either corrupt or is from
BPQ configured to use channel 15.

73, John
What is the default? Here is my port settings:

PORT
ID=KISS
TYPE=ASYNC
PROTOCOL=KISS
IOADDR=3F8H
INTLEVEL=4
SPEED=9600
QUALITY=192
MAXFRAME=5
FULLDUP=0
FRACK=7000
RESPTIME=2000
RETRIES=10
PACLEN=235
MHEARD=Y
PORTALIAS=DIGI
DIGIFLAG=1
MINQUAL=162
UNPROTO=QST-1
UNPROTO=MAIL-1,XXXX,YYYY-4 ; DEFAULT UNPROTO ADDR
ENDPORT

Also, I read in the docs that PAC2 should work with a COMBIOS driver,
so trieed ESS 1
and I just get garbage, but I am thinking it may be looking for 7bit
TNC or a different baudrate.

My TNC is set for 9k6b and is a KPC-2 that works just fine with these
other apps.

-Chris KQ6UP








--
Thanks,
Chris Maness


 

IT WORKS!! Nice, thanks!

-Chris KQ6UP

On Fri, Jun 7, 2024 at 5:24?AM Christopher Maness via groups.io
<christopher.maness@...> wrote:

I am using Qemu. I will set this explicitly and see what happens. I
have it running on a Raspberry Pi now too. DOSFBB is too much for
full emulation on a Raspberry Pi, but no problem to use mubay terminal
to connect through direwolf.

Enjoy your sailing trip.

-VY 73 de Chris KQ6UP

On Thu, Jun 6, 2024 at 11:10?PM John G8BPQ via groups.io
<john.wiseman@...> wrote:

With BPQ32 the default is CHANNEL=A but I'm not sure if that is the case
with BPQCODE. I'm away sailing at the moment so can't easily check so I
suggest you explicitly set CHANNEL=A

What DOS emulator are you using? My recollection is that I got serial
ports working with BPQCODE/DOSBOX but again as I'm away from home I
can't check, and it is a while since I tried on it.

73, John

On 06/06/2024 21:14, Christopher Maness wrote:
On Thu, Jun 6, 2024 at 12:36?PM John G8BPQ via groups.io
<john.wiseman@...> wrote:
BPQCODE accesses the KISS serial port by directly accessing the hardware
and using interrupts, not via any BIOS or OS interface. If your DOS
emulator can map hardware I/O on the client side to software access to a
COM port on the host side then it should work.
Good to know. In this same setup FBB and TSTHOST works just fine with my real
KISS TNC, so that is what has me scratching my head.


The top 4 bits of the KISS control byte is the channel number on
multichannel TNCs. So the displayed frame is either corrupt or is from
BPQ configured to use channel 15.

73, John
What is the default? Here is my port settings:

PORT
ID=KISS
TYPE=ASYNC
PROTOCOL=KISS
IOADDR=3F8H
INTLEVEL=4
SPEED=9600
QUALITY=192
MAXFRAME=5
FULLDUP=0
FRACK=7000
RESPTIME=2000
RETRIES=10
PACLEN=235
MHEARD=Y
PORTALIAS=DIGI
DIGIFLAG=1
MINQUAL=162
UNPROTO=QST-1
UNPROTO=MAIL-1,XXXX,YYYY-4 ; DEFAULT UNPROTO ADDR
ENDPORT

Also, I read in the docs that PAC2 should work with a COMBIOS driver,
so trieed ESS 1
and I just get garbage, but I am thinking it may be looking for 7bit
TNC or a different baudrate.

My TNC is set for 9k6b and is a KPC-2 that works just fine with these
other apps.

-Chris KQ6UP








--
Thanks,
Chris Maness





--
Thanks,
Chris Maness