I noticed that in CC v2.30 there's an useful extra feature in CC. When CC cleans the MFT of a drive then CC now gives an estimate of how much time it will take to ""wipe"" that particular MFT. Although I have asked for a progress bar I think this addition is good enough. No need any more for a progress bar.
Thanks !!!
2) As far as I (and a few others) know the WMFT process is to create a number of small (600 byte?) files sufficient to use all the available deleted entries in the MFT, and then delete them. This doesn't allow for selective overwriting, as NTFS will decide which MFT entry gets used in new file creation.
I'm no programmer, but if you used consistent filenames during wiping, and if you can poll deleted entries in the MFT (that is, pull information for deleted MFT entries) you could poll each entry in the MFT and ask it its filename. If the filename is a known "wiped" name or format, skip it. If not, wipe it.
Again I'm no programmer, and this all seems a bit too complex for very little gain. My guess is that overwriting the MFT entries is probably pretty darn fast already.
In CC v2.33 the user can select to wipe the MFT. But CC won't wipe the MFT when the option ""Wipe Free Space"" (WFS) hasn't been selected. When both options are selected then CC will wipe the MFT first and execute WFS afterwards. And both processes can take a (very) long time.
It may sound weird but the time it takes for these two processes can be reduced (significantly). Let a future version (v2.34 ?) of CC perform WFS first and then wipe the MFT afterwards.