I believe this short narrative is consistent with most of the posts on this latest "build" of JFW 12. I reported to this list that, for some reason, Outlook processes started refusing to close. Responses on this list suggested that JFW was not really the problem. Nevertheless, if JFW had been unloaded during the process of closing Outlook, the processes closed. If, however, JFW continued running during the close, the process remained open approximately 8 out of every 10 times. Freedom Scientific technical support initially told me to install version 12.0.1158. I protested that I knew that build contained at least one horrible bug that made Excel unusable. The technical support person seemed shocked. That brings me to my first point. Wouldn't it be helpful if Freedom Scientific personnel, in the Technical Support department, monitored this and possibly other JAWS lists? I know GW Micro employees regularly interact with users on the Window-Eyes listserv. I can assure you that their presence does not inhibit the freedom of expression of some of the list members. Anyway, the technical support person suggested that, instead of posting on this list all the defects of version 12.0.1158, a call to technical support would resolve the problem -- with just a few settings adjustments. I suspect those changes are pretty close to the ones Dave mentioned on this list, and the changes sounded more like JAWS script editing than a few settings adjustments. Well, since I don't use Excel all that much and since the Outlook problem was truly vexing, I installed the JAWS 12.0.1158 version. I should mention here that the technical support person was very specific about not merely "accepting" it as an update, but rather, I was instructed to go to the Website and download the full package, which I did. I have not yet tried Excel (and perhaps I should, though I don't now remember the specifics of the Excel problems). The downloaded 12.0.1158, however, did not fix the Outlook problem. Using the "ticket number," I called Freedom Scientific back. This time, the tech support person remembered the problem. He said the problem was really a Microsoft problem, though JAWS did something to exacerbate the problem. His suggestion was to do one of the following: 1. Upgrade to Office 2010; 2. Use control plus shift plus escape to bring up the offending process and kill it manually after exiting Outlook; or 3. Continue what I had been doing, namely, remove JAWS every time I stopped or started Outlook. Well, that's my version 12.0.1158 story -- for what it is worth. ############################################################################################################# ANY FEDERAL TAX ADVICE CONTAINED IN THIS MESSAGE SHOULD NOT BE USED OR REFERRED TO IN THE PROMOTING, MARKETING OR RECOMMENDING OF ANY ENTITY, INVESTMENT PLAN OR ARRANGEMENT, AND SUCH ADVICE IS NOT INTENDED OR WRITTEN TO BE USED, AND CANNOT BE USED, BY A TAXPAYER FOR THE PURPOSE OF AVOIDING PENALTIES UNDER THE INTERNAL REVENUE CODE. ############################################################################################################# This E-mail message is confidential, is intended only for the named recipient(s) above and may contain information that is privileged, attorney work product or otherwise protected by applicable law. If you have received this message in error, please notify the sender at 402-346-6000 and delete this E-mail message. Thank you. ############################################################################################################# -- JFW related links: JFW homepage: http://www.freedomscientific.com/ Scripting mailing list: http://lists.the-jdh.com/listinfo.cgi/scriptography-the-jdh.com JFW List instructions: To post a message to the list, send it to jfw@xxxxxxxxxxxxx To unsubscribe from this mailing list, send a message to jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line. Archives located at: //www.freelists.org/archives/jfw Alternative archives located at: http://n2.nabble.com/JAWS-for-Windows-f2145279.html If you have any concerns about the list, post received from the list, or the way the list is being run, do not post them to the list. Rather contact the list owner at jfw-admins@xxxxxxxxxxxxxx