<Note: Skip to the third paragraph if you don't care to read a long introduction in mediocre English >
Hello fellow commiserators! At least for me this issue has been a misery for years now and I have spent more than 30 hours on this (notice the unit is hours, 'cause in days is too much to want to recall) trying all different ways to get rid of these
files. The frustrating thing is that I finally can't be sure what has solved my problem and I don't have a solid answer, however I signed up only to review my experience for anyone that will be hopefully helped.
My case was a bit complicated, since the stubborn files were located in an external hdd (in particular the WD My Book World Edition), which functions like a NAS drive, is formatted in NTFS and has probably some drivers in order to communicate both with windows
and macs. I'm saying this for a few reasons. First, I tried to delete these files in both platforms (mac and windows, but finally the success came while experimenting in the windows part via Parallels). Second, because of the type of the HDD I was never sure
about the permissions and stuff every time I was trying an approach and further this led in need of workarounds, in order to access the files by the command prompt (at least in windows) or check/repair the disk. Moreover, the creation/mutation of the discussed
files into these annoying ones and the error messages, when trying to do an operation with them, could be probably related. Finally, the fact of ejecting the drive (not exactly though, but I told you, for me it has been complicated) itself, did play some role
to the outcome.
The files that would not go away were some ._Thumbs.db, although I believe I had problems with a couple of more file types before, like with some sort of backup files of incomplete html saved files, but this happened more than a year ago
(at that time I just gave up), still with the same drive. I virtually tried hundreds of methods and alternatives, as well as all the ones described within the pages of this thread, without success. However, the last attempt, after which I saw those files disappearing,
was to use this method, similar to the .bat file method mentioned above with one folder. Although by following the instructions, there was no obvious result, I read something in the comment, which lead me to disconnect the image, where those files were located, and
by reconnecting it, I found out that the stubborn files were gone and the parent folders could be deleted. The reason I am not sure, if it was the solution, which did the trick, is because, from what I understand, it is supposed that the solution is applied
on the folder in which the .bat file is put, however, after I reconnected to the image I could delete more folders, previously impossible to erase due to these files, and in which, I mean, I didn't put the .bat file. Related to the speciality that the type
of the HDD introduces, I would like to add that, although I don't have the knowledge to realize what is what exactly, I can access the drive from the windows part, both when mounted as an external shared volume or as a network computer, while the same time
is also mounted in the mac's part. I was experimenting by network computer access. Maybe the Parallels virtual concept makes the whole thing even more manifold, the result however is that, after all, I am not totally sure what I could securely call the solution
method. Also, I found another problematic folder in another image/partition of the HDD, I repeated -I believe- the method and it worked, but unfortunately I didn't come across to more of these files afterwards to be able to draw some more precise conclusions.
I understand that the above makes normally little sense and only if someone had the same setup could probably have a clue, of what I'm trying to say, but I was so frustrated, with all those different ways I tried, that I'm just pleased I could managed to
delete them, when everything else seemed impossible, in terms that the ghost files were obviously there, but I couldn't access them, since they were supposed to be missing. Believe me (like it's not obvious already :)), I could go on to even more details,
like with the wordpad method, where I also had the issue of seemingly delete the file, but it was only seconds later that the file was reappearing or all of my tries with software like Unlocker and Delinv or even the various force delete commands AND the combination
of the above in the hope of deceiving what ever force had been keeping these damn files alive. However, I will leave it you to decide, if you would like to ask more from this kind of stories...