[Resolved] Version 5.1.864 conflict with Dell 1395 wireless card driver

[bob3160]

But I don't care for the "evangelists" continuing to try selling me something I don't want.

I haven't tried to sell you anything simply stated that there was a new signed driver available.
If you in your wisdom have decided not to update to the new version, then so be it.

[DavidR]

<snip>
No other changes to my system were needed (or desired); the new Avast version fixed my problem, as I suspected it would.

It's still a good idea to upgrade your driver. 

No thanks -- "if it ain't broke, don't fix it!" 

Sorry Bob and Nesivos, I too am of the old school of if it isn't broke don't fix it.

Placing DOS into the same argument just shows how weak the argument is. First it isn't a driver but a program/programming language and second it is outdated and no longer updated or serving the purpose (e.g. its sort of broken).

I have had this system for two years and it is running sweet as a nut and I haven't gone seeking out newer drivers. If I get an issue with a driver, graphics, etc. if confirmed the problem is with the driver then do I seek out new/updated drivers. How many times have you flashed your BIOS as that should follow the same logic.

Programs too have drivers, but I rely on keeping my programs up to date and if that update replaces a driver there has to have been a reason, not just that there is a newer one.

[Nesivos]

@Nesivos
@bob3160

See this post:

http://forum.avast.com/index.php?topic=68927.msg579118#msg579118

No other changes to my system were needed (or desired); the new Avast version fixed my problem, as I suspected it would.

It's still a good idea to upgrade your driver.  

No thanks -- "if it ain't broke, don't fix it!"  

Why aren't you still using DOS

Is this a serious question??? Do you really think an unnecessary driver update is the same as moving to a new operating system? If so, I'm beginning to understand why we aren't communicating -- we see the world in vastly different ways.

Here is a challenge for you: Do you know exactly what got "fixed" in the "updated" driver version you are referring to? In other words, do you really know why you updated? Well, I did a little homework and the 5.x versions of this driver just added support for countries that I don't live in. There is absolutely no reason why I need to install this driver when the one I have works fine (in the USA).

If you and others want to tweak your systems like this, that's entirely up to you. But I don't care for the "evangelists" continuing to try selling me something I don't want. Can we just let this thread die? I started the thread because I had a bug to report, and now that Alwil has fixed the bug I really don't have anything else to say on this topic.

XP was working fine for me.

I still upgraded to Windows 7.

Thank you.

Let me tell you about an experience I had with a Realtek audio driver.

I did not notice any problems with my audio.

However, I upgraded to the latest Realteck audio driver and guess what.

The sound quality of the audio improved immensely once I upgraded.

Vendors don't normally upgrade their software unless the upgrade is an improvement.

Maybe you upgrade the Broadcom driver and your wireless connection becomes more secure as a result even though it appears to be working fine without the upgrade.

People who stay with outdated software rather than upgrade do so at their own risk.

In my humble opinion, it is better to stay current rather than keep something old even if you think it is working, unless you can't afford the upgrade which is not the case with the Broadcom wireless driver.

[Tenko]

I think it's better to update when it's necessary. and thumps up for rwaters. Just to inform you...  This guys knows what he is saying and doing.

Cheers

[robinb]

I agree, why update drivers if there are no problems now. If you found you were having a problem  with a particular driver, then of course update the drivers.  Sometimes updating the drivers could make it worse not better.  My motto is what works now do not fix!
If an antivirus program or antispyware program caused the problem that is what needs to be fixed- not the driver that has been working for you until you installed an upgrade or update to these programs

robin

[2nd base]

Folks should always keep their hardware up to date.

[Tenko]

Can we start a new thread with "should we update our hardware driver?" as title and discuss there? I can start it if you want.

Regards

[2nd base]

Nope. It's common sense. No thread required.

[Hermite15]

no need to quote a spam post can you delete the quoted part, it contains links etc...

>>> next time use the report button instead. No need to even comment spam stuff.

[bravepuppy]

Very simple solution (that took me only five hours to find online) to this extremely infuriating problem.

Through your control panel enter Avast's uninstall feature. Only instead of uninstall, select "change."

Uncheck (i.e. deactivate) the "Behavior Shield." If I recall, you then have to restart your computer.

Problem solved.

[rwaters]

Very simple solution (that took me only five hours to find online) to this extremely infuriating problem.

Through your control panel enter Avast's uninstall feature. Only instead of uninstall, select "change."

Uncheck (i.e. deactivate) the "Behavior Shield." If I recall, you then have to restart your computer.

Problem solved.

Yes, that is the solution if you are running version 5.1.864. This was pretty well documented earlier in this thread.

But if you update to the pre-release version 5.1.874 then you can leave the Behavior Shield installed. Check the following thread, which has download links for the pre-release version.

http://forum.avast.com/index.php?topic=68927.0