Prev: Bluetooth DDI
Next: Trick serenum into detecting a device
From: Denny on 28 Mar 2006 13:55
Hi,
Do anybody knows why tracview is not working under amd64. I try to run it
after installing 2003 DDK SP1.The 64 bit version of tarceview is asking for
msvcr70.dll; I cant find this version of dll not in my system and also on the
installed dkk. I'm still stuck at my problem with the driver is not getting
initalized on HCT under USB description test. The DDK release notes says an
error about launching those test in a 64 bit platform; which not exactly the
same I'm experiencing.If anybody can suggest some ideas and steps that will
be greatly appriciated.
thanks,
--Denny


"Denny" wrote:

> Hi Marco,
> Here is more on my testing. I wasn't able to get run any of the bus
> analyzers from the site lvr.com; On XP64 most of them wont run or they make
> my USB controller non functional. I find one more thing on my XP 32 bit;
> while I run the USB description using HCT 12.1.0.1,even though the test was a
> success it leaves my driver in memory and after completion of the test Device
> manager shows that it cannot load the driver since a previous image is there
> in memory(code 38). This also happens only if I start the test fresh. If I
> restart the meachine my driver comes back and without reinitalize if I run
> the test again, this time the driver comes back without any problem after the
> test. I ran the driver verifier and PoolTag during the test and there is no
> resource allocation issues. My driver is a KMDF based driver (I used most of
> the code from osrusbfx2 sample) Is there any known issues there for KMDF
> under 64 bit platform??
> thanks,
> --Denny
>
> "Marc Reinig" wrote:
>
> > Bus analyzers are independent of the host system, they just monitor the bus
> > and know nothing of the host.
> >
> > Visit http://www.lvr.com
> >
> > Marco
> > ________________________
> > Marc Reinig
> > UCO/Lick Observatory
> > Laboratory for Adaptive Optics
> >
> > "Denny" <Denny(a)discussions.microsoft.com> wrote in message
> > news:CC6B5CDD-FF31-4652-A573-9A4CCE7EAE7D(a)microsoft.com...
> > > Thanks for the suggestion.I cannot use a KB since I don't have an extra
> > > mechine to lookup. Can you please suggest me a bus analyzer available for
> > > 64
> > > bit XP and tell what I have to look for?
> > > Thanks,
> > > --Denny
> > >
> > >
> > > "Marc Reinig" wrote:
> > >
> > >> Have you hooked up a USB bus analyzer and/or a kernel debugger to see
> > >> what
> > >> is going on?
> > >>
> > >> --
> > >> Marco
> > >> ________________________
> > >> Marc Reinig
> > >> UCO/Lick Observatory
> > >> Laboratory for Adaptive Optics
> > >>
> > >> "Denny" <Denny(a)discussions.microsoft.com> wrote in message
> > >> news:C91BF1DB-ED26-430F-A791-1A9F69D5E622(a)microsoft.com...
> > >> > Hi,
> > >> > I have a usb driver ported to 64-bit and I'm tryng to get it HCT
> > >> > certified.
> > >> > The driver giving me issues on USb Descriptor,Address descriptor
> > >> > tests.Basically the driver gets unloaded when the test starts and the
> > >> > test
> > >> > hangs for ever. I got it passed successfully on all tests on the 32-bit
> > >> > platform(XP SP2) ; My installation is XP 64-bit SP1. The driver works
> > >> > fine
> > >> > with native 32-bit application on the same 64-bit platform. I also get
> > >> > the
> > >> > verifier test passed. The above tests not writing any error logs , the
> > >> > only
> > >> > thing I can see in the logs is initalizing and if I terminated it
> > >> > forcefully,
> > >> > it says terminated. Any help will be very much appriciated.I tried the
> > >> > device
> > >> > on mutiple ports of the test meachine but the result is same.
> > >> > Thanks
> > >>
> > >>
> > >> .
> > >>
> >
> >
> >
From: Denny on 3 Apr 2006 23:29
Hope somebody will follow-up on this topic. I was able to run debugview while
running the HCT test for my WDF driver. What I can see is that while running
the USB descriptor test, the test remove the driver (I think an attempt to
reinitalize ) and after that it never comes back. It just hung like there is
no device present. After aborting the test if I try to replug the device it
says there is a prevoius image of the driver is still there in memory. I can
unplug and replug the device as many time as I want with out any issues under
normal circumstances on the same amd system. I think it seems like a problem
with the hct and KMDF. My driver is a simple usb driver for a device with an
interrupt endpoint and a control endpoint.There is no specific memory
allocations in the device initialization, so I can't suspect resource leak
also pooltag shows allocations are ok and driver verfier pass the device
using the same HCT(12.0.1); any body have any better idea to dig further...
thanks,
--Denny

From: Maxim S. Shatskih on 4 Apr 2006 04:47
Remember: you must delete your symlinks and deactivate your device
interfaces in SURPRISE_REMOVAL path and not in REMOVE_DEVICE. Doing otherwise
leads to a collision if the app holds an open handle to the device, and you
unplug it and replug back.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim(a)storagecraft.com
http://www.storagecraft.com

"Denny" <Denny(a)discussions.microsoft.com> wrote in message
news:B08BA486-F757-4F19-A401-FF4CD90972C3(a)microsoft.com...
> Hope somebody will follow-up on this topic. I was able to run debugview while
> running the HCT test for my WDF driver. What I can see is that while running
> the USB descriptor test, the test remove the driver (I think an attempt to
> reinitalize ) and after that it never comes back. It just hung like there is
> no device present. After aborting the test if I try to replug the device it
> says there is a prevoius image of the driver is still there in memory. I can
> unplug and replug the device as many time as I want with out any issues under
> normal circumstances on the same amd system. I think it seems like a problem
> with the hct and KMDF. My driver is a simple usb driver for a device with an
> interrupt endpoint and a control endpoint.There is no specific memory
> allocations in the device initialization, so I can't suspect resource leak
> also pooltag shows allocations are ok and driver verfier pass the device
> using the same HCT(12.0.1); any body have any better idea to dig further...
> thanks,
> --Denny
>

From: Denny on 4 Apr 2006 09:19
Hi Maxim,
Thanks to remind me that.But my driver is a WDF driver and I don't handle
any IOCTL's other than my device specific Read/Write.My driver is build upon
the OSR usb sample in the KMDF1.0 and the only modification I did is to
handle the IOCTL handling for the vendor specific read and write
--Denny


"Maxim S. Shatskih" wrote:

> Remember: you must delete your symlinks and deactivate your device
> interfaces in SURPRISE_REMOVAL path and not in REMOVE_DEVICE. Doing otherwise
> leads to a collision if the app holds an open handle to the device, and you
> unplug it and replug back.
>
> --
> Maxim Shatskih, Windows DDK MVP
> StorageCraft Corporation
> maxim(a)storagecraft.com
> http://www.storagecraft.com
>
> "Denny" <Denny(a)discussions.microsoft.com> wrote in message
> news:B08BA486-F757-4F19-A401-FF4CD90972C3(a)microsoft.com...
> > Hope somebody will follow-up on this topic. I was able to run debugview while
> > running the HCT test for my WDF driver. What I can see is that while running
> > the USB descriptor test, the test remove the driver (I think an attempt to
> > reinitalize ) and after that it never comes back. It just hung like there is
> > no device present. After aborting the test if I try to replug the device it
> > says there is a prevoius image of the driver is still there in memory. I can
> > unplug and replug the device as many time as I want with out any issues under
> > normal circumstances on the same amd system. I think it seems like a problem
> > with the hct and KMDF. My driver is a simple usb driver for a device with an
> > interrupt endpoint and a control endpoint.There is no specific memory
> > allocations in the device initialization, so I can't suspect resource leak
> > also pooltag shows allocations are ok and driver verfier pass the device
> > using the same HCT(12.0.1); any body have any better idea to dig further...
> > thanks,
> > --Denny
> >
>
>
From: Doron Holan [MS] on 4 Apr 2006 20:49
we (the KMDF team) are investigating this issue.

thx
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.


"Denny" <Denny(a)discussions.microsoft.com> wrote in message
news:0CD588CF-5CE8-4326-8F1E-A8FF45D7B42B(a)microsoft.com...
> Hi Maxim,
> Thanks to remind me that.But my driver is a WDF driver and I don't handle
> any IOCTL's other than my device specific Read/Write.My driver is build
> upon
> the OSR usb sample in the KMDF1.0 and the only modification I did is to
> handle the IOCTL handling for the vendor specific read and write
> --Denny
>
>
> "Maxim S. Shatskih" wrote:
>
>> Remember: you must delete your symlinks and deactivate your device
>> interfaces in SURPRISE_REMOVAL path and not in REMOVE_DEVICE. Doing
>> otherwise
>> leads to a collision if the app holds an open handle to the device, and
>> you
>> unplug it and replug back.
>>
>> --
>> Maxim Shatskih, Windows DDK MVP
>> StorageCraft Corporation
>> maxim(a)storagecraft.com
>> http://www.storagecraft.com
>>
>> "Denny" <Denny(a)discussions.microsoft.com> wrote in message
>> news:B08BA486-F757-4F19-A401-FF4CD90972C3(a)microsoft.com...
>> > Hope somebody will follow-up on this topic. I was able to run debugview
>> > while
>> > running the HCT test for my WDF driver. What I can see is that while
>> > running
>> > the USB descriptor test, the test remove the driver (I think an attempt
>> > to
>> > reinitalize ) and after that it never comes back. It just hung like
>> > there is
>> > no device present. After aborting the test if I try to replug the
>> > device it
>> > says there is a prevoius image of the driver is still there in memory.
>> > I can
>> > unplug and replug the device as many time as I want with out any issues
>> > under
>> > normal circumstances on the same amd system. I think it seems like a
>> > problem
>> > with the hct and KMDF. My driver is a simple usb driver for a device
>> > with an
>> > interrupt endpoint and a control endpoint.There is no specific memory
>> > allocations in the device initialization, so I can't suspect resource
>> > leak
>> > also pooltag shows allocations are ok and driver verfier pass the
>> > device
>> > using the same HCT(12.0.1); any body have any better idea to dig
>> > further...
>> > thanks,
>> > --Denny
>> >
>>
>>


First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: Bluetooth DDI
Next: Trick serenum into detecting a device