Hi Michael: Usually the cause of multiple script errors like that is that they are trying to access shared objects before they are loaded. There is a script called GWToolkit which is packaged with Window-eyes and is loaded automatically. Itssole purpose its to create objects which other scripts can use. There is another similar script called Homer Shared Objects was written by Jamal Masrui and must be loaded which scripts that he has written. Sometimes a script such as MakePointerFollowCursor will try to access one or more of the objects, provided by GWToolkit or HomerSharedObjects, before the above-mentioned scripts are fully load, causing the errors that you are getting. The only solution to your problem is to make sure you have the latest updates of the scripts and, if errors still persist, contact the authors of the offending scripts and let them know about the errors. Kevin Huber
On 10/23/09, Michael Massey <[email protected]> wrote: > Hi, all! Earlier this morning I encountered multiple script errors after > booting up my Dell XPS-410 desktop. I am running Windows Vista Home Premium > Edition with all updates and the latest service packs installed. I am > running Window-eyes 7.11 upgrade from 7.1 with Eloquence. > > Multiple script errors were generated including in no particular order GW > Tool Kit, Script Active, Loaded Script, Help Context, Word Scramble and Make > Pointer Follow Cursor. That's just a few of them. > > I just kept pressing the restart script button and each script appeared to > start. I then went into the script manager dialog. I found that the > current Cap Beeper script was running with errors. I closed everything > down, exited Window-eyes and restarted it. Things appear to be ok, at least > for now. > > What would cause so many scripts to generate errors? Maybe my solution > wasn't the best one, however, I figured if the restart script option is > available, then I use it. What an experience. I hope somebody can provide > answers. Thanks for reading. > > Mike M > > P.S. I am also running Nod 32 version 4.0 with the Nod 32 3.5 announcement > script running. I don't recall that script generating an error. . > > > __________ Information from ESET NOD32 Antivirus, version of virus signature > database 4536 (20091023) __________ > > 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.
