Search results

No, the computer with the Compaq Smart device failed.

DBAN does not have USB drivers, so you had two choices: (0, 0, 0, -, -) Hard Disk (0, 0, 1, -, -) Partition Both of these represented the internal disk. USB disks never appear and are never selectable. (This feature might be in a future release, though.) DBAN does not read filesystem...

Edit the A:\SYSLINUX.CFG file.

First, this does not indicate a problem. Second, the geometry reported for large disks is usually a fiction. Google for "INT13" if you want to learn more.

Was the disk formatted by Microsoft Windows 95/98/Me prior to running DBAN on the computer?

This is false. The official DBAN release gives you two chances to bail, and it will fail if you just blindly mash the enter key. The wipe parameters cannot be changed after the wipe is started. Yes. Drive letters assigned by Microsoft Windows do not directly correspond to the device numbers...

The argument of the "--method" parameter is the thing that is important here. The dod3pass and dodshort both call the DoD Short method. All other aliases call the original DoD long method. The DoD Short method in DBAN more closely matches the current specification than the long method...

It will become available when a cheque arrives that says "make this happen".

DBAN does not have FiberChannel drivers for lack of space on the floppy disk. The next minor point release will use a different format to increase space so that drivers for USB and Firewire might be added.

DBAN cannot be interrupted after the wipe starts. Push the reset button and restart DBAN with the intended wipe, or wait for the first round of the Gutmann method to finish.

Disabling the floppy driver does not disable the floppy check, it just prevents DBAN from hanging on some computers. If you want to disable the prompt, then you must edit the rc.

Long: dwipe_pattern_t patterns [] = { { 1, &dod[0] }, /* Pass 1: A random character. */ { 1, &dod[1] }, /* Pass 2: The bitwise complement of pass 1. */ { -1, "" }, /* Pass 3: A random stream. */ { 1, &dod[3] }, /* Pass 4: A random character...

The dban-1.0.6 release has been published: http://prdownloads.sourceforge.net/dban/dban-1.0.6_i386.zip?download http://prdownloads.sourceforge.net/dban/dban-1.0.6_i386.iso?download This release has fixes for all reported performance issues.

Disk size (and other attributes) will eventually be available through the GUI. Reporting drive letters from Microsoft Windows is not planned because doing this safely requires reading the registry. Consider this alternative: 1. Put an empty NTFS filesystem in the partition that you wish to...

I must check the documentation before I can answer this question. It might be faster for you to read the source code.

http://www.cipherserver.com/phpbb2/view ... 337338e5ab

No, Promise has been slow to release good drivers. Your best choice would be to move the disks to another computer for wiping.

First, run the BIOS setup program and ensure that the boot order is correct. The floppy drive must be checked before any other device. Second, what is the error message? A blank screen? A line that says "SYSLINUX"? A line that says "INVALID BOOT DISK"?

Drive letters cannot be reliably derived from the partition numbers that DBAN shows because they can be arbitarily reassigned by Microsoft Windows. This information is in the log file, but it is not available through the GUI.

This boot label disables the floppy driver. Some laptop computers without floppy drives crash when a floppy driver is loaded. This option prints kernel messages. Each line is printed by a driver when it gets loaded. The A:\KERNEL.BZI file is the Linux kernel.