hoc
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
hoc [2021/01/06 23:24] – Walter Schulz | hoc [2021/05/16 20:06] – [Fight Flash Fraud] Walter Schulz | ||
---|---|---|---|
Line 3: | Line 3: | ||
==== Benchmark your cards ==== | ==== Benchmark your cards ==== | ||
=== Benchmark with your PC === | === Benchmark with your PC === | ||
+ | |||
+ | {{: | ||
+ | {{: | ||
+ | |||
+ | |||
+ | |||
+ | {{: | ||
+ | |||
+ | |||
=== Benchmark inside camera === | === Benchmark inside camera === | ||
+ | |||
+ | {{: | ||
==== Fight Flash Fraud ==== | ==== Fight Flash Fraud ==== | ||
+ | |||
+ | The problem: | ||
+ | Product forgery sadly is wide spread among flash memory devices. And purchasing from " | ||
+ | Memory devices can easily be manipulated and your camera and your PC are not designed to detect that. Both devices expect all connected memory devices to be trustworthy and your camera and PC will act like all memory device information is good as gold. If a scammer overwrites a flash card's internal capacity information to sell a 16 GByte card as a 128 GB (for example) your PC will act like the card capacity is 128 GB. \\ | ||
+ | And this will happen: Everything is just perfect until the card's real capacity (in this case: 16 GB) is reached. But every byte beyond that limit will be written **from the very beginning** of the card. Overwriting essential information and most likely overwriting all the pics/ | ||
+ | |||
+ | What to do? It is strongly recommended to verify card integrity with tools like h2testw or F3/F3 QT right after purchase. Those tools are freeware and easy to use. | ||
+ | |||
=== Windows: h2testw === | === Windows: h2testw === | ||
+ | |||
+ | German IT magazine c't published h2testw (freeware) to give Windows users a chance to detect flash fraud. This is the [[https:// | ||
+ | After downloading zipped file you can expand contents anywhere. H2testw.exe runs without installation and does not require admin priviledges. Readme.txt in english is included. | ||
+ | |||
+ | Run H2testw.exe\\ | ||
+ | {{: | ||
+ | Select English to change user interface language.\\ | ||
+ | Select target device = your memory card.\\ | ||
+ | Data volume: all available space. (Number in brackets may be different) | ||
+ | |||
+ | Click button "Write + Verify" | ||
+ | {{: | ||
+ | This warning is just for information. This very small area not tested will most likely not affect fraud detection. Scammers usually don't manipulate device info by a fraction that small. ;-) \\ | ||
+ | |||
+ | After confirming " | ||
+ | {{: | ||
+ | Test run can take quite a while. H2testw is not optimized for pure write/read speed. In most cases data transfer rates will be around 30 percent slower than maximum sequential write limit. | ||
+ | |||
+ | After write cylce h2testw will automatically proceed with read/verify cycle.\\ | ||
+ | {{: | ||
+ | |||
+ | Test result for a card not manipulated by a scammer:\\ | ||
+ | {{: | ||
+ | As stated in test results you will find card filled with *.h2w files. You have to delete them manually. | ||
+ | |||
+ | **If h2testw testrun ends with an error message your card may be manipulated!** Verify test results by a second run and - in case second run gives the same results - contact your seller for refund/ | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
=== macOS/OS X/Linux: F3/F3 QT === | === macOS/OS X/Linux: F3/F3 QT === | ||
+ | |||
+ | {{: | ||
+ | |||
+ | \\ | ||
+ | |||
+ | |||
+ | {{: | ||
+ | |||
+ | |||
+ | \\ | ||
+ | {{: | ||
+ | |||
+ | \\ | ||
+ | {{: | ||
+ | |||
+ | \\ | ||
+ | {{: | ||
+ | |||
+ | \\ | ||
+ | |||
+ | |||
+ | {{: | ||
+ | |||
+ | ===== Data recovery ===== | ||
+ | ===== ExFAT ===== | ||
+ | ==== Big Sur, Canon and ExFAT ==== | ||
+ | ==== Camera compatibility ==== | ||
+ | ==== In-cam format and card size ==== | ||
+ | |||
+ | ===== FAT32 ===== | ||
+ | File system used as default by small and medium sized data storage cards. Supported by all cameras able to run ML. | ||
+ | Supports file size up to 4 GB. | ||
===== Incompatible cards ===== | ===== Incompatible cards ===== | ||
Do not try to use these cards/ | Do not try to use these cards/ | ||
- | ==== First EyeFi generation ==== | + | ==== First Eye-Fi |
- | They won't work at all. ML's process of checking for a bootable card is incompatible with EyeFi-firmware (yes, your EyeFi-card has its own firmware). If you want to use first-gen EyeFi with a camera with ML bootflag set: Nope, it wont work at all. You have to uninstall (=remove cam's bootflag) before using such cards. \\ | + | They won't work at all. ML's process of checking for a bootable card is incompatible with old EyeFi-firmware (yes, your Eye-Fi card has its own firmware). If you want to use first gen Eye-Fi with a camera with ML bootflag set: Nope, it wont work at all. You have to uninstall |
ML devs aren't able to fix this issue.\\ | ML devs aren't able to fix this issue.\\ | ||
- | All other WiFi cards will work just fine! | + | All other tested |
+ | |||
+ | ==== Sony 94MB/s 32 GB SDHC ==== | ||
+ | Not exactly incompatible but with strange performance issues in some (not all!) Canon cameras. See https:// | ||
+ | Recommended not to use them because of known inconsistencies. (Confirmed by user andy kh on 70D).\\ | ||
+ | Because they are not longer in production you will likely never meet one. All other Sony cards (including successor 95 MB/s variety) are working without hick-ups. | ||
==== SD-to-CF adapters ==== | ==== SD-to-CF adapters ==== | ||
Line 45: | Line 133: | ||
About overclocking: | About overclocking: | ||
+ | |||
+ | ===== Storage size: Mega and Giga confusion ===== | ||
+ | > Incomplete | ||
+ | Ever wondered why your 3 TB disk appears as 2.72 TB in Windows? And your 128 GB card as 119 GB? \\ | ||
+ | Both numbers are right, you haven' | ||
+ | |||
+ | Storage manufactures count this way: | ||
+ | 1000 Bytes = 1 kByte\\ | ||
+ | 1000 kBytes = 1 MByte (= 1000 x 1000 Bytes)\\ | ||
+ | 1000 MBytes = 1 GByte (= 1000 x 1000 x 1000 Bytes) | ||
+ | |||
+ | Computer programmers count this way:\\ | ||
+ | 1024 Bytes = 1 kByte\\ | ||
+ | 1024 kByte = 1 MByte = 1024 x 1024 Bytes = 1,048,576 Bytes\\ | ||
+ | 1024 MByte = 1 GBytes = 1024 x 1024 x 1024 Bytes = 1, | ||
+ | For computer programmers it is absolutely logical to count in numbers based on 2. And 2^10 is 1024. | ||
+ | |||
+ | (Fun fact: For a long, long time storage manufacturers and programmers used the same binary counting. Confusion began when storage manufactures changed to decimals. | ||
+ | |||
+ | ===== Card performance and camera limits ===== | ||
+ | ==== CF-cards ==== | ||
+ | ==== SD-cards ==== | ||
+ | |||
+ |
hoc.txt · Last modified: 2021/05/16 22:09 by Walter Schulz