W
Winguy
At the site http://www.microsoft.com/msagent/dev/code/TryMSAgent.asp an
animated character is supposed to fly in and actually speak over your
computer speakers, with bird lips moving as Peedy speaks. Additionally,
balloon text appears as the "Agent" speaks. For XP users, there's a link at
the top right of the page at http://microsoft.com/msagent to obtain SAPI
4.01a stuff that is supposed to maybe be necessary to make Agent characters
actually speak instead of just displaying baloon text.
What I want to know is how many XP SP2 "FULLY AND 100% TOTALLY UPDATED"
(others need not apply, thank you!) readers of this message actually get to
hear Peedy speak and see lip movement as the Agent speaks? How many only get
to see the balloon text but do not get to hear Peedy speak and do not see
the bird lips move? If it does fail, how about after trying to install that
SAPI 4.01a stuff, does Peedy still refuse to speak?
If you're not able to hear speech from that website link, then if you try to
install the SAPI 4.01a stuff (carefully note the computer time when you do
that) and then immediately look near the very end of your
"&windir%\setupapi.log" do you see entries similar to:
[2005/06/22 21:26:52 548.1] <--- here's the computer time when the log
started, search upwards for it.
#-198 Command line processed: "C:\Documents and Settings\Administrator\Local
Settings\Temporary Internet Files\Content.IE5\CH012B8T\spchapi[1].exe"
#E361 An unsigned or incorrectly signed file
"c:\temp\ixp000.tmp\spchapi.inf" will be installed (Policy=Ignore). Error
1168: Element not found.
#-024 Copying file "C:\TEMP\IXP000.TMP\speech.dll" to
"C:\WINNT\speech\speech.dll".
#E361 An unsigned or incorrectly signed file "C:\TEMP\IXP000.TMP\speech.dll"
will be installed (Policy=Ignore). Error 0xe000022f: The third-party INF
does not contain digital signature information.
and so on? I'm asking because I've brought this issue to Microsoft's
attention and a tech there has been able to duplicate the problem, but I'd
like to know both how many FULLY UPDATED XP S2 users are and are not having
this problem that keeps Agent characters from speaking? What kind of errors
are occurring and being recorded in the log if you try to apply the SAPI
4.01a stuff? TIA
animated character is supposed to fly in and actually speak over your
computer speakers, with bird lips moving as Peedy speaks. Additionally,
balloon text appears as the "Agent" speaks. For XP users, there's a link at
the top right of the page at http://microsoft.com/msagent to obtain SAPI
4.01a stuff that is supposed to maybe be necessary to make Agent characters
actually speak instead of just displaying baloon text.
What I want to know is how many XP SP2 "FULLY AND 100% TOTALLY UPDATED"
(others need not apply, thank you!) readers of this message actually get to
hear Peedy speak and see lip movement as the Agent speaks? How many only get
to see the balloon text but do not get to hear Peedy speak and do not see
the bird lips move? If it does fail, how about after trying to install that
SAPI 4.01a stuff, does Peedy still refuse to speak?
If you're not able to hear speech from that website link, then if you try to
install the SAPI 4.01a stuff (carefully note the computer time when you do
that) and then immediately look near the very end of your
"&windir%\setupapi.log" do you see entries similar to:
[2005/06/22 21:26:52 548.1] <--- here's the computer time when the log
started, search upwards for it.
#-198 Command line processed: "C:\Documents and Settings\Administrator\Local
Settings\Temporary Internet Files\Content.IE5\CH012B8T\spchapi[1].exe"
#E361 An unsigned or incorrectly signed file
"c:\temp\ixp000.tmp\spchapi.inf" will be installed (Policy=Ignore). Error
1168: Element not found.
#-024 Copying file "C:\TEMP\IXP000.TMP\speech.dll" to
"C:\WINNT\speech\speech.dll".
#E361 An unsigned or incorrectly signed file "C:\TEMP\IXP000.TMP\speech.dll"
will be installed (Policy=Ignore). Error 0xe000022f: The third-party INF
does not contain digital signature information.
and so on? I'm asking because I've brought this issue to Microsoft's
attention and a tech there has been able to duplicate the problem, but I'd
like to know both how many FULLY UPDATED XP S2 users are and are not having
this problem that keeps Agent characters from speaking? What kind of errors
are occurring and being recorded in the log if you try to apply the SAPI
4.01a stuff? TIA