I get these types of errors with my vista system constantly. in your case, I used to get them, and I think you're getting them, when there's an update available for a script at the same time as window eyes is asking you about reporting an error. both reports happen when window eyes is starting, and they seem to cause a conflict that sends window eyes into an infinite loop of errors, restart, etc.
the way I got around it was to configure window eyes not to report any updates at start up, and also not to ask me about sending errors at start up. to do the first I went into every script and set it's update notification to never. I use Jamal's installation script to check on script updates. to do the other I think it's a choice under the window eyes help menu; but it is a check box in the dialog the next time you report an error. hth, Chip ------------------------------ Chip Orange Database Administrator Florida Public Service Commission [email protected] (850) 413-6314 (Any opinions expressed are solely those of the author and do not necessarily reflect those of the Florida Public Service Commission.) > -----Original Message----- > From: Michael Massey [mailto:[email protected]] > Sent: Saturday, May 02, 2009 2:39 PM > To: [email protected] > Subject: Problems Encountered > > Hi all! I encountered problems on both my Dell desktop and > my Dell laptop > after discovering that there is a script update available for > the GW Tool > Kit. > > After at least four attempts to boot my laptop running > Window-eyes 7.01 and > Vista Home Premium edition, my computer would boot, > Window-eyes would start > talking and speech would go away. On one of the reboots the > script update > sound came and speech went away. I then pressed control > alt-w, got speech > back and somehow managed to install the update. I also sent > a kernel 32 > error to GW Micro. > > On the desktop the update sound occurred and I believe I > alt-tabbed to gain > focus to the script update dialog. I seem to recall having > to do this on > both machines but I'm not sure. > > I have also noticed that some times not all of the dialogs read > automatically so I have to manually read the window with > control shift-w. > > I certainly hope version 7.1 is going to solve these > frustrating errors. As > rock solid and stable as Window-eyes is, I have never > encountered as many > errors as I have during these past few months. Thank > goodness errors can be > reported to GW Micro so that they can be resolved. Keep up > the good work > guys! > > Mike M > > P.S. If script updates become available and scripts are set > to update at > start up, what is the easiest way to focus a dialog? . > > > __________ Information from ESET NOD32 Antivirus, version of > virus signature > database 4049 (20090501) __________ > > The message was checked by ESET NOD32 Antivirus. > > http://www.eset.com > > > If you reply to this message it will be delivered to the original > sender only. If your reply would benefit others on the list and > your message is related to GW Micro, then please consider sending > your message to [email protected] so the entire list will > receive it. > > All GW-Info messages are archived at > http://www.gwmicro.com/gwinfo, and can be searched through > and sorted using the search > form at the bottom of the page. > > If you wish to unsubscribe from this list, send a message to > [email protected] and include leave gw-info in the body > of the message. > > If you reply to this message it will be delivered to the original sender only. If your reply would benefit others on the list and your message is related to GW Micro, then please consider sending your message to [email protected] so the entire list will receive it. All GW-Info messages are archived at http://www.gwmicro.com/gwinfo, and can be searched through and sorted using the search form at the bottom of the page. If you wish to unsubscribe from this list, send a message to [email protected] and include leave gw-info in the body of the message.
