I confirmed that we ran this scenario. We are rerunning it now to see
if a reboot is required or not.
Thx
d
– I can spell, I just can’t type.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@seagate.com
Sent: Friday, May 12, 2006 12:18 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] KMDF 1.1 difficulties
SetupApi was not much help at all. Most of the information I got was
from the WinDbg console and Wdf01001.log. I did not look at SetupAct
since from the doncs it looked like what was in the WDF log was in the
SetupAct log.
I still have the logs if you want them.
Gary G. Little
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Friday, May 12, 2006 1:29 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] KMDF 1.1 difficulties
We have done it. One work of advice is that is that you cannot remove
the old coinstaller if there is an installed devnode that is referencing
it. To remove/uninstall the v1.0 version of the device, the v1.0
coinstaller must be present (this is an OS requirement).
Does setupapi/act.log give any indication on what the failure was?
d
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@seagate.com
Sent: Friday, May 12, 2006 9:51 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] KMDF 1.1 difficulties
Doron,
Kudos to all for the KMDF 1.1 release. But … and it seems there always
is one … why is it so damnably difficult to install version x+1 over
version x? I installed 1.1 and then did the obvious things I knew would
need to be done: changed the name of the co-installer in the INF file,
rebuilt the driver(s) with the new WDF, built new install media with new
INF, SYS, and WDF DLL files and then did an install.
I spent nearly 2 hours beating my head against a wall, with messages in
the logs telling me that there was a checked/free problem. I tried both
free and checked versions of the dll with no affect … always the same
messages. So I manually killed the 01000 versions of the co-installer
and deleted the registry entry. Same result in WDF log, WinDbg and
SetupAct.
After doing all that in desperation I did a reboot. That worked
…
well SOMETHING I did before the reboot worked.
Why can’t I simply rebuild my frigging driver and install the damn thing
without having to do anatomically impossible things to install a new
version of KMDF? It begs the question … did the KMDF team install 1.1
built drivers over existing 1.0 drivers?
Oh yeah … while bloodying my forehead against that brick wall, I did
encounter a gotcha in the docs. It state KmdfLibraryVersion = 1.0, but
the samples show KmdfLibraryVersion = 1.1.
If I’m the only one that has this problem, or if I missed it in the
docs, I’ll quietly go back to my blankie.
The personal opinion of
Gary G. Little
—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer