I have been a Dragon user for 20 years, paying around nine thousand for the first set up.  I am a writer and strictly end user. I now have Dragon 11 Pro, with Knowbrainer @2010.  When I used to use Adobe pdf 8, I seemed to be OK. More lately, with the latest Abobe upgrade, the Adobe software puts a reader into play and wipes out part of my Dragon and Knowbrainer features.  I have gone back to Adobe 8 for the time being; but, I do prefer to use Adobe 10 with latest upgrades.  Is there a way to neuter Adobe so that it does not keep reproducing these problems, even after I go in and remove the "reader;" or, is Adobe now set up to constantly, within minutes, to metastasize --like cancer-- their unique cells that kill the Dragon or Knowbrainer cells?

The latest version of Adobe Acrobat Reader X (10.1 or higher) should play well with NaturallySpeaking the 11.5 but not 11.0. Click About NaturallySpeaking under the DragonBar Help menu to verify that you are using 11.5. If you're not using 11.5, you can click Check for Updates. You will find additional options in the NaturallySpeaking Quick Tips (at the top of this page) when you look up “HOOKERR”.

-------------------------

Click KB 2012 REV D to Download a 30 Day Evaluation of KnowBrainer 2012 

 

 

 

 

Wallace,

Lunis has basically covered the general issue. However, let me give you a little more detail.

First, when Adobe Systems move from Acrobat reader 9 to Acrobat reader X, they added an extra layer of security (i.e., Protected mode). This created a basic problem for anybody using Dragon NaturallySpeaking relative to the two possible error messages that you get regarding COM reported an unexpected error code: details are HOOKERR_NONOTIFYWINDOW or any of the associated SendKeys error messages.

Both Nuance and Adobe Systems addressed this problem and fixed it in DNS 11.5. However, if you're not using DNS 11.5 (i.e., you're using DNS 11.0 and have not yet updated to 11.5), then it's time to update your copy of Dragon via the SP1 update patch. If you do that, this fixes the problem and you will be able to use Acrobat reader X without issue.

The latest version of Acrobat reader X is 10.1.3, which is supposed to fix any problems with regard to versions of DNS earlier than DNS 11.5 by prompting you with instructions as to how to turn off the Acrobat reader Protected mode option. However, that works in some cases but not in others, and it works for some users and not for others. So, going that route is somewhat unreliable. Your best bet is to upgrade to DNS 11.5 where the problem is completely fixed.

Chuck Runquist
Technical Project Manager
VoiceTeach LLC
Home of VoicePower®: We don't make Dragon NaturallySpeaking, We make it better!

If there's more than one way to do a job, and one of those ways will result in disaster, then somebody will do it that way.  (variant of Murphy's law - Edward A. Murphy, Jr.)

-------------------------

What about those of us who are still using DNS Professional 10.1?  About a week ago this problem cropped up making my DNS system almost unusable; I uninstalled Acrobat reader X (I was using the latest version) and reinstalled version 9.5 for windows and for a few hours the problem was gone but now has started again.  What other options do I have?

-------------------------

It sounds like you are confusing this issue with a different but related problem which is Adobe Flash; not Adobe Reader. The latest version of Adobe Flash can produce a similar Hookerr problem. Your options are to either disable Adobe Flash in your browser or uninstall Adobe Flash from within Windows Control Panel.

-------------------------

Click KB 2012 REV D to Download a 30 Day Evaluation of KnowBrainer 2012 

 

 

 

So now you are saying that BOTH Adobe 10 or greater AND/OR Adobe Flash Player 11 cause this Hookerr? I had gone back to Adobe reader 9.5 when this started around the beginning of this year and finally no problems and stable dictation. Now within the last few days I have been getting this error all the time. It does not always freeze DNS like it did before but now worsening and within the last hour will not dictate at all.

-------------------------
DNS Preferred10.1,Win 7, 4Gb, Core 2Duo E8400

Uninstall Adobe Flash Playe rand see if the problem goes away. If so you can try an earlier version.
In my case the current version of Flash causes the HOOKER error bu the the May 4th release of the current version works just fine.
Go to this link
http://helpx.adobe.com/flash-player/kb/archived-flash-player-versions.html#main_Archived_versions  

Click on
(Released 4/13/2012) Flash Player 11.2.202.233 (159 MB)


Phil Schaadt

-------------------------
DNS12 Pro BM V Large Vocabulary plus KB or Voice Computer running Win7 64 bit machines with i7-2640M to i7-3960x and i7-3770K processors plus a Sony VAIO Windows 8 machine. DBX Audio Gate with Allen&Heath mixer/USB Audio; Andrea PureAudio USB  usually with Airline 77 or Audio-Technica but also Sennheiser MD431 II, theBoom, et. al.

Nitro Reader, free and which also includes a PDF printer, does not cause any issue with DNS.

-------------------------

Bill
DNS Pro v12.5, KB 2012, Mtech Desktop PC (i7 960 3.2 gHz with 12 GB RAM), Windows 7 Pro 64-bit, 240 GB SSD, Philips SpeechMike 3500, SpeechWare 3-in-1 TableMike, Philips SpeechMike 5274 Classic, MS Office 2010 Professional

Adobe Flash 11.4 and 11.5.502 have the problem with Dragon 11.x. Nuance has no solution. There is a solution which involves ProtectedMode=0 in the Adobe configuration file mms.cfg (solution discussed in other forums) but this could open your system to attack from trojans posing as Flash movies. An acceptable risk, I reckon.

Everitt,

First, Nuance has no control over the Adobe flash player issue because the problem comes from the Adobe Systems side. It's important to understand that when you get the COM reported an unexpected error code: details are HOOKERR_NONOTIFYWINDOW, Dragon is simply reporting that a protected mode setting, whether it be from Adobe Acrobat reader, Adobe flash player, or most likely from Adobe shockwave player is preventing Dragon from accessing a particular application, file, or window. In other words, Dragon is attempting to, for lack of a better way of putting it, something from which it is being blocked. In short, it's not a Dragon problem per se. Dragon is simply being prevented from accessing whatever. Dragon is still functioning properly by virtue of the fact that it's simply notifying you of the problem, frustrating is that may be.

Prior to the problem first arising with Acrobat reader X and progressing through some of the Adobe flash player updates in the last 6 to 8 months, there was no protected mode in any previous version of Acrobat reader or Adobe flash player. So, why should disabling protected mode be any more risky than it was prior to this. Adobe Systems instituted protected mode as a security precaution for itself, without realizing that it had the potential for creating problems for other applications, particularly Dragon NaturallySpeaking. Most of the issues have been resolved. DNS 11.5 resolve the issue with Acrobat reader X. Adobe Systems compensated for the problem with Adobe flash player with the release of version 11.5.502.110 (ActiveX) and 11.4.402.287 (Plug-In). In addition, users of Dragon NaturallySpeaking should not have a problem with the newest Acrobat reader XI.

Second, the problem arises from two different sources: (a) Acrobat reader X below version 10.3 under Windows XP, and (b) Adobe shockwave player in Firefox with an occasional speed bump in earlier versions of Adobe flash player below the two mentioned above. Although I'm sure that some users are continuing to experience this particular problem, disabling Adobe shockwave player in Firefox and uninstalling such if installed in Add or Remove Programs (Windows XP) and Programs and Features (Windows Vista/7) should solve the problem for most users. Note that the problem doesn't exist in Windows 8 because Adobe flash player is handled completely differently. However, Adobe shockwave player may still be a problem in some versions of Firefox. On the other hand, some users have not experienced any problems in this area. The only reason that I'm pointing this out is that saying that Adobe flash player 11.4 and 11.5.502 still has a problem with Dragon 11.5 isn't an absolute, and is not likely a problem with Adobe flash player as much as it is a problem with Adobe shockwave player and Firefox. Anybody still using Dragon NaturallySpeaking 11.0 will continue to have a problem until or unless they upgrade to 11.5. Nuance and Adobe Systems resolved the original issues with Acrobat reader X and protected mode with the release of DNS 11.5. This was reported by both Nuance and Adobe Systems.

Lastly, as long as you are protected with an adequate antivirus, anti-Malware, anti-spyware program, even if you turn protected mode off (ProtectedMode=0), you should be adequately protected. Besides, the likelihood of videos posted on the Internet being infected with Malware or viruses is relatively limited: (a) because it would be reported immediately, and (b) such videos would probably be taken down as quickly as they're put up. I know that some users have posted that this is a dangerous and risky setting. Not really. You're more likely to get infected via your e-mail and/or files sent to you then you are from any flash video. Nevertheless, there is a risk, albeit minimal, but it is, as you say, acceptable given the low probability factor. Nevertheless, using the ProtectedMode=0 option should only be used as a last resort anyway. That is, if you can't find any other means of resolving this particular issue.

Nuance will not have any solution to the problem because it's not Nuance's problem. Nuance can't fix the problem even if it wants to because the problem originates from Adobe Systems. To assume that Nuance could or should fix the problem is like assuming that Adobe Systems should be able to fix bugs in Dragon NaturallySpeaking. Dragon NaturallySpeaking is working perfectly fine even if you are getting the COM reported an unexpected error code: details are HOOKERR_NONOTIFYWINDOW. Locate the source of the problem with your setup and configuration and the problem will go away with Dragon returning to its normal status and function.

Chuck

"The least questioned assumptions are often the most questionable." -- Paul Broca

-------------------------