Search results

  1. P

    Checksum (MD5/SHA-1) Mismatch

    Yes those builds had a mismatch but the latest beta hashes are correct.
  2. P

    Eraser 5.8.8-beta1 Released

    Still all the same.
  3. P

    Eraser 5.8.8-beta1 Released

    No, only way to upgrade without having some files not being replaced is to uninstall the existing Eraser first and restarting after that. Not doing that will let you upgrade Eraser as well but then silently fail to replace those old files.
  4. P

    Eraser 5.8.8-beta1 Released

    Some localization problems in at least two places when retaining configuration from the previous version. One in the about dialog, the other one effectively killing custom erasure methods. +Verified the workaround fix for the drive corruption bug.
  5. P

    Potentially disastrous bug?

    Thanks for confirmation and the updates on this matter. Having V5 refuse to wipe sparse files like V6 with this pattern should be a good enough fix for now.
  6. P

    Potentially disastrous bug?

    Don't have a spare thumb drive at the moment so I trashed a partition for you again. :lol: Is this the information you wanted?
  7. P

    Potentially disastrous bug?

    Well Orbit is most definitely not able to do that on its own, only after using Eraser. You say the same happened to you without touching the files with Eraser? About starting the download by itself, this is a simple feature which can be turned off. :wink:
  8. P

    Potentially disastrous bug?

    I recently found my system partition totally inaccessible to Windows because it was no longer recognized as NTFS. After first suspecting hardware failure of some kind and then digging around a little it appears there are two factors that lead to this major loss of data (without backups that is)...
Back
Top