Stephanie

Yep, daycar.bmp and nightcar.bmp are the graphics for 2D view. They (and all of the other graphics) do use Alpha channel transparency, so you need to be aware of that when making them. I'll start another thread about this with concise instructions. Not without access to Pro Motion. In 2D mode a regular BMP is used, in 3D mode, to account for the ability to change the angle, daycar.spr and nightcar.spr are used. If anyone has Pro Motion I would love to see what we can come up with. Correct, see above. Thanks for the tips, skicrave! For what it's worth those spr files

Nice! Was that the daycar.bmp file that you changed?

What happened when you removed the ezrider program? Did the iGo software still work? For that matter, what happened when you booted without the data.zip file?

One thing is as long as there is an upgrade path, there is a way to get in...the challenge is to figure it out. A few years back I was playing with an embeded linux device called a Zipit. Somebody figured out the manufacturer's upgrade path and after that the door was wide open. So you could probably take their upgrade files and use them to install your own software. Just find where the version info is kept and increment it, so the device thinks you're installing even newer software. As for why they might want to stop (or at least slow down) the tinkerers, who knows. Some companies se

My feelings with the boot time are mixed. Before installing the F700, I had a separate GPS and radio. I'm used to the radio being instant - as soon as the engine is going, I can listen to music, work the controls, etc etc. The GPS, I am used to it taking a minute to kick in. It's just how GPS's work, it takes time to lock on to the satellites and make a fix. Getting the fix is more demanding than keeping the fix. My old GPS had three different 'nag' screens, but if you didn't hit the 'enter' button the screens would each time-out on their own, and by the time they had all timed-out

Good work Giessen - I don't know why that didn't work when I tried it; maybe I messed it up. That's what I was trying to do originally, anyhow Re. a firmware update, I figure the worst-case scenario is that they release an update that replaces our customized data.zip with their original one, and closes the testmode door so we can't get in any more. I've examined the first update thoroughly and I know that before I apply a new one, I'll modify it to contain my own data.zip and fonts etc. That, and maybe wait for someone else to apply it, and then find out what exactly it does an

All the XM graphics are in My Flash Drive\DATA\XM; there are four subdirectories with lots of XM stuff in them. The APL directory contains a bunch of executables and dlls but nothing 'skinable'... I haven't found any other graphic files to mess with. Stuff in the APL directory include the AV.exe and mainmenu.exe and stuff like that - I think that's pretty much the rest of the applications. Outside of the "My Flash Drive" there are some more directories, including Program Files (empty) and Windows. I tried copying the windows directory to my flash disk, and got partway through before

Someone upthread asked about getting a copy of my entire data.zip file. The file can be downloaded from here. You also need to get three free fonts from http://www.simplythebest.net/fonts/ in order to complete the package. The three fonts are "Final Frontier New", "Final Frontier Old", and "Space Age". All four files (the zip and the three fonts) need to be given the following filenames: data.zip finalold.ttf finalnew.ttf space.ttf All four files go in your iGo directory: My Flash Drive\APL2\iGo Presumably you would want to edit out my name and put yours in; my name appears

Wow - I never noticed this. Thank you gjas18!

Here is the clock code from my navigatemap_800_480.ui file: I don't remember all the changes I have made but I think one of them may have been to the template... from xtxt to xtxt2. One other random comment, about these elements. The x= and y= are obvious, w= is the width of the element, h= is the height of the element. You'll see z= quite a bit, that sets how the elements are 'layered' on the screen. If you put two things in the same place on the screen, the lower z number is at the 'back' and the higher z number is in 'front'. mazda_3, the files we are working on are con

I wonder if it is a quirk of the way GSM phones work? If I look at my phone, it doesn't show the call as connected until the other party picks up. I'll hear ringing of course in the earpiece but the GSM system won't log the call as connected till they pick up the phone... I don't know where the ringing sound comes from though, if that's generated inside the handset or if it actually comes from the phone company. So maybe that's the source of the bug; that the nav unit doesn't connect the audio until after the phone signals that the call has connected.

I've only made a couple calls, but now that you mention it, I don't think I've heard the phone ring. It's more like silence, then click and someone is there. I'm using a SE w610i (GSM) handset.

I had a brainstorm this morning about this stuff... no solutions yet but one more piece in the puzzle perhaps. In general_800_480.ui there is a line which calls the safety message xml file: but the i18n directory does not exist. Otherwise I was hoping to view the xml file and see if that was indeed the file that we see as the safety message. So this morning it hits me, that maybe the i18n directory is hidden in the ezrider executable -- and it is! I don't have decompiling abilities -- infact I'm not a windows programmer (or for that matter, a windows user) so I'm lost whe

The AV keybeep sounds are a separate issue and don't live in the data.zip file. See the other thread about removing the keybeeps.

I think if you look in the data.zip\ui_pioneer\common\ui\general.ui file there is a state for a safety message. (I might be mistaken, but I'm pretty sure that's the correct file.) Anyhow, it seems to be referring to an XML file that does not exist, so I don't really know if it's valid or not. It contains the coding to launch and display a safety message then to dismiss it. I haven't really experimented with that however, as I was unable to find the XML file so I figure it's just another dead end -- leftover code from some distant iGo ancestor. From the comments in those files, there's

I'm not using a Mac for this, I'm using Windows to 'explore' the data.zip rather than unzipping then rezipping it. Just double click the zip file, and navigate to the right directory to find the file to edit. I'm using notepad to make the changes, then notepad won't save back into the zip file so I save to the desktop then copy it into the zip file. When I tried unzipping, making changes on the Mac, then rezipping, the nav unit refused to accept my new zip file, it gave an error and wouldn't start the mapping software.

"It depends..." I have no idea what MSNDirect is or what it does... if it's implemented entirely in software then you could *probably* take the software off a 900 or 90 and load it onto the 700. You'd really want a full flash dump to make sure you got everything, just in case... like if there are DLLs or EXEs in the APL directory, or if there's stuff burried right into the windows system then you'd need the windows binary as well.

It had not occured to me that anyone else might want a copy of my data.zip, but I don't mind sharing at all. Later today, or perhaps tomorrow, I should be "finished" with my current messing around, then I'll post a link to it, so if anyone else wants to have at it, or use it as a starting point, it's available. The main reason I didn't think anyone else would be interested, is I've almost completely eliminated 3D mode as I prefer the North-Up 2D view exclusively. More accurately, the mode still 'exists' but there is no longer any way to get to it, as I've removed the 3D buttons. An

Which post's directions are you following? This thread has seen a lot of progress and evolution going on... somewhere around page 3 or 4 I have provided a link to a data.zip file that has the bars and boxes removed already; that would be a good place to use as a starting point.

As far as I know, the EU units use the same software, and should be skinnable just as easily. I'd wager that the data.zip files would be interchangable from a North American unit to a European unit. From what I can see, virtually everything you can see in the iGo software is managed through the skins. The only exception seeming to be that !#^%$ warning/disclaimer message, that we haven't been able to eliminate yet.

Good work typing all that out - I'm too lazy for that much work I am pretty sure the '746' prefix is Pioneer's internal product or series number, but I'm not sure if that relates to the F-series, or something else. There are references to '749' in other files as well, although not the graphics. The '32K' is probably refering to the colour depth or something like that, although maybe that's what the '32b' refers to. 'MN' is for menus, 'OM' is for the map. I believe these '746' files are either Pioneer-specific, or are at least used especially for the ui_pioneer theme. I say that be

I think they are leftovers from the iGo software - when you turn it on for the very first time, it needs to know what language you use, and there are three files for three different resolutions. So on a PDA or whatever, you might get the 320 x 240 screen. There is an awful lot of junk in the data.zip file, stuff that seems to be unused and leftover from prior iterations. Even in the files themselves, seems to be a lot of unused leftover stuff from many previous versions.

I tried it for the blue boxes and it didn't work. :/ It was one of the first things I tried, and I'mnot sure why it didn't work. Edited for clarity: Although there are two kinds of file (visual elements, versus scripts) they all have the same file name of .ui which makes it confusing. The stuff that is in the 800_480\ui directory is almost all visual elements; the stuff that is in the common\ui directory is almost all scripts. Visual elements like and so on, can be turned on and off, or have any properties, manipulated by the scripts. So even though a visual element like the boxes or

This sounded like a good idea and was pretty easy to implement. Add this line of code in navigate_800_480.ui just below the line that displays the time (it's in the first area near the top of the file). You need to make some changes for position and the actual graphic. The x=720 and y=140 will probably not look good, as there are other things in that area usually. I'd suggest x=720 if you want it in the same vertical column as the 3D/2D and compass but y=280 or so to move it down towards the lower right area of the map. You'll have to experiment as to where you want it, exact

CatchMeIfYouCan631, good observations. If you want to elminate the red crosshairs, I would suggest rather than deleting that bmp, just edit it to be fully 100% black. This way, the system won't throw a file-not-found error, but the 'crosshairs' will be invisible. If that doesn't work (if it just gives you black blobs all over the place) then replace the file with a copy of the blank bmp from earlier in this thread; that should replace the crosshairs with 1 pixel invisible dots. I noticed the same thing with the bmp icons' black background; some of the bmps do appear to have transparency