I had the error condition the first time I ran window-eyes after the
updated script, but no longer. And, I've run window-eyes several
times today, which is my custom when changing environments, to change
screen readers for situations I encounter with the different software I use.
At 07:42 PM 1/6/2016, Orlando Enrique Fiol via Talk wrote:
At 10:39 PM 1/6/2016, david pearson via Talk wrote:
>I get the same thing. i did a system restore to last week to get rid of it.
This is definitely overkill. After reviewing and unsuccessfully
editing Windows Enhanced Maintenance.vbs, I simply deleted that file
from my Window-eyes default directory and the errors disappeared.
Orlando Enrique Fiol
Ph.D. Candidate in Music Theory
University of Pennsylvania
Professional Pianist/Keyboardist, Percussionist, Arranger, Performer
and Teacher
_______________________________________________
Any views or opinions presented in this email are solely those of
the author and do not necessarily represent those of Ai Squared.
For membership options, visit
http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/curtis1014%40verizon.net.
For subscription options, visit
http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com
List archives can be found at
http://lists.window-eyes.com/private.cgi/talk-window-eyes.com
_______________________________________________
Any views or opinions presented in this email are solely those of the author
and do not necessarily represent those of Ai Squared.
For membership options, visit
http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com.
For subscription options, visit
http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com
List archives can be found at
http://lists.window-eyes.com/private.cgi/talk-window-eyes.com