Andrewp_one @ 03.05.17, 10:56
Files at 8-10 GB, several films say ... So, if they reproduce without errors (which is unlikely),
What kind of "grandfathers" ????
Once so - then:
1 - We type content from different files, approximately the size of the flash drive (for a start - at least 20GB is more "declared" 7.4?)
2 - This content is placed in the folder (any - to your taste) on the BB. Or - in an existing folder "Collect".
3 - MD5Summer.exe prog (thug) or similar to it - create a file with MD5 with the sums of "Collection"
4 - Copy the content from the folder - to the desired / verified SD card.
5 - After the copying is completed - we are experiencing the above method, we check the MD5 of the content amounts.
6 - if the check will pass "with a bang" (which is unlikely) -
7 - Remove (Safe) Card / Cardrider
8 - Re-insert a card / card reader
9 - We again check the MD5 of the amount of recorded content.
10 - If again "all coincided" - repeat items 1 - 9 under the claimed card size.
Why so, and not how invented
AndrewP_one, ? - You will listen to hours, but the amount of MD5 is generated / is not verified in real time, but with the speed of the process ... Usually - takes seconds - minutes (and not hours) ...
PS If you do not understand how the H2TestW utility works - I will explain on my fingers:
- about doing the same thing I described above -
1 - According to its predetermined algorithm, data blocks records, the composition of the block depends on its sequence number, etc. - When reading the Block, the program is easily calculated, it should be its content. Esno block names are stored in the file directory on the card, the controller of them records without any problems (which you can not say about the contents).
2 - After recording, the program reads the block data (at the addresses from the catalog), compares them with the algorithm calculated by its same. Comparison is successful - the next block is read.
What is the chip? Yes, everything is very simple! Fake does not have real memory cells, more than 7,4GB (in this and most cases) - i.e. A block is read, consisting purely of zeros ... so understandable? In this case, the comparison is invariably fail.
How does this program differ from the stunning most others? It records real data, and reads other real data, and compares them among themselves. Many other programs - simply write something, and are waiting for an answer from the controller - "recorded, or not?" - The controller (patched) Esno affirmatively nods his head. Then the type of type reads data, and asks the controller - "the data is read?" - That again nods his head ... and in the meantime - it is written (let's say) ffff, and is read - 0000. Catch the difference?
Post has been editedrusigor - 04.05.17, 21:19