You cannot hook a device. You can only hook a driver since the table is
in the driver object, not the devobj. This means that you are hooking
every USB hub PDO and FDO, essentially screwing up all of usb
d
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@ulstu.ru
Sent: Monday, December 12, 2005 9:43 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Patch DRIVER_OBJECT.MajorFunction[XXX]
I hooked “/Device/USBPDO-3” device. I’m surprised by time delay. Why
are log records shown in DbgView only after several minutes? Why is
system
hanging during this time? The problem is not that no bytes returned. If
original handler is called in HookRoutine the problem still occurs.
Subject: Re: Patch DRIVER_OBJECT.MajorFunction[XXX]
From: Tim Roberts
> Date: Mon, 12 Dec 2005 14:21:11 -0800
> X-Message-Number: 26
> I’m not sure why this surprises you. What were you expecting this
code
> to do? What you have done here is completely disable whatever device
> you have “hooked”. Every request sent to this driver will return
> nothing at all, include all requests to read data. What if there was
> another driver trying to read data from this device? It’s going to
see
> that no bytes were returned, and in all likelihood will retry the
> request until it gets some data.
>
> Which device did you “hook”?
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .
—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com