<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=iso-8859-2">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">
<div class="moz-cite-prefix">Hi Gerd and Andrzej,<br>
<br>
I do not see any reason why GARMIN should only require UNICODE
maps to be signed, while LATIN1 maps can remain unsigned.<br>
<br>
I suspect that there is a flag in the file header, maybe a new
and undocumented one, that marks the file as "check for
signature".<br>
When the Oregon checks the signature, and finds out that there
is none, it states that the check failed.<br>
<br>
Maybe mkgmap accidentally marks the file as "to be checked for
signature" when it writes out a unicode map.<br>
<br>
Does this soud plausible to you ?<br>
<br>
I uploaded a sample map that produces the error, it just
contains administrative border lines as an overlay layer. I'm
not sure whether it contains an index or not .<br>
<a class="moz-txt-link-freetext" href="http://files.mkgmap.org.uk/download/356/dach_boundary_gmapsupp_error.img">http://files.mkgmap.org.uk/download/356/dach_boundary_gmapsupp_error.img</a><br>
<br>
I can do a little testing if you can provide me with test cases.<br>
<br>
Ciao,<br>
Franco<br>
<br>
<br>
Am 26.08.2017 um 06:59 schrieb Gerd Petermann:<br>
</div>
<blockquote type="cite"
cite="mid:%3CHE1PR0802MB2442E99F11BB535F473ADF0D9E980@HE1PR0802MB2442.eurprd08.prod.outlook.com%3E">
<pre wrap="">Hi Franco,
my understanding is that this is not a bug, but a limitation implemented by Garmin.
My mothers Nüvi also doesn't load unicode maps.
One reason might be that some indexes don't work with unicode and mkgmap doesn't
write the needed ones. I cannot try that now.
If the 750 loads a unicode map without an index we may have a chance by doing more reverse
engeneering of old maps.
On the other hand, I wonder how long they will the support the old img format written by mkgmap,
maybe this is the first step to drop this support.
Gerd
________________________________________
</pre>
</blockquote>
Am 26.08.2017 um 11:51 schrieb Andrzej Popowski:<br>
</div>
<blockquote type="cite"
cite="mid:%3Ced19c093-05ff-3b09-df7d-854842ad48ab@poczta.onet.pl%3E">Hi,
<br>
<br>
> my understanding is that this is not a bug, but a limitation
<br>
> implemented by Garmin.
<br>
<br>
This is true. Garmin maps can be digitally signed. Many new GPS
require, that Unicode map include signature. Signature is a
protection against tampering, which is reasonable for commercial
maps, but it exclude support for 3-rd party maps.
<br>
<br>
</blockquote>
<p><br>
</p>
</body>
</html>