[nos-bbs] Update - JNOS development (or lack thereof) and PK232 ...

[Maiko Langelaar (ve4klm)]

Hi Mark,

> Have you thought to call AEA ?

I wouldn't know what to ask them. That's the problem.

> They are aware of your project and whenever I've called them
> for help they have been very willing.

That's nice to hear, but I hope they realize JNOS is 'obsolete' :)

Here's the latest happenings. I use AirMail to connect with JNOS. I
have a simple message waiting on JNOS for AirMail to pickup. I can pick
the message up using the AirMail telnet client and B2F no problem. It
works consistently, proper checksum values, everything.

If I try to use the AirMail HF client (dxp38) to JNOS (pk232) the
exchange works nicely until the tail end of the binary (FBB) xfer,
where AirMail complains of a missing STX/EOT, binary error. The
really really really stupid thing about all of this is that if I
look at the data sent during the telnet forward and compare it to
the data being sent out the modem during the pk232 forward, it is
COMPLETELY IDENTICAL to the byte, the checksums match, everything
looks fine !

I'm at my wits end I think. My next try out is to connect the
PK232 back to the AirMail client, have the Airmail client init
the tnc to pactor mode, then I'm going to disconnect the tnc
from Airmail back to the JNOS system, and see if taht works.

IF it does, then I'm going to see what pk232 parameters have
changed and what is different (or missing) from the inits that
I did when I started this.

My guess right now is that a byte or two is being converted or
'added to' within the pk232 before it sends stuff out.

Incoming PK232 forwards work very nicely. If there is a mail to
be delivered from Airmail to JNOS, it's been pretty good.

That's the latest from PK232 development ....

:)

Maiko