I've finally solved a problem that's been bugging me for years. One of our file shares ended up with several undelete-able files. Attempting to delete them results in ' Error Deleting File or Folder - Cannot delete file: Cannot read from the source file or disk'. Note: Windows 7's version of this message is something like: Could not find this item: This is no longer located in C: Blah.

METASTOCK 13 Crack, METASTOCK 13 Keygen, METASTOCK 13 Serial, METASTOCK 13 No Cd, METASTOCK 13 Free Full Version Direct Download And More Full Version Warez Downloads. Dead Or Alive 2 Ultimate Xbox Iso Zone there. Metastock 11 PRO Crack forever 29 evaluation daysdownload from 4shared METASTOCK 13 torrent Crack,. Metastock torrents Free Download for Windows - Informer Free download metastock torrents Files at Software Informer. Torrents Open Registrations Checker is a simple application that verifies the Torrent/Tracker sites.

Verify the item's location and try again. Even going to the file's properties to check permissions presented a very blank properties dialog. And a CHKDSK didn't sort thing out either. It turns out the problem was: the filename ended with a dot, e.g. It was something like ' C: Temp Stuff Sales Agreement.'

As far as Windows is concerned this is an invalid file name: so although it gets reported in a directory listing, the standard Windows APIs for manipulating files subsequently deny its existence. So how did this file get created in the first place? The answer: a Mac. The file was on a file share which had been accessed by a Mac user.

Macs tend to write all sorts of metadata to extra '._DSStore' files and suchlike and had left this file behind. So if Windows doesn't appear to allow these file names, how did they get to be created? Well, it turns out that NTFS allows all sort of file name/path weirdness that Windows, or specifically the Win32 API, doesn't allow. For example, NTFS actually allows file paths up to 32K but Windows restricts file paths to no more than 260 characters (MAX_PATH). I suppose this is all for DOS/Windows 9x backwards compatibility. As these files were being accessed over a file share I guess the usual Win32 checks are bypassed. But thankfully you can get Win32 to ignore these checks by prefixing your file paths with?, (ie.

C: Temp SomeFile.txt becomes? C: Temp SomeFile.txt) which I discovered after reading. So at a command prompt (Start >All Programs >Accessories >Command Prompt) I was able to delete the file using: del '? C: Temp Stuff Sales Agreement.' Note: On Windows 7 it seems you can just use wildcards without the? Trick to delete the offending files: e.g.

Del c: temp somefil * If it's a folder/directory you're trying to delete use the rd or rmdir command, e.g.: rd /s '? C: Documents and Settings User Desktop Annoying Folder.' Tip: as you're typing the file/directory name use the TAB key to auto-complete the name (press TAB repeatedly to cycle through possible names).

Of course the corollary of all of this is that you could really annoy somebody by doing this: echo Hi >'?%USERPROFILE% Desktop Annoying file you can't delete.' But you wouldn't do that would you? 2008 21:36 Very helpful! Glad I found this via Google. My problem was a folder name generated by a program. I tried to move it, rename it, etc -- no dice. In my case the last character in the name appeared to be a space.

I couldn't seem to rename it with this trick (got syntax error - sorry, I didn't record exact error message). So I copied the contents into another folder, and then deleted the bad folder ( rd '?

C: folder folder bad name'). It went away.

Some where in some manual the exact syntax rules of these DOS commands is documented, I'm sure. 2008 20:31 Sweeeeeet! Worked like a charm. I had tried booting in safe mode and deleting, MoveOnBoot, and toying with permissions, none of which worked.

The files did indeed come from a Mac and in my case it wasn't a period on the end, but something that looked like a space. I highlighted the name of the offending file, copied it, got in the command prompt window, typed your command, (del '? C: folder name sub folder name ), then right-clicked to get the paste function in the command prompt window and typed the close quote. That way, no matter what the offending character is, there's no guess work. Jillian Michaels 30 Day Shred Level 2 Download Avi Converter. 2008 19:31 @vassos I had the same problem as well.

There were folders under the top level 'bad' folder that I had to delete first before I could do these steps. So, in Windows, I had: c: myfiles badfolder stuff morestuff. I deleted the 'morestuff' and 'stuff' folder in Windows just fine, but I couldn't delete the top level folder (it had a space in it). Once I deleted the subfolders and all that was left was c: myfiles badfolder, the suggesions that Ben had worked. I used rd instead of rmdir, but it shouldn't matter. 2008 21:40 Hi.