Search results

It's Eraser checking for certificate authenticity for the plugins installed. Eraser's built on plugins. And it needs to check that they are legitimate before loading them. How we do that is to state that all automatically loaded plugins need signatures on the plugins and along with this most...

That isn't exactly true. In this case I believe your download is just corrupt.

Re: Conflict between Eraser 6 and Windows 7 administrator ac Glad to hear it =)

I've been doing some Linux development over the last few months (during my absence), but I've still not found evidence that Eraser's concept would work on Linux. So I doubt I'd embark on this. Clarification: concept as in approach to solving the problem of data residue.

The CLI was never official for 6.0. So I don't want to add things to a released, stable branch. I'm working on a CLI in 6.2 But Eraser 6.2 is another ambitious project in itself. And it's hard to find resources to maintain both branches.

Have you exited Eraser before running a new copy?

And even with TrueCrypt, there are some issues with lifespan of SSDs. For now, erasure and SSDs don't mix. There's some discussion (especially among my Electronic Engineer friends) that a properly implemented TRIM will permanently erase data. But I don't think there's formal evidence for it...

If you require a more helpful answer, then please tell us what it says in the log.

Which version of Eraser?

Ah, that's a problem. The run-on-restart tasks now only work for one-time restart tasks. You might be able to get away with creating a new task via command line and task scheduler.

Encryption programs (I'm only going to use TrueCrypt as a representative sample) will erase the disk contents before writing the encrypted partition in-place. So that stuff's probably fine. The unencrypted partition, however, might still have data recoverable. Eraser doesn't work on Linux, and...

Yes, Eraser can't handle compressed drives. This is because the way files are stored when the contents are compressed by NTFS isn't in a form which Eraser can readily erase and guarantee removal. Like you've mentioned, uncompressing the drive would let Eraser work, but it still might not...

Have you tried reinstalling Eraser? Or repairing the install?

Might be in the works for Eraser 6.2. See http://eraser.heidi.ie/trac/ticket/355.

If you do turn of shadow copies, then yes, even as an external drive Eraser will erase the space previously held by VSS. To turn it off: It's in Computer properties (one of the stuff hidden pretty deep). You might want to google on how to turn of System Restore.

Sorry for the delay. Just uninstall what version of Eraser you have at the moment, and then re-install. That should do it.

The crash reports there don't give any useful information (because it's written using .NET). If you got BlackBox enabled, upload the crash report.

Haha, I don't think I have the 5.8 (.hlp?) file any more. It's been that long. Sorry.

Hmm, that is one way of looking at it, but I've implemented the erasure the way it is now because I'd rather have those areas marked erased as really erased. Free space on your disk is a dynamic (i.e. changes with time) concept, it's hard to guarantee any sector being overwritten multiple times...

Did it eventually resolve itself? If it did, see my other thread. I'd like to know what you did to get it to stall.