Avast WEBforum

Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Vlk on March 06, 2005, 06:57:45 PM

Title: ** Introducing ** - pre-release version of upcoming avast update
Post by: Vlk on March 06, 2005, 06:57:45 PM
Edit: the update has now been oficially released (as 4.6.623). Please disregard the message below; instead, simply update to the latest version by invoking the Program Update command from within the avast GUI.[/b]


Hi guys, here comes a pre-release version (4.6.618) of the upoming avast Home/Pro 4.6 update - hopefully solving most of the issues found in the official 4.6 release (4.6.603).

How to install it: simply download and run the following program: http://files.avast.com/files/beta/aswbeta.exe . That's about all it takes.


The fixes in this release include
- ZoneAlarm-related problems
- WebShield now terminating abruptly ended connections
- McAfee firewall related issues
and other.

Please feel free to post your respective comments about this release either here or by starting a new thread in this forum category (the "Beta" subcategory is still locked and will be deleted shortly).

We expect the update to be officially released in less than a week.


Thanks :)
Vlk
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: SirL on March 06, 2005, 09:31:54 PM
I have installed the new beta, and so far no problem.

/SirL
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: milowen on March 06, 2005, 10:40:39 PM
hi there

I'm a new user of avast (since today !) I saw the problem with zone alarm pro (web pages didn't load properly with 4.6.603)

now with 4.6.612, the load of web pages is ok

I still have some problems with websites I have to log to but it may be because I'm an avast newbee ;)
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: bob3160 on March 06, 2005, 10:41:25 PM
Vlk
Where the ashServ shutdown and the on demand zip file scanning problems also addressed?
http://forum.avast.com/index.php?topic=11824.msg99829#msg99829
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: salsadoc44 on March 07, 2005, 03:17:47 AM
i am still having problems logging into Yahoo Mail even w/ the new beta update.  I was using the localhost 12080 work around previously w/ ZA Pro 5.5.062.011.  Yahoo Mail is the only site that doesn't accept my cookes with both Firefox 1.0.1 and IE even w/ medium settings on cookie control and ad blocking on ZA.  i can log into Yahoo Mail just fine if i turn off Web Shield.  I have WinXP SP2 w/ all the updates.  i do not have proxies configured w/ either Firefox or IE.  ZA is allowing all the avast modules.

any ideas to what seems to be the problem now? thanks.

i like the idea of Web Shield, but it's not worth it to me if these problems continue.
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: housi on March 07, 2005, 09:27:07 AM
No problems up to now!
Regards
housi
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: kantjer on March 07, 2005, 02:02:44 PM
With pre-release version (4.6.612) installed the Web shield does not appear to be working on my system.
Although the Blue bal in the system tray area is spinning during browsing the last scan field and the scan counting field in the Web Shield area remain empty.

I also noticed that my firewall (Outpost 2.5 Pro) is now reporting that a number of applications previously accessing the net trough Web Shield  no are asking direct http access.

After experiencing this I did a clean install of 4.6.603 and everything was back to normal, installing 612 and the above situation was back again.

Anybody else seeing this behaviour ?

(I’m back to 603 until there is a solution)
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: jleezer on March 07, 2005, 03:43:14 PM
With 4.6.612 I still get the 0000006E errors in the Warning.log:

7-3-2005   10:36:43   1110188203   SYSTEM   360   AAVM - scanning warning: x_AavmCheckFileDirectEx: http://www.radio10gold.nl/?page=http%3A//www.radio10gold.nl/viewpage.php%3Fpages_id%3D11 (C:\WINDOWS\TEMP\PxB32.tmp) returning error, 0000006E. 
7-3-2005   10:36:43   1110188203   SYSTEM   360   AAVM - scanning warning: x_AavmCheckFileDirectEx: http://www.radio10gold.nl/topframe.php (C:\WINDOWS\TEMP\PxB33.tmp) returning error, 0000006E. 
7-3-2005   10:36:43   1110188203   SYSTEM   360   AAVM - scanning warning: x_AavmCheckFileDirectEx: http://www.radio10gold.nl/viewpage.php?pages_id=11 (C:\WINDOWS\TEMP\PxB35.tmp) returning error, 0000006E. 
7-3-2005   10:36:44   1110188204   SYSTEM   360   AAVM - scanning warning: x_AavmCheckFileDirectEx: http://www2.noordzeefm.nl/poll.php (C:\WINDOWS\TEMP\PxB40.tmp) returning error, 0000006E. 
7-3-2005   10:36:44   1110188204   SYSTEM   360   AAVM - scanning warning: x_AavmCheckFileDirectEx: http://www.radio10gold.nl/scripts/dituurxml.php (C:\WINDOWS\TEMP\PxB43.tmp) returning error, 0000006E. 
7-3-2005   10:37:56   1110188276   SYSTEM   360   AAVM - scanning warning: x_AavmCheckFileDirectEx: http://forum.avast.com/ (C:\WINDOWS\TEMP\PxB52.tmp) returning error, 0000006E. 
7-3-2005   10:38:01   1110188281   SYSTEM   360   AAVM - scanning warning: x_AavmCheckFileDirectEx: http://forum.avast.com/index.php?board=2.0 (C:\WINDOWS\TEMP\PxB54.tmp) returning error, 0000006E. 
7-3-2005   10:38:09   1110188289   SYSTEM   360   AAVM - scanning warning: x_AavmCheckFileDirectEx: http://forum.avast.com/index.php?topic=11838.0 (C:\WINDOWS\TEMP\PxB55.tmp) returning error, 0000006E. 
7-3-2005   10:43:26   1110188606   SYSTEM   360   AAVM - scanning warning: x_AavmCheckFileDirectEx: http://forum.avast.com/index.php?topic=11839.0 (C:\WINDOWS\TEMP\PxB56.tmp) returning error, 0000006E. 
7-3-2005   10:43:53   1110188633   SYSTEM   360   AAVM - scanning warning: x_AavmCheckFileDirectEx: http://forum.avast.com/index.php?topic=11656.15 (C:\WINDOWS\TEMP\PxB57.tmp) returning error, 0000006E. 
7-3-2005   10:44:19   1110188659   SYSTEM   360   AAVM - scanning warning: x_AavmCheckFileDirectEx: http://forum.avast.com/index.php?topic=11837.0 (C:\WINDOWS\TEMP\PxB5A.tmp) returning error, 0000006E. 

I had already reported this for 4.6.603:
http://forum.avast.com/index.php?topic=11426.0
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: Chuck58 on March 07, 2005, 04:20:42 PM
Downloaded the latest last night and no problems here. I had no problems with previous version either, but I use Look n Stop firewall, v2.05p2.
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: lukor on March 07, 2005, 06:18:06 PM
With pre-release version (4.6.612) installed the Web shield does not appear to be working on my system.

What is your browser? Do you use any proxy server in your browser? Thanks. Lukas.
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: EddieMal on March 07, 2005, 06:55:52 PM
 With version (4.6.612) installed  Web shield appears to be working as expected.
Problem with Freedom Firewall Ver 3.2.2002.0307 has now been resolved.
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: kantjer on March 07, 2005, 06:58:38 PM
My default browser is opera8b2 but also tried IE.

I'm also using Ad Muncher with I thinks also acts as a kind of proxy
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: lukor on March 07, 2005, 07:02:06 PM
Hmm, what are your proxy settings in IE (for example). What port does this Ad Muncher use? Due to increasing number of conflicts with all kinds of proxy software, avast's webshield will now support only verified apps. In your situation this might mean you'll have to configure avast to scan the communication between ad muncher and the browser -- to help you further I'll have to know the proxy configuration you are using.
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: kantjer on March 07, 2005, 07:13:33 PM
There is no Proxy configured in IE (or Opera) just configured for direct access.

ad Muncher is using ports in the 1101-1115 range (that is what is configured now in Outpost)

Edit. I disabled ad Muncher and Web Shield is working again. No I need to find out how to be able to use  my favorite ad blocker in combination with Avast
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: Lisandro on March 07, 2005, 08:27:40 PM
Due to increasing number of conflicts with all kinds of proxy software, avast's webshield will now support only verified apps.

What do you mean, the user must 'verify' (allow) the application into webshild properties?
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: lukor on March 07, 2005, 08:45:13 PM
Due to increasing number of conflicts with all kinds of proxy software, avast's webshield will now support only verified apps.

What do you mean, the user must 'verify' (allow) the application into webshild properties?

Technical, until this beta release, all apps were filtered (scanned) except those which were known to cause problems and these apps were excluded from the scanning. It seemed to us, that this approach would be the best. Anyway, as it turns out, there are plenty of apps using HTTP port, and these are often hard to configure with webshield. It may require some configuration tweaking and if this conflicting app is your firewall or your proxy through which you access the internet -- you might end up with the internet cut off and angry  :-[ . So we've decided that we might try the opposite approach. That is, only apps which are know to us not to cause problems with webshield (or known to the user and configured in the avast4.ini) would be filtered and scanned - namely the browsers are known to work correctly.

This behavior can be still switched to the previous -- scan all -- setting, but this must be the act of a knowledgable user.
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: alanrf on March 07, 2005, 08:49:20 PM
Is there any news if/when the Webshield will use the registry override for placement of its disk writes of http traffic?
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: Lisandro on March 07, 2005, 08:54:05 PM
I'm using the beta (4.6.614) but I see no difference in mine avast4.ini file (section WebScanner).
It seems that I must 'exclude' the applications and not 'validate' them  ::)
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: lukor on March 07, 2005, 09:02:31 PM
There is no Proxy configured in IE (or Opera) just configured for direct access.

ad Muncher is using ports in the 1101-1115 range (that is what is configured now in Outpost)

Edit. I disabled ad Muncher and Web Shield is working again. No I need to find out how to be able to use  my favorite ad blocker in combination with Avast

Kantjer, indeed cooperation with avast and Ad-Muncher is a little bit more complicated, as ad-muncher does not use the traditional proxy-in-the-browser approach, it intercept the connection automatically as they leave your browser. I have several work arounds for you.

1) simply allowing WebShield to filter admunch.exe will do the trick. You may edit the avast4.ini file and in the [WebScanner] section add or edit the key OptinProces to include the admunch.exe process name.
E.g.

[WebScanner]
OptinProcess=admunch.exe

But I must warn you, I have seen pages that don't load correctly with this setup. Not to mention these don't not load correctly with ad-munch and without WebShield - but with WebShield things are behaving a little bit differently. ( try http://www.zive.cz/default.asp)

2) you may follow the ad-munch help instruction and enable ad-munch filtering for the ashwebsv.exe process. More info in the ad-munch help files. But basically, first step is to allow the connection to reach webshield - they are stopped (redirected) by ad-muncher by default. This can be done by excluding your browsers from ad-muncher (add -iexplore:* and -opera:* in the options/filter target ad-munch configuration page.

This will enable webshield, but ad-muncher will be disabled. You'll want to enable ad-munch for the ashwebsv.exe (WebShield) process. This can be done by adding the +ashwebsv:* string into the ad-munch config page, but firstly you'll have to download wsock32.dll from them (as said before, more info in their help files).

To sum up, here we have to colliding apps, WebShield and Ad-Muncher. I'll definitely try to identify the problem and when all problems will be sorted out, the solution 1) would be the easiest choice, when there are really no problems with this ad blocker, avast may adopt the process name and filter it's communication without any user intervention. In the mean time, you can configure ad-munch as described in the 2), or use the 1) option and see if any troubles will come up.

Lukas
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: Vlk on March 07, 2005, 09:08:55 PM
Quote
Is there any news if/when the Webshield will use the registry override for placement of its disk writes of http traffic?

The latest version does exactly that.
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: alanrf on March 07, 2005, 10:10:09 PM
Quote
Is there any news if/when the Webshield will use the registry override for placement of its disk writes of http traffic?

The latest version does exactly that.

Vlk, thanks for your response.

It was the first thing I checked out when I installed the pre-release yesterday.  I just verified again before posting today that the Webshield tmp files are still being written directly to the Windows defined temp space.  All others that I checked, NNTP and on-demand tmp files continue to use the registry override.

The install of the pre-release version said it completed successfully.  Are there any versions numbers I should confirm?

Thanks. 

Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: Vlk on March 07, 2005, 10:15:14 PM
Version 4.6.614 should write the temp files to the avast folder (this was changed since 4.6.612 released yesterday).
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: housi on March 07, 2005, 10:44:19 PM
Quote
Kantjer, indeed cooperation with avast and Ad-Muncher is a little bit more complicated, as ad-muncher does not use the traditional proxy-in-the-browser approach, it intercept the connection automatically as they leave your browser. I have several work arounds for you.
Hi Lukor
I don't understand the problem. Since months I'm running admunch.exe together with Avast, and I never had problems with.
Sincerely
housi
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: lukor on March 07, 2005, 10:52:27 PM
The problem is that certain pages are not loaded properly with WebShield and admunch.exe. At least on my test PC. Unless you were using a beta version, Web Shield is not out for so many months  :P

Anyway, if you don't observe any problems (or have not observed) you may add the admunch.exe process to the avast4.ini as described in my post. Sorry for the troubles, this is new and in the latest beta refresh -- I tried to explain why we have done that, other users (those running less compatible products that ad-much is) will understand.

Cheers
Lukas.
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: alanrf on March 07, 2005, 11:07:41 PM
Vlk,

Webshield up and working with the registry override. 

Much appreciated.

Alan
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: rdsu on March 07, 2005, 11:55:37 PM
Hi,

I've been using the Ad Muncher with the Web Shield without any problem and now I can't use the Web Shield when Ad Muncher is enable...  >:(

I've read all the post and don't understand this!!!

I use the HTTP scanner of NOD32 with Ad Muncher, so you have to figure out the best solution for this...

Hope you can find it...

Regards
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: lukor on March 08, 2005, 02:58:11 AM
I've been using the Ad Muncher with the Web Shield without any problem and now I can't use the Web Shield when Ad Muncher is enable...  >:(

I've read all the post and don't understand this!!!

I use the HTTP scanner of NOD32 with Ad Muncher, so you have to figure out the best solution for this...

Hmm, you can't use it?  ??? What does this mean Vampiric ???  >:(

Did you mean, that you are trying to report to us that Ad-Munch is working correctly with avast's WebShield and that you have added the admunch.exe to the avast4.ini file and that that caused no problems and seems to work correctly and that you are suggesting avast should include this process name into the standard installation and should scan the connections made by this favorite tool of yours by default?

Did you mean this?

I don't use NOD32 scanner so I don't really understand why would I need to figure that out.
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: Bernie on March 08, 2005, 11:24:44 AM
Just an idea. Can Kantjers problem be caused because he uses Ad Muncher AND Outpost (which itself already has an Ad filter included)? So that it is basically a problem between this two programs which are partly doing the same.

Addition: I am using Outpost 2.5 and avast! 4.6.614 Both is running fine together.
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: kantjer on March 08, 2005, 11:33:48 AM
Just an idea. Can Kantjers problem be caused because he uses Ad Muncher AND Outpost (which itself already has an Ad filter included)? So that it is basically a problem between this two programs which are partly doing the same.

Hi Bernie,

I had the ad filter in Outpost disabled because i prefer Ad Muncher with its frequent updates of signatures.
I now have Ad Muncher disabled and the ad filter in outpost enabled this works. I need to start experimenting with lukor's tips.

Thanks for thinking with me.
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: rdsu on March 08, 2005, 11:37:01 AM
Hi lukor,

If I don't change nothing, the Web Shield doesn't work if I have the Ad Muncher enable...
I haven't put the admuncher.exe in the avast4.ini, I only put OptIn=0 and now the Ad Muncher works with Web Shield like before...

NOD32 have two different settings for the HTTP Scanner:
Higher efficiency - if set, IMON will be working in active mode in case of the particular application. ex: browsers...
Higher compatibility - if set, IMON will work in passive mode in case of the particular application. ex: download managers, players audio/video...
(http://img190.exs.cx/img190/3987/avastnod32httpscanner7ht.png)

With this, we can control the settings with our needs...

I don't want that you copy this, just take a look and take your conclusions to find the best way to resolve that.

And as I can see, you will put another setting to config only by edit the avast4.ini file... Very bad, in my opinion...

Regards
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: kantjer on March 08, 2005, 12:34:15 PM

1) simply allowing WebShield to filter admunch.exe will do the trick. You may edit the avast4.ini file and in the [WebScanner] section add or edit the key OptinProces to include the admunch.exe process name.
E.g.

[WebScanner]
OptinProcess=admunch.exe


Lukor,

I added OptinProcess=admunch.exe as advised, everything seems to work OK. I know there are/were some problems with sites not loading OK. I'm running the ad Muncher 4.7 beta and this seems to have solved that.

I will keep on testing, if I run into any problems I will report them back.
Thanks
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: lukor on March 08, 2005, 05:21:55 PM
Thanks for your report Kantjer. I'm still testing Ad Munch, and currently the easiest solution (if I omit your beta 4.7 suggestion) is to setup proxy in Internet Explorer / Firefox to WebShield - server: localhost, port: 12080. With this setup Ad-Munch works correctly with the browser and WebShield and I can not observe any problems with page loading. And this way no avast4.ini changes are needed.

Cheers Lukas.
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: housi on March 08, 2005, 06:31:43 PM
@kantjer
Quote
OK. I'm running the ad Muncher 4.7 beta
I'm on 4.6. How did you become this beta-release 4.7?
Sicerely
housi
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: bob3160 on March 09, 2005, 12:28:45 AM
housi
You can get it from HEREl (http://www.softpedia.com/progDownload/Ad-Muncher--Build--Beta-Download-5087.html).
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: housi on March 09, 2005, 12:50:17 AM
Bob
Thanks a lot! Downloaded, works.
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: aarangio on March 09, 2005, 01:08:24 AM
Hi ya,

downloaded the 4.6.614 version....works great... alot smoother than the version before but....sorry.... I do a ccleaner scan and clean then open up FireFox.....  :-[ .....there is no google Home page showing ...i try other sites from bookmarks and nothing shows, so i shut down Avast open FF and then open avast again and it works perfectly.... can someone help me fix this problem as i use ccleaner alot....

Internet 512 ADSL.....XP Professional.... PC Dell Optilex G260n....512 Ram....pentium 4....

thanks in advance,

Adrian  :)
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: jleezer on March 09, 2005, 11:20:45 AM
aarangio, regarding your problem with ccleaner:

I  have the same problem.  I only need to terminate and start again the Webshield to solve it.
It could be related to the cleanup by ccleaner of the c:\Windows\Temp\_avast4_ directory.
http://forum.avast.com/index.php?topic=11892.0 refers to the same issue.

Regards,
Johan
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: Baba on March 09, 2005, 12:51:16 PM
After the download of beta 4.6.614 and activated Web Shield still I was aving problem with ZA Pro and the Ad-Blocking was not working properly as before.

Then I set proxi on localhost 12080 in Internet settings and checked Ignore Server Proxi for Local Address.

Then working O.K. eccept direct login in Yahoo Mail.

Opened the setting in Web Shield and in Basic screen set port 12080 instead of 80 and there too Ignore Server for Local Address is checked.

In this way everything seems working properly.

Have I did the right settings?
I don't know much regarding Proxi settings.

Any suggestion? Or I must leave everything in this way?

Best regards
                                                Baba

Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: Baba on March 09, 2005, 01:31:51 PM
Can't use Windows Update.... :-\
Not displayng the result of needed update beaucose of some error.
May be related to my settings?

Bye
                          Baba
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: aarangio on March 09, 2005, 05:34:50 PM
JohanL,

great...thanks for your help,

Adrian :)
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: kantjer on March 09, 2005, 07:55:35 PM
Can't use Windows Update.... :-\
Not displayng the result of needed update beaucose of some error.
May be related to my settings?

Bye
                          Baba


Same problem here

Edit: http://v5.windowsupdate.microsoft.com/v5consumer/showarticle.aspx?articleid=21&ln=en solved the problem for me
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: Baba on March 09, 2005, 10:01:30 PM
After remouvung proxi settings from IE just live HTTP port 12080 in Web Shield basic window everything works fine.

May I live settings in this way?

Regards
                               Baba
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: Baba on March 09, 2005, 10:26:32 PM
Remouving port 12080  or 80 from HTTP  and leavig empty window in basic settings of Web Shield also works  ;D

Is this o.k.?

Bye
                        Baba
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: kantjer on March 09, 2005, 11:18:27 PM
Remouving port 12080  or 80 from HTTP  and leavig empty window in basic settings of Web Shield also works  ;D

Removing port 80 is the same as disabling Web Shield, not a very good idea.

Try adding port 80 again (do not ad port 12080 here) and also ad the following to the Ignored Addresses:

download.windowsupdate.com

See if that helps
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: Baba on March 09, 2005, 11:49:51 PM
Well, if I set the proxi server in IE option ZA works good (Ad-Blocking) but windows update not even with you suggestion.  :'(

I think I will disable web shield... :-\

Thanks
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: RaLX on March 10, 2005, 05:04:34 AM
Hi ya,

downloaded the 4.6.614 version....works great... alot smoother than the version before but....sorry.... I do a ccleaner scan and clean then open up FireFox.....  :-[ .....there is no google Home page showing ...i try other sites from bookmarks and nothing shows, so i shut down Avast open FF and then open avast again and it works perfectly.... can someone help me fix this problem as i use ccleaner alot....

Internet 512 ADSL.....XP Professional.... PC Dell Optilex G260n....512 Ram....pentium 4....

thanks in advance,

Adrian  :)

Try enabling the option "Only delete files in Windows Temp Folder olders than 48 hours" under Options -> Settings
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: Jazhawk on March 10, 2005, 05:53:53 AM
This still does nothing about NNTP.  Please guys, can you get this resolved soon.

-Jazhawk
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: aarangio on March 10, 2005, 01:00:32 PM
RaLX,

great....thanks for the help,

Adrian  :)
Title: Re: ** Introducing ** - pre-release version of upcoming avast update ** 4.6.618
Post by: Vlk on March 10, 2005, 09:46:18 PM
An update has just been uploaded (version 4.6.618).
Thanks Vlk
Title: Re: ** Introducing ** - pre-release version of the upcoming avast update
Post by: vojtech on March 11, 2005, 11:17:20 AM
This still does nothing about NNTP.  Please guys, can you get this resolved soon.

-Jazhawk

Please try v. 4.6.618 and let me know.
Title: Re: ** Introducing ** - pre-release version of upcoming avast update ** 4.6.618
Post by: barryfs on March 11, 2005, 11:47:09 AM
Sorry if I'm being a little slow here, but is the free version available from the normal download page the version you are speaking about in this thread (4.6.618) ??
Or is it a special beta version that should be downloaded from somewhere else ??

The reason I am asking is that I am new to Avast, and, as I use Zone Alarm, I have been avoiding downloading 4.6 until all the problems have been resolved.

Many thanks
Barry
Title: Re: ** Introducing ** - pre-release version of upcoming avast update ** 4.6.618 **
Post by: Vlk on March 11, 2005, 11:58:14 AM
Barry, this version is not officially available for download (yet).
To install it, you'd need to install a regular (release) version of avast first (4.5 or 4.6 - doesn't make any difference) and then apply the aswBeta.exe program as described in the first post in this thread.

Thanks
Vlk
Title: Re: ** Introducing ** - pre-release version of upcoming avast update ** 4.6.618
Post by: barryfs on March 11, 2005, 12:12:10 PM
Thanks VLK.

I currently use 4.5.549.
Any idea when 618 will be generally available on the download page, as I might just wait for that?

Regards
Barry
Title: Re: ** Introducing ** - pre-release version of upcoming avast update ** 4.6.618
Post by: jedvik on March 11, 2005, 04:56:32 PM
I just downloaded & installed 4.6.618.
I still can't log into Yahoo Mail with Zone Alarm Pro cookie control set to medium.
I get the message: "The browser you're using refuses to sign in. (cookies rejected)."
It still works OK with cookie control off in ZA.
Title: Re: ** Introducing ** - pre-release version of upcoming avast update ** 4.6.618
Post by: lukor on March 11, 2005, 04:59:38 PM
I just downloaded & installed 4.6.618.
I still can't log into Yahoo Mail with Zone Alarm Pro cookie control set to medium.
I get the message: "The browser you're using refuses to sign in. (cookies rejected)."
It still works OK with cookie control off in ZA.


Jedvik, avast webshield does not handle nor blocks cookies. It must be ZoneAlarm which is rejecting them. Do you have Yahoo Mail in some exclusion list in ZoneAlarm?
Title: Re: ** Introducing ** - pre-release version of upcoming avast update ** 4.6.618
Post by: jedvik on March 11, 2005, 05:21:38 PM


Jedvik, avast webshield does not handle nor blocks cookies. It must be ZoneAlarm which is rejecting them. Do you have Yahoo Mail in some exclusion list in ZoneAlarm?
Quote

Nope. I didn't start having the problem until the new version of Avast came out.
It definitely is Avast related. I can get Yahoo Mail to work with either cookie control off in ZA with Webshield on, or it also works with ZA cookie control at medium with Webshield off.
Title: Re: ** Introducing ** - pre-release version of upcoming avast update ** 4.6.618 **
Post by: jleezer on March 11, 2005, 05:24:14 PM
Since installing 4.6.618, I see that the file AshWebSv.err has been created in the
Avast4\DATA\log directory with contents like:

11-3-2005 17:16:58,"http://clustera.icq.com","text/html; charset=iso-8859-1","",302,0,246,510,373,315,511,UNKNOWN PROCESS,PID: 0, SEQ: 0,12006: Cannot parse request.
11-3-2005 17:16:58,"http://status-m.icq.com","image/gif","",200,0,139,1379,1030,918,1379,UNKNOWN PROCESS,PID: 0, SEQ: 0,12006: Cannot parse request.

Should I be worried about these messages are is it some superfluous logging?
Title: Re: ** Introducing ** - pre-release version of upcoming avast update ** 4.6.618 **
Post by: bob3160 on March 11, 2005, 06:59:09 PM
jedvik
Turn Webshield ON and cookie shield off in ZA. If that solves your problem, then it's a fault in ZA NOT avast!
My settings Have cookie control in ZA on mediun and Webshield is on   with out any problems or blockage.
Title: Re: ** Introducing ** - pre-release version of upcoming avast update ** 4.6.618 **
Post by: jleezer on March 11, 2005, 07:29:27 PM
Because of the errors in the file AshWebSv.err, I did check my avast4.ini file.
The WebScanner section looks like:
[WebScanner]
AutoRedirect=1
HttpRedirectPort=80
IgnoreProcess=avast.setup
LoadIsapiFilters=1
ISAPIFilter1=ashWsFtr.dll
IgnoreAddress=
IgnoreLocalhost=1
Igno

This does not look complete to me. Is the last line correct?
Title: Re: ** Introducing ** - pre-release version of upcoming avast update ** 4.6.618 **
Post by: Vlk on March 11, 2005, 09:31:20 PM
JohanL, what you're seeing is perfectly normal.
Title: Re: ** Introducing ** - pre-release version of upcoming avast update ** 4.6.618
Post by: jedvik on March 12, 2005, 02:12:30 AM
jedvik
Turn Webshield ON and cookie shield off in ZA. If that solves your problem, then it's a fault in ZA NOT avast!
My settings Have cookie control in ZA on mediun and Webshield is on   with out any problems or blockage.


Do you use Yahoo Mail? Like I said, that seems to be the only problem site for me now that I'm using the beta version of Avast! I'm not sure why I would blame it on ZA when I can use Yahoo Mail with no problems if I turn off Webshield & leave ZA with cookie control on medium. It would also be a coincidence that the problem only started when the Avast! program was updated.
Oh well... I'll just leave webshield on & cookie control off in ZA & hope I can use them both together sometime in the future.
Title: Re: ** Introducing ** - pre-release version of upcoming avast update ** 4.6.618 **
Post by: bob3160 on March 12, 2005, 03:50:20 AM
jedvik
As you can see from the picture, Yahoo isn't any problem.
Title: Re: ** Introducing ** - pre-release version of upcoming avast update ** 4.6.618
Post by: alanrf on March 12, 2005, 04:38:35 AM
On 2005/03/10 Vlk posted that an update to the pre-release was available (the new version being 4.6.618).

I immediately installed this release but since then I noticed a slight change in my system response.

I have gone back and viewed the iterations of the avast4.ini file on my system. 

With releases .603 and .614 there were (as far as I can tell) no changes to my avast4.ini file. 

With the .618 release I can see that the avast4.ini file was changed (at least in the [MailScanner] section).  The defaults were reset for the port redirects and for the "IgnoreLocalHost" setting (Ignore local communication checkbox in the GUI). 

No complaints to Avast ... this is pre-release, it may have just happened with me,  but other users may want to check that changes they have made and wish to keep have not been overriden by this update.   
Title: Re: ** Introducing ** - pre-release version of upcoming avast update ** 4.6.618
Post by: jedvik on March 12, 2005, 06:01:23 AM
jedvik
As you can see from the picture, Yahoo isn't any problem.

Oh well. I guess SalsaDoc44 & I are the only ones having problems with Avast! & Yahoo.
Here's a quote from him on page 1 of this thread:

"i am still having problems logging into Yahoo Mail even w/ the new beta update.  I was using the localhost 12080 work around previously w/ ZA Pro 5.5.062.011.  Yahoo Mail is the only site that doesn't accept my cookes with both Firefox 1.0.1 and IE even w/ medium settings on cookie control and ad blocking on ZA.  i can log into Yahoo Mail just fine if i turn off Web Shield.  I have WinXP SP2 w/ all the updates.  i do not have proxies configured w/ either Firefox or IE.  ZA is allowing all the avast modules.
any ideas to what seems to be the problem now? thanks.
i like the idea of Web Shield, but it's not wort"h it to me if these problems continue."
Title: Re: ** Introducing ** - pre-release version of upcoming avast update ** 4.6.618 **
Post by: jleezer on March 12, 2005, 09:01:20 AM
As previously mentioned, I keep getting messages in the file AshWebSv.err (in the DATA\log directory) file like:

12-3-2005 8:39:04,"http://b.office.microsoft.com","","",304,0,0,794318,124871,123683,792718,UNKNOWN PROCESS,PID: 0, SEQ: 0,12006: Cannot parse request.
12-3-2005 8:39:04,"http://b.office.microsoft.com","image/gif","",200,0,2769,3047,549,495,3047,UNKNOWN PROCESS,PID: 0, SEQ: 0,12006: Cannot parse request.
12-3-2005 8:39:04,"http://b.office.microsoft.com","","",304,0,0,1993151,132940,131698,1992001,UNKNOWN PROCESS,PID: 0, SEQ: 0,12006: Cannot parse request.

Is this logging superfluous and will it disappear in the official release?
Title: Re: ** Introducing ** - pre-release version of upcoming avast update ** 4.6.618 **
Post by: lukor on March 12, 2005, 12:06:16 PM
It is superfluous, benign and will disappear in the official release  :P
Title: Re: ** Introducing ** - pre-release version of upcoming avast update ** 4.6.618 **
Post by: bob3160 on March 12, 2005, 02:53:06 PM
jedvik
If the problem your having was related to avast!, then I and every one else using Yahoo mail
should also have problems. I've only seen you and SalsaDoc44 complain about this problem.
There has to be something else that causing this. Or, contributing to your difficulty.
I can get to my Yahoomail in 2 different ways:
1. Thru Trillian  and,
2. Going directly to the website and logging on to my account.
Title: Re: ** Introducing ** - pre-release version of upcoming avast update ** 4.6.618 **
Post by: Chuck58 on March 12, 2005, 04:10:16 PM
Add me to the list of the ones having problems getting to Yahoo mail. I'd have posted it earlier but haven't been home to check. I'm run LooknStop firewall and still can't get to yahoo mail with webshield enabled. Turn it off, and I'm okay.

I haven't updated to v618, so can't say if that fixes the issue. I'll load it now and see what happens.

*Edit* 4.6.623 (?) I uninstalled and reinstalled from avast.com, getting a new serial number along with it. According to what it says, I have 4.6.623 on my machine now. Unless I missed a post someplace, I haven't seen anything newer that 4.6.618 listed. Is this a renumbered earlier version or is it the very latest? Whatever it is, yahoo mail works again.
Title: Re: ** Introducing ** - pre-release version of upcoming avast update ** 4.6.618 **
Post by: Vlk on March 12, 2005, 09:14:15 PM
The new avast update has now been officially released. It is labelled as 4.6.623.
All users of the pre-release version of the update can gen the official one (623) simply by invoking the Program Update commend from within the avast GUI.

Thanks
Vlk
Title: Re: ** Introducing ** - pre-release version of upcoming avast update
Post by: johkaz on April 26, 2005, 12:35:24 AM
Hi,

I am up to 4.6.623 update level, and i have had no end of problems with my computer crashing with Avast and Zonealarm working together.
I have tried the update as mentioned above, but i am at the later level.
To try to solve it i have dropped the Zonealarm level down to Medium in the Firewall section.
And i seems to be more stable, at the moment.
Also, at the moment i can access Yahoo for my mail.
My computer OS is Windows XP Home (SR2) + all updates installed
Title: Re: ** Introducing ** - pre-release version of upcoming avast update
Post by: DavidR on April 26, 2005, 01:03:04 AM
The latest version is now 4.6.652, do a manual program update. The .652 release will recognise ZA and pop-up a compatibility window suggesting you don't use the Transparent proxy with ZA but manually set-up the proxy in your browser.

There are a number of flash Tutorials to assist as required.

http://www.avast.com/eng/webshield_issues.html

ZONE ALARM - AVAST Web Shield compatibility dialogue - Install/Update Question - YES or NO

If you are using ZoneAlarm Free you should click NO, because privacy features are not present in ZoneAlarm Free this will not turn off webshield transparent mode proxy.
Use a text editor and edit the avast4.ini file, the default installation location is C:\Program Files\Alwil Software\Avast4\DATA\avast4.ini (I would advise you copy avast4.ini before editing it, just in case).
Locate the line containing ZoneAlarmCompatibility= and delete that line.  Save the edited avast4.ini file.

If you are using ZoneAlarm Pro and Privacy Control in ZoneAlarm is set to High and if you click YES in avast comptability dialogue box the transparent mode proxy in webshield will be turned off you have to manually configure browser to access internet. To manually configure your browser watch instructional video

For IE - broadband users: - Tutorial - Web Shield Proxy Set-up for IE (http://www.avast.com/files/tutorials/ws_ieproxy.htm)
For IE - dialup users - Tutorial - Web Shield Proxy Set-up for IE (Dial-up) (http://www.avast.com/files/tutorials/ws_ieproxy_dialup.htm)
For Firefox users - Tutorial - Web Shield Proxy Set-up for Firefox (http://www.avast.com/files/tutorials/ws_ffproxy.htm)