Larry I had that problem too when I was using it.  If your PC 
is rather slow (CPU wise and not much memory) that MIGHT have 
something to do with it.  I had it worse on an old slow PC 
(800mhz and 128mb), but not as bad on my main PC.  They were 
both XP SP2 and on the same LAN.  So, it might be a CPU thing 
since FF does suck the CPU resources.  But FAIK it could have 
something completely different.  I tried the tweaks and they 
didn't help.
-Clint

God Bless
Clint Hamilton, Owner
http://OrpheusComputing.com )
http://ComputersCustomBuilt.com

----- Original Message ----- 
From: "LarryB" <[EMAIL PROTECTED]>

Yes I am on broadband and I checked those settings as I vaguely 
remember
those instruction. Mine have been set that way. So I guess it 
is
something else. I really do not remember having this problem 
before it
has just started in the last couple of months. I have checked 
if I had
installed anything that might change this but nothing comes to 
mind.
Thanks anyway Peter.
LarryB
K & L
South Carolina


Peter Kaulback wrote:
> Are you on broadband Larry?
>
> There are some tweaks for FF on broadband, I think Clint 
> posted them
> once perhaps (I could be wrong).
>
> Anyways this is what I have, I'm on dialup so I can't verify 
> it :(
>
> 1.Type "about:config" into the address bar and hit return. 
> Scroll down
> and look for the following entries:
>
> network.http.pipelining network.http.proxy.pipelining
> network.http.pipelining.maxrequests
>
> Normally the browser will make one request to a web page at a 
> time. When
> you enable pipelining it will make several at once, which 
> really speeds
> up page loading.
>
> 2. Alter the entries as follows:
>
> Set "network.http.pipelining" to "true"
>
> Set "network.http.proxy.pipelining" to "true"
>
> Set "network.http.pipelining.maxrequests" to some number like 
> 30. This
> means it will make 30 requests at once.
>
> 3. Lastly right-click anywhere and select New-> Integer. Name 
> it
> "nglayout.initialpaint.delay" and set its value to "0". This 
> value is
> the amount of time the browser waits before it acts on 
> information it
> recieves.
>
> HTH Larry, let me know if it does.
>
> Peter Kaulback
>
> LarryB wrote:
>
>> I have noticed that when using FF and I launch to any site 
>> (URL)that
>> it does not connect the first time and shows me a message 
>> that it
>> times out. I try it the second time and it always connects. 
>> Is it just
>> a matter of extending the time if that is possible?
>> Peter might know the answer to this. I believe he uses FF.
============= PCWorks Mailing List =================
Don't see your post? Check our posting guidelines &
make sure you've followed proper posting procedures,
http://pcworkers.com/rules.htm
Contact list owner <[EMAIL PROTECTED]>
Unsubscribing and other changes: http://pcworkers.com
=====================================================

Reply via email to