Dragon Naturally speaking not recognizing commands Options

[kuplo]

Maybe someone here with more experience than I (Wouldnt be hard since I have no experience) can tell me why no matter what command I speak into my microphone, DS9 just types it into my document.

Im thinking that I must have changed something somewhere but don't know what.

The only "command" that DS9 is recognizing from me is the "go to sleep" command and the microphone off command.

I try "select" word and it types into the document select word

Any clues what I might have done to mess it up? It worked fine in the tutorial and worked fine for about an hour or so then it just seemed to stop recognizing commands.

Thanks,

[Matt Chambers]

Maybe someone here with more experience than I (Wouldnt be hard since I have no experience) can tell me why no matter what command I speak into my microphone, DS9 just types it into my document.

Im thinking that I must have changed something somewhere but don't know what.

The only "command" that DS9 is recognizing from me is the "go to sleep" command and the microphone off command.

I try "select" word and it types into the document select word

Any clues what I might have done to mess it up?  It worked fine in the tutorial and worked fine for about an hour or so then it just seemed to stop recognizing commands.

Thanks,
[right][snapback]215856[/snapback][/right]

It is possible that you are in "dictation mode". Try saying "switch to command mode", pausing, and then seeing if any of your commands work.

[kuplo]

Thanks I think I sussed it out. Eventually I shut down DNS9 and found that it was still running in task manager at about 90% cpu usage so I forced it to terminate and when I tried to turn it back on, DNS9 said that it was corrupt and that I needed to repair it.

So I repaired it and rebooted and when it came back on, its now working properly. I also notice now that all the menu choices in the DNS9's menus like Tools and Words etc now are available to be chosen whereas before repairing it, there were a bunch of them that were not available to be clicked on.

But before repairing it, even the switch to command mode command didn't work, so it must have become corrupt somehow even prior to terminating the process when it refused to really shut down.

Thank you for your reply however,