In most cases you can write a small batch file to launch killdisk with the parameter to erase all drives (-ea) as well as the 'exclude removable drives' parameter (-xr).
However, some removable disks report themselves as being fixed disks and this command will not work on those specific drives. They will be erased along with the other drives.
If you include these 2 files when making the boot disk (using the startup scripts tab) the computer will boot and run killdisk with the command line parameters to erase all drives (-ea) and exclude the USB stick (-xd=…).
As soon as the computer boots in bootdisk, these 2 files will determine the physical disk to exclude and launch the program with these parameters. It does not matter if the USB stick reports itself as removable or fixed if you use these files.
The 2 files are just a batch file to copy the exe to the program files folder and run it to get the physical drive that bootdisk booted from. The batch file uses that information to launch killdisk with the erase all drives parameter and exclude the 1 drive we booted from. It also sets the log and certificate file folders to the USB image.
BE VERY CAREFUL WITH THIS.
To boot from a CD, DVD or USB device, make sure that the device has the boot sequence priority over the hard drive.
BIOS (Basic Input Output Subsystem) is a programmable chip that controls how information is passed to various devices in the computer system. A typical method to access the BIOS settings screen is to press ESC, F1, F2, F8 or F10 during the boot sequence.
BIOS settings allow you to run a boot sequence from a floppy drive, a hard drive, a CD-ROM drive or an external device. You may configure the order that your computer searches these physical devices for the boot sequence. The first device in the order list has the first boot priority. For example, to boot from a CD-ROM drive instead of a hard drive, place the CD-ROM drive ahead of the hard drive in priority.
While you are in the BIOS Setup Utility, you will not be able to use your mouse. Use the keyboard arrow keys to move around the screen.
Before you set boot priority for a USB device, plug the device into a USB port.
To specify the boot sequence:
Some computer manufacturers allow you to select the device that contains the boot sequence from a special device selection menu. The example below uses a Dell system board.
To set boot priority using a device selection menu:
Using an incorrect BIOS setting can cause a system malfunction. Please follow the BIOS guide provided with your computer motherboard. If you read these instructions and you are not sure how to change a setting, it is better to leave it as the default setting.
When running cmd scripts (batch files) from bootdisk we run into a significant problem.
We do not know what folder the batch file is running from.
If you include the batch file when you create the bootdisk (user scripts) or double click it from bootdisk explorer, the system never lets on that it knows where the batch file is running from.
That makes it difficult to auto run programs you included, or set parameters for log / cert files if you want them stored on the boot USB.
This can be avoided if you include this line as the first line of the batch file.
cd /d %~dp0
this changes the directory to the folder the batch file is running from.
So, for instance, to run KillDisk and set the log path and certificate path to something on the boot USB you can do the following.
This is an exact batch file I used (nothing changed) that worked to boot bootdisk, run KillDisk and set the cert / log folders, erase a drive, and shutdown the system saving the log and certificate in the desired folders.
cd /d %~dp0 set dr=%~d0 set kdlog=%dr%\kd\log set kdcert=%dr%\kd\cert set kdini=%dr%\kd\ini IF NOT EXIST %kdlog%\NUL md %kdlog% IF NOT EXIST %kdcert%\NUL md %kdcert% IF NOT EXIST %kdini%\NUL md %kdini% x: cd "x:\program files\bootdisk" start killdisk -em=0 eh=80h -cp=%kdcert% -lp=%kdlog% -sd -ip=%kdini% IF NOT EXIST %kdini%\killdisk.ini copy x:killdisk.ini %kdini% cd /d %~dp0
Here is a line by line description if we want to give it to customers or make available online.
Change folder to the folder the batch is running out of:
cd /d %~dp0
Make up a variable to represent the drive letter and store the drive letter in it. The can be used whenever the boot media drive letter is needed:
Make and set variables to store the name of the folders you want to store logs, certificates and settings in:
set kdlog=%dr%\kd\log set kdcert=%dr%\kd\cert set kdini=%dr%\kd\ini
If those folders do not exist on the boot media, create them:
IF NOT EXIST %kdlog%\NUL md %kdlog% IF NOT EXIST %kdcert%\NUL md %kdcert% IF NOT EXIST %kdini%\NUL md %kdini% rem run killdisk with the desired (created) parameters x: cd "x:\program files\bootdisk" start KillDisk.exe -em=0 eh=80h -cp=%kdcert% -lp=%kdlog% -sd -ip=%kdini% IF NOT EXIST %kdini%\killdisk.ini copy x:killdisk.ini %kdini% cd /d %~dp0
In the above batch, exe was launched using start.
The batch file continues after launching KillDisk (does not wait for or know about KillDisk ending so do not use 'start' if you want a return variable form the program you are running. After execution current settings are stored locally to be used the next time killdisk runs.
Hard Drives may be erased individually in a JBOD configuration, however, it is more optimal to configure the array of disks using either a RAID0+1 or a RAID 10 configuration as depicted below.
Edit your script file to include the following lines...
@ECHO OFF FOR %%i IN (c d e f g h i j k l m n o p q r s t u v w x y z)
DO IF EXIST %%i:\user_files\KILLDISK.INI ( SET CDROM=%%i: GOTO END ) :END killdisk -ip="%CDROM%\user_files"
With that in place, no matter what drive letter the CD gets assigned, this script will seek for the drive letter that contains "\user_files\KILLDISK.INI".
Formatting alone is not enough. You should back up all data you need saved then use a data destruction program (killdisk is one) to overwrite all sectors on the disk. Then re-install the OS and copy your data back to the drive.
Any data recovery can retrieve your data after formatting. Although the charity probably won't go looking for old data, you have no idea what other uses will do. The charity might just turn around and sell it and there are people who buy computers just to see if they can get old data from them. You should definitely wipe the drive. Use a program designed to make data unrecoverable. Killdisk in one of them.
If the machines are being de-commissioned it is imperative that the data be securely wiped form the drive. There are software tools designed to do exactly that. Killdisk is a tool that will overwrite every sector on the drive several times to ensure even the best data recovery labs could not restore a single file from the computer.You can even prepare a script for bootable disk that can sanitize a machine automatically, after you insert CD or USB and turn off the PC.
You should use a software like killdisk. The striping information is stored on sectors on the disk, and since Killdisk erases all sectors, it will erase those sectors as well.
Yes, it does. You can place line into for example autoexec.bat to destroy all HDD (Hard Disk Drive) found. See help for the details.
All types of HDD are supported. KillDisk will clean it up properly if hard disk drive or USB disk is visible in BIOS, or accessible under Windows environment (device drivers properly installed).
To be able to use HDD again you need to:
The software uses standard SCSI/ATI function calls (through Windows or DOS) to get serial numbers from hard drives.
Most, if not all, RAID controllers do not properly process these requests.
Typically, a RAID controller is used to hook up 2 or more hard drives in such a way that the operating system thinks it is one drive. Therefore, the operating system can not access the drives individually. When queried for a hard drive's serial number, the RAID controller does not know which serial number to return, so it does not return a serial number at all. All RAID controllers tested will do this even if there is only one drive in the RAID set.
KillDisk is a DOS program and it does not matter which operating system is installed on the machine. If you can boot in DOS mode (from boot diskette for example), you can erase any drives independently of Operating System installed. The only requirement is that machine be a standard PC (Intel-architecture, not PPC, not ARM, not MIPS).
KillDisk runs on any PC-compatible machine, which is based on Intel architecture. It does not run on MIPS, ARM, PPC processors, for example it won't run on Sun SPARC systems or iPad & Android tablets.
Here are a few steps to accomplish this:
@ECHO OFF ::KD-SN.CMD FOR %%i IN (c d e f g h i j k l m n o p q r s t u v w x y z)
DO IF EXIST %%i:\User_Files\KILLDISK.INI ( SET DrvLtr=%%i GOTO END ) :END COPY %DrvLtr%:\User_Files\KILLDISK.INI X:\KILLDISK.INI For /f "skip=2 tokens=2 delims=," %%i in ('wmic bios get serialnumber /FORMAT:csv')
do (set "servicetag=%%i") ECHO logComments="Computer Serial Number: %servicetag%">>X:\killdisk.ini KILLDISK -ip="X:\" :EOF
The script will search for the KILLDISK.INI file and copy it to a temporary location. Then a WMI command queries the system to acquire the systems serial number. This value is then stored directly into the KILLDISK.INI settings file. Once erasure is complete, the PDF certificate will contain all pertinent information of the erase session.
To append the ServiceTag number into the KILLDISK.LOG file (including date/time stamp), you may use the following example:
echo %date:~6,4%-%date:~0,2%-%date:~3,2% %time:~0,8% ServiceTag#: %servicetag% >>
You may add the following lines to your script after the KillDisk command:
For /f "skip=2 tokens=2 delims=," %%i in ('wmic bios get serialnumber /FORMAT:csv')
do (set "servicetag=%%i") ren *.pdf *.ServiceTag-%servicetag%.pdf
These commands will use a WMI call to query for the computer system serial number. The next line renames the KillDisk pdf certificate file name to include this number.
To append the ServiceTag number to the KILLDISK.LOG file (including date/time stamp), you may use the following example:
echo %date:~6,4%-%date:~0,2%-%date:~3,2% %time:~0,8% ServiceTag#: %servicetag% >> KILLDISK.LOG