Well my version of GIR_Editor0.56 only open files that have the new "gir" header which usually are in fw_resources.bin and logo.bin. It crapped out on .gcd, .rgn and even certain .bin You probably mean RGN_Tool opens .gcd and .rgn files and not GIR_Editor ;)Quote:
Originally Posted by Neil [Only registered and activated users can see links. Click Here To Register...]
Yeah that's total crap i wrote in a rush and not what i meant to say at all. I meant it will open, and extract symbols from, logo.bin files and will also open and extract symbols from fw1_resources.bin obtained from rgn and gcd files.
PS: But it can't open the 'old style' GIR files as i said, despite it's name. But of course turboccc never meant for it to do that, he was initially only interested in the symbols from 'new' firmware containing fw1_resources.bin. Naturally it will also happily open a dump from rgn127 [0x7F] because that's where fw1_resources.bin is flashed.
The "old style" is extremely easy to parsed because of 1) someone already posted format and 2) it's just a simple format so looking at hexdump you can easily spot what is and where. I'm sure with turboccc ability, adding it to his proggy shouldn't be hard. Nevertheless, no one is complaining; I'm just stating observation. Since "old style" gir is hard to find, I thought "old timer" like yourself would know which "old garmin" units uses them and hence I can tests them (I've been scouring [Only registered and activated users can see links. Click Here To Register...] for some, but it's a shot in the dark for me.) BTW, there are graphics in some fw_all.bin section as well.Quote:
Originally Posted by Neil [Only registered and activated users can see links. Click Here To Register...]
Turbo's original GIR_Editor [v1.0] only reviewed and extracted from certain resource files according to his change log. I think when he added ability for logo.bin extraction of BMP images in V2.0 that may have been when any bin file containing symbols/images was recognised. Any other .bin file which doesn't contain graphics will be rejected with the message 'Only gir file and logo files are supported' as you know.
There's certainly not any [old-style] .gir files in nuvi-type units' internal files, again as you'd already know. There's none in GMXT or nRoute either. Sorry i don't know of any apart from those in GMPC's program files and have no idea if any others actually exist. Hence my offer to rekit your undies and sock drawers [easier task for me]. Maybe there's something different in old region-only units like StreetPilots?
I'm using GIR_Editor0.56 and it failed to recognized graphics in fw_all.bin of [Only registered and activated users can see links. Click Here To Register...]Quote:
Originally Posted by Neil [Only registered and activated users can see links. Click Here To Register...]
Using hex editor goto 5934132 and it's a start of a small PNG (BMP_SYM_WPT_DOT icon)
Now the fw_all.bin file is a file without "gir" header (unlike logo.bin and fw_resource.bin), so technically it's not a "gir" file; but it does contained graphics.Code:89 50 4E 47 0D 0A 1A 0A 00 00 00 0D 49 48 44 52 00 00 00 07 00 00 00 07 04 03 00 00 00 36 7C 4A E0 00 00 00 30 50 4C 54 45 00 00 00 80 00 00 00 80 00 80 80 00 00 00 80 80 00 80 00 80 80 C0 C0 C0 80 80 80 FF 00 00 00 FF 00 FF FF 00 00 00 FF FF 00 FF 00 FF FF FF FF FF 4F 13 26 49 00 00 00 15 49 44 41 54 08 99 63 F8 FF FF FF 07 86 0F 0C 0C D8 09 90 2C 00 2D D6 11 3B C3 38 D0 93 00 00 00 00 49 45 4E 44 AE 42 60 82
That's why Turbo called it GIR_Editor then, because it can only open bin files with gir header regardless of whether there's graphics or not. Makes sense now. Being aware of the existence of 'actual' *.gir files previously was a disadvantage to me there, i've always wondered about the naming seeing it can't edit *.gir files at all. I suppose it scans the bin file and if it can't see a gir header it rejects the file with that message, is that so?.
Some bright young chap could maybe make a little app to pull the graphics out of other 'non-gir' bin files? Are you likely to find anything different and useful in them d'ya think?
Yes, GIR_Editor was appropriately named. I'd bet the "gir" header was introduced after the 7x0 series, that's why you don't get fw_resource.bin but you do get graphics in fw_all.bin Organization of graphics inside fw_all.bin is still a mystery to me (only look at it about an hour); worst come to worst, say hello to searching for "89 50 4E 47" ... "49 45 4E 44" + 4 bytes afterward. I might write a string scanner to do it just to extract 7x0 icons.Quote:
Originally Posted by Neil [Only registered and activated users can see links. Click Here To Register...]
Took little longer than was expected, in a loud Klingon voice: Qapla'
Spoiler: .
Not bad looking, I don't see Cyclop alert icons, so I take it you can't have Cyclop running on 760TWN firmware?
That doesn't seem correct that Safety cams aren't recognised. I had an US/EU 765 converted to TWN previously and i don't recall it losing that function. It's converted to SG/MY at present and certainly has Cams working, unlikely that other Asian firmware would lack it i guess.
The only likely icon i could find in your list was BMP_DFLT_GPI_SPD_CAM_SYM.png: [Only registered and activated users can see links. Click Here To Register...]. Seems the Asian fw use it as the default for all cams, both redlight & speed. Confirmed for redlight by this SG/MY 765 Screenshot on US41 N. Skokie Hwy [cnr Kilbourne Rd] routing north towards Milwaukee:
[Only registered and activated users can see links. Click Here To Register...]
Here's the product page from Garmin Taiwan:
Google translation of the Specs:Code:http://www.garmin.com.tw/products/ontheroad/nuvi765/#featureTab
[Only registered and activated users can see links. Click Here To Register...]
In the '產品規格' [Specifications] Tab, this Chinese text:
Translates for me using Google as shown in the screenshot above:Quote:
特殊警示： 生產時已預先輸入固定式測速照相點警示功能，並分成已知速限與未知速限之圖示，另外，預留使用者自建點空間。詳細應用方式，請參考網站 [Only registered and activated users can see links. Click Here To Register...] 說明。
May as well still be in Chinese. This is Bing's attempt:Quote:
Special warning : Has been pre-entered production fixed speed camera warning function, and shown into the unknown and the known speed limit speed limit of the addition, the space reserved for user self point. Detailed applications, please refer to the website [Only registered and activated users can see links. Click Here To Register...] instructions.
Maybe you can decipher that better, but to me it seems that it does support Safety Camera alerts [they call it Special warning?].Quote:
Special warning: Production has entered a stationary speed camera warning function, and split up into icons of known speed limits and speed limit is unknown, in addition, the provision for user-built space. More applications, please consult the Web site [Only registered and activated users can see links. Click Here To Register...] notes.
Good info, mate! But I was thinking that since Cyclop alerts often uses those cool red icons and since I didn't find any, I assumed that it didn't support it. TW firmware does seem to have speedcam alerts, but is it Cyclop capable? Remember Cyclop alerts uses a special record that has 3 points and probably some data indicating which build-in icons to use (there are no icons included in the Cyclop .gpi's) Now that I know fw_resources.bin contained icons (including Cyclop's) the next thing to do is to find a correlation between those icons and the data in .gpi This will definitely help to decode Cyclop records some more. But I might need your help to test the .gpi file to see if icons is shown correctly after mod. How you say "sweet!" in Klingon?
Edit: Since my proggy only extract .png, there could be icons in .bmp format that might be Cyclop alerts. So the holy grail is to see TW firmware with Cyclop's .gpi AND showing Cyclop's icons.
