[mkgmap-dev] Error on MapSource with r1919

Wed May 4 19:59:09 BST 2011

El 04/05/11 16:57, Carlos Dávila escribió:
> El 04/05/11 15:18, Steve Ratcliffe escribió:
>> Hi
>>
>>>>> Just another thought ... could it be that C/H/S information should be
>>>>> calculated dynamically based on the actual size of a .img-file?
>>>>> Maybe this could save memory on a GPS when the tiles are loaded ...
>>>>> this
>>>>> is speculation since I don't know exactly how this is implemented.
>>>> Yes it should be. I just hoped that it would not be required, as it
>>>> always worked when the max size was smaller. ;)
>>>>
>>>> I'll see what it would take to get the size into the header.
>>> After merging changes from trunk to locator branch I have the same
>>> problem with the mkgmap-locator. Is there any other information I can
>>> supply or any test to run to help debugging this issue?
>>> _______________________________________________
>>> mkgmap-dev mailing list
>>> mkgmap-dev at lists.mkgmap.org.uk
>>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>> OK the attached patch should now take into account the exact size of
>> the file when setting the 'partition size' in the header.
>>
>> There is a minimum size of 2048 512 byte sectors, anything larger than
>> that is calculated just a little larger, so any mistake will cause a
>> problem. Works for me so far.
> Using your patch I get the messages below and the map can't still be
> loaded in MapSource
> file size 0
> file size 0
> max block 42204
> endSector=42204, from 42204
> try 65472, for mb=42204
> max block 50217
> endSector=50217, from 50217
> try 65472, for mb=50217
> file size 0
> max block 12004
> endSector=12004, from 12004
> try 65472, for mb=12004
> file size 0
> max block 21899
> endSector=21899, from 21899
> try 65472, for mb=21899
> file size 0
> max block 21345
> endSector=21345, from 21345
> try 65472, for mb=21345
> file size 0
> max block 38482
> endSector=38482, from 38482
> try 65472, for mb=38482
> file size 0
> max block 15235
> endSector=15235, from 15235
> try 65472, for mb=15235
> file size 0
> max block 20773
> endSector=20773, from 20773
> try 65472, for mb=20773
> file size 0
> max block 22445
> endSector=22445, from 22445
> try 65472, for mb=22445
> file size 0
> max block 17141
> endSector=17141, from 17141
> try 65472, for mb=17141
> file size 0
> max block 20432
> endSector=20432, from 20432
> try 65472, for mb=20432
> file size 0
> max block 28355
> endSector=28355, from 28355
> try 65472, for mb=28355
> file size 0
> file size 0
> max block 11
> endSector=2047, from 11
> try 65472, for mb=2047
> file size 0
> max block 38682
> endSector=309463, from 38682
> try 65472, for mb=309463
> try 130944, for mb=309463
> try 261888, for mb=309463
> try 523776, for mb=309463
> max block 4871
> endSector=38975, from 4871
> try 65472, for mb=38975
I realized MapSource error is different with the patched version, but 
don't know if this info is useful
App: MapSource
OS: Windows XP Service Pack 2 (actually debian+wine)
Processor: x86, Processor Level: 16, Processors:2, Model: 6 Stepping: 2, 
RAM: 2097151
DSK_PRIVPARTITION.CPP-314-6.13.7.0
Language ID: 1034
Part Number: 006-A0041-00
Build Type: Release
Extra: Opening map at (lat,lon): 40.0342, -2.41699
Resolution: 16

Stack Trace:
2072270818
9448702
8340466