In a message to Anthony about "minpos2", Paul said:

PE> I've just created new versions of MINPOS2 and MINOSQWK which rely on
PE> Squish 1.10 instead of 1.01.  Squish 1.10 is better because it has a
PE> message size limit (according to the instructions), of 64k
PE> [Grimsley, just shut the fuck up will you] instead of 16k.

Wonderful news.

PE> You need MINOSQWK,

Why?  What I have now works.  I INTEND TO KEEP IT THAT WAY UNTIL 1.11 IS
RELEASED.  NFSE

PE> Anyway, I will be sending mail to you that is greater than 16k, and
PE> squish won't handle it if you persist with your current setup.

What the hell do you mean _persist_ with my current setup?  Lose the
attitude, dude.  

The solution is simple.  Don't send me any messages over 16k.  You've
managed to avoid it somehow since BBS time immemorial, so I'm sure you
can wait a bit longer until 1.11 is out.

PE> When it can't toss a large message, it may rename the whole
PE> packet to *.BAD and you lose the rest of the mail that was
PE> in that packet, I can't remember.  The short story is that
PE> I think you should move to a "known" state.

I'm already in a KNOWN STATE - a state that is working FINE thank you
very much.

PE> Your installation was haphazard instead of from the instructions.

My installation was EXACTLY according to your intructions, apart from
details that affect you not.

PE> This also applies to anyone else using Squish 1.01, with
PE> the exception that if you have already installed from
PE> MINOSQWK, you only have to replace the squishp.exe and get
PE> rid of "-U" in the unzip extract command in compress.cfg.

You might have guessed by this stage that i have no intention of being
held to ransom by the Paul "Upgrade your software NOW or else" Edwards
crusade.

'tnt, Amfony.      
--- Maximus/2 2.01wb