Thread: Convert garmin .img pseudo-NT to non-NT? I know it's possible, but how?(SOLVED!!!)

Originally Posted by kunix

I remember that. But don't you think it's true only because your map is too small and you don't test all the available data formats? It would be nice to compare this way something like CNE, huh ?

The example i uploaded here in the thread is just that, an example. I compared and analyzed bigger and complex maps (non-nt and pseudo-nt) and came to some conclusions, this conclusions came from this complex maps and not from the "example" map, the example map is the one i selected to upload here to share, i thought this was obvious.
Obviously this conclusions could be wrong, if you found one counter-example please provide it here so we can analyse it.

Originally Posted by kunix

I'm afraid it's not true. I've seen a map with GMP subfiles having some data (not copyright) beyond the standard header size for almost all headers (except 2, don't remember which ones), but before the next header. This map was an NT one, actually.

Definitely i'm talking about non-nt and pseudo-nt maps, which are the ones treated in this thread (NT maps are different!!!).
And YES the first two bytes in the header give you the size of the header. I'm not the only one saying this, see [Only registered and activated users can see links. ] and seacrh for "Header Length" string.
Also, there is not a "standard header size", you get the size from the first two bytes, it could change between different maps.

Regarding this i downloaded the Malsingmaps which are NT.(in this case this is the only one i analysed, no diversity here besides the several individual maps included)
What i found is that TRE, LBL and NET headers have a length as it is given in the first two bytes of each header, as in the non-NT/pseudo-nt maps.
On the contrary RGN and NOD headers don't. Further analysis make me to believe that the extra data for example in the RGN header, is in fact not part of the RGN header and is another header of x4a length (74 bytes) (info given in the first two bytes of this extra data). This extra header point to some "dictionary" data.
If you download Malsingmaps you will see what i mean.
It is difficult to explain here in a short comment, and it is useless to do so as i don't have any other relevant info.
The extra data in the NOD header doesn't seem to be another header.
From what i saw to convert from NT maps to non-NT maps it would take definitely more work and i think ¡'m not capable of doing this.

Originally Posted by kunix

See, for example, gimglib.c line 153, it parses GMP headers below.
Also function create_patch at gimgunlock.c line 95 should be able to handle NT map data.

If you explain how can i use it to convert from NT to non-nt, or at least pseudo-nt to non-nt it would be great, i just don't see how you can accomplish this with this utilities.