ac> MaximusSourceDoc.doc on the CVS tree should really be 
 ac> corrected.  Although it should be converted to text 
 ac> first.  CVS and binary (.doc) formats don't really work 
 ac> well when you're trying to use 'diff'...

I've updated "MaximusSourceDoc.doc" for the DOS and NT builds. MS
Word 2003 all the way baby :)

I've never used CVS or much diff'ing with text files to appreciate what the
issue is. In MS Word you just turn on "Track Changes" :)

 ac> Why are the NT headers and libaries from 10.6 required? 
 ac>  Is it because 11.0C doesn't supply them?  I didn't 

I haven't precisely found an explanation but from all of my trial, error
and testing you cannot build overlayed DOS executables without the WC 10.6
headers, libs and compiler no matter how you try to arrange your build
environment.

Without overlayed DOS executables, you won't be able to run doors. Being
able to run doors is a big part of running a BBS. 

Do doors work in "max-3.03-etc.tar.gz" under Linux ?

 ac> notice you were using 11.0C when I read your message 
 ac> the first time so you can obviously disregard the link 
 ac> to 11.0C in my previous message because you obviously 
 ac> have it.  Maybe it'll help other people though.

I've downloaded WC 11.c from ftp.openwatcom.org/archive. That version is an
Upgrade. I've tried; but the Upgrade alone is not enough to compile the
source (you need a full install of 11.0 first before upgrading to 11.0c
because the 11.0 seems to have a problem addressing memory during the
build). 11.0c also doesn't come with the Microsoft SDK, which Maximus
needs.

 ac> What happens if you use the NT headers/libs from 
 ac> OpenWatcom 1.0 instead?  Assuming they exist.  An 
 ac> academic question if we can use OW 1.0 to build the 
 ac> entire thing.

I haven't tried. But it would be something I'm willing to check out. So
far, I've observed that OW 1.5 & 1.8 will not build the Maximus sources
due to type conversion problems. Searching Google reveals that the
suggested fixes are to redefine / redeclare your sources to be compatible
with the target conversion types. This is not a fun (or interesting)
exercise. 

 ac> It's long overdue, but it'd be great if we could get to 
 ac> a point where you could just do a CVS checkout and 
 ac> start the build 
 ac> process without needing to extract max-3.03-etc.tar.gz 
 ac> beforehand.  Actually the DOS/OS2/Win builds probably 
 ac> don't need that, just the Linux version.  Strange that 
 ac> it's a requirement though, because there's no source 
 ac> code in there.  In fact it seems to build fine if you 
 ac> just do a cvs checkout, then "mkdir maximus/install_tree".

To my knowledge, "max-3.03-etc.tar.gz" is the Linux port of
"MAXS_302.ZIP". It doesn't support building from multiple hosts
with multiple targets. 

I'm fine with that because I get to hog all the DOS and Win32 stuff when
nobody's interested :)

 ac> Anyway, it's probably a good idea if you were a member 
 ac> of the Maximus project on SourceForge, then you could 
 ac> do CVS commits yourself.  Of course you should avoid 
 ac> doing any major CVS commits until the source has 
 ac> stabilsied, ie. it builds successfully for all targets.

Merging the MAXS_302 stuff with the current CVS tree is a good idea but
could be difficult because v3.03 is specifically for Linux. All the
makefiles have been changed. It uses GCC instead of O/WC, GNU Make vs
Dmake, and there appears to be a big dependency on specific proprietary
headers & libs to build the DOS, NT and OS/2 targets. From what I can
see, these differences cause problems that won't be easily resolved until
we can get Maximus 100% non-propriety & open source for the other
targets. Having one compiler that can do it all eg. Open Watcom would help
a lot but apparently OW is not fully ready for this purpose.

 ac> You can see the list of members here:

 ac> https://sourceforge.net/project/memberlist.php?group_id=63593

 ac> I think you'd just need to contact one of the admins 
 ac> and ask politely to be added.  :-)

Cool. 

Might as well :)


--- Maximus 3.01