Jim,
The toolkit can't do much in this case because the error reporting is
happening inside the script that is using the error reporting feature.
The toolkit simply provides a means of reporting errors that each script
that use, but it doesn't do any error tracking itself (except for error
that might occur in the toolkit script).
Scripts should be written in a way where they fail gracefully if a
required component isn't available. Try running one script at a time
during shutdown to see which ones are causing errors.
Aaron
jim grimsby Jr. wrote:
Ignoring errors, while Windows is in a shutdown
state.
I have a suggestion for the GW toolkit script for Window-Eyes.
I propose that the GW toolkit ignore errors, If Windows is in a shutting
down state.
I have noticed that a few scripts generate errors occasionally when Windows
is shutting down this seems to me, because components that the script
requires is no longer available. This causes the script to then generate an
error. I propose that the GW toolkit simply ignore these errors. When
Windows is shutting down this prevents the generation of erroneous error
messages. I should also note that I am not certain which scripts are
generating errors except for Window manager
I hope this feedback is useful
--
To insure that you receive proper support, please include all past
correspondence (where applicable), and any relevant information
pertinent to your situation when submitting a problem report to the GW
Micro Technical Support Team.
Aaron Smith
GW Micro
Phone: 260/489-3671
Fax: 260/489-2608
WWW: http://www.gwmicro.com
FTP: ftp://ftp.gwmicro.com
Technical Support & Web Development
