Re: safe way to upgrade KMDF from V1.0 to V1.1
- From: "Gennady Mayko" <GMayko@xxxxxxxxx>
- Date: 25 Aug 2006 03:03:49 -0700
I changed it to KMDFV1.5 cointaller. Everything seems the same as--
before. :-(
Any more tips?
I have the similar problem with my drivers when I upgraded them from
KMDF 1.0 to 1.1.
I used regmon utility from sysinternals to log KMDF co-installer
accesses to the registry, and I manually restore those that were
absent, in order to correctly install and start new 1.1 driver.
It seems that KMDF co-installer expects some entries in the registry to
pre-exist and failed when it does not find them. If this is true, it
may be useful to change it's algorithm and create those entries during
it's work if, for some reason, they are absent. Or, at least, clearly
describe this situation to the user in some way.
Regards,
Gennady Mayko.
.
- References:
- safe way to upgrade KMDF from V1.0 to V1.1
- From: hanzhu
- Re: safe way to upgrade KMDF from V1.0 to V1.1
- From: Doron Holan [MS]
- Re: safe way to upgrade KMDF from V1.0 to V1.1
- From: hanzhu
- safe way to upgrade KMDF from V1.0 to V1.1
- Prev by Date: Nonstandard symbolic link to a disk volume
- Next by Date: Re: DMA adapters vs Map registers and Contiguous memory
- Previous by thread: Re: safe way to upgrade KMDF from V1.0 to V1.1
- Next by thread: Mark IRP pending in KMDF driver
- Index(es):
Relevant Pages
|