It seems that in 2008 the only player left on the field is Nuance Communications Inc's Dragon NaturallySpeaking (version 9.5 being the latest edition, being essential a Vista-compatible update of Version 9.0).
I'm a little over a week into the process of familiarizing myself with NaturallySpeaking (DNS) and am rather impressed by it. I'll have more to say on this in the future, but right now thought that I would log a little issue that I came across, in the spirit that such blog postings help other people who encounter the same variety of issues, for example:
- An error was encountered while opening a window
- Best way to install a Netgear FR114P Print Server (and possibly others) under Windows XP -- very popular
- Tips for installing multiple Lotus Notes Client releases on a single system -- quite popular
After installing UT2000 I discovered that DNS refused to start up, with an error dialog stating that it would not continue because an old version 184.108.40.2068 of the speech.dll file was installed (in the WINDOWS\speech folder) and it needed the latest version 220.127.116.112 to operate with good stability and performance.
I spent quite a few hours after that diagnosing and trying to solve this problem. It turned out that when installing UT2000 I had also installed a companion product that could be used to pronounce the typed words, and it was this which had overwritten the latest speech.dll with the older version (a perfect example of so-called "DLL hell").
I tried uninstalling UT2000 and reinstalling it without the speech option, to no effect. I even tried Windows XP restore points and even a full repair but these too were help whatsoever.
It was as a last resort that I uninstalled NaturallySpeaking, fearing that I would lose the hours that I had spent training it to recognize my voice (my "user" files). However the team at Nuance had obviously considered this in their design, and the uninstaller offered the option to retain the user files.
Then I reinstalled NaturallySpeaking and after pointing it to my user files it was back to business. That's all there was to it, what a relief!
Why didn't I try this approach right at the start? I dunno, that's the way thing turn out sometimes I guess. But the moral of this story is to be careful in deciding to install several speech products simultaneously, and maybe making a manual Windows system restore point or a manual copy of the WINDOWS\speech folder before each install would be a way of being able to recover. Your comments welcomed...