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

**Ed_slv** · 30th September 2013, 03:10 PM

Sorry. I did not check it. I will continue search
No way. My oldest file is v086m dated 2005

**Giomen** · 6th October 2013, 03:05 AM

Many people ******* Garmin protection before public unlocker. But not you

I am about that...

**rebelneo** · 6th October 2013, 05:08 PM

Originally Posted by Giomen

But not you

I am about that...

And I did not claim... ))) I'm just saying that Constantine did in 2003...

**Giomen** · 7th October 2013, 12:18 AM

Anybody have Garmin source in 2003, but obviously it was interesting only for KG...

**testlelelala** · 7th March 2014, 07:49 AM

Hi r0cker!

This is good!!!

I get some differences in offsets with "my manual" conversion in comparison to yours. Some i believe are because you delete some copyright info from the headers (i need to look this further).
But also for example in LBL header i think there is a problem with bthe offsets in the extraction.
Take a look at example2.rar file attached to [Only registered and activated users can see links. ]
In LBL at xb0 (4bytes) it indicates the beginning of the LBL "body", so as the LBL header is 236 bytes long in xb0 should have xec which is the offset inmediatly after the header ends.

With your conversion i get in xb0 the offset xd1 which point somewhere inside the header, and not at the beginning of he body

ps: Just an idea: Instead of naming garmin.XXX to the gmp's sub structures, it would be useful if you can call them as the original gmp file.
ie: examplemap.gmp >> examplemap.LBL; examplemap.RGN; etc...

thanks

**r0cker** · 7th March 2014, 09:22 PM

I corrected the small glitch in lbl offset calculation and renamed the filenames to be the same as the gmp

[Only registered and activated users can see links. ]

Regards, R0cker

**testlelelala** · 8th March 2014, 07:51 AM

Thanks for accepting the naming idea!

More feedback:

*LBL; NET; NOD are OK!

*In RGN you forget to adjust the offset at x55
in the example it says x52f it should go x208, as you correctly did in the other offsets in RGN, the rest is OK.

*TRE is OK also, there are differences because you change the copyright info for a custom one, but all offsets point to where they should, so NO problem.
Another idea: perhaps you could put there your name and version, instead of garbage, like: r0cker V2.00 or something...or the option to keep the original copyright info (this probably would need more programming as copyright info change between map compilers, like mapear or carteblanche)

thanks

**r0cker** · 15th March 2014, 07:31 PM

Hi, i've fixed the rgn. could you check it again?

Germain

[Only registered and activated users can see links. ]

**testlelelala** · 16th March 2014, 10:07 AM

Checked.

Excellent!!! working perfect.

Tested with a real pseudo-nt map from mapear.
1-Using your extractor version 3,
2-then joining the files with GMapTool as a non-nt img (short header in options),
3-then opening it with GPSMapEdit and saving as a *.mp format without any problem or error.
all working perfect.
same result as the "manual extraction", EXACTLY the same output as a *.mp map in both cases.

**testlelelala** · 19th March 2014, 05:12 AM

Hi Neil
Could you test this map in your garmin NT-unaware device as you did before?
[Only registered and activated users can see links. ]

The map is converted to non-NT from a pseudo-NT original.([Only registered and activated users can see links. ] you can download also the pseudo-nt original to confirm, just in case, that indeed it is not working)
BUT it is compiled with GMapTool enabling 'Short header' option.

please check if it works now.

thanks