diff options
Diffstat (limited to 'general')
24 files changed, 24 insertions, 24 deletions
diff --git a/general/DCHU/README.md b/general/DCHU/README.md index 65ca524d..ce107bb1 100644 --- a/general/DCHU/README.md +++ b/general/DCHU/README.md @@ -45,4 +45,4 @@ be installed in the following order: * `osrfx2_DCHU_extension` * `osrfx2_DCHU_component` -Technically the order of `osrfx2_DCHU_extension` and `osrfx2_DCHU_component` doesn't matter, but the software within `osrfx2_DCHU_component` will read the registry set by the extension to show that an extension INF's settings are applied *after* the base INF's.
\ No newline at end of file +Technically the order of `osrfx2_DCHU_extension` and `osrfx2_DCHU_component` doesn't matter, but the software within `osrfx2_DCHU_component` will read the registry set by the extension to show that an extension INF's settings are applied *after* the base INF's. diff --git a/general/PLX9x5x/README.md b/general/PLX9x5x/README.md index 432f53b2..bc1c1de3 100644 --- a/general/PLX9x5x/README.md +++ b/general/PLX9x5x/README.md @@ -34,4 +34,4 @@ The device is a PCI device with port, memory, interrupt and DMA resources. Devic To test the driver, run the PLX.EXE test application. -This sample driver is a minimal driver meant to demonstrate the usage of the Windows Driver Framework. It is not intended for use in a production environment.
\ No newline at end of file +This sample driver is a minimal driver meant to demonstrate the usage of the Windows Driver Framework. It is not intended for use in a production environment. diff --git a/general/SystemDma/wdm/README.md b/general/SystemDma/wdm/README.md index 4e2dbab6..23315a12 100644 --- a/general/SystemDma/wdm/README.md +++ b/general/SystemDma/wdm/README.md @@ -26,4 +26,4 @@ The sample consists of a legacy device driver and a Win32 console mode test appl ## Run the sample -To test this driver, copy the test app, SystemDmaApp.exe, and the driver to the same directory, and run the application. The application will automatically load the driver if it's not already loaded and interact with the driver. When you exit the app, the driver will be stopped, unloaded and removed. Because no system DMA controller exists for Windows which uses the advertised DRQ, the sample driver will not proceed any further than failing to acquire a system DMA adapter.
\ No newline at end of file +To test this driver, copy the test app, SystemDmaApp.exe, and the driver to the same directory, and run the application. The application will automatically load the driver if it's not already loaded and interact with the driver. When you exit the app, the driver will be stopped, unloaded and removed. Because no system DMA controller exists for Windows which uses the advertised DRQ, the sample driver will not proceed any further than failing to acquire a system DMA adapter. diff --git a/general/WinHEC 2017 Lab/README.md b/general/WinHEC 2017 Lab/README.md index 1ccabb8b..1d44f060 100644 --- a/general/WinHEC 2017 Lab/README.md +++ b/general/WinHEC 2017 Lab/README.md @@ -18,4 +18,4 @@ products: # WinHEC 2017 Lab -Toaster samples from the WinHEC 2017 Lab: Toaster Driver, PlugInToaster, and Toaster Support App. +Toaster samples from the WinHEC 2017 Lab: Toaster Driver, PlugInToaster, and Toaster Support App.
\ No newline at end of file diff --git a/general/cancel/README.md b/general/cancel/README.md index d74cd255..ff53246b 100644 --- a/general/cancel/README.md +++ b/general/cancel/README.md @@ -36,4 +36,4 @@ To test this driver, run Testapp.exe, which is a simple Win32 multithreaded cons `Usage: testapp <NumberOfThreads>` -**Note** The `NumberOfThreads` command-line parameter is limited to a maximum of 10 threads; the default value if no parameter is specified is 1. The main thread waits for user input. If you press Q, the application exits gracefully; otherwise, it exits the process abruptly and forces all the threads to be terminated and all pending I/O operations to be canceled. Other threads perform I/O asynchronously in a loop. After every overlapped read, the thread goes into an alertable sleep and wakes as soon as the completion routine runs, which occurs when the driver completes the read IRP. You should run multiple instances of the application to stress test the driver.
\ No newline at end of file +**Note** The `NumberOfThreads` command-line parameter is limited to a maximum of 10 threads; the default value if no parameter is specified is 1. The main thread waits for user input. If you press Q, the application exits gracefully; otherwise, it exits the process abruptly and forces all the threads to be terminated and all pending I/O operations to be canceled. Other threads perform I/O asynchronously in a loop. After every overlapped read, the thread goes into an alertable sleep and wakes as soon as the completion routine runs, which occurs when the driver completes the read IRP. You should run multiple instances of the application to stress test the driver. diff --git a/general/echo/kmdf/README.md b/general/echo/kmdf/README.md index 8a4acf4b..9dcdf601 100644 --- a/general/echo/kmdf/README.md +++ b/general/echo/kmdf/README.md @@ -94,4 +94,4 @@ This file merely redirects to the real makefile that is shared by all the driver Sources -Generic file that lists source files and all the build options.
\ No newline at end of file +Generic file that lists source files and all the build options. diff --git a/general/echo/umdf/README.md b/general/echo/umdf/README.md index 4d8cbbe4..c1ae545f 100644 --- a/general/echo/umdf/README.md +++ b/general/echo/umdf/README.md @@ -129,4 +129,4 @@ File Manifest **echodriver.ctl** - This file lists the WPP trace control GUID(s) for the sample driver. This file can be used with the tracelog command's -guid flag to enable the collection of these trace events within an established trace session. -- These GUIDs must remain in sync with the trace control GUIDs defined in internal.h.
\ No newline at end of file +- These GUIDs must remain in sync with the trace control GUIDs defined in internal.h. diff --git a/general/echo/umdf2/README.md b/general/echo/umdf2/README.md index 2ce91193..1a46cc34 100644 --- a/general/echo/umdf2/README.md +++ b/general/echo/umdf2/README.md @@ -83,4 +83,4 @@ As an alternative to building the driver sample in Visual Studio, you can build **msbuild /p:configuration="Release" /p:platform="Win32" umdf2echo.sln** -For more information about using MSBuild to build a driver package, see [Building a Driver](http://msdn.microsoft.com/en-us/library/windows/hardware/ff554644).
\ No newline at end of file +For more information about using MSBuild to build a driver package, see [Building a Driver](http://msdn.microsoft.com/en-us/library/windows/hardware/ff554644). diff --git a/general/echo/umdfSocketEcho/README.md b/general/echo/umdfSocketEcho/README.md index a3c60afa..579013e1 100644 --- a/general/echo/umdfSocketEcho/README.md +++ b/general/echo/umdfSocketEcho/README.md @@ -174,4 +174,4 @@ Note that independent threads perform the reads and writes in the echo test appl File Manifest ------------- -**Dllsup.cpp**: The DLL support code that provides the DLL's entry point and the single required export (DllGetClassObject).
\ No newline at end of file +**Dllsup.cpp**: The DLL support code that provides the DLL's entry point and the single required export (DllGetClassObject). diff --git a/general/event/README.md b/general/event/README.md index 3af1d845..0730c156 100644 --- a/general/event/README.md +++ b/general/event/README.md @@ -36,4 +36,4 @@ To run the test application, enter the following command in the command window: `C:\>event.exe <Delay> <0|1>` -The first command-line parameter, `Delay`, equals the time, in seconds, to delay the event signal. For the second command-line parameter, specify 0 for IRP-based notification and 1 for event-based notification.
\ No newline at end of file +The first command-line parameter, `Delay`, equals the time, in seconds, to delay the event signal. For the second command-line parameter, specify 0 for IRP-based notification and 1 for event-based notification. diff --git a/general/filehistory/README.md b/general/filehistory/README.md index 2e87f94b..43daa06e 100644 --- a/general/filehistory/README.md +++ b/general/filehistory/README.md @@ -34,4 +34,4 @@ The `path` command-line parameter is the path name of a storage device to use as `fhsetup \\server\share` -If the specified target is inaccessible, read-only, an invalid drive type (such as a CD), already being used for file history, or part of the protected namespace, the application fails the request and does not enable file history on the target.
\ No newline at end of file +If the specified target is inaccessible, read-only, an invalid drive type (such as a CD), already being used for file history, or part of the protected namespace, the application fails the request and does not enable file history on the target. diff --git a/general/ioctl/kmdf/README.md b/general/ioctl/kmdf/README.md index ed04bc3b..edfc3651 100644 --- a/general/ioctl/kmdf/README.md +++ b/general/ioctl/kmdf/README.md @@ -74,4 +74,4 @@ KmdfService = \<your driver service name here\>, \<driver service install subsec KmdfLibraryVersion = \<version bound to here, in Major.minor format\> -For example, for V1.0 KmdfLibraryVersion is "1.0"
\ No newline at end of file +For example, for V1.0 KmdfLibraryVersion is "1.0" diff --git a/general/ioctl/wdm/README.md b/general/ioctl/wdm/README.md index e1f9cf7c..76717ec8 100644 --- a/general/ioctl/wdm/README.md +++ b/general/ioctl/wdm/README.md @@ -28,4 +28,4 @@ The sample consists of a legacy device driver and a Win32 console test applicati # Run the sample -To test this driver, copy the test app, Ioctlapp.exe, and the driver to the same directory, and run the application. The application will automatically load the driver, if it's not already loaded, and interact with the driver. When you exit the application, the driver will be stopped, unloaded and removed.
\ No newline at end of file +To test this driver, copy the test app, Ioctlapp.exe, and the driver to the same directory, and run the application. The application will automatically load the driver, if it's not already loaded, and interact with the driver. When you exit the application, the driver will be stopped, unloaded and removed. diff --git a/general/obcallback/README.md b/general/obcallback/README.md index 75e12d1a..70434d2a 100644 --- a/general/obcallback/README.md +++ b/general/obcallback/README.md @@ -52,4 +52,4 @@ C:\> obcallbacktestctrl.exe -reject notepad (specifies that the string C:\> notepad (now you can start up "notepad.exe") Access is denied. -```
\ No newline at end of file +``` diff --git a/general/pcidrv/README.md b/general/pcidrv/README.md index 5b575667..94881da7 100644 --- a/general/pcidrv/README.md +++ b/general/pcidrv/README.md @@ -168,4 +168,4 @@ File | Description -----|------------ KMDF | Contains the driver. KMDF\HW | Contains hardware specific code. -TEST | Contains source of test application (MYPING).
\ No newline at end of file +TEST | Contains source of test application (MYPING). diff --git a/general/perfcounters/kcs/README.md b/general/perfcounters/kcs/README.md index fc916e55..347dc1bc 100644 --- a/general/perfcounters/kcs/README.md +++ b/general/perfcounters/kcs/README.md @@ -24,4 +24,4 @@ This module contains sample code to demonstrate how to provide counter data from This sample driver should not be used in a production environment. -The Microsoft Windows operating system allows system components and third parties to expose performance metrics in a standard way by using [Performance Counters](http://msdn.microsoft.com/en-us/library/windows/hardware/aa373083). Kernel-mode PCW providers are installed in the system as Performance Counter Library (PERFLIB) (Version 2 providers), which allows their counters to be browsed, and allows for data collection and instance enumeration. Consumers can query KM PCW providers by using PDH and PERFLIB Version 1 without any modification to the consumer code.
\ No newline at end of file +The Microsoft Windows operating system allows system components and third parties to expose performance metrics in a standard way by using [Performance Counters](http://msdn.microsoft.com/en-us/library/windows/hardware/aa373083). Kernel-mode PCW providers are installed in the system as Performance Counter Library (PERFLIB) (Version 2 providers), which allows their counters to be browsed, and allows for data collection and instance enumeration. Consumers can query KM PCW providers by using PDH and PERFLIB Version 1 without any modification to the consumer code. diff --git a/general/registry/regfltr/README.md b/general/registry/regfltr/README.md index e01af91d..141c1238 100644 --- a/general/registry/regfltr/README.md +++ b/general/registry/regfltr/README.md @@ -34,4 +34,4 @@ The RegFltr sample contains several examples of user-mode and kernel-mode regist 1. Unregisters the callback routine. 1. Verifies that the sample completed correctly. -The sample driver is a minimal driver that is not intended to be used on production systems. To keep the samples simple, the registry callback routines provided do not check for all possible situations and error conditions. This sample is designed to demonstrate typical scenarios and no other registry filtering driver is expected to be active.
\ No newline at end of file +The sample driver is a minimal driver that is not intended to be used on production systems. To keep the samples simple, the registry callback routines provided do not check for all possible situations and error conditions. This sample is designed to demonstrate typical scenarios and no other registry filtering driver is expected to be active. diff --git a/general/toaster/toastDrv/README.md b/general/toaster/toastDrv/README.md index 846180c8..423d258b 100644 --- a/general/toaster/toastDrv/README.md +++ b/general/toaster/toastDrv/README.md @@ -146,4 +146,4 @@ Doubly-linked-list code This file defines resource information for the ToastMon sample driver. #### UMDFToastMon.inf -Sample INF for installing the Skeleton driver to control a root enumerated device with a hardware ID of UMDFSamples\\ToastMon
\ No newline at end of file +Sample INF for installing the Skeleton driver to control a root enumerated device with a hardware ID of UMDFSamples\\ToastMon diff --git a/general/toaster/toastpkg/README.md b/general/toaster/toastpkg/README.md index b3ada632..a66cfe76 100644 --- a/general/toaster/toastpkg/README.md +++ b/general/toaster/toastpkg/README.md @@ -146,4 +146,4 @@ Doubly-linked-list code This file defines resource information for the ToastMon sample driver. #### UMDFToastMon.inf -Sample INF for installing the Skeleton driver to control a root enumerated device with a hardware ID of UMDFSamples\\ToastMon
\ No newline at end of file +Sample INF for installing the Skeleton driver to control a root enumerated device with a hardware ID of UMDFSamples\\ToastMon diff --git a/general/toaster/umdf2/README.md b/general/toaster/umdf2/README.md index 7b6eb8fb..b5cfa5f7 100644 --- a/general/toaster/umdf2/README.md +++ b/general/toaster/umdf2/README.md @@ -63,4 +63,4 @@ As an alternative to building the driver sample in Visual Studio, you can build **msbuild /p:configuration="Release" /p:platform="Win32" Umdf2toaster.sln** -For more information about using MSBuild to build a driver package, see [Building a Driver](http://msdn.microsoft.com/en-us/library/windows/hardware/ff554644).
\ No newline at end of file +For more information about using MSBuild to build a driver package, see [Building a Driver](http://msdn.microsoft.com/en-us/library/windows/hardware/ff554644). diff --git a/general/tracing/SystemTraceControl/README.md b/general/tracing/SystemTraceControl/README.md index 437f194c..a1a18c9c 100644 --- a/general/tracing/SystemTraceControl/README.md +++ b/general/tracing/SystemTraceControl/README.md @@ -24,4 +24,4 @@ The sample code provided shows how to start an [Event Tracing](http://msdn.micro You can process the Systemtrace.etl file using Tracerpt.exe, a command-line trace tool included in Windows that formats trace events. It also analyzes the events and generates summary reports. For more information about how to use this tool, see [Tracerpt](http://go.microsoft.com/fwlink/p/?linkid=179389) topic on the TechNet website. -You can also process the file using the [Windows Performance Toolkit](http://go.microsoft.com/fwlink/p/?linkid=250774) (WPT), which is available in the SDK.
\ No newline at end of file +You can also process the file using the [Windows Performance Toolkit](http://go.microsoft.com/fwlink/p/?linkid=250774) (WPT), which is available in the SDK. diff --git a/general/tracing/evntdrv/README.md b/general/tracing/evntdrv/README.md index ba3dcd65..13c9542f 100644 --- a/general/tracing/evntdrv/README.md +++ b/general/tracing/evntdrv/README.md @@ -72,4 +72,4 @@ Evntdrv registers as a provider by calling the [**EtwRegister**](http://msdn.mic ## Notes -If you are building the Eventdrv sample to test on a 64-bit version of Windows, you need to sign the driver. All 64-bit versions of Windows require driver code to have a digital signature for the driver to load. See [Signing a Driver](http://msdn.microsoft.com/en-us/library/windows/hardware/ff554809) and [Signing a Driver During Development and Testing](http://msdn.microsoft.com/en-us/library/windows/hardware/hh967733). You might also need to configure the test computer so that it can load test-signed kernel mode code, see [The TESTSIGNING Boot Configuration Option](http://msdn.microsoft.com/en-us/library/windows/hardware/ff553484) and [**BCDEdit /set**](http://msdn.microsoft.com/en-us/library/windows/hardware/ff542202).
\ No newline at end of file +If you are building the Eventdrv sample to test on a 64-bit version of Windows, you need to sign the driver. All 64-bit versions of Windows require driver code to have a digital signature for the driver to load. See [Signing a Driver](http://msdn.microsoft.com/en-us/library/windows/hardware/ff554809) and [Signing a Driver During Development and Testing](http://msdn.microsoft.com/en-us/library/windows/hardware/hh967733). You might also need to configure the test computer so that it can load test-signed kernel mode code, see [The TESTSIGNING Boot Configuration Option](http://msdn.microsoft.com/en-us/library/windows/hardware/ff553484) and [**BCDEdit /set**](http://msdn.microsoft.com/en-us/library/windows/hardware/ff542202). diff --git a/general/tracing/tracedriver/README.md b/general/tracing/tracedriver/README.md index 67e27fc2..400452fd 100644 --- a/general/tracing/tracedriver/README.md +++ b/general/tracing/tracedriver/README.md @@ -70,4 +70,4 @@ Also, because it is not a Plug and Play driver, Tracedrv does not demonstrate tr Tracedrv demonstrates the basic elements required for software tracing. It does not demonstrate more advanced tracing techniques, such as writing customized tracing calls (variations of [**DoTraceMessage**](http://msdn.microsoft.com/en-us/library/windows/hardware/ff544918)), or the use of WMI calls for software tracing. -If you are building the Tracedrv sample to test on a 64-bit version of Windows, you need to sign the driver. All 64-bit versions of Windows require driver code to have a digital signature for the driver to load. See [Signing a Driver](http://msdn.microsoft.com/en-us/library/windows/hardware/ff554809) and [Signing a Driver During Development and Testing](http://msdn.microsoft.com/en-us/library/windows/hardware/hh967733). You might also need to configure the test computer so that it can load test-signed kernel mode code, see [The TESTSIGNING Boot Configuration Option](http://msdn.microsoft.com/en-us/library/windows/hardware/ff553484) and [**BCDEdit /set**](http://msdn.microsoft.com/en-us/library/windows/hardware/ff542202).
\ No newline at end of file +If you are building the Tracedrv sample to test on a 64-bit version of Windows, you need to sign the driver. All 64-bit versions of Windows require driver code to have a digital signature for the driver to load. See [Signing a Driver](http://msdn.microsoft.com/en-us/library/windows/hardware/ff554809) and [Signing a Driver During Development and Testing](http://msdn.microsoft.com/en-us/library/windows/hardware/hh967733). You might also need to configure the test computer so that it can load test-signed kernel mode code, see [The TESTSIGNING Boot Configuration Option](http://msdn.microsoft.com/en-us/library/windows/hardware/ff553484) and [**BCDEdit /set**](http://msdn.microsoft.com/en-us/library/windows/hardware/ff542202). diff --git a/general/umdfSkeleton/README.md b/general/umdfSkeleton/README.md index 5191bafb..6936cfdf 100644 --- a/general/umdfSkeleton/README.md +++ b/general/umdfSkeleton/README.md @@ -20,4 +20,4 @@ products: This sample demonstrates how to use version 1 of the User-Mode Driver Framework to write a minimal driver. -The Skeleton driver will successfully load on a device (either root enumerated or a real hardware device) but does not support any I/O operations.
\ No newline at end of file +The Skeleton driver will successfully load on a device (either root enumerated or a real hardware device) but does not support any I/O operations. |