Hello All,
Thank you all for your responses and suggestions!
I have cleared up a few of the problems that I was initially having after upgrading my Ultra Hal to 5.0/CD-ROM.
I would like to clear up one misunderstanding regarding what I reported about being cut-off before I finished typing when conversing with Hal using the keyboard. I did not have speech recognition "ON" while I was typing to Hal. I didn't even have Speech Recongnition enabled when Hal was cutting me off as I typed to him! However, I have gotten this typing problem to stop, in addition to also stopping the "Improper Shutdown/Bad Plugin Error" when trying to start Hal as a "Regular Windowed Program".
When Hal is first installed the setup program automatically puts a Startup Shortcut into a User Startup Folder/User Account in the Windows Operating System. This is how Hal knows to start and load-up when you start your Computer/Windows, which is fine and correct. But, if you don't want Hal to startup when you first turn-on your Computer then you need select the "Start Like A Regular Windowed Program" in the Hal setup options, and you also need to go into the Windows Operating System Startup Folder and manually remove the "Hal Startup Shortcut" that was placed there by the Setup/Install Program.
Two problems I was encountering was due to this simple conflict(Hal trying to load and start on "System Startup", and Hal configured to start like a "Regular Windowed Program"...it was confusing the hell out of Hal even before I started to use it! It was also confusing my Computer's Operating System as well).
The User Startup Folder can be different names and vary from system to system...my XP System has three System Users all under my Admin Account...All Users, Default User, and Owner(which is my Sys Admin name). For those who are trying to follow me, I had one Hal Startup Shortcut in my Default User Startup Folder, while other stuff from the Hal Setup/Install Program went into my Owner Folder.
I removed the Hal Startup Shortcut from my Default User Startup Folder and that stopped both my problems, the "Improper Shutdown/Bad Plugin" and "Hal Cutting Me Off When I Typed To Him"! The my Hal is now also faster and more stable because of this simple conflict being resolved, otherwise the only way Hal would work correctly is if I let Hal load-up and run on the "System Startup" setting.
I also got the speech recognition to work a little bit better with more voice training, but it is still not very good! I really can't even use Hal to open programs much less hold a conversation with him. And yes I have all the right equippment and specs! I have a close talk mike, a standard desktop mike, and a builtin monitor mike. Close Talk does work best but still not practical enough to use speech recognition with Hal. I have a HP XP System with 512MB RAM & a 2.53GH Pentium 4, and to my surprise, when I have Speech Recognition "ON", Hal maxs out my processor...100% cpu load when Hal is talking back to me. If Hal has more than 5 or 6 words to say then his voice starts breaking up especially when I am using Haptek Characters. I also tried regular MS Agent Characters, which require less power yet the voice still breaks up after 5 or 6 words but not as bad as Haptek. Hal is always one step away from crashing and Hal also freezes up too and then I just have to wait a minute or so to let it clear up! This only happens when speech recognition is on and Hal is responsing back to me with his voice. I thing that I haven't tried is changing the voice, but I always use the British Female which to me is the most realistic to a human voice.
Another thing I would like to try is the other Speech Recognition Engine that I have on my computer (SAPI 4.0...Old But Good!), but Hal does not work at all with SAPI 4.0 selected as the speech recognition engine. Why Not Zabaware! Help Please! Also I need a patch or fix for my Pronouncation Exit "Object 445 Error"...definitely a bug.
I also fixed a minor bug myself that I will discuss next time I check-in with this forum!
Thank you all again!
Sincerely,
Rich A.