Quote Originally Posted by jinxxxxxx View Post
As far as MS v MI i will play and see if I find any differences.
Compare the img files in HexCmp.

Now you try this . Put all of the USA on any some of Canada on a 4gb cf card. the file size should be around 2,040,000,000b according to MS or MI. Put it in your goldwing and see if it works. Do an address find,if the address find works than the mapset is fine. If not reduce it to 2.03gb Now try putting that same img on your 2gb CF. Surprise surprise it wont fit. If you use a 4gb CF card you can load a mapset that is about 200 to 300mb larger than if it is on a 2gb card.
I don't know if you fully got what I was saying about gigabyte vs. gibibyte. To briefly reiterate, a 2GB CF card has something over 2 billion bytes available, the Sandisk in the Post #11 pic has total capacity of 2,047,541,258 bytes so one of 2,040,000,000 bytes will definitely fit ok on it. Look at the img size on that CF in the pic, it's even bigger at 2,044,526,592 bytes and it works just fine. I think your reference to 2.03GB is actually GiB (binary) which is ~2,179,695,900 B so it won't fit on a 2GB CF. A file of 2.03GB (decimal) is ~2,030,000,000 bytes so it will fit. It's so confusing with MS using the original binary form for gigibyte and drive manufacturers using the decimal form. This explains the history:
Code:
Please Login or Register to see the links
It seems that the goldwings that use the CF card can actually read a 2,040,000,000 b file and read a card as larger as 32gb.
As said they can read a file not exceeding 2,147,483,647 bytes and can probably read from a CF larger than 32GB provided it's formatted in FAT32 not exFAT.

Now it would be nice if Garmin would update the FW to read larger file sizes.
That would be nice, but I'll bet they won't bother. It's only a few lines of code to add to an updated firmware, they did it for about 5 years back for US/EU nuvi 7xx and 2xx but not for any earlier devices. I think if they were going to do it for the 06-08 GW navi they'd have done it at latest in Firmware Version 4.50 when they added NT capability.