OK well I did offer to go away...
Yes that makes sense. Storing the results of a computationally expensive result in NV will speed up boot times. I'd have expected it to check to see if the files had changed (if they exist, dates, sizes even hashes) but apparently not.
OK well here's a few things I'm curious about. If any of this is documented anywhere just point me in the right direction and I'll go off and study it.
The .unl files seem like something relatively simple. Is their precise format documented anywhere? I was thinking of throwing together a quick parse/generation tool that wont trigger the stupid anti-virus warnings.
The .gma files? What's known about those? They've got some ASCII stuff in what looks like a header and then nothing obvious. Might be binary data or some kind of cryptographic information to check authenticity.
What do the .sid files do?
The one that I'm still puzzling over is how GN got the Full EU map. Creating data on an SD card (virtual or real) with just GarminDevice.xml is enough to keep GE happy and download maps details (presumably this is so it can recover if someone wipes the visible flash) along with .unl and .gma for the device but I've never been offered Full EU as an option when I change region.
Bookmarks