Interesting indeed! If the bug is related to the formatting of the card, it may be very significant... Under a Windows OS igher capacity cards (above 4GB) must be formated FAT32 or NTFS, while under that limit FAT can be used, so could that be that the cards that do not exhibit the problem are FAT while the ones that do would be FAT32 or NTFS (please note that it could be one or the other, but not necessarily both)?
Worth checking for sure. One quick test might be to try and format a problematic card with FAT (which would limit the partition to no more than 4GB) and see if this changes the behaviour... This can be done using the free version of EASEUS partition manager, by first deleting the existing partition and creating a new one using FAT.
François
|