nickfuzz: That was the method I posted about using until I found the reg entries I posted above (http://ppcgeeks.com/is-this-possible...,start,15.html). Once I tracked down the last of the entries made by setup.dll that method was no longer needed. It also creates an uninstall point. Not that that is a big deal, but getting it all in the rom is a bit more seemless. :)

-saridnour

saridnour, so this entry is not overwritten when you initially boot the device? I have it set correctly in my .hv, but it gets changed somewhere. I will check out what you posted.

[HKLM\Software\Microsoft\Bluetooth\AudioGateway]
Change BTAGExtModule to vcbthag.dll

colonel: This is what I have for that reg entry as a whole. This has not been modified post first boot and should be a representation of what is produced after flashing with my ROM:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Au dioGateway]
"PowerSave"=dword:00000000
"SpkVolume"=dword:00000008
"MicVolume"=dword:00000008
"BTAGExtModule"="\\windows\\vcbthag.dll"
"NoRoleSwitch"=dword:00000001
"BTAGPBModule"="\\Windows\\BthAGPhonebook.dll"
"SupportCLI"=dword:00000000
"Capability"=dword:00000025
"VoiceCmdEnable"=dword:00000000
"LaunchAPEnable"=dword:00000001

Again though I do not use the kitchen for my roms so other data may be getting merged when you create your image files.

-saridnour

Thats strange. I am not using the kitchen either. Getting ready to flash again and we will see what happens.[/list]

Saridnour: I am glad you are patient with reloading roms and tweaking the registry. I spent many hours trying to get the VC registry to load from the kitchen and make the program work fully, but couldn't quite master it. I agree, I would like a fully seamless ROM, but I'll take what I can get. I wonder if it makes any difference that I use the kitchen, and that I have many other things running in my ROM. Thanks for identifying more reg entries that I may have to try later.
:shock: :)

nickfuzz: Try this, take the two reg files (default and user) and copy one into the other and save them as vc.reg. Then import this into your newly installed ROM with your files in place in the \windows dir. This should work and not create and install point as well as verify the entries for your device. Will need to soft reset after the import, but it would be cleaner than running a cab and setup. :) Let me know if you give this a shot.
VC works out of the box so to say without tweaking in my rom so I know it's possible. :)

colonel: I also noticed that Love2chills button 5 fix has differing keys.

HKEY_LOCAL_MACHINE\Software\OEM\VoiceCommand Vs.
HKEY_LOCAL_MACHINE\Software\Microsoft\VoiceCommand

Not sure if you have been working with this or not, but saw you had posted on the thread. Did you get this to work? Tried under the MS path with no results. Haven't had much time to play with it, just thought I would see if you had any info since you may have tried both sets of reg key entries.

-saridnour

Did anyone get this working with the posted kitchen OEM? I tried to use it but come up with the same issue as colonel here. It starts but you don't hear any responses from VC.

I to am having the exact same issue with the posted one from colonel. Ive tried merging the reg entries, and still cant hear any responses. I also tried putting sar reg entries into an RGU and having it go into the main hive file later, but it gets a parse error "at or around line 202"


this is getting exasperating, and my poor phone is being flashed 5x a day haha... anyways, keep us posted if we get a working kitchen OEM.

Thanks!!!

Can someone PLEASE post a verified working MSVC oem(without just the exe) so that all we have to do is toss it in and presto it works?

I don't think there is any such thing at this point (or at least I haven't heard anyone say that they have a fully fuctional VC OEM).