|
From: 江民 on 12 May 2008 06:50 In my driver, i call the function export by a kernel mode dll, while this dll also include a kernel mode dll! (Driver ==> kernel mode DLL(A) ==> kernel mode DLL(B)). Now when os call the driver, the OS will blue screen. The bugcheck is the kernel mode DLL does not have DriverEntry! this is the message: STOP: c0000263 {Driver Entry Point Not Found} The \SystemRoot\System32\DRIVERS\vtminivt.sys device driver could not locate the entry point _vsnwprintf in driver ntoskrnl.exe. Break instruction exception - code 80000003 (first chance) I must keep this calling relation(Must keep the two DLL) Does any body know how to solve this problem? Thanks very much
From: Doron Holan [MSFT] on 12 May 2008 12:51 read the error. it does not say that you do not have a DriverEntry, it is saying that you have an unresolved import > The \SystemRoot\System32\DRIVERS\vtminivt.sys device driver could not > locate the entry point _vsnwprintf in driver ntoskrnl.exe. i am guessing you started to use or are already using ntstrsafe.h and trying to load your driver on win2k. Add the following before #including ntstrsafe.h #define NTSTRSAFE_LIB or add it to your sources file's C_DEFINES, C_DEFINES=$(C_DEFINES) /DNTSTRSAFE_LIB this will put the impl of _vsnwprintf into your driver via ntstrsafe.lib 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. "江民" <dongy117(a)gmail.com> wrote in message news:b045fba6-a5c8-4ec1-9a13-c58ca9e0b8af(a)n1g2000prb.googlegroups.com... > In my driver, i call the function export by a kernel mode dll, while > this dll also include a kernel mode dll! > > (Driver ==> kernel mode DLL(A) ==> kernel mode DLL(B)). Now when os > call the driver, the OS will blue screen. > > The bugcheck is the kernel mode DLL does not have DriverEntry! > > this is the message: > > STOP: c0000263 {Driver Entry Point Not Found} > The \SystemRoot\System32\DRIVERS\vtminivt.sys device driver could not > locate the entry point _vsnwprintf in driver ntoskrnl.exe. > Break instruction exception - code 80000003 (first chance) > > I must keep this calling relation(Must keep the two DLL) > > Does any body know how to solve this problem? Thanks very much
From: 江民 on 12 May 2008 22:01 Hi Doron: Thank you very much! The problem has been solved by you problem!
From: 江民 on 12 May 2008 22:43 Hi Doron: I also have a question. Why the same driver used fine in XP and Vista, but in 2000, it will report this problem? Is it caused by _vsnwprintf problem? thanks.
From: Doron Holan [MSFT] on 13 May 2008 00:08 XP and later exported vsnwprintf which means that you can use ntstrsafe.h in non lib form can be used on these platforms. ntstrsafe.lib was created specifically to support win2k and this missing export 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. "江民" <dongy117(a)gmail.com> wrote in message news:6407b0f7-e003-4c4a-8c40-036321088a82(a)h1g2000prh.googlegroups.com... > Hi Doron: > I also have a question. Why the same driver used fine in XP > and Vista, but in 2000, it will report this problem? Is it caused by > _vsnwprintf problem? thanks.
|
Next
|
Last
Pages: 1 2 Prev: serial ioctl problem Next: How to set NIC to promiscuous mode from FilterHook driver |