MK> Again it wasn't that way by default, straight DOS, and required
 MK> extra software to enable that functionality.  It seems to me that
 MK> emulation of DOS offers very little functionality and in fact adds
 MK> drag to a Linux system.

 RJT> The biggest single advantage to me would be my ability 
 RJT> to take my current setup and drop it in there and have 
 RJT> it work without having to fiddle with it.

 MK> If multinodal Maximus is the goal then it seems to me that one 
 MK> should just use dos/dv and let dv handle the networking aspect for 
 MK> DOS and Maximus.  Why cripple a Linux system just for a few simple 
 MK> text games?

dos/dv setup of Maximus has some smaller limits than an OS/2 setup of
maximus for both single and multi-node environments.  I believe we compiled
the Linux version for the higher limits.  I'm not sure we have all the bugs
worked out for multi-node under Linux.  We were still working on the telnet
/ dial-up issues when I last had time to touch the source code.

 RJT> Games are not an issue for me.  I'm not so sure that 
 RJT> multiline is these days either,  though there was a 
 RJT> time when it might have been.  I think those days are 
 RJT> past,  though.

Multi-node is needed if you want to use Max in in "unix" style
setup instead of a "dos think" style setup.  Grant it, if you are
just going to run one copy of maximus in a local console mode, then it
doesn't matter.  But if you are going to run a telnet line, plus be setup
for a local sysop console, you will need multi-node maximus properly
working.

Take care.....

Bob Jones, 1:343/41


--- Maximus/2 3.01