KMDF and error 127 (procedure not found).

NTDEV
1

Hi guys

I’m trying to build my very first KMDF driver and (of course) having problems. The problem is that when I “net start” my driver it fails with “procedure not found” error.
I’ve built and installed ECHO sample from the DDK (with all this WDF framework co-installing) and it runs. So WDF has installed OK and all these WDF loader - related imports from my driver should also get resolved. Or so I assumed.
So, can anyone give me any advice on what do I miss and (hopefully) how to fix this?

TIA,

Vladimir

2

Did you try depends.exe for your sys-file ?

3

This was somewhat miraculous. The problem disappeared after I removed kernel32.lib, ntdll.lib and wdmsec.lib from my linker options (they were leftovers from my “template” sources file). Yeah, I know, it was sloppy :wink: However, there were no linker errors / warnings no nothing that would suggest any problems. Anyway, it’s solved.

4

Why would you expect the linker to give you a warning? It doesn’t know
about user and kernel mode, it just knows how to resolve imports,
regardless of where they come from.

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@gmail.com
Sent: Tuesday, May 01, 2007 6:25 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] KMDF and error 127 (procedure not found).

This was somewhat miraculous. The problem disappeared after I removed
kernel32.lib, ntdll.lib and wdmsec.lib from my linker options (they were
leftovers from my “template” sources file). Yeah, I know, it was sloppy
:wink: However, there were no linker errors / warnings no nothing that
would suggest any problems. Anyway, it’s solved.

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

5

I was expecting it to warn me that some routines have implementations in more than one libraries that are linking to my driver. At least I think that this what caused y problem: some routine got linked to my .sys from a “wrong” library.