The good folks on the libusb mailing list are doing some initial testing
of the Windows 8 Developer Preview. Several of them are reporting that
(in at least some cases) their USB installs are not producing any record
at all in setupapi.dev.log. One of the fellows created a USB device
with the magic WinUSB descriptor. It did get recognized and WinUSB got
loaded, but there is no evidence in setupapi.dev.log.
We have come to rely heavily on having a verbose record in
setupapi.dev.log of all Device Manager activity. Is it possible that a
decision has been made to bypass that logging for USB devices, or for
successful installs? They are reporting that the installation seems to
be happening more quickly, but I would call that an unfortunate
performance tradeoff.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
I will ask
d
debt from my phone
-----Original Message-----
From: Tim Roberts
Sent: Thursday, September 22, 2011 10:17 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Win 8 Bypassing setupapi.dev.log?
The good folks on the libusb mailing list are doing some initial testing
of the Windows 8 Developer Preview. Several of them are reporting that
(in at least some cases) their USB installs are not producing any record
at all in setupapi.dev.log. One of the fellows created a USB device
with the magic WinUSB descriptor. It did get recognized and WinUSB got
loaded, but there is no evidence in setupapi.dev.log.
We have come to rely heavily on having a verbose record in
setupapi.dev.log of all Device Manager activity. Is it possible that a
decision has been made to bypass that logging for USB devices, or for
successful installs? They are reporting that the installation seems to
be happening more quickly, but I would call that an unfortunate
performance tradeoff.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
OT: Even phones have mortgages now 
Doron Holan wrote:
debt from my phone
–
Kind regards, Dejan (MSN support: xxxxx@alfasp.com)
http://www.alfasp.com
File system audit, security and encryption kits.
Just wondering if you got some updates on this.
For the setupapi log, it seems to me most of the device will still
leave a trace in the windows\inf\setupapi.dev.log. For example,
USB Mass Storage Device will be there due to the wpd bus
enumerator (WpdBusEnumRoot\UMB.…). My Microsoft Wireless
Mouse will also leave a trace since it will download software and
then install the software.
It is generic device like PICkit 2 and my Logitech USB Gamepad
(USB\VID_046D&PID_C216) which seems to leave no trace in
setupapi.dev.log. They do leave a trace in WindowsUpdate.log
since Windows will attempt to download online drivers for them.
This is also true for WinUSB device with the WinUSB Descriptor.
They will not leave a trace in setupapi.dev.log, just like the generic
HID device.
BTW, I like the improvement in Windows 8 Developer Preview
in terms of device detection turn-around time (from insertion
to being usable), at least for most device.
Regards,
Xiaofan
On Fri, Sep 23, 2011 at 1:25 AM, Doron Holan wrote:
> I will ask
>
> d
>
> debt from my phone
>
> -----Original Message-----
> From: Tim Roberts
> Sent: Thursday, September 22, 2011 10:17 AM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] Win 8 Bypassing setupapi.dev.log?
>
>
> The good folks on the libusb mailing list are doing some initial testing
> of the Windows 8 Developer Preview. ?Several of them are reporting that
> (in at least some cases) their USB installs are not producing any record
> at all in setupapi.dev.log. ?One of the fellows created a USB device
> with the magic WinUSB descriptor. ?It did get recognized and WinUSB got
> loaded, but there is no evidence in setupapi.dev.log.
>
> We have come to rely heavily on having a verbose record in
> setupapi.dev.log of all Device Manager activity. ?Is it possible that a
> decision has been made to bypass that logging for USB devices, or for
> successful installs? ?They are reporting that the installation seems to
> be happening more quickly, but I would call that an unfortunate
> performance tradeoff.
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>