TID: Mystic BBS 1.12 A48
MSGID: 1:105/420 a8a59c98
REPLY: 1:129/215 64b9908e
TZUTC: -0800
 g0> Could be an combination issue with the message base packer, and someone
 g0> running the packer way more often than they should be.
 g0> Is it happening with your new scan within the BBS or just when
 g0> downloading QWK?  To be quite honest I rarely do any testing of the QWK
 g0> system these days unless someone mentions an issue, so I'll have to do
 g0> some tests.

 I didn't notice it before in the regular message bases when using them before
I started using QWK.  I have switched to just reading the bases without quick
for now since I couldn't keep track of new messages reliably the other way.  I
don't have my BBS up at the moment to test it myself.  I am really thinking it
has something to do with packing message bases as well. I notice the problem
most often when I've gone overnight/a day or two between logging in to
download QWK packets. If its been an hour or two and I log back it it seems to
remember my last read point correctly.
 This problem shows itself on whatever setups both 20forbeers and Quantum
Wormhole are using.  There was a couple other ones as well, but I don't
remember them off the top of m head.

Let me know if I can help in any way to help figure out what is causing the
issue.


iNoNaMouSe
 Hacking at 14.4kbps from your local Victoria's Secret...

... Schizophrenia beats being alone.

--- Mystic BBS v1.12 A48 (Linux/64)
 * Origin: 2o fOr beeRS bbS>>20ForBeers.com:1337 (1:105/420)
SEEN-BY: 1/123 15/0 90/1 105/7 10 11 44 81 85 420 500 106/201 120/340
SEEN-BY: 123/131 129/305 153/7715 218/700 226/30 227/114 229/110 111
SEEN-BY: 229/112 113 114 206 275 307 317 400 424 426 428 452 470 550
SEEN-BY: 229/664 700 266/512 282/1038 292/854 317/3 320/219 322/757
SEEN-BY: 342/200 396/45 460/58 633/280 712/848
PATH: 105/420 81 229/426