"Joosy" <Spam@free> wrote in message news:46e1d96a$1@dnews.tpgi.com.au...
>
> "Beauregard T. Shagnasty" <a.nony.mous@example.invalid> wrote in message
> news:_0kEi.505516$p47.390661@bgtnsc04-news.ops.worldnet.att.net...
>> Joosy wrote:
>>
>>> "Joosy" <Spam@free> wrote:
>>>> "Beauregard T. Shagnasty" wrote:
>>>>> Joosy wrote:
>>>>>
>>>>>> Firefox is s-l-o-w and virtually useless for browsing.
>>>>>
>>>>> Only on your computer.
>>>>
>>>> LOL. Would the phrase "worse than normal" produce a more useful
>>>> response from somebody.
>>>
>>> More information:
>>>
>>> Just found and installed "No Script". After turning scripts off,
>>> offers the option to allow 127.0.0.1:1025. It is still ridiculously
>>> slow and produces the same message.
>>
>> There is something else wrong with your computer. Firefox is not a
>> s-l-o-w browser.
>>
>> Not much of what you said in your original post made sense. Maybe it is
>> the QuickJava extension, which I've never used. I prefer the PrefBar
>> extension for the toggling of Java, JavaScript and other stuff.
>> http://prefbar.mozdev.org/
>>
>> Uninstall QuickJava.
>>
>> Re your 127.0.0.1:1025 - you may be infected with something.
>> http://www.linklogger.com/TCP1025.htm
>>
>> --
>> -bts
>> -Motorcycles defy gravity; cars just suck
>
> I doubt it was QuickJava, I've had it for six months. It gives no problems
> on two accounts. On the other hand, I have serious doubts about
> TrendProtect. It is now disabled but cannot be uninstalled through Addons.
>
> When all else fails, try persistence.
> - cleared all caches - no go
> - uninstalling Firefox; clean registry and reinstall - no go
> - deactivated every addon (only 4) - no go
> - system restore to a day before the problem started - no go
> - open Firefox; click Tools; click Error Console; click Clear - so far,
> no more unresponsive script messages.
>
> I suspect the last one may be worth remembering
>
>
> --
Change of mind yet again. I HAD CookieSafe off when I wrote the last
message. Switched it back on and the problem came back. Cleared it. Browed
well again. Went to manually check Cookie Exceptions in the Privacy tab and
the script problem occurred. It looks like CookieSafe caused a problem with
FF. Now to fully uninstall CookieSafe then FF then reinstall.


--
Stevie

"Build a man a fire and he will be warm for one night. Set a man on fire,
and he will be warm for the rest of his life."

~ Sun-Tzu on Fire