| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | collecting mail finally. |
Paul, at 08:29 on Sun, May 28 1995, you wrote ... DD>>> Golly, which version did you look at? I am running 2.02 DD>>> here without any unexplained phenomena. PE>> 2.01wb. There were numerous problems, which people here PE>> can verify, DD>> AH ... not configured too well . . . PE> Nice try, not remotely correct. They didn't create FH? for PE> nothing (set the maximum number of file handles under OS/2). PE> I can send you my entire LOCSYSOP messagebase if you want to PE> wade through all the problems. I'm not interested myself. PE> It's 8 meg uncompressed, so presumably that will be 3 meg PE> compressed. It's my longest running uncorrupt area (LOCUSER PE> got corrupted many times thanks to SQFIX32P being a PE> disaster. I don't have the source code to it either. PE> [later] actually, I had a check. The file handle problem PE> was causing personal.ndx to not get created, even though I PE> was using maxfh or whatever, it wasn't good enough. The use PE> of TZ was not documented, it kept on beeping at me whenever PE> my modem screwed up, I had to resort to sticky-taping up my PE> speaker [incidentally, my speaker is disconnected completely PE> these days]. And I got a trap-e sometimes, which didn't PE> help when I went on holiday! Also, there was indeed times PE> when people would lose their lastread pointers and had to PE> reset them themselves. I actually abandoned the BBS PE> completely when squish kept on abending (admittedly that was PE> not maximus, I had a swag of problems with Squish too). The PE> reason for squish abending on that fatal day was that I had PE> set my # of dupes to 0, but I didn't remember that, but PE> squish obviously didn't like it. I switched to Tobruk at PE> that stage, because at least I had the source code to do PE> something about it. However there were bugs in it too, and I PE> figured out the squish problem before I had fixed the bugs in PE> tobruk, and I have never gone live with Tobruk because it PE> doesn't handle out-of-spec messages properly and I haven't PE> gotten around to fixing it. PE>> and that just make me sick so I'm not interested. PE>> At least I can do something about Binkley bugs, which are PE>> far less common anyway. DD>> Oh, what about the ones in MSGED 3.1a? PE> I can do something about any MSGED 3.1a bug that I am PE> experiencing. I can't with Maximus though. I can with PE> Binkley. Squish is the weak link. BFN. Paul. Hmmmmm sounds like problems in the OS/2 version. Damn, I am gearing up to convert the BBS from DOS to OS/2 (I better hang on to the DOS version in case of emergency) David @EOT: --- Msgedsq 3.05* Origin: JabberWOCky CBCS +61 7 868 1597 (3:640/305) SEEN-BY: 640/305 450 711/934 30163/9 @PATH: 640/305 711/934 |
|
| 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™.