|
||||
Just had to do some experimenting to figure out that under
Voice Command/Notification Options just select anything other than "Announce using BT Handsfree Only". Raging Idiot
__________________
Microsoft, Helmi_C, No2Chem, NexVision, tiermann, Colonel, gguruusa, luv2chill, imcokeman, jakdillard...many others. Thank you. We are all on shoulders of giants.
What's in a name? That which we call a genius by any other name would be just as smart. I beat up Sprint and all I have to show for it is this lousy ![]() When you were in diapers and wetting the sheets I was out hacking with the ppcgeeks. |
|
||||
vc 1.6 exe filename issues?
I extracted my voice command .exe file (v1.6) and my exe is named VoiceCMD.exe.
Is this the wrong .exe file? I put that in the Windows directory then try to run it and I get errors. ERROR MSG: Voice Command has encountered a problem. Restart Voice Command and try again. |
|
||||
You may wish to read the previous 5 pages on here because there has been some troubleshooting advice.
I think that you would have to follow the exact EXACT sequence of events detailed on the first post for it to work as originally described. It didn't work for me, but I can possibly attribute that to deviating from the exact sequence, as well as having a number of other programs I install separately. Eventually I just ran the regular setup for VC and later determined that at least one other program was interfering with it on startup. XCPUScalar appeared to be the culprit. Removing it from startup did the trick. |
|
||||
I should also say, that at least with my experience, VC would never start UNLESS it was already (pre)loaded from startup.
Also to note, I experienced many odd problems while troubleshooting this, lockups and screen needing constant alignments. Once I did what I've described above all the issues just "went away". I predict lots of resets in your near future. ![]() |
|
||||
In my startup folder, currently I only have:
__cusTSKTEMP.exe (not sure what this is) poutlook.ink wisbarlite.ink So your saying, remove all these from startup and only put in shortcut to VoiceCMD.exe from Windows dir? |
|
||||
Well, I just noticed that "wisbar lite" is showing up in my startup menu and causing problems. I don't really know what to recommend for you individually, but it appears that the only thing that seems to work every time for me is to remove everything out of the startup directory and leave the voice command files.
Also keep in mind I installed VC the normal method-and I don't remember if I moved the voicecmd.exe file into the windows directory (but it's there) as well as the same voicecmd.exe under \program files\voice command\ Perhaps one of these isn't needed and I'll remove it later, but I don't believe that is effecting the problem at hand. |
|
||||
i tried both ways (putting just the .exe under windows dir and installing it from the .cab file). Neither one work. Still get the error message.
Might do a flash and try this 3.5pr4 + sp1 again and see if that helps. Otherwise, I like the look and feel of this ROM. |
![]() |
|
|
|