TIP: Click on subject to list as thread! ANSI
echo: mystic
to: Nicholas Boel
from: g00r00
date: 2016-07-25 12:07:50
subject: JAM Last Read pointers

NB> If g00r00 could do something about it, by all means that would be great.
 NB> But I wouldn't expect it. Otherwise, I would suggest NOT packing your
 NB> message bases, or setting up a Golded as a point or node off your main

I actually do think I might be able to do something about it, I just need to
get GoldEd going and see what it does first to confirm.

Mystic's packer (I believe) will remove any unknown users from the last read
database while packing, but if GoldEd uses a specific user ID and CRC
value in the lastread database, then I can change Mystic to not remove it.

If it doesn't do anything to identify itself, then we might be screwed like
you said.

--- Mystic BBS v1.12 A30 (Windows)
* Origin: Sector 7 [Mystic BBS WHQ] (1:129/215)
SEEN-BY: 57/0 130/505 512 154/10 226/20 100 250/3 317/2 393/68 633/267 280
SEEN-BY: 640/384 712/620 848 770/0 1 3 100 772/0 1 100 210
@PATH: 129/215 154/10 770/1 712/848 633/267

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.