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

Yes i read that, and have some thoughts about it in that moment.
But changing the offsets of the subfiles already is working perfect!!.
Keep in mind that i already know what it must/should be as i have maps compiled by myself in where i have both, pseudo-NT and non-NT.
I knew before hand that there where differences between pseudo-NT and non-NT map compilation of the same data. Then i realize that this differences where the offsets, this is confirmed as subtracting the same value, change the offsets from pseudo-nt to the ones in the non-NT version, in a way that the pseudo-nt header now became exactly the same as the non-nt header.
None of the headers i revised had an offset that pointed out of the corresponding data of that header subfile.
I think that the info in imgformat-1.0.pdf is not complete/ok , take a look at [Only registered and activated users can see links. ].

Either way, in case some of the offsets do really point to a position in another subfile, this could be detected, just taking into account that if some offset in a header is greater than the end of the corresponding subfile, the subtract value will change including now the header size of the others subfiles that are between or something else.
The regular non-nt img is structured as:
some things
TRE subfile
some zeros
RGN subfile
some zeros
LBL subfile
some zeros
NET subfile
some zeros
NOD subfile

In case this occur, it would need to be revised. But i bet that this won't in case of pseudo-nt.
But just to know that the pseudo-nt has exactly the same data that the non-NT counterpart and that the only thing to change is apparently the offsets, makes it easier to analyse in the future cases as the one you are referring.