gzwl7HiJNXra
New Member
I'm a new user, so forgive if this question has been answered 1000 times. I couldn't find anything in the places where I looked (help file, in this forum). The scheduled erase of free space on my D: drive finished, but it includes the following log entries:
01-23-2006 22:00:00: Running task (D:\).
01-24-2006 06:27:35: Possible failure running task (D:\).
01-24-2006 06:27:35: Failed to erase unused space on D:\4NT302\4nt.exe.
01-24-2006 06:27:35: Failed to erase unused space on D:\4NT302\Bchild.dll.
01-24-2006 06:27:35: Failed to erase unused space on D:\4NT302\ipworks6.dll.
01-24-2006 06:27:35: Failed to erase unused space on D:\4NT302\ipwssl6.dll.
01-24-2006 06:27:35: Failed to erase unused space on D:\4NT302\Language.dll.
01-24-2006 06:27:35: Failed to erase unused space on D:\4NT302\TakeCmd.dll.
01-24-2006 06:27:35: Failed to erase unused space on D:\iTunes\iTunesHelper.exe.
01-24-2006 06:27:35: Failed to erase unused space on D:\iTunes\iTunesHelper.Resources\en.lproj\iTunesHelperLocalized.dll.
01-24-2006 06:27:35: Failed to erase unused space on D:\iTunes\iTunesHelper.Resources\iTunesHelper.dll.
01-24-2006 06:27:35: Failed to erase unused space on D:\Local\mgSimplify\hooksub.dll.
01-24-2006 06:27:35: Failed to erase unused space on D:\Local\mgSimplify\mgSimplify.exe.
01-24-2006 06:27:35: Failed to erase unused space on D:\Local\UpTime.exe.
Since Eraser is probably looking at NTFS indices to find where the free space is (and hopefully locking each index before it erases the sectors that particular index covers), how would it ever be looking at specific files and trying to erase unused space? Also, since those files that are listed are most definitely <b><i>not</i></b> "free," I want to find out why Eraser is trying to erase them (or any other actual file). Please, what's going on here?
01-23-2006 22:00:00: Running task (D:\).
01-24-2006 06:27:35: Possible failure running task (D:\).
01-24-2006 06:27:35: Failed to erase unused space on D:\4NT302\4nt.exe.
01-24-2006 06:27:35: Failed to erase unused space on D:\4NT302\Bchild.dll.
01-24-2006 06:27:35: Failed to erase unused space on D:\4NT302\ipworks6.dll.
01-24-2006 06:27:35: Failed to erase unused space on D:\4NT302\ipwssl6.dll.
01-24-2006 06:27:35: Failed to erase unused space on D:\4NT302\Language.dll.
01-24-2006 06:27:35: Failed to erase unused space on D:\4NT302\TakeCmd.dll.
01-24-2006 06:27:35: Failed to erase unused space on D:\iTunes\iTunesHelper.exe.
01-24-2006 06:27:35: Failed to erase unused space on D:\iTunes\iTunesHelper.Resources\en.lproj\iTunesHelperLocalized.dll.
01-24-2006 06:27:35: Failed to erase unused space on D:\iTunes\iTunesHelper.Resources\iTunesHelper.dll.
01-24-2006 06:27:35: Failed to erase unused space on D:\Local\mgSimplify\hooksub.dll.
01-24-2006 06:27:35: Failed to erase unused space on D:\Local\mgSimplify\mgSimplify.exe.
01-24-2006 06:27:35: Failed to erase unused space on D:\Local\UpTime.exe.
Since Eraser is probably looking at NTFS indices to find where the free space is (and hopefully locking each index before it erases the sectors that particular index covers), how would it ever be looking at specific files and trying to erase unused space? Also, since those files that are listed are most definitely <b><i>not</i></b> "free," I want to find out why Eraser is trying to erase them (or any other actual file). Please, what's going on here?