** Introducing ** - pre-release version of upcoming avast update

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.

Version 4.6.614 should write the temp files to the avast folder (this was changed since 4.6.612 released yesterday).

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

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 :stuck_out_tongue:

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.

Vlk,

Webshield up and working with the registry override.

Much appreciated.

Alan

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

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.

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.

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.

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

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

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.

@kantjer

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

housi
You can get it from HEREl.

Bob
Thanks a lot! Downloaded, works.

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 :slight_smile:

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

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

Can’t use Windows Update… :-
Not displayng the result of needed update beaucose of some error.
May be related to my settings?

Bye
Baba

JohanL,

great…thanks for your help,

Adrian :slight_smile: