Given: C:\src\workspace\boost>bjam "-sTOOLS=como-win32" "-sCOMO_BACKEND=dig" "-sCOMO_BACKEND_PATH=c:\dm" --with-python-root=c:\python24 stage I'd expect the build-process to start, using Digital Mars as backend. Boost.Jam tries to call c:\dm\..\Common7\Tools\vsvars32 and set COMO_MS_INCLUDE to c:\dm\include. Clearly it somehow thinks that it should setup for a VC7 backend, although it *does* correctly issue "como --dig ..." to compile. What's happening? -- /Brian Riis