![]() |
Again, Colonel's rom is not KITCHEN based, so we do not think these are related issues, but thanks for the input. I guess we could try it if necessary.
IMCOKEMAN- I think you are on to something. I have also noticed in 3.3 that occassionally the IR beam stop responding from comm manager, just as bluetooth does. COMM MANAGER is the common link to all 3 issues. Could it be that there is something corrup in the COMM Manager on the Kitchen based roms??? |
Re: Registry Entries for Voice Command v1.6.
Quote:
Thanks In Advance. |
ppc6700freak: you are converting the txt back to hv correct? Are you using the kithen or the "other method"? I use the "other" but have only tinkered with the kitchen. There is not a large difference between them from what I have seen, but others have stated that some keys they have entered had been overwritten by othere things using it. If in the kitchen I would post on one of those threads and see if anyone has feedback.
I would also recomend not inuding this line from my entres: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Au dioGateway] "BTAGExtModule"="\\windows\\vcbthag.dll" "NoRoleSwitch"=dword:00000001 "BTAGPBModule"="\\Windows\\BthAGPhonebook.dll" "SupportCLI"=dword:00000000 "Capability"=dword:00000025 "VoiceCmdEnable"=dword:00000000 "LaunchAPEnable"=dword:00000001 it is already being incudef in the the baseine for most. At least watch to see if it is and remove it as you do not need it in the final reg twice. -saridnour |
Saridnour, Thanks for the reply.
I found the issue. I had word wrap turned on.... |
| All times are GMT -4. The time now is 12:11 PM. |
Powered by vBulletin® ©2000 - 2025, Jelsoft Enterprises Ltd.
©2012 - PPCGeeks.com