--------------- FIDO MESSAGE AREA==> TOPIC: 174 MUFFIN (MAXIMUS) Ref: F3300022Date: 03/01/98 From: ROY J. TELLASON Time: 10:19pm \/To: DAVE GARLAND (Read 0 times) Subj: msg_next Dave Garland wrote in a message to Jun Martin: JM> Indeed, very ELEGANT. DG> Aw shucks, it was nothin'. :) DG> Thanks. I did play with the menus a lot, trying to make the DG> operation self-evident to novice callers. It's a real DG> challenge to make the purpose of some commands obvious to DG> somebody who's never used a bbs before when you only have 10 DG> characters or so to describe them with. Changed some command DG> names, color-coded, grouped commands, and had some conditionals DG> like that example, or where commands the user doesn't have DG> access to are "greyed out", to entice them into upgrading their DG> access. I'd be interested if you'd care to go into more detail about any of this stuff. I'm always looking for more ideas as to how to make my system better, and although I seldom do what others are doing, looking at stuff can be nice to get ideas from... email: roy.j.tellason%tanstaaf@frackit.com --- * Origin: TANSTAAFL BBS 717-432-0764 (1:270/615) --------------- FIDO MESSAGE AREA==> TOPIC: 174 MUFFIN (MAXIMUS) Ref: F3300023Date: 02/28/98 From: ANKUR GUPTA Time: 10:00pm \/To: SVEN BUERGER (Read 0 times) Subj: mamachat -=> Quoting sven buerger to Ankur Gupta <=- sb> @MSGID: 2:249/3030@fidonet d9ce9f11 sb> Tachchen ! AG> Hi gerard, it still dint work. Heres my mmchat.cfg: I changed the AG> logfile name from chat%task% to chat.log but it still dint work. AG> Please help! AG> ------ LOG ON AG> LOGALLES ON AG> LOGFILE "D:\MAX\CHAT.LOG" sb> In the DOS-Version of MaMaChat, you can not use all of the Functions. sb> The Author say (in DOS-Version no Logging): GOD! IM DEAD! I just love MaMaChat, but have to have the logging function to work! Ankur ... "What?!? This isn't the Files section?!?" --- Blue Wave/DOS v2.30 [NR] * Origin: Kamas Bbs, Chandigarh +91-172-548006,07 INDIA (6:606/52) --------------- FIDO MESSAGE AREA==> TOPIC: 174 MUFFIN (MAXIMUS) Ref: F3300024Date: 02/28/98 From: ANKUR GUPTA Time: 10:00pm \/To: GERARD ZOER (Read 0 times) Subj: mamachat -=> Quoting Gerard Zoer to Ankur Gupta <=- GZ> @MSGID: 2:500/143 34f6274b GZ> Hello Ankur! GZ> Monday February 23 1998 19:03, Tim Neale wrote to Ankur Gupta: TN> I'm using the DOS version and also cant get logging to work but when TN> i spoke to the author he mentioned that he hadnt put all the features TN> into the DOS one due to memory limitations, I assumed the logging TN> funtion was one of them GZ> Correct so it seems a DOS limitation. I'm using the OS/2 version.. GZ> Switch over. I _KNEW_ it was'nt my fault that logging wasnt working :) Ankur ... Two most common elements in the universe: Hydrogen & Stupidity. --- Blue Wave/DOS v2.30 [NR] * Origin: Kamas Bbs, Chandigarh +91-172-548006,07 INDIA (6:606/52) --------------- FIDO MESSAGE AREA==> TOPIC: 174 MUFFIN (MAXIMUS) Ref: F3300025Date: 02/28/98 From: ANKUR GUPTA Time: 10:01pm \/To: MARKUS MANDALKA (Read 0 times) Subj: mamachat -=> Quoting Markus Mandalka to Ankur Gupta <=- Hi Markus! MM> Do you use the "DOS-Version" ? Yes, I have to! MM> If yes, it's the problem, because VM-Files that are bigger than x KB MM> can't be started from the DOS-Version of Maximus, so that some MM> Features could not be built in to this version :-( Thats terrible! We are at a loss without it! MM> But if you are good in MEX, i could release the sourcecode, so that MM> some DOS-Users can delete some other thinks and let logging in the MEX MM> or so ... I am not that good in Mex Markus, but im sure others are and they will do it cause its too good!!! -ankur ... Sorry, the dog ate my Blue Wave packet. --- Blue Wave/DOS v2.30 [NR] * Origin: Kamas Bbs, Chandigarh +91-172-548006,07 INDIA (6:606/52) --------------- FIDO MESSAGE AREA==> TOPIC: 174 MUFFIN (MAXIMUS) Ref: F3300026Date: 03/01/98 From: JIM BROWN Time: 03:18pm \/To: SCOTT DUDLEY (Read 0 times) Subj: Maximus filesystem on NT Server: problem15:18:0003/01/98 Hi Scott, SD> Perhaps comparing the basic operating environment could be useful? I SD> am happy to see that Maximus runs on at least *one* NT Server system. SD> If you can figure out what the differences are between his set-up and SD> yours, we will have gone a long way towards tracking down this SD> problem. SD> For example, stuff like this: SD> - filesystem type, - workstation OS, SD> - LAN type and protocol stacks loaded SD> will be very helpful to compare. Ok, sounds like a plan: Filesystem : NTFS and FAT LAN Type : Ethernet (ThinNet coax) Protocol Stacks: NT Server: NetBUEI and TCP/IP Station1 : NetBUEI and TCP/IP Station2 : NetBUEI Station3 : NetBUEI Station4 : NetBUEI Server OS : Windows NT 4.0 with SP3 Workstation OS : Windows 95 OSR2 Please note that I am not using any 32 bit BBS or mailer software. Also note that Maximus is not running on my NT server. The server is acting as a file server for Maximus running on the Win95 workstations. However, Squish *is* run on the NT server. Thanks again for your time. ...jim ... Linking error. Your mistake is now in every file. --- Squish/386 v1.11 * Origin: BitByters BBS, Rockland, Ontario, Canada (1:163/215) --------------- FIDO MESSAGE AREA==> TOPIC: 174 MUFFIN (MAXIMUS) Ref: F3300027Date: 03/01/98 From: GARY GILMORE Time: 05:33pm \/To: SCOTT DUDLEY (Read 0 times) Subj: Maximus filesystem on NT Server: problem17:33:5003/01/98 SD> I am happy to see that Maximus runs on at least *one* NT Server system. It's been running ok in the tests I've been doing on a machine I'm setting up, so make that two. :-) (Granted, it's not a full-time setup yet, but I've seen no problems.) --gary --- Maximus v3.01 * Origin: http://oeonline.com/~garyg/maximus/ (1:2410/400) --------------- FIDO MESSAGE AREA==> TOPIC: 174 MUFFIN (MAXIMUS) Ref: F3300028Date: 03/01/98 From: GARY GILMORE Time: 05:53pm \/To: ZORCH FREZBERG (Read 0 times) Subj: Max/NT - Dos Doors ? ZF> The problem is that Win95 is COM-port stupid. Not really. Communications performance in Win95/98 is a quantum leap from trying to do a BBS under Win3/WFWG. However, Win95/98 doesn't want to let you pass a hot port from a 16bit program to a 32 bit one, and vice-versa. If you use all 16bit, or all 32bit programs, you don't have a problem. Since I don't see BBS-related authors falling all over themselves to write 32bit BBS-related software (mailers, doors, BBS software, etc), therein lies a problem. (Though Scott did give us a 32bit Max, and I think it was one of the first console-mode BBSes to be 32bit.) ZF> There is a possibility, I am told, that the Win98 rewrite *may* have ZF> partly addressed this Not that I've heard. ZF> If you know _anyone_ on the Win98 Beta teams I happen to know someone. ZF> push them to ask MS to address the issue. I doubt it would have much effect, unless all 15000+ beta testers pushed for it. (And we got Bill Gates to run a BBS.) --gary --- Maximus 3.01 * Origin: http://oeonline.com/~garyg/maximus/ (1:2410/400) --------------- FIDO MESSAGE AREA==> TOPIC: 174 MUFFIN (MAXIMUS) Ref: F3300029Date: 03/01/98 From: VICTOR LOBERGER Time: 07:31pm \/To: WAYNE ARNTSEN (Read 0 times) Subj: Help Wayne, WA> all The Old Message , Another words , It will keep WA> Building up , I have My Remax Sey for 20 or 25 But The WA> is Message Up 1000 or 1100, And I have Look Del the OLs WA> BBS is Started Up an New one, So I waas wondering If WA> Someone Could help Me out On This one. Thanks Very and You probably set the RENUM MAX *after* you SILTed everything the first time. If you reSILT your .CTL files, you'll probably be OK. FWIW, here's a copy of the first message area on my BBS. I keep changing the RENUM MAX quite often, but then I have to reSILT too. MsgArea 1 ACS Transient Desc Comments to the SysOp Path F:\Max\Msg\L_Commen Override MESSAGE MSG_ENTER Transient Override MESSAGE MSG_REPLY Transient Override MESSAGE MSG_KILL Sysop Renum Max 300 Renum Days 180 Style Squish Local Pvt Tag LOCAL_COMMENTS End MsgArea Good luck! Victor --- Maximus/2 3.01 * Origin: Aarrgghh! BBS-Running Max/2, MainDoor/2 & Squish/2 (1:154/731) --------------- FIDO MESSAGE AREA==> TOPIC: 174 MUFFIN (MAXIMUS) Ref: F3300030Date: 03/01/98 From: PETER CONNERTY Time: 11:33am \/To: TOMMY MOORE (Read 0 times) Subj: Telneting TM> Um, how do I make a dos maximus system telnetible? Someone in here said TM> that they do it anddI was wondering how they did that cause that sounds TM> like something I wanna do since I'm allways on the net staying on the TM> line so it'd be cool to have it telnetible. TM> Thanks if ya can help. Get hold of netmodem, Install it, and thats as easy as it is... Mine is telnetable this way, maxbbs.dyn.ml.org but only when I'm online.. catcha _ __ _ |_| | |_| |eter |__onnerty NetWork Co-Ordinator for |_|attleNet 169:1500/101@battlenet Telnet maxbbs.dyn.ml.org ICQ UIN : 2877141 HTTP : www.auslink.net/~connerty Files : battle@auslink.net EMail : connerty@auslink.net ___TheEdit v2.11 [unregistered for 437 days!] ...This copy of ProBoard has been unregistered for 505 days! --- * Origin: Hills BBS +61-8-8389-6779 (3:800/851) --------------- FIDO MESSAGE AREA==> TOPIC: 174 MUFFIN (MAXIMUS) Ref: F3300031Date: 03/01/98 From: PETER CONNERTY Time: 11:36am \/To: JUSSI HAMALAINEN (Read 0 times) Subj: Telnet maximus3.01/dos JH> Sounds like Max is having problems recovering from a shell. I have no JH> idea how to fix this problem... Anyone? COM/IP was my problem, changed to Netmodem, and all is ok now... _ __ _ |_| | |_| |eter |__onnerty NetWork Co-Ordinator for |_|attleNet 169:1500/101@battlenet Telnet maxbbs.dyn.ml.org ICQ UIN : 2877141 HTTP : www.auslink.net/~connerty Files : battle@auslink.net EMail : connerty@auslink.net ___TheEdit v2.11 [unregistered for 437 days!] ...This copy of ProBoard has been unregistered for 505 days! --- * Origin: Hills BBS +61-8-8389-6779 (3:800/851)