Search results

Actually Eraser 6 now converts user-provided expressions to a regular expression. I don't think it would be too much to change that in 6.2 -- do you want to open a Trac ticket for it?

Re: Small amount of space left after wipe. Did the task run to completion? If it did then we've got a problem. Otherwise, if you're watching the amount of free disk space decrease, it's normal.

So, the installation proceeds fine but when you try starting up the program nothing happens on the screen? Does Task Manager show Eraser.exe running on your computer?

I'd fix it in the coming days; if the fix is urgent you can try a nightly build on our downloads page (I'll state the build to use in the ticket when it's fixed) Regular nightly build warnings apply.

If you're referring to the installer problem, a quick Google will show: http://www.google.com/search?q=windows+ ... error+2203.

Which same problem? The OP describes two.

Re: [v5&6] "Elevation Required" message while Erasing Free S And... what is the problem you're seeing? How do you know it doesn't work? Files can still be added to Eraser for erasure. Have a look at the documentation, which include screenshots and step-by-step instructions.

Have you tried paragraph 8 of http://eraser.heidi.ie/forum/viewtopic.php?f=35&t=6215?

Good catch. The command line does not respect the method GUID when specified on the command line. I've opened Trac Ticket #443.

I've also fixed a database bug that was slowing down the forum and the website. I've clicked around and the forum does seem much for snappy now. Do you see it too?

Possible - yes; likely - no. More often than not the problem with unused space erasure is not that it doesn't work, but that it gives users a false sense of security. Let me explain. While the process works very well (to date, I've not had a single confirmed report of Eraser's unused space...

Re: Images deleted from right click Erase are easily recover You probably have a spare copy residing somewhere, such as in the volume shadow copies. Empty those, run an unused space erasure, and check again.

Good point - then I think it pretty much boils down to chance; there's no way to determine whether Eraser caused a drive to fall off the cliff even if two drives worked the exact same way, except one received erasures and the other did not, because of either experimental error or chance. To...

Yeah, .NET assemblies have two versions. One is the assembly version which is used for .NET to state dependencies, and that would affect loadability of task lists; the other is the file version, which is what you can see in Explorer. I left the assembly version but changed the file version. The...

Oh, just a point: you need to include the correct Eraser assemblies that are for your particular platform. If you are building an x86 WinPE environment you'll need to get the Eraser.Util.Native.dll from the 32-bit installation package (or a 32-bit installation of Eraser -- running on 32-bit...

There have been concerns about these ever since we've had engineers using Eraser... but so far there hasn't been complaints that Eraser can measurably reduce the life of a mechanical disk drive. SSDs are obviously a different matter altogether. Don't try erasing unused space on your SSD: that...

Fixed in r2652.

Darn, I missed that one. 6.0.11 should not have this problem. I'll fix the code now.

Hello, I'm happy to announce the immediate release of Eraser 6.0.10. Eraser 6.0.10 has got a few stability bugs fixed. You are highly encouraged to upgrade to this version. Read the full announcement and download it from there. Joel

It does seem like a corrupt Windows Installer Database. I don't know any workarounds here except to reinstall Windows. There are fix-it tools available; you can try http://support.microsoft.com/kb/2438651.