PM>> Have you tried running SQPACK against it. Packing the

 PM>> message base may help, and it can't hurt!



 AM> No, I don't think so.  It's either sqpack or sqfix that modifies the

 AM> last read pointers of Maximus though, which means I then have to go into

 AM> max and read the last message in each echo to reset them before adding

 AM> anything more to the messagebase.  A bit of a snafu.  In fact I

 AM> discovered just how delicate max's last read pointers are in this packet

 AM> - I'd been looking through my netmail area last night and went back to a

 AM> particular message so that I could resend it - about 15-20 message

 AM> back...  Low and behold, there are over 20 messages in my next qwk

 AM> packet! :(  Almost all old ones...  Stupid unintelligent software.



I doubt that sqpack is the culprit. Most sysops would run it fairly
regularly and their users would be jumping up and down if it reset the last
read pointers.



Wouldn't it be less hassle to run PQWK to convert your packets to QWK?



 PM>> In that case you're on your own. You could always collect

 PM>> the Squish echo and see if anyone has some more ideas. If



 AM> I'm a PC user, not a masochist. ;)



Not a masochist? This from the man who runs the worlds most complicated point setup!



 PM>> you find anything, let me know. I'd like to see if I can

 PM>> break the 100 msgs/sec mark :-)



 AM>  bits of it go flying off all over the place>



Nah, it'll take more than one measly pin :-)





Paul



--- GoldED/2 2.42.G1114