Nachrichtall archives are meant to work alike. binary_w?archive has not been maintained. It may or may not work. It really has no reason for being as far as I can tell. The problem is that the wide characters can included -1 which is confused with EOF. When I discovered this, it didn't see a way to work around it and didn't really understand how one could do binary i/o with wide character archives. I've just assumed I've missed something dumb and moved on. For practical purposes, just use binary_i/oarchive. Robert Ramey "Oliver Mutz" <omutz@isdcad.de> wrote in message news:008901c6d1cb$b896e1a0$150aa8c0@int.isdcad.de... In my application I'm trying to serialize data alternatively to xml_wiarchive or binary_wiarchive. Writing and reading XML works without any problems. Binary writing seems to work too, but reading the file throws an exception with exception_code 'unregistered_class'. What I do is reading the XML data, writing binary and reading binary back in. I thought there should be no difference which kind of archive I use. Am I missing a point? *** Nope, it is a goal that all archives work alike. I would be thankful for any hint. I know that it is hard to guess where the problem might be without seeing any code, but I by now I was not able to create some simple example which shows the same behaviour. I'm using Windows XP (SP2) with MSVC 8.0. Thanks. Oliver _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users