summaryrefslogtreecommitdiff
path: root/wmi
diff options
context:
space:
mode:
authorDen Delimarsky <[email protected]>2019-03-13 19:15:06 -0700
committerDen Delimarsky <[email protected]>2019-03-13 19:15:06 -0700
commitdbc7785c3a7ced56ecac6b5a9dfb81ef45dedac6 (patch)
tree2a8e1a39358b66cc2bc0d85e163956aafd5ccd16 /wmi
parentffeacc14932f98db4e7926825909a37d2b6d332f (diff)
Update manifests
Diffstat (limited to 'wmi')
-rw-r--r--wmi/wmiacpi/README.md2
-rw-r--r--wmi/wmisamp/README.md2
2 files changed, 2 insertions, 2 deletions
diff --git a/wmi/wmiacpi/README.md b/wmi/wmiacpi/README.md
index e70e9a2d..d3eb3338 100644
--- a/wmi/wmiacpi/README.md
+++ b/wmi/wmiacpi/README.md
@@ -44,4 +44,4 @@ To add the sample code to your ACPI bios and access through WMI:
1. Copy *Acpimof.dll* to %windir%\\system32 and add a value named "MofImagePath" under the HKEY\_LOCAL\_MACHINE\\CurrentControlSet\\Services\\WmiAcpi key. The contents of the value should be a path to the *Acpimof.dll* file.
1. Restart your computer. When Plug and Play (PnP) recognizes the new device with a pnpid of pnp0c14, it will install *Wmiacpi.sys* automatically and make the MOF resource in Acpimof.dll available to the WMI schema.
-Note that you do not need an INF file because Windows supplies an INF for the ACPI-WMI mapping driver device as part of the operating system.
+Note that you do not need an INF file because Windows supplies an INF for the ACPI-WMI mapping driver device as part of the operating system. \ No newline at end of file
diff --git a/wmi/wmisamp/README.md b/wmi/wmisamp/README.md
index fd8f3df4..e6960cde 100644
--- a/wmi/wmisamp/README.md
+++ b/wmi/wmisamp/README.md
@@ -47,4 +47,4 @@ WmiMofCk validates that the classes, properties, methods and events specified in
- If the -x parameter is specified, a text file is created that contains the text representation of the binary .mof data. This can be included in the source of the driver if the driver supports reporting the binary .mof via a WMI query rather than a resource on the driver image file.
- Usage: wmimofck -h\<C Header output file\> -x\<Hexdump output file\> -t\<VBScript test output file\> \<binary mof input file\>
-**Note** A byproduct of compiling the .mof file is a .vbs file. This is a VBScript file that is run from the command line on the target machine running the new device driver. It will cause WMI to query all data blocks and properties, and put the results into a .log file. This can be very useful for testing WMI support in your driver. For more sophisticated testing, the VBScript can be extended by hand.
+**Note** A byproduct of compiling the .mof file is a .vbs file. This is a VBScript file that is run from the command line on the target machine running the new device driver. It will cause WMI to query all data blocks and properties, and put the results into a .log file. This can be very useful for testing WMI support in your driver. For more sophisticated testing, the VBScript can be extended by hand. \ No newline at end of file