Ok, Mainmenu.exe contains the source of the safety message.

I placed var vDriveCarefully=0 with lots of different formats i.e. DriveCarefully=0,etc...

I tried different values such as -1 and 1 and 0.

I only had the mainmenu.exe file with the .dlls and the ini files ....parrot, etc.. in them from its parent directory and I also had only the sys.ini file going in the appropriate folder to keep everything controlled, so in other words there were no other files on the flash disk.

DriveCarefully variable was placed in all the .ini files.

Result: Message still comes up.

Next Actions that will have to be taken....decompile mainmenu.exe because it's all in there.

I'm travelling for the next couple of days, but I can upload the disassembled file when I return. Any good place to upload?

I've been through all the possible files for the safety/caution message, either its in too deep to decompile, or its defined as InitializeCriticalSection and DeleteCriticalSection

That's all I can gather.

Maybe we are going about this the wrong way.

Is there away to get a script to run at a specific point? Could we trigger a script when you press whatever things cause this message to come up? This script would do the button press for you...

I have asked leetcoder to point me to the entry point where the destination button is pressed. Maybe it we all ask him nicely he will help us out.

If any knows how to get the device emulator or our avic to work with ida pro or any other debugger, that would rapidly increase my progress. Right now I am hand tracing the instructions and commenting the code.

Paul

Hey guys... In the file data.zip/ui_pioneer/common/ui/navigatemap.ui, there is a code snippet that caught my eye:

...


 
The sc_SkipMessageBox script's code is:




 
I haven't been able to track down the code for vActionNotConfirmed or sc_HideMessageBox yet, but has anyone tried messing with this code to see if commenting it out skips the safety message?  It seems like it's something run-once and disable...
 
Also noticed some messages that the init is sending to MainMenu and AV:

	EXEC "other.pioneer.postmessage" "MainMenu" "WM_APP_AV_IGOMAP" 1
	EXEC "other.pioneer.postmessage" "MainMenu" "WM_APP_MAINMENU_CLONING" 5



 
and
 





 
Has anyone managed to set some breakpoints in the simulator and catch these message events?

FourG,

Those do look like interesting snippets of code. Have you tried modding these lines and/or deleting the entire file? If I remember correctly, I deleted the entire iGo directory tree and ran mainmenu.exe on the Windows CE emulator (still can't get it to sync up/debug with IDA Pro on vista!!!!!). The message still popped up. You may want to confirm this on your AVIC. That would either confirm or deny that those snippets are doing what you think they are doing.

Back to hand tracing MainMenu.exe!!!

Paul

FourG,

 

Those do look like interesting snippets of code. Have you tried modding these lines and/or deleting the entire file? If I remember correctly, I deleted the entire iGo directory tree and ran mainmenu.exe on the Windows CE emulator (still can't get it to sync up/debug with IDA Pro on vista!!!!!). The message still popped up. You may want to confirm this on your AVIC. That would either confirm or deny that those snippets are doing what you think they are doing.

 

Back to hand tracing MainMenu.exe!!!

 

Paul

Any further progress ? been quiet for a few months....

Any further progress ? been quiet for a few months....

Not quite yet, just got the F90BT and GEX-P10HD hooked up on the desk with an ATX power supply this weekend but haven't had time to start hacking (pesky thing called work keeps getting in the way ). It's on the Todo list, but like Dr Paul mentioned even with the entire APL2 directory nuked the message still pops up in the simulator (have to confirm on actual hardware). Hopefully there's a registry hack to kick the USB into ActiveSync mode so I can attach a remote debugger...