mark lewis wrote in a message to Roy J. Tellason:

 ml>> if you can handle MIME encoded email, i'll forward what i was sent
 ml>> to you in email... its some text about the situation and then three
 ml>> or four pictures... its multipart MIME encoded stuff...

 RJT> Not a problem.  Shoot it at incoming%tanstaaf{at}frackit.com,  I
 RJT> hope it's not terribly large.  Anything up there around the
 RJT> size of a floppy or so will give me trouble.

 ml> i'm not sure how large it is in total... i'll give it a shot and if
 ml> necessary, you'll let me know and i'll break it up into smaller
 ml> parts with one pic per part...

I start getting into trouble up around a couple hundred K or so...

The symptom amounts to a "clogged pipe",  which basically means
that I can't get anything else until I finish that particular transaction. 
Can't flush that file out of the queue,  etc.  Or so I'm told.

There were a couple of things a while back that were 3-5M,  and that got me
really jammed up for a while!

 ml>> i don't want to spoil it for others... and words just will not
 ml>> depict the true situation... you've got to see the pictures
>

 RJT> Ok,  I will be looking forward to it.

 ml> on its way shortly... my system currently has wordpad wading
 ml> (literally) thru a 65MEG log file of a tcp/ip trace... i'm trying
 ml> to figure out why my latest upgrade of OS/2's INJOY is not 
 ml> redialing when my isp drops my connection... hopefully i'll locate
 ml> the entries in the trace file...

Yikes!  That's pretty big.  Must be a lotta details in there.

I find that some stuff gets cumbersome to deal with when you get up over a
meg or so,  here,  even with editors and whatnot that will deal with that
sort of thing.  Maybe finding bits that aren't needed and chopping them out
will help to cut the size of that down.  That's an approach that I've used
with some success in the past...

---