AVG 8 is a Bully?

Do you have a question? Post it now! No Registration Necessary.  Now with pictures!

Threaded View
After upgrading from AVG 7 to version 8, I noticed it insists on
loading before my firewall program.  That seems like a bad idea.
Anyone know how to control the order in which startup programs load
(without the overhead of yet another startup program) ?

DC

Re: AVG 8 is a Bully?

Quoted text here. Click to load it

Could it be because of the order in which they were installed?



Re: AVG 8 is a Bully?

On Tue, 3 Mar 2009 17:39:56 -0500, "FromTheRafters"

Quoted text here. Click to load it
I don't think so.  I removed AVG 7 then installed AVG 8.  The firewall
would have been installed well before that.

Re: AVG 8 is a Bully?

On Tue, 03 Mar 2009 16:21:12 -0600, DennyCrane@MadCow.net wrote:

Quoted text here. Click to load it

The recommendation at the link below says "If the order of startup
programs matters to you, execute them from a script or batch program
where you can control the order." No additional programs are required.


Order of Startup Programs
http://oakroadsystems.com/tech/winxptip.htm


Re: AVG 8 is a Bully?

On Tue, 03 Mar 2009 16:21:12 -0600, DennyCrane@MadCow.net wrote:

Quoted text here. Click to load it


Yeah. Uninstall the piece of shit.

Re: AVG 8 is a Bully?

DennyCrane@MadCow.net wrote:

Quoted text here. Click to load it

And your point is what?  Load order is unimportant.

The Windows Firewall won't permit network traffic until it becomes
ready.  Doesn't matter if something loaded before it.  This eliminates
the window of opportunity during bootup of an application getting
network access before the firewall is ready.  It was one of the few
features of this firewall that was lacking in other firewalls for quite
some time.

Some firewalls used to insert a Winsock Service Provider in the TCP
stack.  Their handler wasn't enabled until the controller process was
ready so no network traffic was possible until this controller enabled
the handler.  I don't recall using that method anymore since it is
possible to reorder the chaining in the Winsock handlers.

In version 2.x of Comodo Personal Firewall, there was a user
configurable option to disable the network interface until the firewall
was ready.  Most users didn't know about that buried option but it was
there.  In v3, the option is gone because this is the default behavior
of that firewall.  See my posts in Comodo's forums at:

http://forums.comodo.com/empty-t20715.0.html
http://forums.comodo.com/empty-t20728.0.html

Forums for a product are a good place to ask such questions as yours.
In a virtual machine, I installed Comodo Internet Suite (because that's
the only download they offer now for their firewall) and installed just
their firewall.  I then installed Grisoft's AVG antivirus product.  I
then ran LoadOrder.  Comodo's kernel-mode drivers were loaded long
before AVG's; however, order isn't important.  The network interface
being disabled until the firewall is ready is what is important.

For your UNIDENTIFIED firewall, you probably should go visit its forum.

Re: AVG 8 is a Bully?


Quoted text here. Click to load it

Why is somebody as informed as you are using AVG 8?


Re: AVG 8 is a Bully?

John wrote:

Quoted text here. Click to load it

I did NOT say that I *use* AVG.  I have a couple family members that
still want to use it despite my arguments against it.  I *tested* the
AVG product and did so in a VIRTUAL MACHINE.  When testing was done, I
reverted the VM back to its baseline snapshot.

Site Timeline