Hello Bob!

Oct 12 18:31 03, Bob Jones wrote to Bo Simonsen:

 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...

 BJ> I haven't dug that far into it.  Based on the error messages I've 
 BJ> seen, I believe there is definately a starting address not being 
 BJ> calculated and stored in the MEX compiled code.  

Hmm.. My bet is also that it's using "dynamic memory allocations".

 BJ> Since Wes was 
 BJ> working on this (and having "fun" trying to find the
bug), I haven't 
 BJ> spent much time on this issue -- yet.....

Okay.. But I don't have a clue of then Wesley would be back.. My patience
is not so big as it has been :/

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

 BJ> Try local console (bin/max -k) mode.  If I remember correctly, this 
 BJ> gets around the problem with file transfers and will allow you to 
 BJ> test out .QWK format without the file transfer code working.  

The file upload doesn't work at all1

...

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

 BS>> Okay..

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

That's what I'm using now, but I would presuiate if I could be comfortable
by using Maximus for message editing.

Regards,
Bo

--- Msged/LNX 6.1.2 (Linux/2.4.22-1-586tsc (i586))