Hi, I just tried the newly released version with this toolset (I don't think many will use and support it, but still useful). Output when building move from boost/libs/move/test: ..\..\..\b2.exe toolset=msvc-7.1 variant=debug C:/Data/Libs/boost/tools/build/src/tools\msvc.jam:1075: in configure-really *** argument error * rule generate-setup-cmd ( version : command : parent : options * : cpu : global-setup : default-global-setup-options : default-setup ) * called with: ( 7.1 : C:\Program Files (x86)\Microsoft Visual Studio .NET 2003\Vc7\bin : C:\Program Files (x86)\Microsoft Visual Studio .NET 2003\Vc7 : <command>C:\Program Files (x86)\Microsoft Visual Studio .NET 2003\Vc7\bin\cl.exe : i386 : : x86 : vcvars32.bat ) * missing argument global-setup C:/Data/Libs/boost/tools/build/src/tools\msvc.jam:809:see definition of rule 'generate-setup-cmd' being called C:/Data/Libs/boost/tools/build/src/tools\msvc.jam:201: in configure C:/Data/Libs/boost/tools/build/src/tools\msvc.jam:153: in msvc.init C:/Data/Libs/boost/tools/build/src/build\toolset.jam:43: in toolset.using C:/Data/Libs/boost/tools/build/src\build-system.jam:461: in process-explicit-toolset-requests C:/Data/Libs/boost/tools/build/src\build-system.jam:527: in load C:\Data\Libs\boost\tools\build\src/kernel\modules.jam:289: in import C:\Data\Libs\boost\tools\build\src/kernel/bootstrap.jam:139: in boost-build C:\Data\Libs\boost\boost-build.jam:17: in module scope I've found a workaround adding this to user-config.jam, in case anyone needs a workaround: using msvc : 7.1 : : <setup>"C:/Program Files (x86)/Microsoft Visual Studio .NET 2003/Vc7/bin/vcvars32.bat" ; Of course that path is in a 64-bit Windows OS, adjust it to your installed path. Best, Ion