Anyone know why Outpost Firewall, which seems to do some I/O every 4 seconds, triggers AVAST Home 4.1.289 on a quiet Win98FE system. Results captured with Filemon.exe
Thank you
Arn
12:45:49 AM Outpost:FFFE90CF Attributes C:\PROGRAM FILES\COMMON FILES\AGNITUM SHARED\AUPDATE\UPDATE.INI SUCCESS GetAttributes
12:45:49 AM Outpost:FFFE90CF Open C:\PROGRAM FILES\COMMON FILES\AGNITUM SHARED\AUPDATE\UPDATE.INI SUCCESS OPENEXISTING READWRITE DENYWRITE
12:45:49 AM Outpost:FFFE90CF Ioctl C: SUCCESS Subfunction: 08h
12:45:49 AM Outpost:FFFE90CF Attributes C:\PROGRAM FILES\COMMON FILES\AGNITUM SHARED\AUPDATE\UPDATE.INI SUCCESS Get Modify
12:45:49 AM Outpost:FFFE90CF Seek C:\PROGRAM FILES\COMMON FILES\AGNITUM SHARED\AUPDATE\UPDATE.INI SUCCESS End Offset: 0 / New offset: 0
12:45:49 AM Outpost:FFFE90CF Seek C:\PROGRAM FILES\COMMON FILES\AGNITUM SHARED\AUPDATE\UPDATE.INI SUCCESS Beginning Offset: 0 / New offset: 0
12:45:49 AM Outpost:FFFE90CF Read C:\PROGRAM FILES\COMMON FILES\AGNITUM SHARED\AUPDATE\UPDATE.INI SUCCESS Offset: 0 Length: 512
12:45:49 AM Outpost:FFFE90CF Close C:\PROGRAM FILES\COMMON FILES\AGNITUM SHARED\AUPDATE\UPDATE.INI SUCCESS CLOSE_FINAL
12:45:49 AM Ashserv:FFFE8213 Attributes C:\PROGRAM FILES\ALWIL SOFTWARE\AVAST4\DATA\AVAST4.INI SUCCESS GetAttributes
12:45:49 AM Ashserv:FFFE8213 Open C:\PROGRAM FILES\ALWIL SOFTWARE\AVAST4\DATA\AVAST4.INI SUCCESS OPENEXISTING READWRITE DENYWRITE
12:45:49 AM Ashserv:FFFE8213 Ioctl C: SUCCESS Subfunction: 08h
12:45:49 AM Ashserv:FFFE8213 Attributes C:\PROGRAM FILES\ALWIL SOFTWARE\AVAST4\DATA\AVAST4.INI SUCCESS Get Modify
12:45:49 AM Ashserv:FFFE8213 Seek C:\PROGRAM FILES\ALWIL SOFTWARE\AVAST4\DATA\AVAST4.INI SUCCESS End Offset: 0 / New offset: 0
12:45:49 AM Ashserv:FFFE8213 Seek C:\PROGRAM FILES\ALWIL SOFTWARE\AVAST4\DATA\AVAST4.INI SUCCESS Beginning Offset: 0 / New offset: 0
12:45:49 AM Ashserv:FFFE8213 Read C:\PROGRAM FILES\ALWIL SOFTWARE\AVAST4\DATA\AVAST4.INI SUCCESS Offset: 0 Length: 2620
12:45:49 AM Ashserv:FFFE8213 Close C:\PROGRAM FILES\ALWIL SOFTWARE\AVAST4\DATA\AVAST4.INI SUCCESS CLOSE_FINAL
This “problem” is not related to Outpost in any way. It’s normal for avast to periodically touch its avast4.ini file (it’s not triggered by Output), just like it’s normal for Outpost to periodically touch its update.ini…
Yes, I care, but I may be unable to do anything about it. I keep overhead to a mininimum on my geriatric 300mhz chip. However, when I terminate Outpost, Avast’s activity totally stops.
C:\PROGRAM FILES\COMMON FILES\AGNITUM SHARED\AUPDATE\UPDATE.INI was added to Avast’s excluded files; rebooted system; no change.
Are you saying Avast! hits it’s avast4.ini file every 4 to 5 seconds? That’s what shows on my system monitor.
Are you saying Avast! hits it's avast4.ini file every 4 to 5 seconds? That's what shows on my system monitor.
I wouldn’t be too surprised… but maybe only under Win2K/XP. Under (geriatric ;D) Win98 it behaves differently (the Standard Shield’s are very different).
However, when I terminate Outpost, Avast's activity totally stops.
That is an interesting point (you didn’t say that in the original post). In this case I guess there must be some connection – try e.g. pausing the Standard Shield and/or terminating the whole on-access protection to see if it has any effect…
Ummm… How do I do that? I can’t find a close request or a flag that says do not run on next boot. Maybe I’m just missing something. Can I safely close ASHMAISV in the Task manager???
Shut it off, and the I/O activity ceased for Outpost and Avast. For anyone out there running Outpost version 1, this option hangs out under the HELP menu.
Thank you to Technical & VLK for your help and suggestions
Arn