Subj : Mystic BBS To : Carl Austin Bennett From : Michael Grant Date : Mon May 14 2001 02:13 pm Hello Carl. 14 May 01 13:49, you wrote to me: CB> I just downloaded the new version (1.07.3) and it seems to have the CB> same problems with quoting. Thanks for letting me know; I'll go and grab it. CB> I think CarolS was seeing the same problems with Telegard; while It's much ado about nothing; just as is Dale's obsession with every message needing in his view to have 100% correct MSGIDs. CB> Mystic is a completely separate code base, at least one person has CB> remarked that there are some very strong similarities in look and CB> feel at times. Although written from scratch, Mystic was largely structured around Renegade BBS. Renegade was originally a hack of Telegard; and all are also similar in structure to Remote Access. I've tried all of the above and several other RA & Renegade compatible packages, and I found Mystic to be the most flexible and easiest to customize, which was what I was mainly looking for in a BBS. MG>> I refuse to change my choice of software just because you don't MG>> like the way it quotes; and it's none of your damn business what MG>> software I choose to run. If you don't like it, you don't have to MG>> read my messages. CB> Pity James didn't change this when he made the other bug fixes. James has been doing his best, but I understand real life has intruded upon his progress in Mystic. I don't mind putting up with a few minor bugs; the package offers me the sorts of things I want in a BBS, and I like it and will stick with it. None of the bugs cause any major problems for others in this network, so I see no reason for people to obsess over them and critisize someone over choosing Mystic as a BBS package. CB> I notice that .QWK support is fixed now under Squish, but that a CB> couple of other items remain unresolved. CB> A Squish base over several thousand messages in size seems to cause CB> problems (Mystic either loops back or jumps to an invalid position CB> after a while) and the garbage text at the end (where it's showing CB> part of the SDޝ header of the next Squish message) is still there. I have every confidance that James will eventually address these problems; he seems a very capable programmer. I think his only limitation is the time he has to give to the program's development, which is understandable. CB> I believe MOOSEID/REPLY were on the list of items that'd been CB> addressed in 1.07.3, although I haven't set up any neat and stricter CB> traps to test this. Thank goodness for that! --- GoldED+/386 1.1.4.5 * Origin: MikE'S MaDHousE: WelComE To ThE AsYluM! (1:134/11) .