DOS-names (8 char) vs FULL Windows names in exclude list

Avast Free Antivirus / Premium Security
1

I noticed something strange :frowning:

To test some beta issues with ZoneAlarm I wanted to add ZoneAlerm stuff to avast!'s exclude list.

Earlier I have always use DOS-names for this lists (to be sure) and added “C:\PROGRA~1\ZONEAL~1*.EXE” to the list, but that didn’t stop “ZoneAlarm.exe” from beeing scanned. “C:\Program Files\ZoneAlarm” however did?!?!?

Any reason for this (it is the same path :slight_smile:

In Forte Agent I use “C:\PROGRA~1\AGENT\DATA*.DAT” to prevent scanning of the .DAT files (same for .IDX) and that works OK (no need for “C:\Program Files\Agent\Data*.dat”)

Why does this work, and not the other ?!?!?!

BTW: Tried to add both, but then the last entries are lost or truncated, is there a max number of chars in the exclude list?

2

Avast is a 32bit util, so no truncated names that is only for those 16bit applications.

3

Is there a possibility taht avast just check the full path (not short DOS) like an exact ‘text’ string before the name of the file, I mean, PROGRA~1 does not match the text PROGRAM FILES ::slight_smile:

4

Had to include both (as ZoneAlarm uses both :slight_smile:

The problem is that the 5.5 beta ZoneAlarm hangs during startup. And it seems like it might be something with avast!

The avast! globe stops spinning while the ZA client starts up, and the computer halts completly.

I donæt know if it is the virus scanning, or avast! trying to connect to internet while ZA start, but it’s frustrating

5

Lars-Erik, definitivelly, I gave up to solve ZA 5.5 problems with avast and my proxy filter :frowning:
I changed to Agnitum Outpost because of this.
A lot of users had to do this as ZA 5.5 become very unstable in their systems.
Sorry, I don’t know the solution. By your answer (Had to include both (as ZoneAlarm uses both), I suppose my first assumption was wrong :-
Had to include both (as ZoneAlarm uses both :slight_smile:

6

Do you know if there has been any contact between avast! and ZoneLabs. I’d really hate having to drop one of them.

Have you researched what is happening?

Does it hang when avast! scans ZA at start?

Or when avast! check on internet while ZA is starting?

Everything hangs in the middle of the avast! globe turning just as ZA client is starting. And only at boot time.

System is stable as can be if the boot just is OK…

7

No, I don’t… In fact, you know, I’m not an Alwil guy but I can bet not. Alwil team is trying to release the 4.5 version and ZA was recently sold, many changes in both sides.

No, I use ZA free. Sent an email never answered.
Btw, all my emails to ZA support were for nothing :frowning:

Yes, you’re right. Can you do this tests and researches…? I think you have the knowleadge and this will help a lot of users with firewall troubles (or, better, compatibility troubles at boot).

Fully agree. That happens frequently when I’ve been using ZA 5 >:(

8

Technical

Fully agree. That happens frequently when I've been using ZA 5
That's no longer an issue with the current version. It doesn't hang, it doesn't forget, it only protects. :) :)
9

I have some communication with ZoneLabs now (as I do some beta testing of 5.5), and in the last response they asked if I could try disabling avast! to see if that helps. So they are aware of the problem. For starters I have now disabled scanning of the ZA files (not easy, they are spread around the HDD :slight_smile: No hang this boot, but I’ll try for a while to see if this is the problem (can’t really see why, but…)

BTW: You can help by helping beta-testing ZA with avast!, use this link: http://download.zonelabs.com/bin/free/beta

10

Actully, Technical was right (as usual :)).
avast! matches the exclusions as ‘text’ - i.e. “c:\program files” is different from “c:\progra~1”. And, the other application may use both to access/start a file.

Lars-Erik, if I remember correctly, you were using Win98SE - is it still the case? I’m sort of surprised to hear that ZoneAlarm would have conflicts with avast! both on Win98 and WinXP (which is what Technical is using, right?).

11

That’s right, still on Win98se (until I get my new harddisk and can clone Win98se to two partitions - and then upgrade one of them to WinXP Pro :slight_smile:

What shocked me was that the first ZA 5.5 beta had no problem, it was with the second beta things started hanging

12

Here, Windows XP SP2.
I don’t think is just an ZA and avast problem… Maybe other software were interfering ant that time. ZA, from time to time, consumed all CPU resources :frowning:

Lars, did you try to delay the update of avast? (‘Settings’ on my signature).
I suppose you’re using DSL ::slight_smile:

13

Sorry Lars-Erik
I misread your first post didn’t realize you are doing beta testing for ZA. Hope once the buggs are all ironed out, they will finally recognize avast!
I removed the other post.

14

Have crossed my mind, I’ll try that as well. For now I try not scanning the ZA files at start, and have had no hang so far :slight_smile:

But I need to test for some days to be sure. Then I’ll other stuff (like delaying the avast! time before checking for updates)

15

This is one of the best things in avast world…
(Almost) Everything could be configurated and fit into the user needs 8)

16

After adding these exclusions to avast! ZA has not caused a crash at boot (strange thing is that it didn’t get all exclusion with c:\windows\system\vs*.dll, had to use \vs.dll - even stranger, with the first one it still scanned “za*.dll” and “rsa*.dll” files at start, but with “\vs.dll” it doesn’t - the logic in that I don’t get, anyone that can explain?):

C:\PAGEFILE.SYS,
C:\WIN386.SWP,
\SYSTEM.DA?,
\USER.DA?,
C:\WINDOWS\TEMP*.TMP,
C:\MSDOS.SYS,
C:\WINDOWS\TEMP_AVAST4_\UNP,
C:\Program Files\ZoneAlarm*.,
C:\PROGRA~1\ZONEAL~1*.*,
\vs.dll

17

OK, some experimenting. These exclude settings seems to make Avast! and ZoneAlarm 5.5 beta co-exist without lockups at boot time. But I really think avast! and ZoneLabs should find out WHY this lockup problem happends :frowning:

c:\progra*\zoneal*\zlclient.exe
c:\windows\system\vs*.dll
c:\windows\system\zonelabs*.dll
c:\windows\system\zl*.dll

18

For the completeness: what is the rest of your Standard Shield settings? (mainly, the second and fourth page)

19

Lars-Erik
Does the Beta your testing finally recognize avast! as an AV program?

20
  1. page: All marked
  2. page: Scan on open (?,{},386,AD?,ASP,ASX,BAS,BAT,BIN,CH?,CLA*,CMD,COM,CPL,CRT,CSS,DLL,DO?,EML,ECE*,EXE,HLP,HT*,INF,INS,ISP,JS*,MDB,MDE,MHT,MS?,NWS,OCX,OV?,PCD,PDF,PIF,PO?,PP?,PRC,PRF,REG,RTF,SCF,SCR,SCT,SHB,SHS,SWF,SYS,VB?,VSD,VXD,WS?,XL?), Always scan WSH-files, Scan Created/Modified, Only with selected ext, Default extension set, Additional extensions (?,ACE,ARC,ARJ,ASP*,CAB,ECE*,GZ*,LHA,LZH,RAR,TAR,ZIP,ZOO)
  3. page: No marks, Excetions: \PAGEFILE.SYS,\WIN386.SWP,\SYSTEM.DA?,\USER.DA?,C:\WINDOWS\TEMP*.TMP,C:\MSDOS.SYS,C:\WINDOWS\TEMP_AVAST4_\UNP*,c:\progra*\zoneal*\zlclient.exe,c:\windows\system\vs*.dll,c:\windows\system\zonelabs*.dll,c:\windows\system\zl*.dll