>can some kind soul tell me what I have to do to get codewarrior to accept
>lines like
>
>#include ":bsd:sys:param.h"
>
>I have CW 8 (since I have unix I don't have much need for nwer versions of
>CW anymore) and I have looked through every manual everywhere I can think
>of and I can't seem to figure it out, I have fooled around with the access
>paths but to no avail.  And I can't compile it with Think C 7 as it is
>written to use SIOUX.
>
>This is really getting frustrating.

I converted the code from Think C to CW for two reasons.  First, the code 
produced with my Think C6.0 would sometimes hang while formatting.  
Putting in debug code made the problem disappear.  Converting to CW 
solved it for me.  Second, Think C 6.0 would hang my PPC Mac and toss 
it's cookies with Type 11 errors.  CW 6.0 never did.

The conversion to use CW only took me an afternoon, and the biggest 
change was adding prototypes for the various functions.  Plus fixing some 
parameters and variable typing that Think C never caught.  The additional 
code to use SIOUX was really not much more than an addition.  It 
shouldn't take some long to replace it with the Think C code, or make it 
conditional for either compiler.

As for your problem with paths, this seems to be a "feature" of CW.  I 
run into it all the time going between my PPC and 68K Mac.  It seems that 
once the project build is started, i.e. there are some objects in the 
project, CW thinks it knows where eveything is located.  I found that 
using the delete objects and compact project removes this knowledge and 
allows CW to rebuild from scratch.  Although if you've already diddled 
with the project path settings or some of the include statements you may 
want to restore everything back to the original state first.

hope this helps,
-bob