About the disappearing icons ***BUG***

I downloaded Avast 4.8 tonight for the first time and installed it on my Windows 98SE system. I wanted it primarily as an on-demand scanner for checking downloaded files. After running my first scan, I discovered that most of my small file icons as well as all the icons in my Start menu had disappeared. A reboot brings them back, but it’s a PITA having to reboot every time I want to use the scanner.

So I came here, hoping that someone had found a solution or workaround for this BUG. I searched the forum and instead of a solution, or even an admission that this was a problem, all I found were people passing the buck by blaming Windows 98’s poor memory management.

I registered here specifically to debunk this idea.

Here is a shot of my system running just the programs Total Commander and FreeRAM XP Pro;

http://i41.tinypic.com/fa4qoy.jpg

Resources - System:82, User:82, GDI:85
RAM: 358MB

Here is my system after running Avast’s simple user interface with no skins;

http://i40.tinypic.com/23ur60o.jpg

Resources - System:78, User:78, GDI:83
RAM: 351MB

And here’s what happens after running a scan;

http://i41.tinypic.com/dypshy.jpg

Resources - System:82, User:82, GDI:84
RAM: 358MB

You’ll note that my system has plenty of resources and RAM available, both while Avast is running and after the scan.

Also note that only some icons disappear. It seems that only those icons which are selected automatically by the system disappear. The jpeg icons persist probably because I manually set the icon for them rather than letting Windows select it.

Finally, I’m no stranger to Windows 98 running out of resources. When that happens, a lot more than icons disappear. Window contents, text, buttons and more disappear, then programs start crashing. One element of the OS doesn’t just permanently (until a reboot) disappear. That is a clear sign of a rogue program doing something it shouldn’t.

So, is this enough to convince everyone that Avast 4.8 was released with a major bug, or will they continue to blame Windows 98?

I do not try to run any OS as old as Windows 98. I do have some very old laptops that run Windows Me … the same problem occurs there too.

There is no such problem in currently supported Windows operating systems.

I made the move to XP 6 years ago primarily due to the increasing problems of “Windows resource management” in the older operating systems and was amazed how these all ceased to exist on the same system running Windows XP.

I have next to this system now the system that was just about crippled running Windows Me. It is (6 years later) still running just fine with Windows XP and without the problem you are seeing the older OS. Same system - just updated the OS to XP.

To be honest there really are very few users of avast still using these outdated and unsupported operating systems. avast have already announced that avast 5 - expected to be available later this year - will not support the Win9x operating systems (Win 95, Win 98, Win98 SE, Win Me). While avast will continue to support avast 4.8 for some time for these operating systems I think you should not expect any significant further effort by avast to address issues such as the one you raise.

avast like other companies cannot afford to dwell in the past - especially in the current economic climate - the avast team have to eat and support their families.

Hi,

An early post of mine gave a workaround which, for me, was quicker than icon recovery via rebooting.

In every other respect I find both Avast Home and W98SE to my liking and I no longer scan on demand.

My regards

PS I hope you noted the W98SE “12080 Local Host” setting(s) if primarily is not the same as exclusively.

PPS If you download say, to one standard “docking” folder you could right click and try the Context Menu.

Addendum: CharleyO, your link below is correct. Thanks

Mike,

may I ask that you seek out your workaround and post a link that may help Rekrul?

With thanks,

Alan


I think this is the one, alan.

http://forum.avast.com/index.php?topic=35348.msg302279#msg302279

Mike, please correct me if I am wrong.