Install direct to Zumo: Chose a single map that would not fill remaining storage on the Zumo and tried. Chose a smaller map set slightly over 2MB and got the same error. Reformatted the card, installed into the Zumo and tried again. Smaller / Different SD card: Tried a 16Gb card that I use for European maps. Keep us in the loop so other zumo 350 folks may benefit from your findings in the future. This would be the last thing I suggest trying giving the effort required. The test would be to redownload/reinstall the "new improved" 2019.10 to the zumo/Mac and then repeat the MapInstall to a SD card. I wonder if your download of the 2019.10 to the zumo and your Mac was done with the original 2019.10 version and if part of that map update's "recall" problem could be affecting your zumo update. The current map, 2019.10 was revised for some reason known only to Garmin. What if you tried a quite small region of 1-1.5GB in size.Īh, yet one more thought. If the 2GB limit is the issue, your other map region attempts must be under 2GB. The only final thought I have is that you say you tried other map regions of about 2GB. I like your thought that the old SD card may have finally died and that you'll look for another or a smaller card to repeat the test. Obviously, the error message from your first post is nonsense and that makes me think that some Garmin-unexpected error occurred resulting correctly in an error message but the text of the error has no connection to what the actual error was. I found one but the install is beyond what I'm comfortable with, both in source and skills required. Tried looking for the Mac equivalent of your H2testw program. I am wondering if my friend's card has bit the dust. Suggestion 4) Card was sourced from Best Buy a few years ago and has been working. Suggestion 3) I'll see if I have a smaller SD card and give it a whirl. I uses the MS-DOS(FAT) choice on all my SD cards that I use in my own devices (Nuvi 360, 765, 775, 2689) Suggestion 2) Should be good on the formatting. Same problem and error message though it does identify the file as being only 2MB. As per your suggestion, I chose a few maps about 2MB in total. Suggestion 1) File Size: It is not the file size. Good luck and keep us in the loop on your progress. If in doubt, the H2testw program can verify your SD card. If you have a blank 4, 8 or 16GB SD card, what happens if you try using it to install your mapset of everything other than Canada and the Border States?Ĥ) Where'd you buy the 32GB SD card? If from Asia through eBay or something similar, know that there are a lot of counterfeit SD cards sold at bargain prices that are not 32GB cards. (Remember that I'm not a Mac user so question all that I write.)ģ) Your choice of a 32GB SD card is at the max of what a zumo 350 can handle. What would happen if instead of choosing everything other than Canada and Border states, you instead chose a smaller subset (maybe drop Mexico and the Caribbean)? If MapInstall selected a mapset under 2GB in filesize and it did install to the SD card, then maybe the zumo can't handle 2+GB files.Ģ) When I saw your FAT format statement, I was going to suggest you try FAT32 instead, but I gather that when Macs offer SD card formats, their FAT is actually a FAT32 and if that's right, you should be OK. The 3xx series: ? If the 350 can't handle files over 2GB in size, that may explain why past map updates worked for you since the SD card map file may have been under 2GB up to this map update. Note that the FAQ doesn't say that the 3xx can't read files over 2GB in size (I love double negatives apparently), but it does say that if a zumo 4xx or 5xx has the latest software updates, it can handle files of 2+GB. It is questionable whether the zumo 3xx series can handle files over 2GB in size. While we're waiting for someone with an answer, here are a few thoughts from a non-Mac non-zumo user.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |