reactos/drivers/base/nmidebug/nmidebug.rc

#include <winver.h>
#include <ntverp.h>

#define VER_FILETYPE             VFT_DRV
#define VER_FILESUBTYPE          VFT2_DRV_SYSTEM
#define VER_FILEDESCRIPTION_STR  "NMI debug driver"
#define VER_INTERNALNAME_STR     "NMIDEBUG.SYS"
#define VER_ORIGINALFILENAME_STR "NMIDEBUG.SYS"
#define VER_LANGNEUTRAL

#include <common.ver>
NMI Support Patch 13: [NMIDEBUG]: Add new NMI Debug driver. It registers an NMI callback on startup. The callback does nothing useful at the moment, but you can enhance it to add all sorts of debugging information that would otherwise be unavailable in situations such as an interrupt storm, IRQL hang, etc. When you send an NMI, such as by using QEMU, you should see the driver print a string. svn path=/trunk/; revision=44878 2010-01-02 04:50:08 +00:00			`#include <winver.h>`
			`#include <ntverp.h>`

[DRIVERS] * Improve resource files. CORE-7637 svn path=/trunk/; revision=61132 2013-11-28 22:19:35 +00:00			`#define VER_FILETYPE VFT_DRV`
			`#define VER_FILESUBTYPE VFT2_DRV_SYSTEM`
			`#define VER_FILEDESCRIPTION_STR "NMI debug driver"`
			`#define VER_INTERNALNAME_STR "NMIDEBUG.SYS"`
			`#define VER_ORIGINALFILENAME_STR "NMIDEBUG.SYS"`
NMI Support Patch 13: [NMIDEBUG]: Add new NMI Debug driver. It registers an NMI callback on startup. The callback does nothing useful at the moment, but you can enhance it to add all sorts of debugging information that would otherwise be unavailable in situations such as an interrupt storm, IRQL hang, etc. When you send an NMI, such as by using QEMU, you should see the driver print a string. svn path=/trunk/; revision=44878 2010-01-02 04:50:08 +00:00			`#define VER_LANGNEUTRAL`

[DRIVERS] * Improve resource files. CORE-7637 svn path=/trunk/; revision=61132 2013-11-28 22:19:35 +00:00			`#include <common.ver>`
No results found.