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

Doron,
I changed it to KMDFV1.5 cointaller. Everything seems the same as before. :-(
Any more tips?

Doron Holan [MS] дµÀ:
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

.

Relevant Pages

  • Re: WDK build environment...
    ... Doron Holan wrote: ... Please do not send e-mail directly to this alias. ... Sorry only if he builds with the Windows 2000 environment. ... Windows 2k/XP/2k3 Filesystem and Driver Consulting ...
    (microsoft.public.win32.programmer.kernel)
  • Re: KMDF NDIS <==> USB driver
    ... Doron Holan wrote: ... What is the most resemble DDK/WDK sample for this kind of driver? ... I look at topics from this group and found a thread on KMDF NDIS ... with the NDIS driver communicating to the USB as ...
    (microsoft.public.development.device.drivers)
  • Re: Disable default action for DIF_PROPERTYCHANGE
    ... Doron Holan wrote: ... no matter if the bit is not reported ... disappears from the Action Menu (in the Device Manager window). ... When driver resets this bit, the "disable" item reappears in the Action ...
    (microsoft.public.development.device.drivers)
  • Re: ASM vs HLL : absurd war
    ... |> No limitation like this with ASM. ... From the Athlon Optimisation Guide: ... | MS didn't bother with that driver after they got it working. ... |> but my favourite are the AMDs (fast shift, fast bit, and cheaper). ...
    (alt.lang.asm)
  • Re: XWLAN 2.12
    ... I am using Willibald Meyer's GenMac wrapper driver with my Intel ... >> Will it be possible for the user to choose the hotspot in a future ... > limitation of the wlan utility. ...
    (comp.os.os2.networking.misc)
Loading