Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 4 of 33 FirstFirst ... 2345614 ... LastLast
Results 31 to 40 of 323
  1. #31
    Master
    Join Date
    Dec 2009
    Location
    NZ
    Posts
    103
    Rep Power
    81

    Default

    Quote Originally Posted by karl-01 View Post
    Current update (051012) cannot be modified accordingly...
    It will be difficult to keep up with the frequent updates. You may have to experiment with your favourite HEX editor.
    e.g. I just downloaded the latest GlobalMapper 64bit v14.0 (b100512) and the offset is 00416830
    The version will probably change by this time tomorrow.

    Tested still working with B0 01 C3 90

  2.    Advertissements


  3. #32
    Member + Global Mapper up to the latest
    Join Date
    Oct 2012
    Location
    berlin
    Age
    44
    Posts
    57
    Rep Power
    12

    Default

    This seems to work for the 64bit version.
    The corresponding bit-sequence cannot be found for the 32bit version.

    I use notepadd++ with a HEX-plugin; seems to work okay.

    Cheers

  4. #33
    Navigation software expert Global Mapper up to the latest
    Global Mapper up to the latest
    Cnfhbr's Avatar
    Join Date
    Jan 2010
    Location
    CIS
    Posts
    1,033
    Rep Power
    507

    Default

    Quote Originally Posted by karl-01 View Post
    The corresponding bit-sequence cannot be found for the 32bit version.
    New build (b100512) was modified twice in this period. Hold your horses!
    Last edited by Cnfhbr; 7th October 2012 at 12:19 PM.

  5. #34
    Navigation software expert Global Mapper up to the latest
    Global Mapper up to the latest
    Cnfhbr's Avatar
    Join Date
    Jan 2010
    Location
    CIS
    Posts
    1,033
    Rep Power
    507

    Default

    It looks like the rework of the current build has calmed down ([Only registered and activated users can see links. ])

    Additions for the current build v14.0.2 (b100512):
    Spoiler: CLICK
    [Only registered and activated users can see links. ]
    [Only registered and activated users can see links. ]

  6. #35
    Member
    Join Date
    Jun 2010
    Location
    usa
    Posts
    19
    Rep Power
    0

    Default

    To Cnfhbr:
    Why was B0(old Data) at offset 00414101 changed to 01? I patched mine with B0(00414001) and it work for me but I don't know what B0 might do to program I just used old data. Could you help me out with this? And what program did you use to Decompiler the EXE.

  7. #36
    Navigation software expert Global Mapper up to the latest
    Global Mapper up to the latest
    Cnfhbr's Avatar
    Join Date
    Jan 2010
    Location
    CIS
    Posts
    1,033
    Rep Power
    507

    Default

    Quote Originally Posted by Basskiller View Post
    Why was B0(old Data) at offset 00414101 changed to 01?
    The correct offset is 00414000 for the current build ...

  8. #37
    Member + Global Mapper up to the latest
    Join Date
    Oct 2012
    Location
    berlin
    Age
    44
    Posts
    57
    Rep Power
    12

    Default

    Hi,

    do I understand correct:
    You speak about the offset of the 64bit-version?

    Any glue about the 32bit-version?
    I cannot find related bit sequence in none of the versions after b092712.

    Ciao

  9. #38
    Navigation software expert Global Mapper up to the latest
    Global Mapper up to the latest
    Cnfhbr's Avatar
    Join Date
    Jan 2010
    Location
    CIS
    Posts
    1,033
    Rep Power
    507

    Default

    Global Mapper v14.0.2 (b100512) [64-bit]. For patch :

    Code:
    Please Login or Register to see the links

    Global Mapper v14.0.2 (b100512) [32-bit]. For patch :

    Code:
    Please Login or Register to see the links

  10. #39
    Member
    Join Date
    Jun 2010
    Location
    usa
    Posts
    19
    Rep Power
    0

    Default

    Yes for the 64bit ver
    The original Data offset 00414000 = 89542410
    My data was offset 00414000 = B0B0C390
    yours is offset 00414000 = B001C390

    I have not looked at 32 bit ver yet!

    So what does the 01 or the B0 do to the program?

  11. #40
    Member + Global Mapper up to the latest
    Join Date
    Oct 2012
    Location
    berlin
    Age
    44
    Posts
    57
    Rep Power
    12

    Default

    I have tried the modifications given on 11-10-2012 for v14.0.2 (b100512) [32-bit] and it works perfectly!!!!

    The 32-bit update-versions from b101212 and b101312 are slightly different; it is just one HEX-word:

    Global Mapper v14.0.2 (b1012/1312) [32-bit]. For patch :
    Code for b101312:
    RAW Offset | Old Byte | New Byte
    -----------------+----------+----------
    002f6283 74 00
    002f6284 35 00
    002f6288 75 00
    002f6289 30 00
    002f62a2 8B 00
    002f62a3 CB 00
    002f62a4 E8 00
    002f62a5 07 00
    002f62a6 CF 00
    002f62a7 FF 00
    002f62a8 FF 00
    002f62a9 80 00
    002f62aa 7B 00
    002f62ab 29 00
    002f62ad 0F 00
    002f62ae 84 00
    002f62af EE 00
    002f62a0 04 00

    The difference is at 002f62af and is EE instead of E9; the code as given above seems to work.

 

 

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •