🚀 go-pugleaf

Figured it out. Don't you know you have to do something stupid then announce
it to the world before you can see the forrest for the trees?

When I replaced the 1.5b7 constructor with the 1.6b4 i had been using with
CW6, I neglected to also use the associated linker and PalmRez post
linker....

live and learn - it compiles and links now just fine


--

Carl Lippitt
DOC / WCG / CTO

"Carl Lippitt" <carl@slothware.net> wrote in message
news:njY47.28096$47.10224001@news2.rdc2.tx.home.com...
> Help?
>
> A project which successfully compiled and linked under CW6.0 (WinNT - SDK
> 3.5), will not link with the new CW 7.0 (which has been updated to the 7.1
> release). After removing all object code from the project and rebuilding
the
> project, all C, resource, and .r file compile correctly, a map.TMP file is
> built, then somewhere in the link phase, the following error is reported:
>
> Unexpected error #32, DirectBits not supported
>
> Q1: what does this mean?
>
> I am NOT using the constructor that came with CW7.0/7.1 since 1.5b7 could
> not read my resource file which I had built with 1.6b4 tools under CW6.0.
I
> wonder if this has any bearing on the link failure?
>
> I've sent this info to the technical support folks at Metrowerks, but was
> wondering if anyone else has seen this same problem, and if so - Q2: HOW
CAN
> I FIX IT?
>
> Thanks.
>
> --
>
> Carl Lippitt
> DOC / WCG / CTO
>
>
>