Subj : Reply Splitting To : William Mcbrine From : Ken Hrynchuk Date : Wed Oct 31 2001 02:03 am William Mcbrine wrote to Ken Hrynchuk on 10-28-01 10:17: -=> Ken Hrynchuk wrote to William McBrine <=- KH> I've noticed, in this version, that there's a limit to the size of the KH> reply that's being split, after which truncation will take place. The WM> Technically this limit (available memory) applies to all versions, but WM> you'd only notice it in the XT version, since that's the only one that WM> experiences significant memory constraints. I've used the Linux version WM> of MultiMail to enter and split replies that were over 40 megs long. Thanks for the detailed explanation, William. It's good to know that the PM version will probably do the job, if need be. WM> Of course, it should be possible to redesign the split function so that WM> it doesn't require the message to be in memory, but I'm not sure that WM> would be worth the trouble. I also suspect that there wouldn't be much of a need for you to do so. WM> I must say, I'm surprised to hear of someone trying to post WM> multi-thousand- line replies with the XT version. What the heck are WM> these things? All the MP3s and movies that I've been enjoying on the 4.77MHz box. :) Actually, this stems from a penchant of mine for running, testing and tweaking backwardly-compatible software. I'm a firm adherent to the KISS principle, and will only attempt to 'upgrade' when absolutely necessary. When I ran into the limit, I thought it would be prudent to let you know. KH> Also, it's no biggie, but I must admit that I do miss the ability to KH> 'prompt to save read pointers'; I found it quite handy for testing. KH> WM> Heh. I didn't think anyone had ever used that but me, and I gave i up WM> some time ago. (Now I habitually press 'U' after reading something that WM> I want to save.) Understood; and, thanks for not placing your own needs above those of your users. Ken *** MultiMail/XT v0.41 --- TriToss (tm) Professional 11.0 - #108 * Origin: The Hall of Fame * Canton, Ohio * 330.456.0483 (1:2215/300.0) .