Hello, Can anyone point me in the right direction ?
I compiled my driver using the w2k3 environment.
I am using WDF 1.7 and when i install my driver on LH it installs ok.
When i install the same driver on W2k3 Server I get this error in the .log file
WdfCoInstaller: [09/17/2007 19:05.11.120] ReadComponents: WdfSection for Driver Service mydriver using KMDF lib version Major 0x1, minor 0x7
WdfCoInstaller: [09/17/2007 19:05.11.140] Extract resources: could not find resources WDFCAB_RESOURCE, error error(1814) The specified resource name cannot be found in the image file.
I then modified the .inf file to load the 1.1 wdfcoinstaller instead of the 1.7 wdfcoinstaller and now it loads but i get a #I163 Device not started: Device has problem: 0x25: CM_PROB_FAILED_DRIVER_ENTRY. error. Not suprised by this
error but has anyone run into this problem with w2k3 and 1.7 ? I have read some where that there were problems with coinstallers not including something for older windows but i thought they were fixed in 1.7. BTW this on a Itanium processor.
As already answered on microsoft.public.development.device.drivers:
Right now WDF 1.7 only works for Longhorn. This is supposed to be fixed in
the next version of the beta WDK. You need to go back to WDF 1.5 (the
Vista WDK) to run on older OS’es
wrote in message news:xxxxx@ntdev… > Hello, Can anyone point me in the right direction ? > > I compiled my driver using the w2k3 environment. > I am using WDF 1.7 and when i install my driver on LH it installs ok. > When i install the same driver on W2k3 Server I get this error in the > .log file > > ---------- > WdfCoInstaller: [09/17/2007 19:05.11.090] DIF_INSTALLDEVICE: > Pre-Processing > > WdfCoInstaller: [09/17/2007 19:05.11.120] ReadComponents: WdfSection for > Driver Service mydriver using KMDF lib version Major 0x1, minor 0x7 > > WdfCoInstaller: [09/17/2007 19:05.11.140] Extract resources: could not > find resources WDFCAB_RESOURCE, error error(1814) The specified resource > name cannot be found in the image file. > > ---------------- > > I then modified the .inf file to load the 1.1 wdfcoinstaller instead of > the 1.7 wdfcoinstaller and now it loads but i get a #I163 Device not > started: Device has problem: 0x25: CM_PROB_FAILED_DRIVER_ENTRY. error. > Not suprised by this > error but has anyone run into this problem with w2k3 and 1.7 ? I have > read some where that there were problems with coinstallers not including > something for older windows but i thought they were fixed in 1.7. BTW > this on a Itanium processor. > > thanks > Mel > >
Hello, Can anyone point me in the right direction ?
I compiled my driver using the w2k3 environment.
I am using WDF 1.7 and when i install my driver on LH it installs ok.
When i install the same driver on W2k3 Server I get this error in the .log file
Right. As the release notes say, the KMDF 1.7 beta works only on Server
2008. You’ll have to go back to 1.5 for earlier systems, or wait for
another release of 1.7.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Hate to be the bearer of bad tidings (but it’s part of what I get paid for, I s’pose)- the next WDK (Srv2K8 RC / Vista SP1 Beta, IIRC) is still going to have what we call the “lean” coinstallers.
I had thought otherwise, and may have been the source of what turned out to be misinformation.
Also, a caution- even if we do ship the “fat” coinstallers in a WDK, they will still be beta software- you cannot redistribute (and thus ship) WDF 1.7 until the “gold” 6001 WDK is released to you.
Right now WDF 1.7 only works for Longhorn. This is supposed to be fixed in
the next version of the beta WDK.