04-18-2016, 07:45 AM
(04-18-2016, 07:30 AM)rahlquist Wrote: After the image is written, Phoenix then will look at the storage and say, hey you have another 3GB free and the instructions in the image file say to expand partition X if there is free space, so it does.
I will only comment on this Phoenix Card behaviour and add a link to one of the many problems related to USB card readers on high speed ports: Overheating paired with data corruption. And it's as easy as always to detect that using h2testw and/or f3.
Phoenix Card in Startup mode first partitions the card and then tries to write specific blocks of data to the card (that are not necessarily inside partitions, for example the bootloader and env stuff is just a few sectors at the beginning even before the partition table itself). Phoenix Card uses a rather primitive checksum algorithm to verify some of the written data. But at least this checksumming succeeds most of the times in detecting both data corruption and counterfeit cards (since the system partition is located beyond the card's real capacity).
Anyway: the technical background is close to irrelevant if people would simply learn to use h2testw or f3 first to check both card and burning process. If Phoenix Card or WinDiskImager will fail, those two test tools will fail for sure and also show the reason.