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@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. ..Steve