8842Re: [BPQ32] RE:Fix for Outpost Telnet Probem - was Winmor TNC Whack-a-Mole (Outpost Issue?)
- Jul 7, 2012Installed the new DLL yesterday and so far so good. Also, my telnet users are getting good with the Enter key so that doesn't hurt.
I did have one crash shortly after installing the new DLL but it was good thereafter for close to 6 days before I installed the latest version. The Windows error message was the same as before: Switch BPQ32 Corrupt Raw Message.
On 7/6/2012 6:20 AM, John Wiseman wrote:The BPQ32.dll I uploaded last week was not built correctly, and may cause stability problems with some confgurations. If you installed it. plese replace with this:73, John
From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of John Wiseman
Sent: 01 July 2012 22:08
Subject: RE: [BPQ32] Re: Winmor TNC Whack-a-Mole (Outpost Issue?)
Thanks, Steve.That is encouraging. Can you try this? - it should fix the problem with long lines.Remember bpq32.dll goes in the system32 folder.73,John
From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of kb1tce
Sent: 01 July 2012 19:17
Subject: [BPQ32] Re: Winmor TNC Whack-a-Mole (Outpost Issue?)
Well John, we're now thinking that's it.
We checked one of the messages from our "crasher" and it consisted of two lines. The second line by itself was about 500 words and 1000 bytes.
That message was crashing W0ECM's local BPQ32 when sending from Outpost. He had received it ok (by HF/Winmor) but when he tried to forward it to me he got the crash. He then inserted a pile of carriage returns and everything went fine.
We were fooling ourselves with the brief test messages on Outpost 2.4 because we didn't have messages that contained the real problem.
Hopefully that's it as far as the diagnosis goes. I would be quite willing to try your test version that addresses this.
--- In BPQ32@yahoogroups.com, "John Wiseman" <john.wiseman@...> wrote:
> I recently found an error in the Telnet code which could cause a problem
> with sending messages from Outpost with a very long list of TO calls (around
> 30, depending on the length of each address). It could also cause problems
> with very long lines (greater than 500 or so bytes) in the message body. If
> either could apply in your case I can send you a test version to see if it
> fixes the problem.
- << Previous post in topic