| AOL runs extremely slow but other processes run fine Hello all,
My mother will not ditch AOL, so I have to deal with her asking me over and over again why it runs so slow and simply saying "It's AOL" doesn't solve any problems for me.
I finally got around to formatting her computer because nothing else would speed AOL up, however, the format did nothing to solve the lag times when loading pages and even loading the welcome screen on AOL.
The system specs are: Intel Pentium D 2.80ghz, 2.00GB RAM, Nvidia 6200
The version of AOL that is being used is the latest 9.1.
Are there any solutions to "speeding" AOL up and not having hang times when loading web pages that do not occur otherwise when using IE or firefox? |
|
 BK3
join:2001-04-10
Geneva, IL | Dial up or broadband access? If dialup, the only thing you may be able to do is find a better access phone number. If broadband, have you checked your MTU and RWIN?
--
Atomic batteries to power - Turbines to speed - ready to move out. |
|
 koma3504AdvocatePremium
join:2004-06-22
North Richland Hills, TX | reply to bigyeah
Can She get Dsl/Cable at her address if so Do that.
you can set the Aol browser to use local lan instead of dial up and it will be super speedy even if it is lagging. |
|
| The connection is Cable, Optimum Online 15mbps |
|
koma3504AdvocatePremium
join:2004-06-22
North Richland Hills, TX | Ok perhaps it got a update to the aol software that caused it to run slow. |
|
| reply to bigyeah
Same problem here. Vista 32bit, Cable broadband, brand new well equiped Sony all-in-one (decrapified), all updates installed. My customer is not ready to be weaned from AOL so we're running AOL 9.1 as browser and email. There are no obvious background service hogs, but AOL now slows to a crawl or stops altogether. IE works great.
The only clue is it seems to first occur when logged into AOL as User1 then closing the browser and switching to User2 and logging in to AOL. BUT, subsequent reboot, clean temps, restart AOL doesn't improve the slowed down and/or stopped browser.
Has anyone else pinned down a recent update to IE or AOL that might have caused this (Dec 2008)? Any other clues? I'll report back after my next go at this. |
|
