Hi Walter Oney
Thanks for the reply.
No, the problem happens only on Windows 98 . And also this problem comes
only when I open waveIn of USB audio device that is exposed from any
application. After I don’t receive the unload routine . If I open waveOut of
USB audio device there is no problem. If I just plug in and plug out then
also I get unload routine properly.
When the bus driver is not unloaded , I found the following modules are not
unloaded which are redbook.sys, swmidi.sys and wdmaud.sys along with the bus
driver. Through softice when I checked the device objects of each driver I
did not find any reference count or any IRP pending . But on the bus driver
the reference count is set to 1 . But in bus driver there is no IRP pending
or any resource unreleased.
Leaving the driver is ok , the problem is when I put the device back into
the system, the device instance is increasing. If the Audio device is not
installed for that instance it is going through standard mechanism of
looking for the drivers which is annoying .
Any ideas what else I can do ?
Thanks in advance
sri.
-----Original Message-----
From: Walter Oney [mailto:xxxxx@oneysoft.com]
Sent: Thursday, February 06, 2003 1:43 AM
To: NT Developers Interest List
Subject: [ntdev] Re: Doubt about IRP_MN_REMOVE_DEVICE
“Deevi, Srinivasa” wrote:
Loading of MS audio driver and working with it is fine. Now the problem is
,
I see a reference count in the child device object and active thread count
as zero . I found this value when I got IRP_MN_REMOVE_DEVICE for child DO.
This problem occurs only in Windows 98 . I don’t have any problem with
windows 2K and XP . Because of this our driver does not unload since there
is a reference to our child device object . For our base driver does not
have any reference count and active thread count.
If you’d said you were having this problem on all OS’s, I’d have guessed
that it was caused by the fact that KS.SYS likes to keep drivers loaded
just in case they might be needed again later today (it uses a timeout
value that keeps increasing as you continue to load and unload the same
driver). Is it possible that this really is what you’re experiencing
instead of a difference between OS’s?
If the timed delay before unloading feature isn’t the source of your
problem, you’ve probably just encountered a bug in 98. Since it will
almost surely not be fixed, my advice is to just ignore it and let your
driver stay in memory.
–
Walter Oney, Consulting and Training
Basic and Advanced Driver Programming Seminars
Now teaming with John Hyde for USB Device Engineering Seminars
Check out our schedule at http://www.oneysoft.com
You are currently subscribed to ntdev as: xxxxx@microtune.com
To unsubscribe send a blank email to xxxxx@lists.osr.com