Irv Koch wrote in a message to Roy J. Tellason:
 RJT> You create a *.ANS file,  run ANS2MEC,  and then edit the 
 RJT> resulting *.MEC file, inserting whatever MECCA codes you like.  
 RJT> This is the way I've done it here,  and I *always* end up 
 RJT> altering the file before I even start adding to it,  which is 
 RJT> why I don't ever use ANS2BBS -- you don't get to look at the 
 RJT> intermediate version of things.
 IK> While you're at it, I have a question too.  Remember I'm one of 
 IK> the "no files or ansi here" people ... only I just made an 
 IK> exception.  When I tried ans2bbs, first I got a "no such ansi 
 IK> character" message for one line out of a hundred or two.  But, 
 IK> worse, the resulting bbs file, when DISPLAYED by Oracle, was 
 IK> chockablock full of command codes shown as normal characters 
 IK> (not functioning). 
 IK> If I go the two step route, will it fix the problem, or am I 
 IK> going to have to redo the mec files heavily before the 2nd 
 IK> step?  (If it's any major effort, this minor project goes back 
 IK> down the tube.)
I'm not sure what you're running into there,  but I have a heck of a hard 
time looking at *.BBS files and figuring anything out.  On the other hand,  
when I'd run ANS2MEC I'd look at the resulting file with a text editor and 
take out all sorts of odd stuff that didn't make any sense to me.
And if you've got a main menu as I do which consists of a bunch of colored 
blocks,  it's *so* much easier to try and draw it with something like THEDRAW 
and then convert it,  rather than trying to make a mecca file that'll all 
line up properly.  As it is,  I still had occasional problems now and then 
with things not wanting to line up right,  though they were easily fixable.
What are you trying to convert?
email: roy.j.tellason%tanstaaf@frackit.com 
--- 
---------------