Wondered whether this was a known problem. I disabled skins for the Simple User interface, and had problems. When I hovered over " Tools", “Settings”, or “Help”, the box would turn blue but nothing else would happen. Also, hitting ‘S’ for Settings did nothing. The workaround was to go back to the skinned version, so it is not that big a deal.
OS: Windows 95 (aint many of us old timers left)
avast! version: 4.8 Home Edition
Build: Feb2009 (4.8.1335)
VPS file version: 090509-0
I’m surprised the skinless version didn’t work, that if anything I would have though been the most likely to work.
What exactly happens, memory scan anf no display of the skinless SUI, etc. ?
What errors are displayed, if any ?
What happens if you use the C:\Program Files\Alwil Software\Avast4\ashSimp2.exe directly ?
What happens is that the user interface displays. This is the box with “Area to scan”, “Type of scan”, “Information”, “Scan”, plus “Tools”, “Settings”, “Help” near the top. The check boxes work, eg “Local Hard Disks”, and “Start scan” starts the scan.
The parts that don’t work are the “Tools”, “Settings”, and “Help”. I assume these are drop-down menus, but nothing drops down. When I hover over them they turn blue, but nothing else. No errors are displayed. Also, hitting the ‘S’ key for “Settings” does nothing.
C:\Program Files\Alwil Software\Avast4\ashSimp2.exe is exactly the same.
Do drop down menus work in Windows Explorer and other applications ?
If so they should work in the menus of the skinless interface as that uses the default windows functionality. Try a repair of avast. Add Remove programs, select ‘avast! Anti-Virus,’ click the Change/Remove button and scroll down to Repair, click next and follow.
This is the first time I have heard this in over five years that I have been using the forums, so you are unique ;D (sorry I couldn’t help myself).
So if the repair doesn’t have any effect, it looks like the skinned option for you.
You are right, the menu doesn’t show on Windows 95 (only on Windows 98 or higher).
Interesting that nobody noticed this before - it must have been there from the very beginning.
The problem will be fixed in the next program update.