Hello Bob.
ML> folks *don't* have PktSort nor know how to use it, so the messages
ML> don't get seen on that system (or its downlinks).
BJ> If squish is choking on the message size of recent large messages,
BJ> then you have it set to run with smaller buffers than it can run
BJ> with. And therefor, you are choosing to limit what messages are
BJ> processed on your end based on message length. Based on your tear
BJ> line (timEd/2), you're running under OS/2.
It's not for me, Bob. It's for 2 of my downlinks that are running small
DOS systems with limited memory. Both have questioned about the
".lng" packets that Squish is leaving in their inbounds. I've
got no problems with long (or ar least reasonable long) messages. SquishP
does fine with them. (Though I've seen it choke on a particular messasge
some joker posted that was almost 350k in length of UUEncoded junk. But
that wan't in this Echo and it was a long time ago.
Best regards,
Marc
--- timEd/2 1.10.y2k+
* Origin: Sursum Corda! BBS New Orleans 1-504-897-6006 USR33k6 (1:396/45)
SEEN-BY: 633/267 270
@PATH: 396/45 106/2000 633/267
|