See the Forensicator's blog, he explains the whole process in detail (relative modification timestamp differences) as well as explaining about the FAT filesystem anomalies discovered and other factors observed that this article and most articles critical of his research (or Lawrence's referencing of the research, to be precise) tend to omit in order to make a strawman out of transfer rate attainability.
I've responded to Wemple (Washington Post), Uchill (The Hill), Biddle & Tait but the same observations are relevant to this article by Karl Bode as he uses the same tactics to undermine what is referenced by Lawrence in his article.
http://g-2.space/distortions
Techdirt has not posted any stories submitted by adamcarter.
Re: Re: Re: Also worth noting - compression and resumption
See the Forensicator's blog, he explains the whole process in detail (relative modification timestamp differences) as well as explaining about the FAT filesystem anomalies discovered and other factors observed that this article and most articles critical of his research (or Lawrence's referencing of the research, to be precise) tend to omit in order to make a strawman out of transfer rate attainability.
http://theforensicator.wordpress.com/
Re: Re: try again
What mistake?
There was no conversion mistake - as is being suggested.
Re: The answer is obvious
Which causes CPU usage and creates a disk footprint that makes you far easier to detect.
(We're talking a total batch of files at around 19Gb, of which the NGP-VAN archive's contents appear to be a subset of)
Rebuttal
I've responded to Wemple (Washington Post), Uchill (The Hill), Biddle & Tait but the same observations are relevant to this article by Karl Bode as he uses the same tactics to undermine what is referenced by Lawrence in his article.
http://g-2.space/distortions