Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Beta - Avast => Topic started by: RejZoR on September 23, 2014, 06:11:10 PM
-
I suggest you make a NG virtual machine creation a part of installer progress and not after installation, so users know the high CPU usage is the result of avast! installation and not a bug. I mean, if they see a high CPU usage and the installer says "Creating virtual machine installation" or something along those lines with note "CPU usage may remain high for a few minutes", they will be assured it's fine and all part of a normal installation process. But if CPU is getting hammered later on, they will think it's a problem.
You could also use a popup that would reassure users that high CPU usage is a normal thing for the duration of NG installation. I know it will be run at lower priority in RTM, but i think it would still be smart to let users know what's going on. So they don't panic unnecessarily.
-
With regards to NG will there be a right click option or will it all be automatic using deepscreen ?
-
I suggest you make a NG virtual machine creation a part of installer progress and not after installation, so users know the high CPU usage is the result of avast! installation and not a bug. I mean, if they see a high CPU usage and the installer says "Creating virtual machine installation" or something along those lines with note "CPU usage may remain high for a few minutes", they will be assured it's fine and all part of a normal installation process. But if CPU is getting hammered later on, they will think it's a problem.
You could also use a popup that would reassure users that high CPU usage is a normal thing for the duration of NG installation. I know it will be run at lower priority in RTM, but i think it would still be smart to let users know what's going on. So they don't panic unnecessarily.
Absolutely +1
-
+1
That in the other hand would make installation process longer (some users may also say that "avast! installation is the longest..." etc on different forums).
Avast! was supposedly working on replacing VirtualBox with something from in-house (meaning better performance). If and when it arrives, we'll see how long it takes to install.
-
Does it matter how long it takes to install? It's not like you're doing that every day or every week. Most users don't do it ever again... So, 30 seconds or 5 minutes, makes no real difference. If you have to install 500 machines, you need deployment system anyway, in which case it would take 5 minutes for all 500 machines.
-
Does it matter how long it takes to install? It's not like you're doing that every day or every week. Most users don't do it ever again... So, 30 seconds or 5 minutes, makes no real difference. If you have to install 500 machines, you need deployment system anyway, in which case it would take 5 minutes for all 500 machines.
Totally agree. Not making part of the install process makes everyone wonder why avast! is being such a system hog.
-
Does it matter how long it takes to install? It's not like you're doing that every day or every week. Most users don't do it ever again... So, 30 seconds or 5 minutes, makes no real difference. If you have to install 500 machines, you need deployment system anyway, in which case it would take 5 minutes for all 500 machines.
Totally agree. Not making part of the install process makes everyone wonder why avast! is being such a system hog.
Also, we have all had to install Service Packs and MS updates that have and could take over10 minutes or more so I don't think the "long install process" carries much validity.
People will install once (as mentioned) and that's it.
My one cent worth ;D