In review the test compiler status tables things are looking very much better. There a number of pending issues: a) test_demo and others are failing at runtime in both gcc and vc environments. They pass on my machine. In checking the code in example/demo I come upon the following: void save_schedule(const bus_schedule &s){ // make an archive std::ofstream ofs("../example/demofile.txt"); boost::archive::text_oarchive oa(ofs); oa << s; } void restore_schedule(bus_schedule &s) { // open the archive std::ifstream ifs("../example/demofile.txt"); boost::archive::text_iarchive ia(ifs); // restore the schedule from the archive ia >> s; } Which in light or our test strikes me as suspicious. It makes a couple of presumptions which I don't know are really true: 1) that the current directory while the test is being run is boost/libs/serialization/test and that the directory 2) boost/libs/serialization/example has it permissions set to permit file creation. Upon reflection it seems that there is no reason to suppose these to be true. I wonder if someone could check to see if this is the problem. Meanwhile I'll investigate what it would take to change the demos so that this is not a problem. b) in several cases it seems that there is a build configuration issue as it relates to multi-threading libraries. This might be an issue with intel 8.0, and gcc 3.4.1 builds. c) I don't think that gcc 2.95 can be used with the serialization library. The error messages seem to indicate this gcc doesn't have templated streams and the serialization library requires them. Perhaps some combination of gcc 2.95 - stlPort might work. I will exclude markup to skip the vanilla gcc 2.5 tests. d) I'm hoping that the metacomm test setup can make spirit 1.61 available and set SPIRIT_ROOT accordingly. This would resolve most of the issues with vc 6.0, 7.0, and borland. Robert Ramey