Date: January 31, 2005
From: NoClue, Bob
BobNuke Disk v. 1.0
Introduction:
Anybody who has 'nuked
and paved' a lot of machines
will know that nuking with format
or fdisk is,
quite often, not enough. Drive overlays or disk managers (like EZ
Drive), viruses or even partition table corruption require
that you fully remove the existing partition table. format
won't touch the partition table at all. fdisk
won't remove an existing partition table...all entries can be removed
so that it can look like there are no partitions, but the table and its
descriptors and the MBR remain.
To address this problem, CompuClues Forum Member Bob posted
a debug routine, that has come to be known as the 'BobNuke'
routine. By booting to a DOS (or Win9x) floppy and running the routine,
you can wipe out the Partition Table, the MBR, and the filesystem.
Over the past few years, I have begun to BobNuke every drive during the
nuke and pave. I find that I can avoid a lot of hassles that way. I
have run this routine on hundreds of drives over the years, and never
once had a problem. However, I should add a couple of caveats here:
First,
make sure that this procedure is safe to do on your hard
drive. I don't know how to tell you to do that, but you take
full responsibility for what you do to your computer.
I
would think long and hard before using this routine on a laptop
computer. I'd probably call the laptop OEM and ask their
support team about the problem and this routine before going ahead with
it. It wouldn't surprise me to find out that a disk manager
program supplied with a laptop was essential to the operation of the
laptop.
Most
importantly, you should understand a little about what it is that you
are doing here. The BobNuke routine is designed to wipe your hard drive
clean. If you haven't done a current backup before running it, you
won't have to worry about doing one later...all information on the
drive will be lost. I'd suggest you read the 'Nuke
& Pave 101' document in
the Arcanum at bitzenbytes.com before you attempt this. If you have any
questions about anything in the document, post them in the CompuClues
Forum.
Okay...now
let's get to the image file...
As I mentioned above, I
use the BobNuke routine every time I nuke and pave. As many times as I
have done it, I can't seem to commit the steps to memory. I have even
gone so far as to print out the steps, and keep the paper on the bench.
Those that know me will tell you that I hate having to rely on
dead-tree media for anything. :)
Also,
I often find
myself out in the field without my boot disk. With the prevalence of NT
kernel-based operating systems (NT, 2k, XP) , it's not as easy to make
one as it used to be. I had considered uploading an image file of my
trusty Win98 boot disk, but figured that Microsoft might have something
to say about that. Open Source to the rescue...
FreeDOS
is an open-source DOS-compatible operating system. It includes lots of
DOS-style utilities, including debug,
fdisk
and format.
I created a FreeDOS bootable floppy, then copied the files I needed to
it. I made a text file containing the debug routine, and a batch file
to run debug
and import the text file into it. I then used dd
for Windows to
create an image of the disk. To write the image back to floppy, I use RawWrite
for Windows.
I
have also uploaded the current (at the time of this writing) version of
RawWrite for Windows to the Bitzenbytes
Downloads section.
How to create and
use
this disk:
- Download and
unzip rawwritewin
(no install necessary, I just unzipped it to \Program
Files\rawwritewin\ and made a shortcut to the .exe).
- Download bobnuke.zip
and unzip it to a place where you can find it later.
- Pop a floppy
disk in
the drive.
- Run rawwritewin.
- Browse to bobnuke.img
(the file you extracted in step 2)
- When rawwritewin
has
finished, put the floppy disk into a machine that needs its C: drive
nuked.
- Boot to the
floppy.
- Hit Enter twice
to get
past the date and time prompts.
- Type bobnuke
and hit Enter.
fdisk is included on the floppy for creating and checking partitions.
So is a lot of other stuff:
KERNEL.SYS
COMMAND.COM
DEBUG.COM
XCOPY.EXE
FDISK.EXE
FORMAT.EXE
MOVE.EXE
CHKDSK.EXE
DISKCOPY.EXE
DEFRAG.EXE
DEFRAG.HLP
MEM.EXE
EDIT.EXE
DISKCOMP.COM
HELP.EXE
FC.EXE
APPEND.EXE
BOOTFIX.COM
APROPOS.BAT
WHATIS.COM
ASSIGN.COM
JOIN.EXE
FASTHELP.EXE
FIND.COM
SORT.COM
DELTREE.COM
GRAPH-HP.COM
GRAPH-PS.COM
GRAPHICS.BAT
GRAPHPIN.COM
ATTRIB.COM
TDSK.EXE
CHOICE.EXE
COMP.COM
CTMOUSE.EXE
CTMOUSE2.EXE
DEBUG98.COM
DELTREE2.COM
DEVLOAD.COM
EMM386.EXE
EXE2BIN.COM
FDAPM.COM
HIMEM.EXE
LABEL.EXE
MIRROR.EXE
MODE.COM
MORE.EXE
MOUSE.EXE
NANSI.SYS
PRINT.COM
PRINTQ.EXE
RECOVER.EXE
REPLACE.EXE
SHARE.COM
SUBST.EXE
SWSUBST.EXE
SYS.COM
TREE.COM
TUNZ.COM
UNDELETE.COM
UNFORMAT.EXE
XMSTEST.EXE
XMS2TEST.EXE
BOBNUKE.TXT
BOBNUKE.BAT
Most of the stuff will seem familiar to those of you who remember DOS.
I can't seem to get Help working, but whatis commandname
will give you an idea of what each command does. |