There's a new Development Release that contains a work-around for APRS messaging clients that don't properly support acking messages (like the new IRC 'bot).
With this version, if you see a message like:
ackXX - Bogus (non)ReplyAck
in a chat window, it means that the remote system dropped the required } from their ack message.?? APRSIS32 will now accept this, provided that the XX is expected, and will go on with the next message to that system.? Whenever you see this, please notify the remote system owner that they should read:
Or drop a message here with the station you were chatting with and I'll try to follow up with the author/implementer of the remote client.
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
