Here it is:Quote:
Originally Posted by Cnfhbr [Only registered and activated users can see links. Click Here To Register...]
[Only registered and activated users can see links. Click Here To Register...]
Not sure if it's pro.
Here it is:Quote:
Originally Posted by Cnfhbr [Only registered and activated users can see links. Click Here To Register...]
[Only registered and activated users can see links. Click Here To Register...]
Not sure if it's pro.
Thanks, but this is a FREE version, see the [Only registered and activated users can see links. Click Here To Register...]
Money isn't the point in that case, it's a matter of principle!Quote:
Originally Posted by catymag [Only registered and activated users can see links. Click Here To Register...]
First of all, the program was initially designed to "borrow" topographical data from official (locked) maps by Garmin for personal gain.
This feature is available in the current version 2.0.77.1 too (in original, not patched version) and few people know about it.
You can try this, for example, with the locked [Only registered and activated users can see links. Click Here To Register...] or [Only registered and activated users can see links. Click Here To Register...]
Thus, I believe that the patching of this program is not shameful. ;)
But each have own conception of light and dark sides :)Quote:
Originally Posted by Cnfhbr [Only registered and activated users can see links. Click Here To Register...]
Practice is show what if you need to good maps the soft must be free for use. It is very good start for developer because if it is not so they see on other soft. All the more so this program always looks as semi criminal soft! Hackers dread it nonetheless :)
Why? Why is dread? They are afraid of wolves - in the woods do not go! Many people ******* this software. Not always successfully...... There's a virtual machine :)Quote:
Originally Posted by Giomen [Only registered and activated users can see links. Click Here To Register...]
Many people ******* Garmin protection before public unlocker. But not you :) I am about that...
And I did not claim... ))) I'm just saying that Constantine did in 2003...Quote:
Originally Posted by Giomen [Only registered and activated users can see links. Click Here To Register...]
Anybody have Garmin source in 2003, but obviously it was interesting only for KG...
Hi, i've coded a small utility to easily extract TRE, RGN, LBL, NOD and NET subfiles. Garmin GMP Extract will automatically adjust the offsets. So, give it a try if you want and give me feedbacks. Latest version can be found at[Only registered and activated users can see links. Click Here To Register...]Code:http://www.searchevolution.com/gps/software/Garmin-GMP-extractor.html
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. Click Here To Register...]
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
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. Click Here To Register...]
Regards, R0cker