similar to: slightly OT: dban

I'm integrating DBAN (http://dban.sourceforge.net/) into our PXE boot menu system (using vesamenu.c32) but it just hangs when I'm using vesamenu.c32 and confusingly when I revert our menu system to using vesa.c32 it works ok. I've stripped out any extraneous configuration but it still seems to have the same problem. When I use this in pxelinux.cfg it boots into DBAN ok: default

greetings list, i am creating a new thread because of comment made by; From: Nicolas Thierry-Mieg <Nicolas.Thierry-Mieg at imag.fr> in thread "Subject: [CentOS] erase disk". in past readings about; erasing an hdd, forensics of hard disk drives, dban, destroying hdd i submit these links for those who may wish to further their knowledge on primaries of hdd forensics;

Hello, I'm interrested in testing any possible workaroud for the Dell Optiplex GX620 keyboard problem, as I just can't downgrade the BIOS version on each and every Gx620 I have to (re)install ! (Plus I can't find a link to download the old A10 BIOS itself.) Don't hesitate to give me guidance on how to proceed, because I can't find anything relevant on the website

Sorry for the delay, we were too busy drinking and playing with explosives yesterday. :) Here are some tests. We did one on a similar machine and it worked. We deleted the configuration file, obviously. # Dell OptiPlex GX620 ISOLINUX 5.11 5.11-pre7 isolinux: Starting up, DL = 82 isolinux: Loaded spec packet OK, drive = 82 isolinux: Main image LBA = 00000115 isolinux: Image checksum error,

Same CD. Any Linux distribution without the 5.X series boots on this machine. We can use 4.06 and it boots just fine. It's not the computer's hardware. Like I said, we can take the CD out of the GX620 and place it in the 9010 and it boots. Put 4.06 on the CD, and they both boot. Patrick On Sat, Jul 6, 2013 at 7:18 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Fri, Jul 5,

Hi, I was discussing the common practice of disk eradication used by many firms for security. I was thinking this may be a useful feature of ZFS to have an option to eradicate data as its removed, meaning after the last reference/snapshot is done and a block is freed, then write the eradication patterns back to the removed blocks. By any chance, has this been discussed or considered before?

I'm not exactly sure what you need. Is this it? ISOLINUX 4.06 0x513e88f5 isolinux: Starting up, DL = 82 isolinux: Loaded spec packet OK, drive = 82 isolinux: Main image LBA = 0000011D isolinux: Main image read, jumping to main code... I created an iso with isolinux-debug.bin as the boot loader and booted it on that machine. If this is not what you are looking for, what are correct steps?

Hello all. Again I call upon the greats of this mailing list to help me with an issue related to MEMDISK - notably when paired with various Dell OptiPlex and Latitude systems. The issue presented itself sometime ago and I best dealt with it by remaining with version 3.83 of the SYSLINUX package. But valuing the improved changes fostered by newer versions, I would prefer to move forward with

System: Dell OptiPlex GX620 (Both BIOS A10 and A11 affected) Medium: Physical CD-RW Observed: ISOLINUX 5.11 0x51D1AE48 ETCD_ is the only line displayed on-screen. A flashing cursor trails at the end of the line. Escape key does not return boot: prompt. Line1 of syslinux.cfg: DEFAULT vesamenu.c32 Note: Reverting to syslinux-4.06 allows for successful booting on the same system. Patrick On Tue,

James Szinger wrote: > Disclaimer: My $dayjob is with a government contractor, but I am speaking > as private citizen. > > Talk to your organization's computer security people. They will have a > standard procedure for getting rid of dead disks. We on the internet > can't > know what they are. I'm betting it involves some degree of paperwork. > > Around

On 15 Nov 2014 05:06:52 +0200, Ady wrote: > > I would start by updating the BIOS. Prudent advice. As it turns out, I'm already at the latest version. On 15 Nov 2014 07:31:27 +0100, Geert Stappers wrote: > > And would reduce 'iPXE => pxe.0 => lpxelinux.0 => "vmlinux"' > into 'iPXE => "vmlinux"' That makes sense generally, but at

DBAN is obsolete. NIST 800-88 for some time now says to use secure erase or enhanced security erase or crypto erase if supported. Other options do not erase data in remapped sectors. Chris Murphy

Hi, I have a dozen of drives, ranging from 10Gb to 200Gb. I want to wipe them clean before donating them. I have a IDE/SATA to USB converter that works. I can see the drives properly. DBAN does not currently support external USB drive. Any other alternatives? -- Thanks http://www.911networks.com When the network has to work

This same system boots with syslinux-4.06. Let me know if there is any further info you need. We tried syslinux-5.11-pre5 as well. Patrick Verner partedmagic.com

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I am having trouble with one Dell system and pxelinux: The keyboard does not properly work. The computer boots, I press F12 to select the boot device, then I select the network card. Up to that point the keyboard works fine. Then pxelinux is booted, and I use menu.c32 to display a menu (or vesamenu.c32 - same result). Now the keyboard does not

We have tried compiling the binaries our self and using the pre-compiled in the syslinux tar ball as well. It just locks up with the text we provided. The problem is booting from CD, booting from USB works. I suspect the problem is in isolinux.bin. The CD only fails on this one machine. It works on everything else we tried. 4.06 worked without any issue on this same machine. Parted Magic has been

Looks like I can't install syslinux's bootloader on an ntfs partition? What I'd like to do is remotely setup a bootloader to wipe the hard drive contents on old assets. I was kind of hoping, that I could install syslinux on a remote workstation, and then throw a dban image and the corresponding menu and syslinux.cfg files on the remote workstation and then reboot it and have the

A kind request for help please. MEMDISK is causing an issue with the Dell OptiPlex GX280 and GX620 platforms. Booting a PC-DOS/Ghost, disk image is successful (and proper) when using version 3.83. See results below: MEMDISK 3.83: Ramdisk at 0x07eeaa00, length 0x007bc000 command line: initrd=images/ghostclient/280_620/osbootc.img BOOT_IMAGE=memdisk MEMDISK: Image seems to have fractional end

Very Dumb Question : I have tried about four times now, using an old pentium2 with two hard drives (20 GB and 30 GB) to install both CentOS 4.4 and Fedora Core 6 in such a way as to enable dual-boot between them. I've tried it by installing 4.4 first, and then FC6. I've tried it by installing FC6 first, and then 4.4. I've tried it with and without giving the installer permission to

I tried to upgrade one user's system, a Dell Optiplex GX620, and yum got a GPF. After *much* grief, I finally gave up, and rebuilt the system. Or, rather, I'm trying to. First problem: I did a minimal install from the graphical installer - I don't know if that's relevant - but when it boots, it does *not* install the NIC driver, tg3, on boot. I've got eth0 defined in