Hi everyone, We've been using Boost since around '98 and have had a great deal of mileage out of the smart pointer libraries (thanks!) and are now starting to try out some of the other libraries. We ran into two problems with the filesystem library, the first we're starting with. 1) The initial problem was that we had always been compiling with the __fastcall convention, but the Boost libraries are built using __cdecl. In the end we switched to __cdecl, but should there not be a #define with the build declaration in the headers? 2) The path class only uses narrow strings. For use with the standard C++ libraries this seems fine, but I think once the new standard goes through there should be wide character variants for the file library. In any case we often use bits of the Win32 API which do take wide characters. I'm just wondering if we should just copy the path class to make a wpath class path and if we do so should we give that copy back to integrate with the normal Boost library? This second is probably of more relevance to us now that we've changed our build options. Kirit