I have a Visual Basic 6.0 program that I wrote with Windows 2000
installed that used Microsoft's DirectSS control (xvoice.dll). This
control has an event called AudioStop. I was using the control to read
a list of numbers and used the AudioStop event to tell the program
when it had finished "speaking" one number and could begin the next.
This program worked like a charm...until I "upgraded" to Windows XP
home edition. Now the AudioStop event doesn't even fire. I'm reduced
to setting a fixed time limit for each number, which results in long
pauses when the numbers are short and numbers getting cut off if
they're too long.
I suspected that it was simply a case of different versions of
xvoice.dll, and in fact the version I was using on Windows 2000 was
4.0.4.2512 and the version on Windows XP is 4.0.4.3303. However,
un-registering the newer version and registering the older version did
not make any difference. My only other thought is that it has
something to do with Visual Basic .Net, which I had installed on the
Windows 2000 system, but do not have on the Windows XP system.
Unfortunately, I could not find any information to support or disprove
that hypotheses and Visual Basic .Net will not run on Windows XP Home
Edition so I can't install it and see if that makes a difference.
I would be interested in knowing why the AudioStop event no longer
fires, but an answer would be more than satisfactory if it simply told
me how to fix it. I have searched microsoft.com extensively and also
the internet at large but have not found any answers, so you are my
last resort.
Thank you for any help you can provide and also thank
you for providing such an excellent resource for those of us with
lots of questions and few answers! |