Hi Greg,

Check out the following websites. One or a combination of both may help
resolve your problem with Dragon NaturallySpeaking crashing:

http://www.speakeasysolutions.com/blog/2011/03/07/dragon-error-com-returned-an-unexpected-error-code-details-are-hookerr_nonotifywindow/

http://www.speakeasysolutions.com/blog/2012/06/14/com-returned-an-unexpected-error-code-details-are-hookerr_nonotifywindow-from-flash-update/

Please let me know if either works for you.

Steve - C4, 24 years

On Wed, Aug 1, 2012 at 7:29 PM, Greg <[email protected]> wrote:

> Hi Steve,
>
> Thanks for your reply.  You have me pegged right on.  I am using DNS
> v11.5, Mozilla Firefox and Adobe Reader X/Adobe Flash are installed.  All
> are up-to-fate.  Also, I have "Enable Protected *M*ode at startup"
> unchecked in the Adobe Reader X Preferences section.
>
> The error message is the: HOOKERR_NONOTIFTYWINDOW error.
>
> Can you help me get this back to working?
>
> Greg - c/5
> since 1987
>
>
> On Wed, Aug 1, 2012 at 3:47 PM, Quad Dude <[email protected]> wrote:
>
>> Hi Greg,
>>
>> If you are using Dragon NaturallySpeaking v.11.0 or v.11.5 and are using
>> the Mozilla Firefox web browser, there are known issues if you also have
>> the latest versions of Adobe Reader X and/or Adobe Flash installed. Let me
>> know if this is the case and what if any error messages you are receiving
>> when DNS crashes and I may be able to assist.
>>
>> Steve - C4, 24 years
>>
>> On Wed, Aug 1, 2012 at 9:36 AM, Greg <[email protected]> wrote:
>>
>>> Nuance just sent me an email on the new version of Dragon, and I am
>>> tempted.  After using v.10 and v.11.5 on a Windows 7 machine for several
>>> years with no problems whatsoever, Recently. Dragon has begun crashing a
>>> lot (A LOT!) almost to the point of not working at all.  No luck finding
>>> the exact cause of the problem and short of uninstalling vital components
>>> in my browser(s) I can't keep Dragon working.  I wonder if DNS 12 will work
>>> any better.
>>>
>>> I also wonder, and this is cynical I know, but I wonder if this recent
>>> problem I am having with v11.5 is in any way related to the timely release
>>> of v.12.
>>>
>>> Greg - c/5
>>> since 1987
>>>
>>

Reply via email to