On Tue, Sep 15, 2015 at 2:25 PM, James Button <[email protected]> wrote: > OK - another stab in the dark
Of course - that's what sysadmins do! :) > Any filenames too long for the filesystem and the API that is handling the > files - as in the 250 (approx max) for normal windows 'stuff' > That one used to get me (ages ago) when files with long names had been > moved, and their foldernames made more user-understandable by changing them > from the 11 chars (8.3) to something with the users full name and location. I don't think so. This is a fairly vanilla box, running a small set of specialized apps (including an Access database and Optio print processing). But it's worth a check. > Other possibility - access restrictions, or MFT corruption such that names of > files returned by a 'directory' listing are not actually accessible. Access restrictions, no, but MFT corruption? That's something to investigate. > Both are reminiscent of dealing with wild piglets - well hidden and you'll > have to get down and root around in the muck to find and deal with them. > And then you'll get attacked by their 'owners' for interfering with them! Well, I'm not too worried about upsetting anyone. And, if all else fails, we'll see what happens this coming weekend. Kurt
