WinUSB on XP without WDK

Hi,

warning. newbie question follows!

I'm trying to use WinUSB (WDK 7) on XP with SP2. After a wee bit of work
finally got the INF file to recognise and install the WinUSB and KMDF drivers
when the device is connected. Everything works beautifully, my small test app
communicates (via WinUSB) with my target hardware. So feeling dead chuffed
with myself I asked my college to try out my new driver package (INF +
coinstallers).
And that's where it all went sour! His system is also XP SP2 but without WDK
(shouldn't be necessary right). Driver install works fine, but when he fires
up the test application it hangs on the 1st WinUSB_WritePipe call. After
trying various things (examing installed driver, log files, registery,
rebooting etc.) we install WDK on his system, and low and behold everything
works suddenly.

Now obviously, I've missed something, but I'm dammed if I can spot it.
Anyone here come across a similar issue, or are the symtoms ringing any bells
for anyone?

Also, on a side issue, how can I find the control GUID for WinUSB to use
tracelog to dig a bit deeper into what's happening when the WinUSB call hangs?

thanks in advance

are you installing with the winusb and kmdf v1.9 coinstallers? if you get
as far as opening a winusb handle, there should be no need for any more wdk
components, a hang in winusb_writepipe is indicative of a bug in your app or
the hw is hung

d

--

This posting is provided "AS IS" with no warranties, and confers no rights.


"giajh01" <> wrote in message
news:5D6AECC3-6631-4E1A-B24A-...
> Hi,
>
> warning. newbie question follows!
>
> I'm trying to use WinUSB (WDK 7) on XP with SP2. After a wee bit of work
> finally got the INF file to recognise and install the WinUSB and KMDF
> drivers
> when the device is connected. Everything works beautifully, my small test
> app
> communicates (via WinUSB) with my target hardware. So feeling dead chuffed
> with myself I asked my college to try out my new driver package (INF +
> coinstallers).
> And that's where it all went sour! His system is also XP SP2 but without
> WDK
> (shouldn't be necessary right). Driver install works fine, but when he
> fires
> up the test application it hangs on the 1st WinUSB_WritePipe call. After
> trying various things (examing installed driver, log files, registery,
> rebooting etc.) we install WDK on his system, and low and behold
> everything
> works suddenly.
>
> Now obviously, I've missed something, but I'm dammed if I can spot it.
> Anyone here come across a similar issue, or are the symtoms ringing any
> bells
> for anyone?
>
> Also, on a side issue, how can I find the control GUID for WinUSB to use
> tracelog to dig a bit deeper into what's happening when the WinUSB call
> hangs?
>
> thanks in advance

yes I'm using the v1.9 CoInstallers.

Not sure I follow why, a libaray call hanging is necessarily a bug in the
application
making the call. Just for clarification, the exact same app and HW works
fine on my own PC.

I've since had a chance to test this on 2 other PCs (one incidently only
supporting USB1.1) and on both those systems the test application runs fine.
Obviously there's
something dodgy on my the single PC, but God knows what it is. I guess I
could try persuading my collegue to uninstall WDK and see if the problem
reappears but to be honest I don't fancy my chances of either
a) him agreeing
b) the problem reappearing

"Doron Holan [MSFT]" wrote:

> are you installing with the winusb and kmdf v1.9 coinstallers? if you get
> as far as opening a winusb handle, there should be no need for any more wdk
> components, a hang in winusb_writepipe is indicative of a bug in your app or
> the hw is hung
>
> d
>
> --
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "giajh01" <> wrote in message
> news:5D6AECC3-6631-4E1A-B24A-...
> > Hi,
> >
> > warning. newbie question follows!
> >
> > I'm trying to use WinUSB (WDK 7) on XP with SP2. After a wee bit of work
> > finally got the INF file to recognise and install the WinUSB and KMDF
> > drivers
> > when the device is connected. Everything works beautifully, my small test
> > app
> > communicates (via WinUSB) with my target hardware. So feeling dead chuffed
> > with myself I asked my college to try out my new driver package (INF +
> > coinstallers).
> > And that's where it all went sour! His system is also XP SP2 but without
> > WDK
> > (shouldn't be necessary right). Driver install works fine, but when he
> > fires
> > up the test application it hangs on the 1st WinUSB_WritePipe call. After
> > trying various things (examing installed driver, log files, registery,
> > rebooting etc.) we install WDK on his system, and low and behold
> > everything
> > works suddenly.
> >
> > Now obviously, I've missed something, but I'm dammed if I can spot it.
> > Anyone here come across a similar issue, or are the symtoms ringing any
> > bells
> > for anyone?
> >
> > Also, on a side issue, how can I find the control GUID for WinUSB to use
> > tracelog to dig a bit deeper into what's happening when the WinUSB call
> > hangs?
> >
> > thanks in advance
>
> .
>

you need to attach a debugger (windbg) and see exactly where the call is
hanging

d

"giajh01" <> wrote in message
news:0C295F9C-387B-4E87-B1FE-...
> yes I'm using the v1.9 CoInstallers.
>
> Not sure I follow why, a libaray call hanging is necessarily a bug in the
> application
> making the call. Just for clarification, the exact same app and HW works
> fine on my own PC.
>
> I've since had a chance to test this on 2 other PCs (one incidently only
> supporting USB1.1) and on both those systems the test application runs
> fine.
> Obviously there's
> something dodgy on my the single PC, but God knows what it is. I guess I
> could try persuading my collegue to uninstall WDK and see if the problem
> reappears but to be honest I don't fancy my chances of either
> a) him agreeing
> b) the problem reappearing
>
> "Doron Holan [MSFT]" wrote:
>
>> are you installing with the winusb and kmdf v1.9 coinstallers? if you
>> get
>> as far as opening a winusb handle, there should be no need for any more
>> wdk
>> components, a hang in winusb_writepipe is indicative of a bug in your app
>> or
>> the hw is hung
>>
>> d
>>
>> --
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>>
>> "giajh01" <> wrote in message
>> news:5D6AECC3-6631-4E1A-B24A-...
>> > Hi,
>> >
>> > warning. newbie question follows!
>> >
>> > I'm trying to use WinUSB (WDK 7) on XP with SP2. After a wee bit of
>> > work
>> > finally got the INF file to recognise and install the WinUSB and KMDF
>> > drivers
>> > when the device is connected. Everything works beautifully, my small
>> > test
>> > app
>> > communicates (via WinUSB) with my target hardware. So feeling dead
>> > chuffed
>> > with myself I asked my college to try out my new driver package (INF +
>> > coinstallers).
>> > And that's where it all went sour! His system is also XP SP2 but
>> > without
>> > WDK
>> > (shouldn't be necessary right). Driver install works fine, but when he
>> > fires
>> > up the test application it hangs on the 1st WinUSB_WritePipe call.
>> > After
>> > trying various things (examing installed driver, log files, registery,
>> > rebooting etc.) we install WDK on his system, and low and behold
>> > everything
>> > works suddenly.
>> >
>> > Now obviously, I've missed something, but I'm dammed if I can spot it.
>> > Anyone here come across a similar issue, or are the symtoms ringing any
>> > bells
>> > for anyone?
>> >
>> > Also, on a side issue, how can I find the control GUID for WinUSB to
>> > use
>> > tracelog to dig a bit deeper into what's happening when the WinUSB call
>> > hangs?
>> >
>> > thanks in advance
>>
>> .
>>

Hi,

sorry for not getting back on this sooner. As expected the enthusiasm level
for uninstalling WDK was low. It did however transpire that my collegue had
similar/worse issues (BSOD even) with a USB->Com adaptor on the same PC. In
short appears to be a HW issue there. If I discover anymore I'll post it here



"Doron Holan [MSFT]" wrote:

> you need to attach a debugger (windbg) and see exactly where the call is
> hanging
>
> d
>