Thread: Digital FX 2.0 Transparent Released

Originally Posted by dmistry

*wishful thinking*

atleast it drew you out John!

Originally Posted by mnwcsult

My last two post sum up the problem no response from CDRskul


http://www.mp3car.com/vbulletin/road...runner-18.html

I have come upon the solution by rereading the in file instructions about dialing strings

#### Answer and Hangup AT Commands, use *** to show where the dialed number should be.. ie ATD150; is ATD***; ####

Answer=ATA
Hangup=AT+CHUP
Dial=ATD**********; <<<<<<< I have too many stars


The Instructions clearly show ATD followed by (3) ***, my interpertation was a * for each number in a telephone number, as the example showed ATD150 3 digits.

Actually *** is the placeholder for the dialed telephone number. Where the entered telephone number will be substituted for the placeholder ***. And the placeholder is always three *.

Originally Posted by barnyard

Ok, I've had this problem for a while, and I'm not even sure where to start... see the below screenshot, all of the iGuidance menus are shifted to the left, and cut off. I'm running at 640x480, and everything else works, just the menus are screwy. Any suggestions?

Just incase someone else has this problem, I figured out what was causing it. I had the windows taskbar on the right side of the screen because it's easier to "click" on an 8" touchscreen. The taskbar was shifting iG's menu over the width of the taskbar.

Originally Posted by dmistry

Kbreeden, so this morning I get in the car and do a restart from the resume and can you believe the CPU issue went away and I now have GPS location working.

Glad to hear it.

Originally Posted by dmistry

One final thing to solve and I should have a fully working system, I have tried a bunch of things to get the volume to lower when GPS is speaking like setting the GPS volume higher than the master volume etc. STill does not work any ideas on this one?

There's been a lot of discussion of this and I'm not sure the cause has ever been determined. I had the problem also and was pulling my hair (what's left of it anyway) out trying to figure it out. Finally, I did something - I have no idea what - and it has worked ever since. Best as I could tell, there was some sort of conflict between how Blue's RRConfig and the DFX skin were handling this. I can't remember for sure, but it seems to me that Blue may have recently updated his RRConfig program to address this somehow. Maybe Blue will chime in or you can review the last couple of pages of his RRConfig thread for some insight.

Cough...

yes the last config update, I took out the igpause stuff, b/c too many users having probs.

Originally Posted by kbreeden

There's been a lot of discussion of this and I'm not sure the cause has ever been determined. I had the problem also and was pulling my hair (what's left of it anyway) out trying to figure it out. Finally, I did something - I have no idea what - and it has worked ever since. Best as I could tell, there was some sort of conflict between how Blue's RRConfig and the DFX skin were handling this. I can't remember for sure, but it seems to me that Blue may have recently updated his RRConfig program to address this somehow. Maybe Blue will chime in or you can review the last couple of pages of his RRConfig thread for some insight.

The master JohnWPB don't agree but i also believe the above is true - you have to chose which either RRConfig or DFX you want to handle that function. I chose RRConfig and disabled DFX's (in ExcTBL) and all work fine. There are a few tweaks you got to do to IG's volume, the wav volume and the main volume but in the end it work fine. There is a thread about that but i don't remember where.

Originally Posted by dmistry

May be he will release his code/psds or whatever! *wishful thinking*

You don't know John very well then do ya...

Just be patient people...

i'm itchy