Search results

Yes, while you as a user aren't too concerned about messing with the Windows install, Eraser (and the rest of Windows) does! The second approach you propose will still not work as expected since Eraser relies on Windows for disk I/O. You can try doing an erase of C: (make a folder erasure...

I think the first thing we would need is to get .NET working in UBCD4Win (Otherwise, at least Mono.) I don't find any references to that having been achieved, so until that's done I'll have to wait for that to happen. It's a bit too late to rewrite everything in unmanaged code now.

You're probably looking for https://eraser.heidi.ie/forum/viewtopic.php?f=35&t=6014. Filling up the drive is expected when an unused disk space erase is run, you'll have to let the task run to completion otherwise data may still be left on your drive.

Hmm, Eraser never had the ability to erase temporary files and the link; you are probably thinking of CCleaner. However, if you want Eraser to do the erasures for you, there is a suggested list in the FAQ.

Nice catch.

I fixed this in 6.1, but I can't backport this to 6.0 because I would have to toss all the GUI code in the air and hope it all falls back in it's correct place... so I'll leave this as a 6.2 fix. The temporary workaround is to change your screen resolution (DPI) to 96dpi. It's annoying, and I...

I don't think so. I've never tried it on a thin client, and it's probably best for the sanity of your network admin that you don't attempt...

That's going to be a relatively low priority task; you can edit the contents of the task before you execute it.

Re: Erasing USB key Drives Did the task finish?

A wiki article is being set up by DavidHB and myself in the Trac Wiki. Please contribute to the test regime, if you have constructive ideas.

Yay! =jumps= :lol:

Nothing stopping us from putting up a sticky here linking to it though, like I did for localisations.

I think testing and such should be done by developers, the forum is targeted at end-users, most of the developer documentation is in Trac, anyway (localisation documents, building guide etc.)

We could actually host it on Trac as a Wiki.

This is old, but I think I've finally fixed the problem. All Eraser 6.0 builds after r2564 have the fix applied and should work. See #406 for details.

This is old, but I think I've finally fixed the problem. All Eraser 6.0 builds after r2564 have the fix applied and should work. See #406 for details.

This is old, but I've finally fixed the problem. All Eraser 6.0 builds after r2564 have the fix applied and should work. See #406 for details.

Fixed in r2561 for Eraser 6.2 and r2562 for Eraser 6.0. r2562 brings about reparse point support for Eraser 6.0 roughly equal to 6.2. However, when 6.2 is released there will be near-perfect reparse point support (because of #277.) I somehow think that 6.2 would be a under-the-hood upgrade for...

Woops David, you actually diagnosed it right. My bad... that happens when one attempts to crack bugs right open before getting a shot of tea.

Oh, and I'm not sure if we should include this in our document for Eraser testing. Links would only become more complicated as people become aware of its capabilities. Perhaps we should develop a regime or set of steps? Shall we discuss this offline David? Or we can start drafting a document on...