Claire Brucker said:
The error message told me that there was no solutiion to the IE
problem but advised me to get SP3 which maybe could make it more
stable. I did. It didn't. So far Firefox is working much more
smootlhy, doesn't get stuck and so far a hasn't cut off.
From what I recall from the other thread, you never gave us the complete
text of this error message, and a number of us were concerned it might
have been generated by a malware infection. I'm not saying that I'm
certain you have malware, but the message was a suspicious one, and you
really should rule out the possibility you have malware!
Also from that thread, there were helpful suggestions that you either
ignored or simply didn't see. Firefox is a fine browser and allows you a
large selection of plugins which can be very useful. But it's not
perfect. You might want to reconsider solving your IE problem; otherwise
you might find other related problems may crop up.
In the event you didn't see my last post, here is the pertinent
information from it:
There is a proper protocol for installing SP3, which you didn't follow.
Granted, at the time, you didn't know this. But you know it now. If you
decide to do this the right way, post back and we can guide you in the
upgrade.
You should only upgrade to SP3 if you are certain there is no malware on
your system. From what I can tell, you never ruled this out.
It is better to upgrade from IE6 to IE7 *before* upgrading to SP3.
Sometimes what needs to be done to solve IE problems is to downgrade IE
from IE7 to IE6. But this cannot be done if you are running SP3!
Did you try running IE7 in no add-ons mode by any chance?
That last question you should address first. If you don't have any
malware, it's possible that the reason from your IE problem lies in one
of the add-ons.
If you want to do this the right way, you will need to uninstall SP3 and
then uninstall IE7 (which will leave you with IE6). I know it's a PITA,
but it's the only correct way to fix your problem, if you choose to do
so. I suppose you can just rely on Firefox and hope for the best, but in
the long run, I'm sure it's better to address and solve your actual
problem (I am concerned that it will eventually come back to bite you!).