[darth_ash]

Ur hard-drive's directory structure may be slightly corrupt.
Run chkdsk c: /f in cmd to scan ur c: drive.

[Advertisements]

I run chkdsk on a regular basis and always do the full scan (including the /f command).

I appreaciate the advice to try using Linux but I'm not going thru the effort to install/deal with another OS to get rid of one 4kb gif file.

My big gripe originally was that I could not delete it OR move it from my desktop.

Somehow I've been able to get it moved to the root and thus out of sight (and also set to hidden) so thats enough for me for now.

I'm wiping this harddrive in the next few months anyways.

I do not feel like its just worth that much effort at this point.

It makes as much sense as fixing a loose rear speaker cover on a 89 Ford that I'm going to dump at the junkyard shortly anyways, you know?

Thanks all for the help!

I'm sure the advice will come in useful for someone in the future.

~DA

Edited by dakotaaviator, 11 August 2005 - 09:11 AM.

[dakotaaviator]

I run chkdsk on a regular basis and always do the full scan (including the /f command).

I appreaciate the advice to try using Linux but I'm not going thru the effort to install/deal with another OS to get rid of one 4kb gif file.

My big gripe originally was that I could not delete it OR move it from my desktop.

Somehow I've been able to get it moved to the root and thus out of sight (and also set to hidden) so thats enough for me for now.

I'm wiping this harddrive in the next few months anyways.

I do not feel like its just worth that much effort at this point.

It makes as much sense as fixing a loose rear speaker cover on a 89 Ford that I'm going to dump at the junkyard shortly anyways, you know?

Thanks all for the help!

I'm sure the advice will come in useful for someone in the future.

~DA

Edited by dakotaaviator, 11 August 2005 - 09:11 AM.

[farlane]

Dunno if your still on this but I had a similar problem and i followed the instructions mentioned in http://support.micro...b/120716/EN-US/

The idea is to use a file name like \\.\<driveletter>:\<path to file> to circumvent file name checking in the del and other commands.

Seems like the invalid filename characters you mentioned are not checked by Windows, but by the application that makes the file. A less optimal written program could this way make a file which cannot be removed by other programs.