Search results

  1. D

    Problems with wireless keyboard

    This advice is correct, and you probably found the correct option for enabling USB keyboard support in DBAN. The DBAN 1.0.x releases requires that USB keyboards remain in legacy compatibility mode. If the change won't stick until the DBAN blue screen starts, then start DBAN at the black...
  2. D

    Erasing data on a hard drive with bad sectors

    DBAN will report "failed" if it can see the bad sectors, but it will try to finish the wipe. Note that disks with bad sectors are often wiped very slowly.
  3. D

    SATA-II HDD: Not supported?

    DBAN probably doesn't have a driver for your motherboard chipset. Use another product, or wait for the DBAN beta release.
  4. D

    Any other possibilities?

    The CRC error indicates that the memory or CPU in this computer is bad. When these parts fail entirely, you'll probably lose some data.
  5. D

    SATA-II HDD: Not supported?

    Are you having problems with DBAN and a specific disk? Provide manufacturer and model information.
  6. D

    DBAN problem - recycling reboot

    The computer is crashing and rebooting into Microsoft Windows. This is usually caused by bad memory. Download the Memtest86+ utility and run it on this computer. DBAN will not run reliably if the memory diagnostic reports any bad lines.
  7. D

    DBAN for wiping multiple drives in a Sun Enterprise 3500

    Contact Techway for a Sun Sparc solution.
  8. D

    DBAN 1.0.7 is the current release.

    Ask this question in the Eraser forum.
  9. D

    Super slow performance

    DBAN is known to be slow on computers with the Intel 945 chipset. A driver for this hardware will be in the next DBAN release. Until then, use a different product to wipe these computers.
  10. D

    please help verify errors ......[blanking]

    Verify errors mean that the hard disk is bad. Physically destroy it.
  11. D

    :o StiLL CONFUSED about ISO

    Read this two documents and then describe what confuses you. The documentation will then be fixed.
  12. D

    Maxtor External HD

    The current DBAN release does not recognize external USB disks. A potential solution is to create an empty filesytem on the external disk and run a freespace wipe with Heidi Eraser.
  13. D

    DBAN 1.0.7 is the current release.

    DBAN 1.0.7 is the current release. Please upgrade to the current release before making a support request. ... _id=439240
  14. D

    Bad Sectors

    If you are asking these questions, then you should physically destroy the hard disk. Most modern hard disks use logical 512 byte sectors, but do not assume any behavior that happens beneath the drive firmware.
  15. D

    How to Compile v1.0.6 Correctly?

    First, ensure that you have applied the patches from the DBAN source tarball. Second, use the uclibc instead of glibc. Running DBAN in a glibc environment is untested and unsupported. It follows that you must use the obsolete gcc wrappers. Third, the rc and dwipe in dban-1.0.6 are...
  16. D

    Better seed?

    Neither, because any part of a random file is also random. If you are splitting a large random file into smaller 512 byte seeds, then remember to use the `dd skip=` option or all of the seeds will be identical.
  17. D

    Destroying data on another computer using Nuke Disk

    You can use the DBAN media on any computer. Download the software on a computer with an Internet connection and follow the instruction in the README.TXT file.
  18. D

    help with failure code 255

    Send the log file to me. Run the wipe again, but this time start it with "quick" at the boot prompt. One of the disks probably has bad sectors.