If I had already deleted the data I wanted to make sure was gone, I would want to set all un-used parts of the drive to 0's. (where the data used to live) because deleting doesn't actually get rid of the data, just the pointer to that data. Then by writing 0's to the unused parts of the drive, your are effectively overwriting what used to be there with non-sense. As another poster pointed out, there seems to be a threshhold that the data is considered un-recoverable, mentioning that for the company he worked for previously, was 9X. The standard for DoD (Deriks Boott & Nuke) I read was 7X. Anyway, I'll be happy with the 2 I have already gotten and seems like the drive is on it's last leg with the 3rd. B-) On Monday 06 December 2004 04:05 pm, Doug McGarrett wrote:
At 08:39 AM 12/6/2004 -0700, Brad Bourn wrote:
Isn't there a way to set all unused parts of the drive to 0's?
B-)
On Monday 06 December 2004 08:35 am, Anders Johansson wrote:
On Monday 06 December 2004 16:16, Brad Bourn wrote:
Is there a simple command I can run to make sure that the data on the drive after I delete the source code dir is completely gone?
/snip/
I think you have it backwards; what you want to do is set all _used_ parts of the drive to something useless. The convention is to set everything to the letter "e". Once I knew why, but I no longer do. It is probably a succession of 1's and 0's. --doug