Chris4877
New Member
Hi, everyone!
Somewhere on this forum is a topic about sparse files, and the Eraser error "Task completed with errors." I can't find it right now, to give a link, but I did read through it a few weeks ago.
I have been getting this error, too, and, when I looked at the details in the log, I found that it had something to do with "sparse" files.
Now, I'm just a humble user, not a programmer or some other kind of IT professional, so a lot of what is in the topic I mentioned above is incomprehensible to me.
Having said that, I have three points to make:
1. I only noticed the errors after installation of the latest update to Eraser.
2. The drive on which I was performing the erase is compressed NTFS (Win7 Ultimate x64).
3. When I de-compressed the drive, the Eraser errors went away, and when I re-compressed the drive, the errors returned.
I should also add that the files are no longer visible after task completion, which is probably good enough (I hope).
Just my 2 cents' worth, maybe it will help in correcting any bugs associated with this error (if, in fact there are any bugs).
Best regards to all,
Christopher Souter
(Sydney, Australia)
Somewhere on this forum is a topic about sparse files, and the Eraser error "Task completed with errors." I can't find it right now, to give a link, but I did read through it a few weeks ago.
I have been getting this error, too, and, when I looked at the details in the log, I found that it had something to do with "sparse" files.
Now, I'm just a humble user, not a programmer or some other kind of IT professional, so a lot of what is in the topic I mentioned above is incomprehensible to me.
Having said that, I have three points to make:
1. I only noticed the errors after installation of the latest update to Eraser.
2. The drive on which I was performing the erase is compressed NTFS (Win7 Ultimate x64).
3. When I de-compressed the drive, the Eraser errors went away, and when I re-compressed the drive, the errors returned.
I should also add that the files are no longer visible after task completion, which is probably good enough (I hope).
Just my 2 cents' worth, maybe it will help in correcting any bugs associated with this error (if, in fact there are any bugs).
Best regards to all,
Christopher Souter
(Sydney, Australia)