Hi, Yes, I have had the same problem on win7 32bit and WE8. For as far as I know, was the last thing I installed the latest Nvda version and I installed it not as usb version. After a reboot, this problem was happening with Window-Eyes. Not sure if the Nvda installation caused this. I think not. Before I restarted, I loaded Nvda and unchecked the options about starting up at the logon screen and after login.
Regards, Marten On Fri, 21 Dec 2012 16:38:28 -0500 Chris Skarstad <[email protected]> wrote: > I can absolutely confirm this...in fact, I was speaking to one of my room > mates along with Jesse as the craziness was taking place. Quite literally > every 2 seconds or so, an instance of Window-eyes would load, there would be > a gw toolkit error, wineyes reloads, gw toolkit error, wineyes reloads, gw > toolkit error...it was absolutely crazy! All toled I think there were quite > literally about 300 instances of Window-eyes running in processes, and that's > no exaggeration either. I'm amazed we were able to get control of the pc, > load NVDA and uninstall Window-eyes. I'm very glad I wasn't the only one to > experience it but at the same time I feel bad that someone else had to go > through all that. I wonder what would cause such a thing to happen? I've > seen gw toolkit errors before, but after that happened the dialogue just went > away and no other instance of Window-eyes was started at all. > Weirdest damn thing I've seen in a while. > > > > On 12/21/2012 1:23 PM, Curtis Delzer wrote: > > > > > > At 09:47 AM 12/21/12, Jesse wrote: > >> Hi there. Wow oh wow does that sound familiar. The only way to get it > >> completely removed was to use Revo Uninstaller with NVDA. It >> happened > >> just > >> as you called it on a friends laptop Tuesday and that was the final >> > >> answer. > >> > >> As for how to report this error to the GW staff? Great question >> > >> since it > >> loops like a bad song in cue. But if its any consolation, your not >> the > >> only > >> one whose dealt with this nightmarish set-up. > >> Jesse > > > > I quoted the entire message above to the GW-info list so all can see. > I > > think, that disabling window eyes from within services in msconfig > should > > work. Heavens knows I have no other call at the moment and was > extremely > > fortunate I was able to corral the run away before it got > too much out of > > control. It took me probably ten reboots and on the > tenth I was able to > > seize control of my computer from the runaway > within gw-toolkit. > > I saw it enough times to see that. I wonder if there is a command > line > > option to start without scripts, and if that command would > circumvent the > > problem long enough to prevent it happening so I can > either update the > > script or delete the script. > > > > > >> -----Original Message----- > >> From: Curtis Delzer [mailto:[email protected]] > >> Sent: Friday, December 21, 2012 11:42 AM > >> To: Window-Eyes discussion list > >> Subject: window-eyes going CRAZY > >> > >> How to describe? When window-eyes comes up on my system, a >> gw-toolkit > >> error > >> pops up, window-eyes reloads, toolkit error, window-eyes reloads. . . . > >> It loaded about 83 times on my computer and the only way I could find >> > >> this > >> out was by using NVDA because window-eyes was too busy in a >> continuous > >> loop > >> of error reporting from within the toolkit script. > >> I, somehow, was able to unload it by using my external triple talk > >> synthesizer (which is backup), and while it loaded I was pressing > >> control-insert f4 frantically. > >> Now, I need to know how, to make sure window-eyes does not load before I > >> attempt to re-boot my computer. Is it in services in msconfig on >> > >> windows 7 > >> and can I stop it there? > >> Anyone else have this happen! I am hoping my CD with window-eyes >> comes > >> today > >> and I can uninstall window-eyes and / or repair, but looks like I may >> > >> need a > >> new install. > >> wish I knew the error and how to send the error report to GW-Micro while > >> using in another screen reader program. > >> > >> Curtis Delzer > >> 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. > >> > >> GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can > >> manage your list subscription at http://www.gwmicro.com/listserv. > > > > 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. > > > > GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You > can > > manage your list subscription at http://www.gwmicro.com/listserv. > > > 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. > > GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can > manage your list subscription at http://www.gwmicro.com/listserv. 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. GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage your list subscription at http://www.gwmicro.com/listserv.
