differnce between devcon install and devcon update

NTDEV
1

Hi ,

whats the difference between these three methods of installing a driver using devcon

1)devcon.exe update SpbTestTool.inf ACPI<hwid>
2)devcon.exe install SpbTestTool.inf ACPI<hwid>
3)devcon.exe install SpbTestTool.inf root\drivername

2

There’s this amazing thing called Google. I think you’d really like it if you gave it a try.

By typing in “DEVCON install vs DEVCON update” I got a lot of pages, including this one from the WDK documentation:

http://msdn.microsoft.com/en-us/library/windows/hardware/ff544780(v=vs.85).aspx

I know, crazy… Who would think to actually look in the documentation?

Peter
OSR

3

On 05-Sep-2012 16:12, xxxxx@osr.com wrote:

There’s this amazing thing called Google. I think you’d really like it if you gave it a try.

By typing in “DEVCON install vs DEVCON update” I got a lot of pages, including this one from the WDK documentation:

http://msdn.microsoft.com/en-us/library/windows/hardware/ff544780(v=vs.85).aspx

I know, crazy… Who would think to actually look in the documentation?

Peter
OSR

http://lmgtfy.com/?q=DEVCON+install+vs+DEVCON+update

A very cool idea.

4

Hope, this will be very useful…

http://msdn.microsoft.com/en-us/library/windows/hardware/ff554721(v=vs.85).aspx

5

xxxxx@sasken.com wrote:

whats the difference between these three methods of installing a driver using devcon

1)devcon.exe update SpbTestTool.inf ACPI<hwid>
> 2)devcon.exe install SpbTestTool.inf ACPI<hwid>
> 3)devcon.exe install SpbTestTool.inf root\drivername

You do need to read the reference material, but since #2 is an FMM
(“Frequently-Made Mistake”), let me give you an executive summary.

#1 says “replace the existing driver for ACPI<hwid> with the one in my
INF file.” That’s useful.

#3 says “create a brand-new fake device called ‘root\drivername’, then
use the driver in my INF file to drive it.”. That’s useful.

#2 says “create a brand-new fake device called ‘ACPI<hwid>’, then use
the driver in my INF file to drive it.”. That’s NOT useful, because
despite the device ID, there won’t be any real hardware underneath it.
The device object in this case is exactly the same as in case #3 – it
is fake.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.