Hi, Paul.

PE> FM>  OK, forget that, saw your reply to Bob.
What was the bug?

PE> A character would get repeated on a message with a 
PE> terminator (only rarely generated).

Oh. I don't think I ever saw it.

PE> FM> Did I tell you I saw what was giving the performance hit? When the US

PE> No.

PE> FM> feed was restored and I got that huge download, I decided to do
PE> FM> something else while it was converting to QWK. On my Windows desktop I
PE> FM> have a prog which continually monitors resources, disk space, etc. I
PE> FM> could see the disk space going down in only 4k chunks. Presumably
PE> that's
PE> FM> what you've fixed?

PE> I don't know.  Tell me if the same thing happens with this version,
PE> it's a long time since I did the optimizations.  I did it based on
PE> a profiler though.

Not installed yet, will do so today or tomorrow. I may not be able to
give you instant feedback though, it needs a fairly big packet to really
see that as my normal packets are processed fast enough that I wouldn't
have much time to switch back to the desktop to see it. Hmmm, if do the
download/unpacking/conversion in a window instead of full-screen I
should see it. Plus I need to have less than 10Meg free disk space, as
below that it shows the space in K, above that in Meg and I don't see 4k
changes. At the moment I do have < 10M free. :-(

I'm not sure that a profiler would show you the problem. If it's just
timing your *code* execution, it may not indicate where *DOS* is taking
a long time, such as in file I/O.

Regards, FIM.

 * * Programming: It's not a job, it's an adventure!
@EOT:

---