...
 BS> Okay, the current mecca thing does only work on private 
 BS> messages.. BTW Did you look into the MEX source, I did 
 BS> look in there several times, but couldn't find the 
 BS> problem.. AFAIR is the problem then it tries to store a 
 BS> adress in a array there looks to small to me...

I haven't dug that far into it.  Based on the error messages I've seen, I
believe there is definately a starting address not being calculated and
stored in the MEX compiled code.  Since Wes was working on this (and having
"fun" trying to find the bug), I haven't spent much time on this
issue -- yet.....

 BJ> Another option is to start using the QWK off-line functionality....

 BJ> Or start observing the '*'s in the Area list 
 BJ> menu....  Oh, yeah, That 
 BJ> may be part of what is running under MEX, so I see 
 BS> it via my OS/2 BBS 
 BJ> (which is why most of my replies are still from 
 BJ> 1:343/41 -- that plus 
 BJ> I still have a bug in my configuration that is 
 BS> loosing messages to my 
 BJ> linux box)....

 BS> But QWK upload doesn't work well :( 

Try local console (bin/max -k) mode.  If I remember correctly, this gets
around the problem with file transfers and will allow you to test out .QWK
format without the file transfer code working.  You do have to pickup
(download) and place (upload) files in their proper directories to play
with this.  I know I've tested .QWK (local, max -k) downloads on my OS/2
machine many years ago.  I haven't tested it on the Linux machine.  Since I
haven't used off-line mail readers for my BBS usage, I haven't realy tested
the .QWK upload options.  With message areas using sub-divisions, and the
way .QWK limited to 8 character area names, and how my area names got
munged at the time to get 8 characters, I didn't care for that interface,
and never persued it.

 BS>> And can I put something like a signature in?

 BJ> That will need to be an ehancement to Maximus.....

 BS> Okay..

Only thought is an off-line mail reader and running .qwk format from the
local console mode to possibly do this right now....  Ok, or something
running against the squish (or *.msg) file areas directly -- like MSGED.

Take care....

Bob Jones, 1:343/41



--- Maximus/2 3.01