Stephanie

It would probably throw an error message or window. It might continue working or it might sieze up. With the iGo stuff, if I've omitted something it throws a little windows error message, then pretty much locks up.

Tilt the volume knob up to zoom in, tilt it down to zoom out. Tilting it left and right will move to the next or previous track, on the iPod or CD. As far as putting soft zoom buttons on the screen, it is probably possible. It would take some searching though - it's easy to add buttons or other visual elements, the trick is making them do something useful. You could search all the script files in data.zip to find something that controls the zoom level; it would be in I haven't noticed any zoom scripts in my exploration but I haven't been specifically looking for them.

Time remaining: navigation.time_to_destination ETA: navigation.eta_at_destination You can find all the variables used in the three info lines, by looking in data.zip\ui_pioneer\common\ui\navigatemap.ui around line 978.

My mistake, i had a typo in my last post. (Dang data.zip with it's redundant files and multiple folders) data.zip\ui_pioneer\800_480\ui\navigatemap_800_480.ui data.zip\ui_pioneer\common\ui\navigatemap.ui Those are the two paths/folders that I was refering to.

navigatemap.ui is located in data.zip\ui_pioneer\common\ui It should not be confused with navigatemap_800_480.ui which is located in data.zip\ui_pioneer\800_480\navigatemap_800_480.ui The difference between them is files with the 800_480 in their name are mostly graphical/visual elements, while the files that are in the common\ui directory are mostly scripts. Cheers!

CRC's aside, I might have messed something up. Sick, drugged, befuddled, etc. I'm still a little gunshy about playing with the .res files however, so I'm not going to try again -- at least, not for a while.

I doubt it. A firmware update will probably come with its own data.zip, so it might be necessary to replace that file, but unless they do something very drastic, it shouldn't impact any of this.

You might need to activate images in firefox, or something like that? I use Safari (on Macintosh) and see all the images just fine. Also I think you need to be logged on to the site to see the images? I seem to recall before I registered, I couldn't see any images...

Actually, I do. But then, I'm wierd that way. I generally want to know everything there is to know about a product, inside and out, before plunking out the $ for it. Especially if it's a big-ticket item.

Please Note: This Howto assumes the following: 1) You know how to get into Testmode 2) You know how to navigate folders, copy and paste, in Windows CE 3) This HOWTO is based in part on information found at this blog post and on the knowledge presented by other contributors here on these forums. 4) With the exception of copying/pasting files, all editing of files will be done on your desktop/laptop computer, *not* the nav unit directly. 5) I will include a copy of my complete data.zip file at the end of this post, you may use it as a basis for your own work, you may edit it to your purpos

See what, specifically?

I still haven't dug too deeply into the 'mdl' file but I went ahead and made a 3d bmp icon for myself - it's basically the same as my daycar.bmp but I squished it a little bit on the vertical plane so it has an illusion of being from slightly behind. I still don't use 3d mode much but I figured I'd do this anyways... was a bit bored. I did these pics with the map in 'day mode' but night mode looks much better - it's just harder to get a good picture of. I'm still somewhat annoyed that I can't find any way to display the heading in degrees - that's the only thing missing now from my m

As you know, the content of those three boxes in the lower left can be customized through the normal Navi settings menu. So if you're still using the original text elements etc then you can just change the context through the settings as per the manual. If you've replaced the original elements with your own and you need the actual internal variables to display what you want, then have a look in data.zip\ui_pioneer\common\ui\navigatemap.ui and down towards the bottom you will find all the variables for the various options for those three lines.

It's possible I messed something up, I've got a cold or flu or something and I'm kind of dizzy and befuddled. But I thought I had done everything ok, all i had changed was the strings table to edit the warning text. Whatever I did though, it prevented the thing from booting, and made me think it was bricked when testmode failed the first time around. If they did want to ensure people didn't tamper with the main software though, doing a crc or some other kind of check against the mainres.res file would certainly make that a lot tougher. As an aside, I wonder if this is part of

Well I went into the MainRes.Res file and edited the message. All I did was change the text. My plan was to see if the text did indeed change on the nav unit, then we'd know for certain we were on the right track. (We've had a few red herrings within the navi software after all.) So I made my new MainRes.Res file, copied it to the F700 after moving the original to MainRes.bak. Then I rebooted and waited for my new message. And waited, and waited. The 'starting...' screen was there for ever. Well, big sigh, didn't work, but I figured no worries, it just wasn't reading the new MainR

The navi is basically stand-alone software, it's separate from the rest of the functions. Unfortunately the scripting in the iGo software is unable to affect the rest of the system, as near as I can tell.

Now that I have my F700 looking and working more or less the way I want, I'm trying to achieve something that (I think) should be a fairly basic GPS function. In my old gps, I had about 60 'Landmarks' set up, with all different icons. I have some businesses, some friends and family, some vacation areas, etc etc. Now with my old GPS V I basically drove to these places, then pushed a button to save the coordinates as a landmark. Then I could name them and put an icon on them. With a Sony NavU that I played with for a week, you could type in an address, it would find the address, then you

Considering the iPod dock connector (on the iPod) carries everything, audio, video, power, controls, etc etc, I suspect that the reason that Pioneer chose to do it the way they did, because it saved them money. Doing it this way means that they can use basically an off-the-shelf cable for the iPod side. It means they don't need to use a special purpose connector on the radio side. It means they can use the same inputs for iPods as for any other A/V source, i.e. they didn't need to wire a second set of inputs that were strictly for the iPod. They could have stuck an iPod dock connec

It would have to be mechanical. It is not possible for the laser in a dvd player / reader to develop enough energy to burn the disk. Readers are maximum 5mW while writers can peak at over 200mW. Even if an electronic fault put enough current into a 5mW diode, it'd just overheat and die rather than pump out any more light energy. I might not know much about audio stuff but I do know lasers..

The iPod cable has an iPod dock connector on one end, and at the other end is a USB connector, and three RCA connectors (L/R/V). On the iPod end you just need the dock connector plugged in. On the Nav end, you need the USB, as well as the three RCA connectors, plugged to the radio. If the installer hooked up the USB cable but neglected the RCA connectors (perhaps thinking they were redundant) you would have iPod control, but no audio/video.

I've tried a few times to launch explorer from within the iGo program, but without success. :/ I noticed the existing scripts using an execute command "EXEC" but I was unable to get explorer to launch with this. I tried a few different ways to do it, none of them did anything.

Awesome! Thank you, Bman69! I'm at work right now but I'll try this out when I get home this afternoon.

I've got the 700 and to me the album art looks ok. There are a few where it looks really good, and a few where it looks a bit pixellated, but I figure that's due to the quality (or lack thereof) of the images in the first place, not the fault of the 700. I'm using an iPod nano, 8gb, whatever version is the current one.

Enough with the suspense already -- please, tell us where you found the rest of the images!

Sure. You can download my latest/current data.zip file here. Briefly, anything you want to make clickable, add into the element onrelease='run scriptNameHere' and any element that you want to control through scripting, you have to assign an unique ID (so something other than xxx). So for the latlong thing, I've got the speedo element containing onrelease='run sc_steph_showPos' then in the latlong is onrelease='run sc_steph_hidePos' The scripts themselves I have put in scripts_800_480.ui down at the very bottom. I have five of them there, showPos and hidePos, then