wdk

Is it possible to pass Windows HLK test for drivers compiled with WDK7.1

由 心已入冬 提交于 2019-12-08 00:35:07
问题 We are facing critical situation about signing our drivers. I am wondering, is it possible to pass windows HLK test successfully for the drivers which are compiled with WDK 7.1 Because we were able to sign them using HCK but now after some bug fixes, the new version has to pass HLK test for windows 10 support, which can't ! Any advice is highly appreciated. Thank you very much. 回答1: The answer is Yes. The best thing you can do is just compile your drivers using wdk10 using VS2015 keep target

Windows biometric framework sample umdf driver: This device cannot start. (Code 10)

由 橙三吉。 提交于 2019-12-07 23:40:29
I am trying to run a windows biometric driver sample and I am naive to driver development I have changed the hardware id in the inx file and rebuilt the driver project and installed the resulting driver on my Windows 10 Pro version 1803. I am using a Fingerprint Morpho Device 1300 E3 Driver got installed successfully but there is one error showing up: This device cannot start. (Code 10) The specified request is not a valid operation for the target device. I reviewed the file C:\Windows\INF\setupapi.dev.log It shows the next warnings: sig: {_VERIFY_FILE_SIGNATURE} 10:13:03.130 sig: Key =

Where can I find a minimalistic WDM driver template with source code in it? [closed]

由 心不动则不痛 提交于 2019-12-07 21:43:14
问题 Closed. This question is off-topic. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 5 years ago . I came across kernel-mode drivers with very little experience. Here's what I am trying to do: Have a user-mode application that loads the driver. Have the user-mode application write to it, in order to send it an instruction. Have the driver send the RDMSR instruction to the Intel chip. Return the results back

Driver load/unload fails if WinDbg attached with breakpoint

由 时光毁灭记忆、已成空白 提交于 2019-12-07 19:18:17
问题 I just started with driver development. For some experiments with loading, unloading and debugging I have written the following simple driver: #include <ntddk.h> void DriverUnload(PDRIVER_OBJECT pDriverObject) { UNREFERENCED_PARAMETER(pDriverObject); DbgPrint("Driver unloading\n"); } NTSTATUS DriverEntry( PDRIVER_OBJECT DriverObject, PUNICODE_STRING RegistryPath) { UNREFERENCED_PARAMETER(DriverObject); UNREFERENCED_PARAMETER(RegistryPath); DriverObject->DriverUnload = DriverUnload; DbgPrint(

Windows virtual mouse driver

由 五迷三道 提交于 2019-12-07 10:23:23
问题 I am developing a KMDF virtual mouse driver. The general idea is a KMDF root enumerated non-filter driver which will be able to send output reports to the mouse and keyboard driver stacks. My driver is already working and sending requests to other driver stacks, but with no result. Report types and packet formats are pretty undocumented on Microsoft resources. There are no information about which data and to which device I need to send in order to move the mouse pointer, simulate clicks (with

Retrieving PCI coordinates by Windows' API (user mode)

由 微笑、不失礼 提交于 2019-12-07 05:28:37
问题 Is there a way to obtain PCI coordinates (bus/slot/function numbers) of devices by using Windows c/c++ API (e.g PnP Configuration Manager API)? I already know how to do it in kernel mode, I need an user-mode solution. My target system is Windows XP-32 bit. 回答1: I've eventually found a simple solution (it was just a matter of digging into MSDN). This minimal code finds the device's PCI coordinates in terms of bus/slot/function: DWORD bus, addr, slot, func; HDEVINFO h; // Obtained by

How to understand the “NTSTATUS”, “NT_SUCCESS” typedef in windows ddk?

由 落爺英雄遲暮 提交于 2019-12-07 04:51:12
问题 Two questions: 1. In "ntdef.h" the NTSTATUS is defined as follow: typedef __success(return >= 0) LONG NTSTATUS; what the hell is the "__success(return >= 0)"? 2. In "ntstatus.h", STATUS_SUCCESS is defined to 0. #define STATUS_SUCCESS ((NTSTATUS)0x00000000L) // ntsubauth But the NT_SUCCESS macro in "ntdef.h" is: #define NT_SUCCESS(Status) (((NTSTATUS)(Status)) >= 0) Shouldn't it be "Status == 0" ? 回答1: __success is an "Advanced Annotation" defined in SpecStrings_strict.h, which defines it as

How to get Audio Formats supported by physical device (WinAPI, Windows)

由 懵懂的女人 提交于 2019-12-06 11:21:19
问题 I have an audio device (a USB microphone) and I want to find out what audio formats it supports natively (bit depth & sample rate), on OS X there is a nice kAudioStreamPropertyAvailablePhysicalFormats Core Audio property, but I fail to find something similar on Windows. I know there is this question Windows Core Audio Api get all supported formats on capture device but The answer is bad... and I'm not limited with windows Core Audio APIs, I need any way. Windows itself somehow knows it, so

Overloading operator new with WDK

由 喜欢而已 提交于 2019-12-06 09:26:45
i'm building a simple code in wdk in "native subsystem" i have a library that overload new and delete operator here is the code: #include<ntddk.h&gt #define HEAP_ZERO_MEMORY 0x00000008 #define HEAP_GROWABLE 0x00000002 typedef NTSTATUS (NTAPI * PRTL_HEAP_COMMIT_ROUTINE)( IN PVOID Base, IN OUT PVOID *CommitAddress, IN OUT PSIZE_T CommitSize ); typedef struct _RTL_HEAP_PARAMETERS { ULONG Length; SIZE_T SegmentReserve; SIZE_T SegmentCommit; SIZE_T DeCommitFreeBlockThreshold; SIZE_T DeCommitTotalFreeThreshold; SIZE_T MaximumAllocationSize; SIZE_T VirtualMemoryThreshold; SIZE_T InitialCommit; SIZE_T

Is it possible to pass Windows HLK test for drivers compiled with WDK7.1

由 夙愿已清 提交于 2019-12-06 07:31:22
We are facing critical situation about signing our drivers. I am wondering, is it possible to pass windows HLK test successfully for the drivers which are compiled with WDK 7.1 Because we were able to sign them using HCK but now after some bug fixes, the new version has to pass HLK test for windows 10 support, which can't ! Any advice is highly appreciated. Thank you very much. The answer is Yes. The best thing you can do is just compile your drivers using wdk10 using VS2015 keep target OS as windows7 install it on windows10 and test it using HLK. Or secondly you know that drivers are forward
订阅 wdk