I guess that's a typo and 'not maps works' should be 'now maps work'.
Check the format on your cards. It's possible to format 4GB cards in FAT16 under Windows (because they're actually ~3.7GB as a binary Gigabyte [GB] is about 0.93 Gibibytes [GiB] which is decimal). Windows will baulk at formatting in FAT32 only above 4GiB which is ~4.3GB. Both your units should be just as capable of using FAT32 as FAT16 SD cards however. Maybe the 4GB card was formatted with a Mac or some dodge 3rd party software. To be absolutely sure of the correct format use [Only registered and activated users can see links. ] or SDFormatter [google that one].
Logically there is no reason why either your 360 or 760 with latest fw should have any problem using even a 32GB FAT32 card provided the image is at least 1 byte below 2GiB [i.e. max. 2,147,483,647 bytes] in a Garmin root folder named gmapsupp.img [with latest fw 7xx can use a second image named gmapsup1.img in the card's Garmin folder too, but not 3xx/6xx]. So no matter what the problem is with the image being corrupted, on either FAT16 or FAT32 formatted cards,the 360 is totally unable to read an image over the FAT16 limit of 2GiB or larger in size [even 2,147,483,648 bytes will choke them in theory]. The full NA 2015.30 you're trying to use is 2,368,667,648 bytes, i.e. ~2.37GB or ~2.21GiB so over the FAT16 limit.
Bookmarks