G'day kunix, thanks for replying. It's OK with the dangerous stuff, i'm doing all the testing on a 'half-broke' SP2790 which owes me next to nothing. I know i was being cavalier about this but that's because there was no immediate response so i thought i'd 'have a go'! I think i've already blocked part of rgn49 by trying to flash a detail map gmapprom.img as RGN with region changed in hex from the RGN_Tool default 33 to 49. In answer to flagmax I don't know what i'm doing with hex to be honest, as i said i simply lucked-in with the basemap region # change, but with the primary detail map it's changed ok to 49 from the default 33 set by RGN_Tool but i suspect to the incorrect Section # because i now can't flash a secondary map gmapsupp.img to the unit, that is, it flashes apparently but then the map details aren't shown on the boot screen nor shown in the unit's menu of selectable details maps. That makes me suspect that both primary and secondary maps share rgn49 and i've blocked the section which is used by the secondary map. Here's the before and after for my self-made detail map RGN file for Rarotonga:
[Only registered and activated users can see links. ]
So nothing else has changed in the file other than the region # from 33 to 49, exactly as i did with the Pacific basemap where i successfully changed 33 to 03 and it works on the unit. But the change to 03 in the basemap rgn results in the Section showing in RGN_Tool as XXXX [unsupported section identifier] and 'unknown.bin'. But 33 and 49 have a defined Section, 3305 and 4905 respectively yet there's no other difference in hex as shown above, however the section name is different, dskimg.bin for 33 and section4905.bin for 49 [i didn't name the bin files used for the rgn making as that, it was gmapprom.bin originally]:
[Only registered and activated users can see links. ]
So my bush logic tells me that RGN_Tool has nothing to do with setting the Section and by my changing the Region in hex the same 'default' (05) is maintained for both Sections, 3305 and 4905. So i've maybe flashed the Primary map to the wrong section which has now somehow 'blocked' me loading the Secondary map. So what is the right section and how do we change it? You've mentioned makergn.exe kunix, and i mused about that for setting the correct region but i know nothing about it. I think maybe you even spawned it, but even if you didn't you'd know how it works backwards:
After making that post and getting no quick reply even though i knew who'd read the thread i set about playing with my 'home baked' basemap rgn file, and so emboldened promptly cocked-up the primary map rgn file and flashed it to section 4905 which partially crippled my 2720's rgn49.
So, i don't expect you guys to give me a lesson in hex editing but i'd like to know if anything further can be done with the primary map rgn file in hex to set the correct section # [wotever it is], or, if that's a really stupid question, after you've stopped laughing point me to some easily understandable tut on using makergn.exe and please tell me, if you know, what section i need to set for the primary and secondary maps because i'm now almost sure that they both are flashed to rgn49. While you're at it can i fix my unit's rgn49 which now won't flash a secondary map gmapsupp successfully? That's not so important i can live with that because i can always combine maps and flash as gmapprom primary map anyway.
My unit's gonna die itself eventually anyway i reckon from the intermittent screen-freeze problem. But if you can say how to erase 49 entirely or make a working flashable gmapprom.rgn file we at least can fix the OP's 2720 i think.
@technit
The General has arrived to lead the Cavalry. I'm hoping this isn't the Battle of Little Bighorn figuratively for both our 2720s ...... How's the BAT file going?



Likes: 






Reply With Quote

Bookmarks