The bad header error could also be caused by firewalls or anti-virus applications. I know for a fact, for example, that Viper strips HTTP headers which will cause you to get the referrer error.

Aaron

On 5/5/2010 2:00 PM, Michael Massey wrote:
Hi.  Martha, that bad header was the first error I encountered when trying
to download the Window-eyes 7.2 upgrade.  Like I said, I followed Mike
Lawler's suggestions of deleting the temporary files under browser history
from within the internet options dialog in Internet Explorer eight.

I can't say for certain that this solved the problem, however.

I am now running Window-eyes 7.2 on my Dell XPS-410 desktop after having to
perform a second restart after multiple script errors.  The scripts are now
running correctly after the second restart so all appears to be well again.


Mike M.
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.


--
Aaron Smith
Product Support Specialist * Web Development
GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825
260-489-3671 * gwmicro.com

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.


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.

Reply via email to