Quote Originally Posted by osiris4isis View Post
Yep, I was able to parse the .hex file and pulled 13 voice files which I've extracted the .wav files.
Umm, my SP2610 has 14 voices: Celtina, Dansk, Deutsch, Espanol, Francais, Italino, Maygar, Nederlands, Norsk, Poliski, Portugues, Soumi, Svenska and of course, English [which is the only one out of alphabetical order. It's at the top of the list in 2610's Menu>Option>Language choices].

Which one isn't updated in the Audio Pack? I'm guessing EN.

*.wav use in there makes sense, rather than the use of *.vpm files in a visible Voice folder for a modern unit. There the file system's in rgn48 [hex 30] and which in many modern units can be dumped and like an image file, the bin file can extracted in programs such as PowerISO to yield a copy of the file system [you'd already know that though i'm sure].

I just need some more AUDPKG files to test my proggy. You think the Nuvi have same RGN section (0x11) that contained AUDPKG?
Here's one for SPc3xx which is also a 'region' type unit:
Code:
Please Login or Register to see the links
I have an SPc320 so can maybe help with testing there if you wish.

I don't have old units other than SP 2610, 2720 and c320, but you can easily find links for other 'old-type' audio packs from the helpful GMAPTool site, e.g.:
Code:
Please Login or Register to see the links
No rgn11 in the nuvi type units. Or to be more correct, if they do have it it's not populated and will extract empty. You're no doubt aware that modern nuvi-type units have 255 possible regions ['rgn' sections] but many will either return an error or an empty file. This may occur not only because the region is absent or empty, but because it's protected in firmware against being copied, erased or written to. The fact that there are still references to AUDPKG and AUDIMG in modern fw may not be significant. It could be that they're simply left-over placeholders from early firmwares i suppose. Garmin maybe developed the older 'region' unit firmwares further for use in the modern 'file system' units and it's just still there, leftover and unused. But that's very much an uneducated guess, maybe it does serve some very real purpose in nuvi-type units but i simply dunno and have no way to confirm or disprove that. I bet you can though if you want to.

What tool did you use to extract that section?
[Only registered and activated users can see links. ]. I've tried to get the old hands to show interest in these 'old-school' units as you'll see when you read that thread. The tool is very old and the thread originally was for extracting data from map image files in OF [Old Format, i.e. non-NT] maps last used by Garmin for CNs back in ~2009. Posts 31 onwards are regarding extracting regions from these old units. As you'll see from the last several posts, i was pretty-much running solo there.

Kunix made his own dumper to extract regions from GW navi units, i think so he could develop and add-back a modified language pack for US units to use EU languages [there's quite a few US 06-08 GW bikes been imported into EU and elsewhere, but they only had EN voice in region 11]. It's possible his dumper is 'generic' or could be made so to extract all populated regions from any unit. I know he's able to modify 'boot.bin' to even dump the protected regions on modern units for instance. Perhaps he'll jump in here and explain further.

BTW, what does RGN stands for? A .rgn file is not the same as RGN section inside an IMG file, right?
AFAIK RGN/rgn is just an abbreviation for 'region'. The context dictates the exact meaning however. An *.rgn file for firmware flashing is certainly not the same as a physical 'Region' therefore, obviously. However for example, a rgn file's components such as fw_all.bin can be matched to a copy of 'rgn14' [hex OE] extracted from the unit running the same fw version when the empty bytes, the trailing FFs, are removed.

I'm not a coder as you know, my programming experience can be regarded as nil. My interest in GW navi units is mostly because originally they could only read OF maps, but with the introduction of US V4.50 fw were able to read NT maps. These units are loosely based on StreetPilot 21x0 hardware so my hope is that somehow that fw 'trigger' can be applied to SP fw to similarly enable them because presently they're still stuck with OF maps. They're also waterproof units and are still popular with bikers and importantly they're fully portable, unlike GW navis which can't be easily shifted from bike to bike.

I'm happy to help you with testing and i'll spin this off into it's own thread if we get too OT here.