Avast WEBforum

Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: firzen771 on March 08, 2011, 05:35:42 PM

Title: Sandbox Settings Error
Post by: firzen771 on March 08, 2011, 05:35:42 PM
so ive mentioned this overlap in the sandbox settings several times and never seem to get a response or acknowledgement that others see this problem. ive had this error in both the stable v6.0.1000 and in the pre-release version.

as u can see in the 2 images ive attached, the exact same settings option is repeated in 2 diff menus of the sandbox's settings
Title: Re: Sandbox Settings Error
Post by: Rednose on March 08, 2011, 06:13:19 PM
Yeah, you are right, it shouldn't be in the parameters menu ( I think ). I will email Petr about it.

Greetz, Red.



Title: Re: Sandbox Settings Error
Post by: firzen771 on March 08, 2011, 07:19:05 PM
Yeah, you are right, it shouldn't be in the parameters menu ( I think ). I will email Petr about it.

Greetz, Red.





i agree, it shuldnt be in the Parameters, and thanks
Title: Re: Sandbox Settings Error
Post by: DavidR on March 08, 2011, 07:49:11 PM
I don't have the full sandbox, but surely there is a requirement for this duplication as it is possible to sandbox other applications, email, FTP, P2P, etc.

If this were only in the Browsers section then these instances wouldn't be covered.

Title: Re: Sandbox Settings Error
Post by: igor on March 08, 2011, 07:59:48 PM
The duplicated option has already been removed internally.
Title: Re: Sandbox Settings Error
Post by: Lisandro on March 08, 2011, 08:11:57 PM
The duplicated option has already been removed internally.
Thanks Igor. Great response time.
Title: Re: Sandbox Settings Error
Post by: Rednose on March 08, 2011, 08:32:59 PM
So now it all depends on Ms. Vlcek ( Ondrej's wife ) how long we will have to wait for the next update ;D

Greetz, Red.
Title: Re: Sandbox Settings Error
Post by: firzen771 on March 08, 2011, 10:25:55 PM
The duplicated option has already been removed internally.
Thanks Igor. Great response time.

i suppose... except for the fact that ive been mentioning this in various threads since v6.0.1000 was first released so its actually been a while for it to even be acknowledged...

o well, long as its now fixed