@Neil
He have so small gupdate.gcd becouse, he drag/drop keyboard rgn in webupdater and this 64kb gcd was keyboard files ;)
Printable View
@Neil
He have so small gupdate.gcd becouse, he drag/drop keyboard rgn in webupdater and this 64kb gcd was keyboard files ;)
Of course, thanks Loly. The .rgn has been converted to a .gcd by WebUpdater and then loaded to the unit. I don't see that in fact the keyboards .rgn file is at all capable of being effectively used that way. Although the .gcd filed is loaded to .System it's then totally ignored on reboot [there's no boot.bin]. This is why Smokefree was unable to load the keyboard folder that way. This is not what WU does when it downloads from the server itself, it places D162200.zip in the Garmin folder to be utilised on next boot.
On looking further at the 64KB gcd file with RGN_Tool it is empty, however when checked with a hex editor it contains seemingly valid info. Can anyone enlighten me?
Drag it in RGNtool, save pk_text.zip inside there is keyboards folder: pk_text.zip\Keyboards - ZIP archive, unpacked size 947.088 bytes
Which is the way i do it, as i suggested [Only registered and activated users can see links. Click Here To Register...]:Quote:
Originally Posted by catymag [Only registered and activated users can see links. Click Here To Register...]
But what has me intrigued is the way WU deals with the rgn file when it's loaded the way Smokefree attempted [a method confirmed as valid by Giomen [Only registered and activated users can see links. Click Here To Register...]]:Quote:
Just to add to his learned words of wisdom, another way the get the keyboard files from the .rgn is to open it with RGN_Tool and just select save to get the file pk_text.zip which can then be extracted to obtain the folder 'Keyboards' containing all the .kbd files.
I don't believe that the file can be successfully loaded by either of the above methods, WU or Updater.exe, however i would have thought that WU would have loaded it as a zip file rather than a gcd before i tried it myself and therefore had no reason to question Giomen's statement before that. It was only because Smokefree said that the Keyboards weren't loaded by that particular method and Loly pointed out that the gcd at 64KB was the keyboards that i attempted to replicate it myself.Quote:
you must put nuvi12xx_13xx_14xxKeyboards_320.rgn to Updater or Webupdater icons and this program will do all for you.
I've dragged rgn in WU and it loaded it as D166000.zip in Garmin folder in virtual nuvi
[Only registered and activated users can see links. Click Here To Register...]
I never use neither SW nor Maps updaters in silent mode. It is main reason to be on this forum where there are answer on any question. Only one exception take place for CN on new device. But it is another reason for stay here it is interesting for me as the words plentiful moderator like Neil resolve this problem :)Quote:
Originally Posted by Neil [Only registered and activated users can see links. Click Here To Register...]
Which is exactly how it should treat the .rgn file, in the same way as if it had been directly downloaded from the server by WU itself. I've replicated Smokefree's experience using an actual [not stunt double usb] UK 1340 [the closest unit i have to an EU 1440] and i've got the same result as he did. No zip file in the Garmin folder, but a 64KB GUPDATE.GCD in the .System folder which cannot load. Got me beat why it's happening.Quote:
Originally Posted by catymag [Only registered and activated users can see links. Click Here To Register...]
Spoiler: pic
The gcd file shows as empty in RGN_Tool, unlike the rgn which has the zip file in the first section. In a hex editor though, the gcd does appear to contain relevant kbd info.
However when i updated with WU normally [on line], the D162200.zip is placed correctly in the Garmin folder.
HaHa! You flatter me Sir! ..... or do you? I'm never quite sure ...... :doubt: [I've given the post a 'like' just in case you were being nice to me]. Now how about an actual solution to this mystery, you got any ideas G?Quote:
Originally Posted by Giomen [Only registered and activated users can see links. Click Here To Register...]
@Neil I downloaded it from starting post.
Code:http://download.garmin.com/software/nuvi12xx_13xx_14xxKeyboards_320.rgn
Caty, I'm sure that you, Smokefree and i all used the same rgn file from Post #1's link on the Garmin server when we dragged it onto WU. I'm equally sure that it contains the same file which is accessed by WU online to load D162200.zip into the Garmin folder for it to then extract to a new Keyboard folder on reboot. I've just never seen WU deal with an ancillary rgn file by converting it to a useless gcd as it did for SF's 1440 and my 1340. Yet the exact same rgn file is correctly loaded for you as D162200.zip when dragged to WU exactly as it should. That's the only mystery to me.
G'day, I'm probably off topic. (Same, same BUT different !)
Garmin seems to believe that here in Australia, we speak "British English" & use an "American English" keyboard !!!
So, I edited the "en_AU.glx" file. (see below)
Code:<catalog codepage="utf-8" direction="0" display_name="Australian English"
......................
So, I copied the "en_US.kbd" file.
then renamed it "en_AU.kbd"
and changed the display_name (see below)
Now I can select "Australian English" for text & keyboard.Code:<?xml version="1.0" encoding="utf-8"?>
<keyboards>
<header>
<lang_id>en_US</lang_id>
<display_name>Australian English</display_name>
<trans_name>STR_LANGUAGE_AMERICAN_ENGLISH</trans_name>
<code_page>1252</code_page>
</header>
...............................
(o)(o)
=(_)=
