Your avast settings won’t be remembered when doing a clean reinstall. Try savint
It wouldn’t hurt to try that option copy the registration key, Tab, Ctrl=V and enter before doing the clean reinstall if it doesn’t work. Though I suspect you may have other graphical artefacts in the future. So this avast ini file hack might be worth a try for some similar graphical artefacts in avast 4.8 with a certain firewall.
Menu, Display Remnants, Log Viewer Remnants, Graphics glitches, etc.
Edit the C:\Documents and Settings\All Users\Application Data\Alwil Software\Avast5\avast5.ini (this is the XP location may differ for win2k) using Notepad [Common] section, add the following line to the section SunbeltKPFHack=2, save the file, you will be prompted by the avast! Self-defence module if this is OK answer Yes. Whilst this is primarily for Sunbelt or Kerio Personal Firewalls it may well work even if you don’t use either of these firewalls. You may need to reboot to have the changes in the avast4.ini file to come into effect.
Blind registering worked. It ended up being ctlV tab ent.
I tried the SunbeltKPFHack=2 with no changes after several reboot sequences. Avast! didn’t notify me about someone trying to change the file, I just got a system error something about the file possibly being locked. So I used NTFS4DOS to copy a changed version into the directory. It worked well besides not fixing my graphics issue.
Now I suppose that it’s on to complete un-re-install. I think I’ll give it one more reboot since I haven’t after registering.
If you don’t use ‘notepad’ the other editors are only allowed to open it for read permission, so windows would tell you it is write protected/locked, etc. etc. So did you use windows notepad ?
So if you have been able to enter the key, and effectively got round that particular hiccup, what else is wrong ?
If nothing is wrong, leave it and see if you get any graphical artefacts, which hopefully if you manage to set that hack in the avast5.ini file would resolve that.
I didn’t know that. I used Notepad2 to edit it. Good to know for next time.
So if you have been able to enter the key, and effectively got round that particular hiccup, what else is wrong ?
I would say that registering was my most important problem. The graphic artifacts and lack of accepting mouse input in those particular popups is still manifesting. It may be that I will have to just live with these issues. Avast! is usable and working which is more than mcafee was doing and it catches more malware and has more options.
If nothing is wrong, leave it and see if you get any graphical artefacts, which hopefully if you manage to set that hack in the avast5.ini file would resolve that.
The SunbeltKPFHack=2 hack is inplace and the popups are still not rendered correctly and cannot accept mouse input but, c'est la vie.
I wouldn’t mind unreinstalling, it will give me an opportunity to go through the settings again and make certain I am familiar with them.
Given that you also have another topic on the go with a screen saver problem (I don’t know if the is the same in win2k), it would probably be best to do a clean reinstall and see if that has any effect on that too.
I see you have more than 20 posts so you could go to PROFILE then Modify Profile then update your Signature: with information like my signature as this helps the helpers offer pertinent advice like DavidR avast! a Technical advisor.
-uninstalled avast and any other programs that I’m not using and rebooted
-rebooted
-booted into safemode and used the avast5 removal tool
-rebooted
-rebooted and installed avast5.0.545
the same graphical errors persist still. avast works great though, I just can’t see certain options. I think I’ll be able to live with it for now.
Thanks for the help guys. I’ll let you know if I ever figure it out. Maybe it would fix it if I reinstall w2k and install avast first thing. (That won’t be happening soon)
You’re welcome, sorry it wasn’t successful. As you say reinstalling w2k isn’t a task to undertake lightly as you would have all the SPs and rollup update 1 to reinstall also without any certainty that it would resolve the problem.
