Updating Drivers - help 7

Carl · External Since: Dec 20, 2009 Posts: 6

I saw a plug for DriverMax on CNet, downloaded it and tried to update
my drivers.

It's my first time attempting to update a driver.

I chose to be careful and try updating just one, to see how it went.

It didn't.

After following all the instructions for updating the driver for my
Broadcom Bluetooth 2.0 USB Device, receiving a notification from
DriverMax that the driver had been updated and restarting my Netbook
running Windows XP Home SP3, I went to Device Manager > Broadcom
Bluetooth 2.0 USB Device > Properties > Driver only to find that the
driver version was 5.1.0.5800, dated 7/28/08 and not the downloaded v
4.2.7001.1.

Any advice, suggestions, etc., as to where to go from here or on how
to update drivers in general??

Bruce Chambers · External Since: Jun 26, 2005 Posts: 6856

Carl wrote:
>

>
> Any advice, suggestions, etc., as to where to go from here or on how
> to update drivers in general??
>

Only seek and obtain device drivers directly from the respective
devices' manufacturers web sites. The drivers archived at 3rd party
sites, such as you tried are not at all likely to be the most recent or
most appropriate.

--

Bruce Chambers

Help us help you:
http://www.catb.org/~esr/faqs/smart-questions.html

http://support.microsoft.com/default.aspx/kb/555375

They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety. ~Benjamin Franklin

Many people would rather die than think; in fact, most do. ~Bertrand Russell

The philosopher has never killed any priests, whereas the priest has
killed a great many philosophers.
~ Denis Diderot

user1435 · External Since: Nov 15, 2004 Posts: 2438

"Carl" wrote in message

>I saw a plug for DriverMax on CNet, downloaded it and tried to update
> my drivers.
>
> It's my first time attempting to update a driver.
>
> I chose to be careful and try updating just one, to see how it went.
>
> It didn't.
>
> After following all the instructions for updating the driver for my
> Broadcom Bluetooth 2.0 USB Device, receiving a notification from
> DriverMax that the driver had been updated and restarting my Netbook
> running Windows XP Home SP3, I went to Device Manager > Broadcom
> Bluetooth 2.0 USB Device > Properties > Driver only to find that the
> driver version was 5.1.0.5800, dated 7/28/08 and not the downloaded v
> 4.2.7001.1.
>
> Any advice, suggestions, etc., as to where to go from here or on how
> to update drivers in general??

If the downloaded version is 4.2.7001.1 as you stated, then they're an older
version of the driver which is now installed, version 5.1.0.5800.

--

Brian A. Sesko
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://members.shaw.ca/dts-l/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375

Leonard Grey · External Since: Jan 12, 2009 Posts: 115

Some things to know about updating drivers:

1- Only update a driver if an updated version corrects a problem you are
currently experiencing with the hardware in question. There is no reason
to update a driver merely because a new version is available.

2- Always obtain updated drivers directly from the device manufacturer,
if you can. That's the only way to know that you're getting the genuine
article.

Windows Update will also offer drivers -- which Microsoft gets from the
hardware manufacturers -- but for the optimal results and the best
support you should still go directly to the hardware device manufacturer
for updated drivers. Windows Update is good for users who are not
knowledgeable or experienced enough to install drivers on their own.

3- If the hardware device in question was installed by your computer
manufacturer, your first stop for drivers, even before you try the
device manufacturer, is your computer maker's website. The reason is
that the computer maker may have customized the hardware for its own
purposes.

4- Always follow the computer or hardware manufacturer's installation
instructions very carefully.
---
Leonard Grey
Errare humanum est

On 12/20/2009 12:56 PM, Carl wrote:
> I saw a plug for DriverMax on CNet, downloaded it and tried to update
> my drivers.
>
> It's my first time attempting to update a driver.
>
> I chose to be careful and try updating just one, to see how it went.
>
> It didn't.
>
> After following all the instructions for updating the driver for my
> Broadcom Bluetooth 2.0 USB Device, receiving a notification from
> DriverMax that the driver had been updated and restarting my Netbook
> running Windows XP Home SP3, I went to Device Manager> Broadcom
> Bluetooth 2.0 USB Device> Properties> Driver only to find that the
> driver version was 5.1.0.5800, dated 7/28/08 and not the downloaded v
> 4.2.7001.1.
>
> Any advice, suggestions, etc., as to where to go from here or on how
> to update drivers in general??
>

Tim Meddick · External Since: Feb 16, 2009 Posts: 147

Just to emphasise what "Leonard Grey" was saying in his reply ;

If a device is functioning properly, there is no need to attempt to look for "updated
drivers" at all.

In 99% of cases, the drivers that came with / installed with your hardware is the
optimal one for the job.

And in many cases, in attempting to update needlessly, you may end up with a
non-functioning and incompatible driver and will have to use XP's "roll back"
facility.

==

Cheers, Tim Meddick, Peckham, London. Smile

"Carl" wrote in message

>I saw a plug for DriverMax on CNet, downloaded it and tried to update
> my drivers.
>
> It's my first time attempting to update a driver.
>
> I chose to be careful and try updating just one, to see how it went.
>
> It didn't.
>
> After following all the instructions for updating the driver for my
> Broadcom Bluetooth 2.0 USB Device, receiving a notification from
> DriverMax that the driver had been updated and restarting my Netbook
> running Windows XP Home SP3, I went to Device Manager > Broadcom
> Bluetooth 2.0 USB Device > Properties > Driver only to find that the
> driver version was 5.1.0.5800, dated 7/28/08 and not the downloaded v
> 4.2.7001.1.
>
> Any advice, suggestions, etc., as to where to go from here or on how
> to update drivers in general??
>

Unknown · External Since: Apr 29, 2007 Posts: 488

"Leonard Grey" wrote in message

> Some things to know about updating drivers:
>
> 1- Only update a driver if an updated version corrects a problem you are
> currently experiencing with the hardware in question. There is no reason
> to update a driver merely because a new version is available.
Did you ever hear of 'PREVENTIVE MAINTENANCE'?
Don't oil it if it doesn't squeek? Don't fix it if it isn't broken?
Very poor stand. Why do you think autoupdates came about?

> 2- Always obtain updated drivers directly from the device manufacturer, if
> you can. That's the only way to know that you're getting the genuine
> article.
>
> Windows Update will also offer drivers -- which Microsoft gets from the
> hardware manufacturers -- but for the optimal results and the best support
> you should still go directly to the hardware device manufacturer for
> updated drivers. Windows Update is good for users who are not
> knowledgeable or experienced enough to install drivers on their own.
>
> 3- If the hardware device in question was installed by your computer
> manufacturer, your first stop for drivers, even before you try the device
> manufacturer, is your computer maker's website. The reason is that the
> computer maker may have customized the hardware for its own purposes.
>
> 4- Always follow the computer or hardware manufacturer's installation
> instructions very carefully.
> ---
> Leonard Grey
> Errare humanum est
>
> On 12/20/2009 12:56 PM, Carl wrote:
>> I saw a plug for DriverMax on CNet, downloaded it and tried to update
>> my drivers.
>>
>> It's my first time attempting to update a driver.
>>
>> I chose to be careful and try updating just one, to see how it went.
>>
>> It didn't.
>>
>> After following all the instructions for updating the driver for my
>> Broadcom Bluetooth 2.0 USB Device, receiving a notification from
>> DriverMax that the driver had been updated and restarting my Netbook
>> running Windows XP Home SP3, I went to Device Manager> Broadcom
>> Bluetooth 2.0 USB Device> Properties> Driver only to find that the
>> driver version was 5.1.0.5800, dated 7/28/08 and not the downloaded v
>> 4.2.7001.1.
>>
>> Any advice, suggestions, etc., as to where to go from here or on how
>> to update drivers in general??
>>

Unknown · External Since: Apr 29, 2007 Posts: 488

"Tim Meddick" wrote in message

> Just to emphasise what "Leonard Grey" was saying in his reply ;
>
> If a device is functioning properly, there is no need to attempt to look
> for "updated drivers" at all.
Don't look if not having a problem but, what if an update is made known to
you
from the proper source?.
> In 99% of cases, the drivers that came with / installed with your hardware
> is the optimal one for the job.
>
> And in many cases, in attempting to update needlessly, you may end up with
> a non-functioning and incompatible driver and will have to use XP's "roll
> back" facility.
Many cases??? Could you give actual figures on that or is that emotional
comment?

> ==
>
> Cheers, Tim Meddick, Peckham, London. Smile

>
>
>
>
> "Carl" wrote in message
>
>>I saw a plug for DriverMax on CNet, downloaded it and tried to update
>> my drivers.
>>
>> It's my first time attempting to update a driver.
>>
>> I chose to be careful and try updating just one, to see how it went.
>>
>> It didn't.
>>
>> After following all the instructions for updating the driver for my
>> Broadcom Bluetooth 2.0 USB Device, receiving a notification from
>> DriverMax that the driver had been updated and restarting my Netbook
>> running Windows XP Home SP3, I went to Device Manager > Broadcom
>> Bluetooth 2.0 USB Device > Properties > Driver only to find that the
>> driver version was 5.1.0.5800, dated 7/28/08 and not the downloaded v
>> 4.2.7001.1.
>>
>> Any advice, suggestions, etc., as to where to go from here or on how
>> to update drivers in general??
>>
>

"J. P. Gilliver · External Since: Oct 21, 2009 Posts: 51

In message , Unknown
writes:
>
>"Leonard Grey" wrote in message
>
>> Some things to know about updating drivers:
>>
>> 1- Only update a driver if an updated version corrects a problem you are
>> currently experiencing with the hardware in question. There is no reason
>> to update a driver merely because a new version is available.
>Did you ever hear of 'PREVENTIVE MAINTENANCE'?
>Don't oil it if it doesn't squeek? Don't fix it if it isn't broken?
>Very poor stand. Why do you think autoupdates came about?

But oiling rarely breaks whatever it is, whether it was squeaking or
not. Installing "updated" drivers has certainly been known to break
things; for example, when the updated drivers render some (perhaps
unrelated) part of your existing system (hardware _or_ software
unusable. Not the fault of the driver makers - they can't test every
combination (of hardware and software and both), and generally _are_
trying either to fix something or add something.
>
>> 2- Always obtain updated drivers directly from the device manufacturer, if
>> you can. That's the only way to know that you're getting the genuine
>> article.
>>
>> Windows Update will also offer drivers -- which Microsoft gets from the
>> hardware manufacturers -- but for the optimal results and the best support
>> you should still go directly to the hardware device manufacturer for
>> updated drivers. Windows Update is good for users who are not
>> knowledgeable or experienced enough to install drivers on their own.
>>
>> 3- If the hardware device in question was installed by your computer
>> manufacturer, your first stop for drivers, even before you try the device
>> manufacturer, is your computer maker's website. The reason is that the
>> computer maker may have customized the hardware for its own purposes.
>>
>> 4- Always follow the computer or hardware manufacturer's installation
>> instructions very carefully.
>> ---
>> Leonard Grey
>> Errare humanum est
>>
>> On 12/20/2009 12:56 PM, Carl wrote:
>>> I saw a plug for DriverMax on CNet, downloaded it and tried to update
>>> my drivers.
>>>
>>> It's my first time attempting to update a driver.
>>>
>>> I chose to be careful and try updating just one, to see how it went.
>>>
>>> It didn't.
>>>
>>> After following all the instructions for updating the driver for my
>>> Broadcom Bluetooth 2.0 USB Device, receiving a notification from
>>> DriverMax that the driver had been updated and restarting my Netbook
>>> running Windows XP Home SP3, I went to Device Manager> Broadcom
>>> Bluetooth 2.0 USB Device> Properties> Driver only to find that the
>>> driver version was 5.1.0.5800, dated 7/28/08 and not the downloaded v
>>> 4.2.7001.1.
>>>
>>> Any advice, suggestions, etc., as to where to go from here or on how
>>> to update drivers in general??
>>>
>
>
(If you weren't going to answer the rest of the post, it'd have been a
good idea not to quote it, but no matter.)
--
J. P. Gilliver. UMRA: 1960/<1985 MB++G.5AL-IS-P--Ch++(p)Ar@T0H+Sh0!:`)DNAf
** http://www.soft255.demon.co.uk/G6JPG-PC/JPGminPC.htm for ludicrously
outdated thoughts on PCs. **

"I'm tired of all this nonsense about beauty being only skin-deep. That's deep
enough. What do you want, an adorable pancreas?" - Jean Kerr

Carl · External Since: Dec 20, 2009 Posts: 6

On Dec 20, 1:45 pm, "Brian A." wrote:
as to where to go from here or on how
> > to update drivers in general??
>
> If the downloaded version is 4.2.7001.1 as you stated, then they're an older
> version of the driver which is now installed, version 5.1.0.5800.

Sorry, Brian, got my numbers backward:

4.2.7001.1 was the version my Netbook was running and...

5.1.0.5800 was the version I downloaded and tried to install.

Carl · External Since: Dec 20, 2009 Posts: 6

On Dec 20, 1:55 pm, Bruce Chambers wrote:
>
> Only seek and obtain device drivers directly from the respective
> devices' manufacturers web sites. The drivers archived at 3rd party
> sites, such as you tried are not at all likely to be the most recent or
> most appropriate.

That's one lesson I've learned on this one. Thanks, Bruce.

(Love your Diderot quote).

Carl · External Since: Dec 20, 2009 Posts: 6

On Dec 20, 3:19 pm, Leonard Grey wrote:
> Some things to know about updating drivers:
>
> 1- Only update a driver if an updated version corrects a problem you are
> currently experiencing with the hardware in question. There is no reason
> to update a driver merely because a new version is available.
>
> 2- Always obtain updated drivers directly from the device manufacturer,
> if you can. That's the only way to know that you're getting the genuine
> article.
>
> Windows Update will also offer drivers -- which Microsoft gets from the
> hardware manufacturers -- but for the optimal results and the best
> support you should still go directly to the hardware device manufacturer
> for updated drivers. Windows Update is good for users who are not
> knowledgeable or experienced enough to install drivers on their own.
>
> 3- If the hardware device in question was installed by your computer
> manufacturer, your first stop for drivers, even before you try the
> device manufacturer, is your computer maker's website. The reason is
> that the computer maker may have customized the hardware for its own
> purposes.
>
> 4- Always follow the computer or hardware manufacturer's installation
> instructions very carefully.
> ---
> Leonard Grey
> Errare humanum est
>
> On 12/20/2009 12:56 PM, Carl wrote:
>
>
>
> > I saw a plug for DriverMax on CNet, downloaded it and tried to update
> > my drivers.
>
> > It's my first time attempting to update a driver.
>
> > I chose to be careful and try updating just one, to see how it went.
>
> > It didn't.
>
> > After following all the instructions for updating the driver for my
> > Broadcom Bluetooth 2.0 USB Device, receiving a notification from
> > DriverMax that the driver had been updated and restarting my Netbook
> > running Windows XP Home SP3, I went to Device Manager> Broadcom
> > Bluetooth 2.0 USB Device> Properties> Driver only to find that the
> > driver version was 5.1.0.5800, dated 7/28/08 and not the downloaded v
> > 4.2.7001.1.
>
> > Any advice, suggestions, etc., as to where to go from here or on how
> > to update drivers in general??

Thanks Leonard. Good advice, every point. Especially the first one:
if it ain't broke, don't fix it.

Carl

Carl · External Since: Dec 20, 2009 Posts: 6

On Dec 21, 9:43 am, "Tim Meddick" wrote:

> And in many cases, in attempting to update needlessly, you may end up with a
> non-functioning and incompatible driver and will have to use XP's "roll back"
> facility.

Thanks, Tim. Bless that rollback facility. I've had to us it once in
this effort

Carl · External Since: Dec 20, 2009 Posts: 6

On Dec 21, 1:22 pm, "Unknown" wrote:
> "Leonard Grey" wrote in message
>
> news:eCpSuGbgKHA.3552@TK2MSFTNGP06.phx.gbl...> Some things to know about updating drivers:
>
> > 1- Only update a driver if an updated version corrects a problem you are
> > currently experiencing with the hardware in question. There is no reason
> > to update a driver merely because a new version is available.
>
> Did you ever hear of 'PREVENTIVE MAINTENANCE'?
> Don't oil it if it doesn't squeek? Don't fix it if it isn't broken?
> Very poor stand. Why do you think autoupdates came about?

As I think about it Leonard, the preventative maintenance approach is
what probably drove me to this. I am a major believer in the adage
that an ounce of prevention is worth a pound of cure, but am also well
aware of its opposite: leave well enough alone. It sometimes can be
tough to reach a good balance between the two.

Leonard Grey · External Since: Jan 12, 2009 Posts: 115

Drivers do not require preventive maintenance.

The parts in your car experience wear...they require preventive
maintenance. Software stored on your hard drive does not suffer 'wear'
so there is no preventive maintenance to perform.

That said, there is one occasion when you want to have the latest
drivers on your machine: before you make major upgrades to your
operating system, like installing a Service Pack or upgrading Internet
Explorer. That's because these upgrades are more likely to have better
support for recent drivers than for drivers that are years old.

But even on those occasions, you don't need to upgrade every single
driver on your system; just update for I/O devices like your video card
and sound card.

Always test your hardware after upgrading a driver. Sometimes 'upgraded'
drivers are worse than what they replace.

---
Leonard Grey
Errare humanum est

On 12/22/2009 9:44 AM, Carl wrote:
> On Dec 21, 1:22 pm, "Unknown" wrote:
>> "Leonard Grey" wrote in message
>>
>> news:eCpSuGbgKHA.3552@TK2MSFTNGP06.phx.gbl...> Some things to know about updating drivers:
>>
>>> 1- Only update a driver if an updated version corrects a problem you are
>>> currently experiencing with the hardware in question. There is no reason
>>> to update a driver merely because a new version is available.
>>
>> Did you ever hear of 'PREVENTIVE MAINTENANCE'?
>> Don't oil it if it doesn't squeek? Don't fix it if it isn't broken?
>> Very poor stand. Why do you think autoupdates came about?
>
> As I think about it Leonard, the preventative maintenance approach is
> what probably drove me to this. I am a major believer in the adage
> that an ounce of prevention is worth a pound of cure, but am also well
> aware of its opposite: leave well enough alone. It sometimes can be
> tough to reach a good balance between the two.
>

Unknown · External Since: Apr 29, 2007 Posts: 488

The IMPORTANT part of this discussion is where and how you get the driver
update.
It is NOT whether you have a problem.
If for example you have a video card and there is an update from the
manufacturer it is
sheer stupidity NOT to install it so that two years down the road you don't
experience a
problem caused by the lack of it. How many times do you read about someone
with a
problem only to find out their system hasn't been updated?
"Carl" wrote in message

On Dec 21, 1:22 pm, "Unknown" wrote:
> "Leonard Grey" wrote in message
>
> news:eCpSuGbgKHA.3552@TK2MSFTNGP06.phx.gbl...> Some things to know about
> updating drivers:
>
> > 1- Only update a driver if an updated version corrects a problem you are
> > currently experiencing with the hardware in question. There is no reason
> > to update a driver merely because a new version is available.
>
> Did you ever hear of 'PREVENTIVE MAINTENANCE'?
> Don't oil it if it doesn't squeek? Don't fix it if it isn't broken?
> Very poor stand. Why do you think autoupdates came about?

As I think about it Leonard, the preventative maintenance approach is
what probably drove me to this. I am a major believer in the adage
that an ounce of prevention is worth a pound of cure, but am also well
aware of its opposite: leave well enough alone. It sometimes can be
tough to reach a good balance between the two.

Chuck4 · External Since: Jun 14, 2004 Posts: 701

It's fairly important to find out why the driver update exists. Bug fix?
Additional capability? Accommodates new hardware revisions, etc.

"Carl" wrote in message

On Dec 21, 9:43 am, "Tim Meddick" wrote:

> And in many cases, in attempting to update needlessly, you may end up with
> a
> non-functioning and incompatible driver and will have to use XP's "roll
> back"
> facility.

Thanks, Tim. Bless that rollback facility. I've had to us it once in
this effort