Thread: Extraction and Experimenting with Garmin voice Audio Packs and fw symbols, icons

Originally Posted by Neil

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.