Unknown Device,...

[Kerem Gümrükcü]

Hi,

this maybe sounds strange, but for testing purposes, i
need to have a unknown device visible in the device
manager. How can i place a unknown device, best
would be two, three and four. But they must be removable
again!

Please dont ask why, i know this sounds strange but
i am working on a application that looks for unknown
devices and then works on them,...

Is there any safe way to place several dummy
unknown device into the systems device nodes?

Thanks in advance,...

Regards

Kerem

--
--
-----------------------
Beste Grüsse / Best regards / Votre bien devoue
Kerem Gümrükcü
Microsoft Live Space: http://kerem-g.spaces.live.com/
Latest Open-Source Projects: http://entwicklung.junetz.de
-----------------------
"This reply is provided as is, without warranty express or implied."

[Tim Roberts]

"Kerem Gümrükcü" <kare...@hotmail.com> wrote:
>
>this maybe sounds strange, but for testing purposes, i
>need to have a unknown device visible in the device
>manager. How can i place a unknown device, best
>would be two, three and four. But they must be removable
>again!
>
>Please dont ask why, i know this sounds strange but
>i am working on a application that looks for unknown
>devices and then works on them,...

In the future, don't ever say "please don't ask why". It just sounds
childish and conspiratorial. It's especially strange here, since you
immediately went on to TELL us why.

However, I would point out that there is no real way to "work on" an
unknown device, since by definition such a device does not have a driver.

>Is there any safe way to place several dummy
>unknown device into the systems device nodes?

What resources do you have at your disposal? If you have a couple of USB
devices that are not in the standard USB classes, they appear as unknown
devices. Have any unusual web cameras?
--
Tim Roberts, ti...@probo.com
Providenza & Boekelheide, Inc.

[Kerem Gümrükcü]

Hi Tim,

>In the future, don't ever say "please don't ask why". It just sounds
>childish and conspiratorial. It's especially strange here, since you
>immediately went on to TELL us why.

sorry, it shouldnt sound like that. I thought this is a unusual
question so,...anyway, you are right, it sound childish and
conspiratorial,...we are grown ups,..and i am a little too tired,
so i must honestly apologize here Tim,...sorry for that foolish
words,..

I have some webcams, but whatever i plug into my system
will be recognized and bound into the device nodes, so thats
why i look for something that my system (XPSP3) does not
know. I was thinking about placing something "unknown"
somewhere maybe in the registry and then trigger a hardware
scan, forcing the system to search for the "unknown" devices
driver, leading to a "Question-Mark" in the Device Manager,...

So thats what i wanted to do,...is there any way,...?

Regards

Kerem

--
-----------------------
Beste Grüsse / Best regards / Votre bien devoue
Kerem Gümrükcü

Latest Project: http://www.codeplex.com/restarts

Latest Open-Source Projects: http://entwicklung.junetz.de
-----------------------
"This reply is provided as is, without warranty express or implied."

"Tim Roberts" <ti...@probo.com> schrieb im Newsbeitrag
news:sh5q94p5kn7l7ookk...@4ax.com...

[David Craig]

How that works is fairly undocumented. There are little registry entries
created hither and yon and I suspect some variations between different
versions of Windows and maybe even service packs. Find devices or take one
of your own and change the VID/PID that won't match anything Windows uses in
the inbox drivers.

"Kerem Gümrükcü" <kare...@hotmail.com> wrote in message
news:%234Xnyid%23IHA...@TK2MSFTNGP06.phx.gbl...

[Pavel A.]

Install VMware.
Connect some USB device installed on the host, to a virtual machine.
Then watch what VMware does to the actual device connected to the host.
You probably want to do the same.
This is not easy (requires a driver) but the direction will be clear to
you.
A simpler and supported way can be using WinUSB
( details and examples - in WDK )

Regards,
-- PA

"Kerem Gümrükcü" <kare...@hotmail.com> wrote in message

news:#4Xnyid#IHA....@TK2MSFTNGP06.phx.gbl...

[Tim Roberts]

"David Craig" <dri...@nowhere.us> wrote:
>
>How that works is fairly undocumented. There are little registry entries
>created hither and yon and I suspect some variations between different
>versions of Windows and maybe even service packs. Find devices or take one
>of your own and change the VID/PID that won't match anything Windows uses in
>the inbox drivers.

Yes, that's why I asked about what resources he had available. We have a
number of miscellaneous EZ-USB and FX2 devices hanging around. It's
trivial to write a new VID/PID into their EEPROMs, thereby creating an
"unknown device".

However, it would also be possible to take the toaster bus sample from the
WDK, and modify it to create a set of PnP IDs that no one every heard of.

[Doron Holan [MSFT]]

you don't even need to use the toaster bus. just use devcon to create a
root enumerated PDO with a bogus hw ID....something like

devcon install %windir%\inf\machine.inf FAKE\ID

there is nothing special about machine.inf, i just picked it at random. any
INF would do

d

--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.

"Tim Roberts" <ti...@probo.com> wrote in message
news:2mnu94h43tvavf739...@4ax.com...