On a XP computer, I've tried to do a wipe free space a couple times, usually I let it run overnight and it's BSOD'd when i wake up in the morning. Today I tried another one and decided to watch it. it did all the cluster tip areas, then filled up my hard drive, but when it got to the point of where it should erase the temp folder and files it creates, it sat there for a couple hours, not progressing, and I couldn't even get it to show me a status by double-clicking the task name (just said querying). I attempted to cancel the task which it didn't so i just exited Eraser which worked for some reason.
Anyway, when I went into the folder and sorted the files by size in increasing order, I was able to erase the first couple manually. then i got to a file named ,y)NaBafg}r3l6CeXo, and when i try to do that manually, i get a pop-up that says unknown parameter y)NaBafg}r3l6CeXo, press enter to continue. notice how its that file name minus the comma, so I'm assuming when you use the explorer integration, it just adds command lines to the gui scheduler, where a comma signifies a parameter in the command line.
Maybe a comma and some other special characters need to be taken out of the random name generating? and maybe a timeout or something needs to be added into the wipe free space routine so it doesn't get hung up on files or can at least report them, which is what I'm assuming happened since it sat for over two hours without any increase in free disk space on my hard drive which i should have seen as it successfully erased the temp files it created.
Anyway, when I went into the folder and sorted the files by size in increasing order, I was able to erase the first couple manually. then i got to a file named ,y)NaBafg}r3l6CeXo, and when i try to do that manually, i get a pop-up that says unknown parameter y)NaBafg}r3l6CeXo, press enter to continue. notice how its that file name minus the comma, so I'm assuming when you use the explorer integration, it just adds command lines to the gui scheduler, where a comma signifies a parameter in the command line.
Maybe a comma and some other special characters need to be taken out of the random name generating? and maybe a timeout or something needs to be added into the wipe free space routine so it doesn't get hung up on files or can at least report them, which is what I'm assuming happened since it sat for over two hours without any increase in free disk space on my hard drive which i should have seen as it successfully erased the temp files it created.
