I am working on a driver for a 1394 device and the guys in manufacturing
were wondering if this was possible:
When you plug in the device, PNP goes through it’s wizard to install the
driver. If you unplug the device and plug it in again, it installs itself
quickly and quietly with no UI stuff popping up. This is good.
If you plug in a different device, one that has never been plugged into the
system before, the PNP goes through it’s wizard to install the driver. What
the HW testers would like is if there was a way to realize the drivers are
already installed and just setup the new device quickly and quietly. It
would make life easier for them.
JimA
James,
First, if your driver were signed, you would not see the UI for new
devices once the driver is installed.
But are you looking for a quicker way to configure the devices on a
production line? My own solution for this purpose is to have a driver
that communicates with the 1394 bus driver but is not loaded as a result
of connecting a 1394 device. In other words, this driver is always
loaded and simply exposes to my user-mode app the 1394 functions such as
enumerating nodes and performing read/write. This way, you do not need
to go through the whole installation process simply to configure the
device.
Hope this helps!
Mat
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of James
Sent: Thursday, June 17, 2004 12:00 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] 1394 driver installation question
I am working on a driver for a 1394 device and the guys in manufacturing
were wondering if this was possible:
When you plug in the device, PNP goes through it’s wizard to install the
driver. If you unplug the device and plug it in again, it installs
itself
quickly and quietly with no UI stuff popping up. This is good.
If you plug in a different device, one that has never been plugged into
the
system before, the PNP goes through it’s wizard to install the driver.
What
the HW testers would like is if there was a way to realize the drivers
are
already installed and just setup the new device quickly and quietly. It
would make life easier for them.
JimA
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@cvds.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
> the HW testers would like is if there was a way to realize the drivers are
already installed and just setup the new device quickly and quietly. It
would make life easier for them.
First: the drivers must be WHQL-signed for this.
Second: write an install app which will pre-install the drivers with
SetupCopyOEMInf. After this, the actual device plugging will be resolved
without bothering the user.
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com
The best way to do this is to execute a server-side install. However, this
requires a signed driver package and an installation app. You can get a
test signature for the device (see discussion on this in the ‘WFP is evil’
thread). Look at “Writing a Device Installation Application” in the DDK
documentation.
–
Bill McKenzie
Software Engineer - Prism 802.11 Wireless Solutions
Conexant Systems, Inc.
“James” wrote in message news:xxxxx@ntdev…
>
> I am working on a driver for a 1394 device and the guys in manufacturing
> were wondering if this was possible:
>
> When you plug in the device, PNP goes through it’s wizard to install the
> driver. If you unplug the device and plug it in again, it installs itself
> quickly and quietly with no UI stuff popping up. This is good.
>
> If you plug in a different device, one that has never been plugged into
the
> system before, the PNP goes through it’s wizard to install the driver.
What
> the HW testers would like is if there was a way to realize the drivers are
> already installed and just setup the new device quickly and quietly. It
> would make life easier for them.
>
> JimA
>
James wrote:
I am working on a driver for a 1394 device and the guys in manufacturing
were wondering if this was possible:
When you plug in the device, PNP goes through it’s wizard to install the
driver. If you unplug the device and plug it in again, it installs itself
quickly and quietly with no UI stuff popping up. This is good.
If you plug in a different device, one that has never been plugged into the
system before, the PNP goes through it’s wizard to install the driver. What
the HW testers would like is if there was a way to realize the drivers are
already installed and just setup the new device quickly and quietly. It
would make life easier for them.
JimA
Hello,
what about programing the unique id after HW-test. That the way we do it.
Uwe