The problem isn't necessarily trying to access a closed filesystem with a driver that's been created by reverse engineering. I think the problem is that there are a lot of crappy Windows programs that can really screw things up on Microsoft's somewhat crappy filesystem, period.

The NTFS driver built into the system and the Paragon version I'm trying now seem to do very well reading all files/folders that have not been messed up in this way. That is to say, ones using only long filenames without any backward compatibility kludges.

The problem files are also an issue with network browsing from the Mac. I'm going to see what happens when I browse them from another Windows PC.

As an aside, does anyone know how to delete a "stuck" folder in Windows? That MIA folder brings up a message saying "refers to a location that is unavailable..." and I can't do anything with it, including cd from the command prompt.