How long should ~4gb Basecamp take to build and transfer directly to microSD?

Former Member over 13 years ago

I used Garmin's US Topo 100k, almost the whole country in an openstreetmap routable, and most of the new york layers on GPSfiledepot. I left it on overnight, transferring directly to microSD through a 5-in-1 card reader through a USB port.

After 16-18 hours, it had finished building the map index and the map set, and failed 4% into a transfer to the microSD.

Is this normal timing or do others build and transfer faster? My computer isn't a screamer but it isn't all too slow either (quad core unspecified MHz, 4gb ram, windows 7 64 bit).

Any tips to increase speed or likelihood of finishing? I just restarted the bugger and am going to wait another day and see what happens, but some anecdotes / suggestions would be lovely in the interim. Thanks in advance, everybody.

edit: Subquestion: Oh. Since it finished building last time, is there any way to skip that step the second time around? Perhaps a temporary gmapsupp file in temp cache or some such? I don't see built in functionality, I tried just hitting back and then next again at the map install failed screen, but this began rebuilding everything and will easily take 16+ hours again.

0 JaVaWa over 13 years ago

I guess I'm mislead by the remark on page 8 of the document of John Mechalas about the img file format (I assume you know about that document) where he states that there is a hard limit of 4 GB because of 32 bit integer file offsets, but after checking of some other info I saw that there are only relative offset pointers in the subfiles, not in the main header or FAT blocks.
So you're right... however, as long as the devices use FAT32 for the file system the possibility to create img files larger dan 4 GB is not going to be useful.
The way they do it now with multiple img files in the current models solves this problem, but that's not going to help users of older devices...