BL> The most common editor is qedit, and that will crash on 200K.

 DB> Is that the "qedit" that became the "SemWare
Editor"? The copy
 DB> I have here announces itself as: "QEdit Advanced v2.15 August
 DB> 1991". Yes, that's for DOS (plain, vanilla, 16-bit, no tricks).
 DB> I created a 387Kb text file (concatenating my log files
 DB> together a few times) and QEdit loaded the file in a flash - in
 DB> its entirety, without problems. 

  Qedit (that did become the semware editor and doubled in size) uses
low DOS for its files. Depending on what else you have running at the
time, it can handle files up to about 550K... less if you have other
things like an OLR running.

 DB> Whether or not it's economically viable to be sending such
 DB> messages around the world is irrelevant - your editor shouldn't
 DB> crash on a file that small. 

  Irrelevant? What a nice way to reply to my complaint. Can you solve 
all the problems of the world the same way? Does saying that famine is 
irrelevant make people eat better? I saw a message by Michael Butler 
recommending that all messages be truncated at 12K to limit costs. The 
problem was that people were sending UUencodes split up as you split 
your 200K, even so.

 DB> your editor shouldn't crash on a file that small. 

  Don't tell me what I want to read offline. I *designed* pkt2qwk to
bark on 30K because that's all I want it to pass. A 30K file is
roughly 600 lines, and that's more than enough on *any* subject.

 DB> Geez, after complaining about how anal Paul is for adhering to
 DB> FTSC specs, you're really working overtime to rip the crown
 DB> from him... 

  I still consider that sendimg an unsolicited 200K Australia-wide is
the height of irresponsibility in email.

Regards,
Bob
___ Blue Wave/QWK v2.12
@EOT:

---