Re: safe way to upgrade KMDF from V1.0 to V1.1

Tech-Archive recommends: Fix windows errors by optimizing your registry



if you built the driver in the WDK, the driver requires KMDF v1.5. you
need to build the driver in the server sp1 ddk w/the v1.1 bits. this is why
your DriverEentry is never called.

you cannot use the chk coinstaller on any fre build, it is a limitation of
update.xe


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.


"hanzhu" <hanzhu@xxxxxxxxxx> wrote in message
news:uCu%23GxAyGHA.1304@xxxxxxxxxxxxxxxxxxxxxxx
I have a driver based on KMDFV1.0 StaticBus and it contained only a little
change. It worked well for the last few months. However, when I tried to
upgrade it to KMDFV1.1 today, it cannot been initialized. Device manager
told me the error code is 37. However, Devcon.exe returned success info for
install operation.
My steps as the following:
1) change the coinstaller to the corresponding one of V1.1(x86fre build)
2) update the .inx file according to the sample of KMDFV1.1
3) devcon install statbus.inf "root\statbus.inf"
4) sxe ld:statbus.sys hit, set a breakpoint on statbus!DriverEntry
5) The breakpoint was never hit.
6) devcon returned successfully, however device manager couldn't start the
device. I found out wdfldr.sys,wdf0010.sys and statbus.sys had been
unloaded.

several questions:
1) How can I upgrade it successfully?
2) I build the driver with WDK5483. I'm afraid the tools chain is not
installed successfully since it complains about "_objects.mac file time is
in the future". How can I validate it?
3) Is it safe use the check build KMDF coinstaller on a free build
win2k3sp1? There is something different if I use chkbuild coinstaller. I
can observe some info in Windbg and Devcon.exe failed when it returned.
Any hints and help will be appreciated.


.



Relevant Pages

  • safe way to upgrade KMDF from V1.0 to V1.1
    ... I have a driver based on KMDFV1.0 StaticBus and it contained only a little change. ... Devcon.exe returned success info for install operation. ... Is it safe use the check build KMDF coinstaller on a free build win2k3sp1? ...
    (microsoft.public.development.device.drivers)
  • Re: WdfConInstaller 1.7 does not seem to install on WinXP SP3
    ... It is unclear from your original email - is the KMDF echo driver working correctly on your system? ... Error 39 - this is probably an issue in your INF file that isn't copying the WDF coinstaller or other files properly to the system. ... I reproduced it by doing a fresh install of WinXP SP3 ...
    (microsoft.public.development.device.drivers)
  • self-signed NIC coinstaller prevent the nic from being disabled?
    ... We have a self-signed NIC miniport driver package ... which includes the driver, coinstaller, inf and catalog file. ... the commercial CA certificate for the sign self, ... The problem is after driver and coinstaller are installed on Windows 2003, ...
    (microsoft.public.development.device.drivers)
  • Re: self-signed NIC coinstaller prevent the nic from being disabled?
    ... We have a self-signed NIC miniport driver package(NDIS 5 for Windows 2003) ... the commercial CA certificate for the sign self, ... The problem is after driver and coinstaller are installed on Windows 2003, ...
    (microsoft.public.development.device.drivers)
  • Re: self-signed NIC coinstaller prevent the nic from being disable
    ... We have a self-signed NIC miniport driver package(NDIS 5 for Windows 2003) ... the commercial CA certificate for the sign self, ... The problem is after driver and coinstaller are installed on Windows 2003, ...
    (microsoft.public.development.device.drivers)