Yes, I had to do this for the same reasons. Also, I had to go into each script and make sure it was not set to update itself, or the same sort of error would occur when it had an update available.
I too am using Jamal's installation/update script as I find the web interface to script central cumbersome and awkward, and quite time consuming to work my way through. I also never see any useful information (discussions, ratings, etc.) posted there, so I was wondering if others find it as I do, or am I missing valuable discussions or information by using Jamal's script? thanks. 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: Jeff Weiss [mailto:[email protected]] > Sent: Wednesday, May 06, 2009 1:28 PM > To: [email protected] > Subject: RE: Window-Eyes 7.01 failing on start-up > > What I did was just go into the script manager and unload the > WeUpdate script. > I use Jamal's install packages script, set to both, to get > both new scripts and updated scripts. > I find this more convenient than having any scripts check for > updates themselves. > Hope this helps, > Jeff Weiss > > -----Original Message----- > From: John Farley [mailto:[email protected]] > Sent: Wednesday, May 06, 2009 12:10 PM > To: [email protected] > Subject: Window-Eyes 7.01 failing on start-up > > Dear list, > > I have just started my home PC. > It is using Windows XP Pro with WE 7.01. > > When it started up I got the musical note telling me there is > an update to the WE Update script to V1.1.1 for Italian > localisation. WE then crashes. > > I killed WE a few times and re-started it all with the same result. > > To get round the issue I unplugged my router and re-started the PC. > As WE could not see the update I started up OK. I then > switched scripting off and re-started the router. All is > working with scripting off. > > Any advice please? > > > > Regards, John > > John Farley > > Personal Contact Work contact Phone : > 01442 259243 01442 227731 VOIPe : 01442 895132 > Mobile: 07815 056076 07785 928755 > E-Mail: [email protected] [email protected] > > Help raise funds for The Dacorum Talking Newspaper, shop at > www.buy.at/dtnhemel > > > 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. > > 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.
