This is how I got to finally surf the web.

This user has been with this version for a while now and running fine. Suddenly, every time she gets online and plays games, her cache maxes out and the entire program crashes. There is no way that a game site, pogo, can max out and entire cache file which is huge (somewhere in the neighborhood of 500 MB) And she's been at this site several times before with no issues.

Plus she allowed an AOL tech support to Remotely access her computer and they added all kinds of dial up and network adapters to her system.

She boots her system and shows 81% of her system resources free, and signs onto AOL and goes to 1 website and suddenly she's dropped to 35% of her resources free, and maxed out her cache.

Can anyone explain this? And why would you need DUN/RAS adapters to dial up (this was apparently installed by aol tech support)

Have you solved the problems. I am unable to use the AOL 8.0. I was getting the waol.exe error and AOL tech support wasn't able to help me. You may can help me.

you have any updates yet on the AOL thing?

I have spoken to over 200 AOL users over the past 5 weeks.
I work for a nationwide computer technical support company
doing technical support on a pay-per-minute basis.
*** "Typical AOL 8.0 problems" *** include:

Increased memory requirements for this version of the AOL client
force many users to unload non-vital startup components and
other boot-loaded programs that aren't mission critical to free
up as much RAM as possible before the new AOL client will
function reliably.

AN AOL Tech Support Manager explained:
You really should have at least 128MB of RAM, and around 70
percent of system resources should be available to run smoothly.

-------------------------------------------------------------------

I have also come across several AOL 7.0 clients that have RECENTLY
developed problems with Internet Explorer browsing capability.
There are also assorted CRASHES involving WAOL.EXE and various
Windows components.

On several Win98 and WinME systems, the AOL client will attempt
to connect up to three times. It appears at this point that the
client has successfully logged into AOL, but IE will not connect
to any web sites. Users report that the AOL package appears to work
(mail, normal aol pages function) but not IE or anything using
the TCP stack or Windows dial-up networking.

Removing the AOL adapter from the network control panel fixes
some of these systems.
Running 'Repair Interner Explorer' utility from System Information
fixes some of these systems.
Running INETWIZ has successfully repaired a small number
of these systems.

Worst case scenario: (as best I can tell, the customer was still down)

Removed all AOL software (Add/Remove Programs)
Removed Dial-up Networking component (Add/Remove programs)
Removed ALL components from Network control panel.
Removed and reinstalled all modem drivers.
Reinstalled Internet Explorer (5.5)
Reinstalled AOL 7.0 and let Network components reinstall as needed.

This problem is teched out to varying degrees by AOL technical support, at which point the AOL tech deems the modem drivers or Windows OS to be at fault, and tells the AOL customer to call us
to fix the problem. Several AOL customers report spending HOURS with AOL customer support techs before being abandoned.

Please post any information that surfaces regarding any sources to
current AOL problems and any verified FIXES for these problems.

(I'd almost have to refer to these as possible 7.0/8.0 release BUGS)

thanks for your time and help!

You are correct. There is a very good chance that AOL v8 will fix this issue. I believe that the problem you are having is related to a bad java dll file or alike (aol has problems like this). Don't concern yourself with that, just uninstall AOL 7 and get the upgrade. Make sure to uninstall v7 before running the install for 8. Yes, you have an option during the uninstall to save your settings. This will ensure that the critical program files have been deleted. If you don't have the upgrade, reinstalling v7 after completely uninstalling it should do the trick as well.

If you can get the full error message next time, I can better diagnose the issue. However, 80 percent of the time you get an error like this, a reinstall will fix it. Please post back if I am wrong for another solution.