BJ> Bo:

 BJ> Didn't you say something about auto-generating the FTSC product
 BJ> table from an FTSC document?  If so, what files were updated for
 BJ> this change?  Did you add any new files to the code?  Was this
 BJ> strictly a squish change?  

 BS> No actually not, it didn't work out well, so I removed it..

Ok.  That is an interesting idea thou....  We may want to keep the awk
command as an optional build target that we only occationaly execute, and
then check in the updataed .c file after the change.....  Do you know how
to set that up?

 BJ> I remember that the last time I touched
 BJ> the FTSC product table, I made two types of entries, one #ifdef'ed
 BJ> for the Unix / Linux (and maybe OS/2 and Win32) code and the other
 BJ> for the DOS code (so that we don't blow up table space when we get
 BJ> back to trying to compile a 16 bit version of the code)....   

 BS> I did put the same #ifdef thing about ti.

Good.

 BJ>  What
 BJ> program were you using to extract info from the FTSC table?  Do we
 BJ> have that program tested in the ./configure script Wes wrote?  If
 BJ> not, the ./configure script needs updating to test for the program,
 BJ> and generate needed enviornment settings, etc. 

 BS> I used a AWK script, taken from the mbse bbs, it was 
 BS> put in, in the makefile so it did run the awk script before compiling ..

Ah....  Ok....  Let's make this an optional target to run the awk
script....  Normal users wouldn't need to run this, but when the FTSC
product code list gets updated, one of us could run the script and check in
the updated .c (or .h) file with the updated table.....

 BS> Regards,
 BS>         Bo

Thanks!

Bob Jones, 1:343/41


--- Maximus/2 3.01