Hello Michele.

10 May 04 18:23, you wrote to you:

 MM>> Now from  what I know it sets the TCPIP port to 4002. When its
 MM>> running and I telnet localhost 4002 it never connects up.
 MD>         Followup. I saw in the latest CVS changelog that I need to use
 MD> maxcomm to actually deal with the TCP/IP side (oops!) Do I still need
 MD> to set the port in the maximus binary via the -p option as well?

Well max -pt1 -n1 will create a socket called max1 and maxcomm will connect
to it. It's described in README.2ST.

 MD> the
 MD> cvs runbbs.sh shows that flag is still used (my older runbbs.sh was
 MD> from the older maximus. The current /maximus/scripts/runbbs.sh does
 MD> also have a proper exit as well.

The old runbbs.sh wouldn't workout.. Only the one described in README.2ST

 MD>         The other questions in reguards to the serial ports were not
 MD> answered in the readme files in the top of the maxius tree. Is there
 MD> any serious differences vs the regular maximus 3.0x documentation that
 MD> I need to be aware of? Is mex still DOA? (Being an Grizzled Opus
 MD> veteran (females rarely get grizzled ;)) I have never used mex. Just
 MD> the standard display codes which are very similar among the two bbs
 MD> systems. Eventually I do want to try mex.

MEX works very well now! Just a dummy error, wes may have been missed..

Bo

--- GoldED+/LNX 1.1.5-31012