Subj : Squish limitations
To   : Paul Lentz
From : Mike Tripp
Date : Wed Mar 19 2008 11:12 am

Hello Paul!

19 Mar 08 02:10, Paul Lentz wrote to Mike Tripp:

PL> I'm actually running it on a semi-modern Winders98Se machine with like
PL> only 256 (or maybe it's 512, can't remember) mego-rams... but I might
PL> toy with the buffers statement and see if it does anything else.

Scott basically tried to support whatever the environment had to offer...which
is why the 16-bit DOS, 32-bit DOS, OS/2, etc. versions as released all had
different limits.  Don't know about the Win32 flavor, myself, as it was
released solo, after the general release of the others...sort of a "So long and
thanks for all the fish", before he left Fido.

PL> The main point is tht I'd like Squish to at least pretend to handle
PL> them and not create annoying renamed .LNG files I have to delete by
PL> hand from time to time. I know I don't want to read those longy things
PL> my own self.

In that case you just need to add the undocumented Winders command "DEL *.LNG"
somewhere in your mail processing routine's tossing block.<g>  Seriously, if
they're breaking Squish, they're probably gonna break something else you're
running later once you adjust Squish to pass them further into the food chain.

I've also had good luck negotiating with the originator of the long
messages...since it seems that most don't mind folks actually being able to
read them.  A little whining about the BinkD FAQ got it split down to chunks
that DOS GoldEd could swallow at the source. I run the DOS version under DOS,
OS/2, and Windows...since it is the only one that will.<g>  Before that, I'd
have to switch to the OS/2 box and fire up GoldEd/2 just to kill the offending
message in order to regain normal access to the area everywhere else.

.\\ike

--- GoldED/2 2.50+
* Origin: -=( The TechnoDrome )=- Austin,TX 512-327-8598 33.6k (1:382/61)