Sam H. wrote:
>BTW, here is a good "killfile" utility. It is not one of the
>best, but it is certain to render a file unrecoverable by ordinary
>mortals like us:
(snip)
and Bernie responded:
Nice. However it's not a good utility. It's probably good enough for any
data you believe to be sensitive however, especially since most people
don't even know about "undelete".
For a good one you need to write random values to the old location of the
file. With the BATch file the file you want "killed" might be larger than
command.com, and the data used to overwrite it isn't random. A good program
also does this atleast seven times since that's when it's assumed to be too
costly to recover it.
//Bernie
When a file is overwritten, don't the new bytes take the place of the old? How
could it be found what bytes were previously in a given spot on the disk? Does
a disk have a way of keeping a record of previous data that was overwritten?
Would it be accessible by software means alone, or would it require special
(Drive Savers?) techniques?
