I've just setup a new instance of WinXP SP2 and installed very little, only support applications/drivers, such as Alcohol and nVidia drivers, including all the post SP2 service packs. So I can't imagine I've installed anything that would cause what I'm reporting. What prompted this action was several failures, one of which was the HS Speaker application not working at all -- I'm certain something was corrupt, so to test this theory I figured I would start from scratch and see what happens.
The fresh installation of WinXP seems to be working fine after I've installed HS2.1.104. My Speaker Client worked flawlessly, recognized the attention command and speaks as expected when HS is not running as a service. Note that I can go to control panel and successfully launch the Speech applet. When I enable the Run As Service feature of HS and restart Windows, I notice something strange. The HS Speaker Client loads, but freezes and has to be terminated if I press the Start Listening button. Oddly enough, I go to Control Panel and attempt to start the Speech applet and I get the following message:
An exception occurred when trying to run "%WINDIR%\system32\shell32.dll, Control_RunDLL "%PROGRAMFILES%\Common Files\Microsoft Shared\Speech\sapi.cpl", Speech"
I attempted to search the MSKB and only found the following article which did not pertain nor help my situation: http://support.microsoft.com/kb/906373/en-us
Instead, I simply turned off the Run as Service feature in HS, restarted Windows and the world was right again. I'm at a loss for determining what might be causing this problem, but naturally, several other resource website recommended renaming keys, reinstalling this and that, etc. In the end, if all I have to do is Run As Server or not Run As Service to cause/resolve this problem, respectively, then HS is must be the root cause, would it not?
Thoughts or recommendations anyone? I would like to run HS as a service, but I'd also like to have the speech working too.
The fresh installation of WinXP seems to be working fine after I've installed HS2.1.104. My Speaker Client worked flawlessly, recognized the attention command and speaks as expected when HS is not running as a service. Note that I can go to control panel and successfully launch the Speech applet. When I enable the Run As Service feature of HS and restart Windows, I notice something strange. The HS Speaker Client loads, but freezes and has to be terminated if I press the Start Listening button. Oddly enough, I go to Control Panel and attempt to start the Speech applet and I get the following message:
An exception occurred when trying to run "%WINDIR%\system32\shell32.dll, Control_RunDLL "%PROGRAMFILES%\Common Files\Microsoft Shared\Speech\sapi.cpl", Speech"
I attempted to search the MSKB and only found the following article which did not pertain nor help my situation: http://support.microsoft.com/kb/906373/en-us
Instead, I simply turned off the Run as Service feature in HS, restarted Windows and the world was right again. I'm at a loss for determining what might be causing this problem, but naturally, several other resource website recommended renaming keys, reinstalling this and that, etc. In the end, if all I have to do is Run As Server or not Run As Service to cause/resolve this problem, respectively, then HS is must be the root cause, would it not?
Thoughts or recommendations anyone? I would like to run HS as a service, but I'd also like to have the speech working too.
Comment