How to change a KMDF sample code to a VC6.0 project?
in [Device Drivers]
|
From: Leafbanana on 13 Jan 2010 04:41 Hi, Is there any way to change a KMDF sample code to a VC6.0 project? I'm tryinh to change them to VC projects, like what I did to my old WDM drivers, but the system crashes at the call to WdfDriverCreate. I notices there is a "KMDF_VERSION_MAJOR=1" entry in the Source files of KMDF samples. Where should I add it into my VC project? I guess this is the reason why the system crashes at call to WdfDriverCreate.
From: Maxim S. Shatskih on 13 Jan 2010 11:17 > Is there any way to change a KMDF sample code to a VC6.0 project? Building drivers with VC 6.0 is not supported. After all, it has old and obsolete compiler and linker. Nothing strange KMDF does not work at all. You can use DDKBUILD.BAT to integrate the WDK's BUILD to the VC project as "custom build step". -- Maxim S. Shatskih Windows DDK MVP maxim(a)storagecraft.com http://www.storagecraft.com
From: Burkhardt Braun on 13 Jan 2010 14:52 Hello, On Jan 13, 9:41 am, Leafbanana <Leafban...(a)discussions.microsoft.com> wrote: > Hi, > > Is there any way to change a KMDF sample code to a VC6.0 project? although I donno if it works with VC6, you might take a look at VisualDDK under sourceforge.net > I'm tryinh to change them to VC projects, like what I did to my old WDM > drivers, but the system crashes at the call to WdfDriverCreate. > > I notices there is a "KMDF_VERSION_MAJOR=1" entry in the Source files of > KMDF samples. Where should I add it into my VC project? I guess this is the > reason why the system crashes at call to WdfDriverCreate. A stop-message in WdfDriverCreate is seemingly caused by a mismatch between the KMDF-Version in the SOURCES and the installed version or, related to that mismatch, you might install your driver with the wrong coinstaller- dll! Take care that all the required KMDF version numbers are correctly. Regards Burkhardt Braun
From: Doron Holan [MSFT] on 14 Jan 2010 17:41 it is blowing up in WdfDriverCreate (or at least the driver's jump table entry to the API in wdf0100.sys) b/c the jump table has not been initialized properly, not because of a version mismatch. if it were a version mismatch, his DriverEntry routine would have never been called. The WDK build environment takes care of putting the right pieces in place so that the jump table is initialized properly d -- This posting is provided "AS IS" with no warranties, and confers no rights. "Burkhardt Braun" <burkhardt.braun(a)gmx.net> wrote in message news:eb44ab74-1c45-4994-a6f9-9fabeb3421b7(a)m26g2000yqb.googlegroups.com... > Hello, > On Jan 13, 9:41 am, Leafbanana <Leafban...(a)discussions.microsoft.com> > wrote: >> Hi, >> >> Is there any way to change a KMDF sample code to a VC6.0 project? > although I donno if it works with VC6, you might take a look at > VisualDDK under sourceforge.net > >> I'm tryinh to change them to VC projects, like what I did to my old WDM >> drivers, but the system crashes at the call to WdfDriverCreate. >> >> I notices there is a "KMDF_VERSION_MAJOR=1" entry in the Source files of >> KMDF samples. Where should I add it into my VC project? I guess this is >> the >> reason why the system crashes at call to WdfDriverCreate. > A stop-message in WdfDriverCreate is seemingly caused by a mismatch > between > the KMDF-Version in the SOURCES and the installed version or, related > to that > mismatch, you might install your driver with the wrong coinstaller- > dll! > Take care that all the required KMDF version numbers are correctly. > Regards > Burkhardt Braun > > >
From: Burkhardt Braun on 14 Jan 2010 22:19 Hello Doron, On Jan 14, 10:41 pm, "Doron Holan [MSFT]" <doron.ho...(a)online.microsoft.com> wrote: > it is blowing up in WdfDriverCreate (or at least the driver's jump table > entry to the API in wdf0100.sys) b/c the jump table has not been initialized > properly, not because of a version mismatch. if it were a version mismatch, > his DriverEntry routine would have never been called. The WDK build > environment takes care of putting the right pieces in place so that the jump > table is initialized properly I have seen a jump to null in WdfDriverCreate. That disappeared with changing the KMDF versions in the build environment and not with any changes in the code. What is the reason, that the jump table was not intialized properly? BTW: the versions I used in a mix have been 1.5 and 1.7. Regards Burkhardt Braun
|
Pages: 1 Prev: Problems with text transforms Next: Message Compiler (MC.EXE) auto-generates "broken" code |