This is probably a topic for a whole other thread, but I'm sure you guys are aware that this thing seems to be running sqlite...

has anyone checked out what's going on in those tables?

also,... bump.

The i18n folders are located in the language packs: My Flash Disk\APL2\iGo\CONTENT\LANG

What we are looking for is the reverence to the drive_carefully.xhtml file.

I see in the update files that the .res files are 7z archives. You can open them in winrar or winzip

inside the archives there are parameter files (.pnd files) , which you can edit in a text editor

Maybe someone understands this and can find a way to leave the message out (or install tomtom instead )

has anyone played with line 105 of variable_dev.ui ?

Won't hurt trying, but that variable is not used anywhere in iGO scripts, so I doubt that it will control the message display. It must be done somewhere in Pioneer's shell...

Won't hurt trying, but that variable is not used anywhere in iGO scripts, so I doubt that it will control the message display. It must be done somewhere in Pioneer's shell...

maybe. I'm thinking it maybe defined there by default (out of scope)... and if we add it to like the top of each of the files (hack in like a global scope), something might happen!

That I doubt. Once the UI file is loaded, variables are global, and redeclaring it elsewhere is known to lead to all kinds of problems.

Idk if this will contribute any info, but I got into map mode wihout the message..

The other night, I stopped by a friend's house to hang out, and when I got there, I called his cell. The unit booted up into the iPod menu since I didn't use the map prior, and when the call went through, it went into map mode, but we all know it does that. However, when the call ended, the unit stayed in map mode and worked fine, no warning screen came up until i physically pressed the map button while it was on map mode. It seems like the bluetooth use bypasses the warning screen. Maybe this could be a clue as how to bypass it?

Interesting... Probably connected to the bug of a phone call always bringing up the map? Still, as far as I could see, something handled outside of iGO. Would be nice if I am wrong about this...

WIN CE EMULATOR AVIC411 POST

I was toying with the WIN CE emulator and 7zip to see if i could get around the nag screen and...

if you look at My flash\Apl\MainRes\NSWinsOpening there is a file called "UIN_WIN_PLCaution.win"

I deleted this file and in to the emulator brought up the main screen clicked destination and it crashed on me.

I was hoping some one with a little more knowledge then I would give this a look see and figure out if it was just another crash or dose it have to do with the fact the unit cant find the nag screen so it dies

will aslo post this in the mag screen msg

[/url]

I assume this was a dead end? Kinda too bad. I could see the warning being a cause of accident.

it must be hardcoded into an exe which we cant edit very easily :/ sorry but until we get someone to reverse engineer them this is going no where

an early reply since i dont even have the unit hooekd up yet..but in my d1, if i set a destination and reset the unit before reaching there. upon the second restart the message doesnt come up..is that a possible angle worth checking into?

Something interesting related to this...

I have noticed that when I start up the AVIC, if it has been left one some screen other than the map (ipod, fm, etc) I can get into the map without having to press "OK". All I do is make a call with my phone through the bluetooth, then after I hang up, the screen automatically goes to the map. This happens every time I do this in that order. Then, while I am on the map screen, I can press the "MAP" button and the safety message will pop up with the "OK" button.

Don't know if anyone else has experienced this or if it might give some insight into how we can get around the message.

Sorry just realized this has been covered a few posts ago.

I am new here - interested in helping out. There are alot of hackers in the communities I frequent that could figure this out - and change it if it can be changed. They will know if it was coded into the chips or if it's all software.

One question - was the message prior to V2 the same as V2? I mean exactly the same? Same button, same button position, same color when you press on it. Same text?

If someone has already backed up their stock radio (all the files) can you send me a link - I can't do mine until tonight because I got the wrong SD card. I want to post it to the sites I frequent and ask someone to do their magic.

If the disclaimer was different prior to V2 upgrade and is coded into the chip then the flash upgrade is where the key is. I can download the upgrade to V2 and poke around. Maybe one of the hacks can look at the flash upgrade and alter it.

Well there is a little DD that needs to be done on this - I will start snooping.

I am new here - interested in helping out. There are alot of hackers in the communities I frequent that could figure this out - and change it if it can be changed. They will know if it was coded into the chips or if it's all software.

 

One question - was the message prior to V2 the same as V2? I mean exactly the same? Same button, same button position, same color when you press on it. Same text?

 

If someone has already backed up their stock radio (all the files) can you send me a link - I can't do mine until tonight because I got the wrong SD card. I want to post it to the sites I frequent and ask someone to do their magic.

 

If the disclaimer was different prior to V2 upgrade and is coded into the chip then the flash upgrade is where the key is. I can download the upgrade to V2 and poke around. Maybe one of the hacks can look at the flash upgrade and alter it.

 

Well there is a little DD that needs to be done on this - I will start snooping.

Message was exactly the same and it is called from the executable (EZRider)....

Sorry for the noobishness but as i've stated in the past, I am not very computer tech savvy...but what exactly does EZRIDER.exe do? I know it's an executable file and it's connected to the warning screen, but what about rewriting an ezrider.exe but excluding the warning screen coding?

And is it possible that there is maybe a hidden file that brings up the warning screen? It seems from reading these posts that every time a file is deleted it results in the unit crashing upon pressing map, but what if those are completely irrelevant files to what you're really looking for?

Sorry for the noobishness but as i've stated in the past, I am not very computer tech savvy...but what exactly does EZRIDER.exe do? I know it's an executable file and it's connected to the warning screen, but what about rewriting an ezrider.exe but excluding the warning screen coding?

 

And is it possible that there is maybe a hidden file that brings up the warning screen? It seems from reading these posts that every time a file is deleted it results in the unit crashing upon pressing map, but what if those are completely irrelevant files to what you're really looking for?

EZRider = iGO = navigation software on the AVIC.

I don't think that the warning is from ezrider.exe. I think that it is actually in the mainmenu.exe. I have been running the executable in the Windows CE V5.0 emulator. The warning screen pops up even after I deleted all the iGo files.

Does anyone have an editor that can read the .bpnd files in the .res files correctly? I thought I saw Guga mention they were .xml files or something of that nature, but opening them in a non-hex editor gives you some extra ASCII characters (kind of like F|O|N|T...). Also made sure it wasn't a SQLite DB that just happened to store strings as Unicode or something like that.

Anyway, there's a .bpnd file in one of the .res files (I think it was AVRes.res or something like that) that looks to be related to a warning message. Just couldn't read it out correctly to correlate which .exe calls it or how to kill it.

EDIT: Correction. It's in MainRes.Res under MainRes\NSWinsOpening\UIN_WIN_PLCaution.win.pnd.bpnd. Killing off some of the NULs didn't result in any strings matching the warning message, so... Losts of Font and Text Content IDs though, so it still might be in MainMenu.exe if it was indeed built with NSBasic (gotta love eVB/NSBasic forms).

I don't think that the warning is from ezrider.exe. I think that it is actually in the mainmenu.exe. I have been running the executable in the Windows CE V5.0 emulator. The warning screen pops up even after I deleted all the iGo files.

This makes sense, as the warning only come up the first time you initialize the map function? I'm still waiting on my unit so I cant offer much help yet but from what I've been reading it sounds like the warning only comes up once until you turn the car off. From a programming prospective this has to be part of the main unit program, not the mapping software. Has anyone looked at the launch code from the main dash screen for the units? the code for the MAP button? Just my .02

Has anyone checked out Navi.exe in the APL folder? It seems very small only 7kb.

I was just thinking that it might be the program that brings up the warning.

I was playing around with NAVI.exe and replaced the WM_PAINT branch with a branch that send PostQuitMessage to see if I could get NAVI.exe to immediately return. I then booted into test mode and copied my modified binary over into APL directory and ran MAINMENU.exe directly. After touching the DESTINATION icon, I still got the safety warning message.

I decided to try one more thing before restoring my AVIC back to default. I deleted NAVI.exe and reran MAINMENU.exe. I still got the safety warning after touching the DESTINATION icon. All of this leads me to believe that the safety message is still in MAINMENU.exe.

I bought a male-male usb cable hoping to remote debug MAINMENU.exe but I can't get Vista to recognize the AVIC over USB. Anyone able to help me? I've already sent leetcoder a PM asking for a good pointer to start tracing at the code that responds to pressing the DESTINATION icon. Anyone else interested in disassembling MAINMENU.EXE?

Paul