SD> You might want to check the PASCAL echo for more stuff. 
 SD>  Right now, I wish I could figure out how the hell to 
 SD> use the Pascal structures for Maximus as I am writing a 
 SD> CGI for the last 10 callers, but the thing just doesn't 
 SD> work.  Unfortunately, I've so little C experience that 
 SD> I can't properly read the Pascal structures and the 
 SD> comments (Scott had a weird way of programming, I've been told).

You figured out your CGI stuff yet ?

My theory on it is invoke 

  max maxcgi.prm -b0 -j "$1;|;$2;"

where $1 and $2 are the username & password passed from the CGI or
cookie, and maxcgi.prm is an alternate PRM file which is configured to use
a different welcome file ("Uses Welcome Misc\altwelc" in
maxcgi.ctl).

altwelc.mec contains "[mex]m\runcgi[hangup]".

Your perl CGI would copy/rename whatever mex program you wanted run to
m\runcgi before calling Maximus. eg. "copy \max\m\lastcals.vm
runcgi.vm" etc. where lastcals.vm is the compiled MEX for writing
lastcallers details to a plain text file; perhaps formatted with HTML tags,
which is later appended to your perl CGI output.

If I can find out how (and where) in the source code Maximus loads Mex
programs, I could redirect output to file rather than BBS comms routines. 

Probably modify the Mex max.mh include file to use stdio.h or something ...
.

--- Maximus/2 3.01