From 41c29cb92feff490270b4ce31f67d7baddecc457 Mon Sep 17 00:00:00 2001 From: Den Delimarsky Date: Wed, 13 Mar 2019 21:54:14 -0700 Subject: [PATCH] Update README files --- filesys/cdfs/README.md | 2 +- filesys/fastfat/README.md | 2 +- filesys/miniFilter/MetadataManager/README.md | 2 +- filesys/miniFilter/NameChanger/README.md | 2 +- filesys/miniFilter/avscan/README.md | 2 +- filesys/miniFilter/cancelSafe/README.md | 2 +- filesys/miniFilter/cdo/README.md | 2 +- filesys/miniFilter/change/README.md | 2 +- filesys/miniFilter/ctx/README.md | 2 +- filesys/miniFilter/delete/README.md | 2 +- filesys/miniFilter/minispy/README.md | 2 +- filesys/miniFilter/nullFilter/README.md | 2 +- filesys/miniFilter/passThrough/README.md | 2 +- filesys/miniFilter/scanner/README.md | 2 +- filesys/miniFilter/simrep/README.md | 2 +- filesys/miniFilter/swapBuffers/README.md | 2 +- general/DCHU/README.md | 2 +- general/PLX9x5x/README.md | 2 +- general/SystemDma/wdm/README.md | 2 +- general/WinHEC 2017 Lab/README.md | 2 +- general/cancel/README.md | 2 +- general/echo/kmdf/README.md | 2 +- general/echo/umdf/README.md | 2 +- general/echo/umdf2/README.md | 2 +- general/echo/umdfSocketEcho/README.md | 2 +- general/event/README.md | 2 +- general/filehistory/README.md | 2 +- general/ioctl/kmdf/README.md | 2 +- general/ioctl/wdm/README.md | 2 +- general/obcallback/README.md | 2 +- general/pcidrv/README.md | 2 +- general/perfcounters/kcs/README.md | 2 +- general/registry/regfltr/README.md | 2 +- general/toaster/toastDrv/README.md | 2 +- general/toaster/toastpkg/README.md | 2 +- general/toaster/umdf2/README.md | 2 +- general/tracing/SystemTraceControl/README.md | 2 +- general/tracing/evntdrv/README.md | 2 +- general/tracing/tracedriver/README.md | 2 +- general/umdfSkeleton/README.md | 2 +- gnss/ReadMe.md | 8 ++++---- gpio/samples/README.md | 2 +- hid/firefly/README.md | 2 +- hid/hclient/README.md | 2 +- hid/hidusbfx2/README.md | 2 +- hid/vhidmini2/README.md | 2 +- input/kbfiltr/README.md | 2 +- input/layout/README.md | 2 +- input/moufiltr/README.md | 2 +- network/config/bindview/README.md | 2 +- network/modem/fakemodem/README.md | 2 +- network/ndis/extension/README.md | 2 +- network/ndis/filter/README.md | 2 +- network/ndis/mux/README.md | 2 +- network/ndis/ndisprot/6x/README.md | 2 +- network/ndis/ndisprot_kmdf/README.md | 2 +- network/ndis/netvmini/6x/README.md | 2 +- network/radio/HidSwitchDriverSample/README.md | 2 +- network/radio/RadioManagerSample/README.md | 2 +- network/trans/WFPSampler/README.md | 2 +- network/trans/ddproxy/README.md | 2 +- network/trans/inspect/README.md | 2 +- network/trans/msnmntr/README.md | 2 +- network/trans/stmedit/README.md | 2 +- network/wlan/WDI/README.md | 2 +- network/wlan/ihvsampleui/README.md | 2 +- network/wsk/echosrv/README.md | 2 +- nfc/NfcCxSample/README.md | 2 +- nfp/net/inc/README.md | 2 +- pofx/PEP/README.md | 2 +- pofx/UMDF2/README.md | 2 +- pofx/WDF/README.md | 2 +- pos/drivers/MagneticStripeReader/README.md | 2 +- pos/drivers/barcodescanner/README.md | 2 +- print/OEM Printer Customization Plug-in Samples/README.md | 2 +- print/SampleOpenXPS/README.md | 2 +- print/SampleXPS/README.md | 2 +- print/SimplePipelineFilter/README.md | 2 +- print/autoconfig/README.md | 2 +- print/cpsuisam/README.md | 2 +- .../v4PrintDriverSamples/PrinterExtensionSample/README.md | 2 +- .../v4PrintDriver-ConstraintScript/README.md | 2 +- 82 files changed, 85 insertions(+), 85 deletions(-) diff --git a/filesys/cdfs/README.md b/filesys/cdfs/README.md index d7e5b86cf..81159c2b7 100644 --- a/filesys/cdfs/README.md +++ b/filesys/cdfs/README.md @@ -24,4 +24,4 @@ Cdfs is a read-only file system that addresses various issues such as accessing ## Universal Windows Driver Compliant -This sample builds a Universal Windows Driver. It uses only APIs and DDIs that are included in OneCoreUAP. \ No newline at end of file +This sample builds a Universal Windows Driver. It uses only APIs and DDIs that are included in OneCoreUAP. diff --git a/filesys/fastfat/README.md b/filesys/fastfat/README.md index 5994fe0a3..865cb9e1d 100644 --- a/filesys/fastfat/README.md +++ b/filesys/fastfat/README.md @@ -58,4 +58,4 @@ You can build a driver from the command line using the Visual Studio Command Pro Installation ------------ -No INF file is provided with this sample because the *fastfat* file system driver (fastfat.sys) is already part of the Windows operating system. You can build a private version of this file system and use it as a replacement for the native driver. \ No newline at end of file +No INF file is provided with this sample because the *fastfat* file system driver (fastfat.sys) is already part of the Windows operating system. You can build a private version of this file system and use it as a replacement for the native driver. diff --git a/filesys/miniFilter/MetadataManager/README.md b/filesys/miniFilter/MetadataManager/README.md index b8838c3c6..dd7bf6df8 100644 --- a/filesys/miniFilter/MetadataManager/README.md +++ b/filesys/miniFilter/MetadataManager/README.md @@ -34,4 +34,4 @@ Similarly, the minifilter might close its metadata file if it sees an explicit F The metadata minifilter also handles the case when a snapshot of its volume object is being taken. In this scenario, the minifilter acquires a shared exclusive lock on the metadata resource object while calling the callback that corresponds to the pre-device control operation for IOCTL\_VOLSNAP\_FLUSH\_AND\_HOLD\_WRITES. The lock is later released in the callback that corresponds to the post-device control operation for IOCTL\_VOLSNAP\_FLUSH\_AND\_HOLD\_WRITES. The lock is acquired to prevent any modifications on the metadata file while the snapshot is being taken. -For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide. +For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide. \ No newline at end of file diff --git a/filesys/miniFilter/NameChanger/README.md b/filesys/miniFilter/NameChanger/README.md index 210eff25d..94c24899a 100644 --- a/filesys/miniFilter/NameChanger/README.md +++ b/filesys/miniFilter/NameChanger/README.md @@ -98,4 +98,4 @@ F:\\X\\Y After the minifilter attaches, the "B" subdirectory of F:\\A is no longer visible. Its contents now appear under the "Y" subdirectory of F:\\X. -For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide. +For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide. \ No newline at end of file diff --git a/filesys/miniFilter/avscan/README.md b/filesys/miniFilter/avscan/README.md index 6fbfa1162..9750e0aab 100644 --- a/filesys/miniFilter/avscan/README.md +++ b/filesys/miniFilter/avscan/README.md @@ -22,4 +22,4 @@ The AvScan minifilter is a transaction-aware file scanner. This is an example fo ## Universal Windows Driver Compliant -This sample builds a Universal Windows Driver. It uses only APIs and DDIs that are included in OneCoreUAP. \ No newline at end of file +This sample builds a Universal Windows Driver. It uses only APIs and DDIs that are included in OneCoreUAP. diff --git a/filesys/miniFilter/cancelSafe/README.md b/filesys/miniFilter/cancelSafe/README.md index cdebf8fc8..a81d971e1 100644 --- a/filesys/miniFilter/cancelSafe/README.md +++ b/filesys/miniFilter/cancelSafe/README.md @@ -29,4 +29,4 @@ Design and Operation The *CancelSafe* minifilter initializes a cancel-safe queue when it is attached to a volume. When the minifilter is deployed, it monitors read operations that are passing through the I/O stack. If the read operation is being performed on a file named csqdemo.txt, it is queued onto the cancel-safe queue. Queued operations are completed after a brief pause through a separate worker thread that is running in system context. -For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide. \ No newline at end of file +For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide. diff --git a/filesys/miniFilter/cdo/README.md b/filesys/miniFilter/cdo/README.md index 41379efaf..8feba54e0 100644 --- a/filesys/miniFilter/cdo/README.md +++ b/filesys/miniFilter/cdo/README.md @@ -31,4 +31,4 @@ Design and Operation When the CDO minifilter is deployed, it creates a CDO object named "FileSystem\\Filters\\CdoSample" in the Microsoft Windows object namespace and enables applications to open it and perform certain operations on it. -For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide. +For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide. \ No newline at end of file diff --git a/filesys/miniFilter/change/README.md b/filesys/miniFilter/change/README.md index 38c004680..12e8e17ab 100644 --- a/filesys/miniFilter/change/README.md +++ b/filesys/miniFilter/change/README.md @@ -31,4 +31,4 @@ The primary tasks of the filter for tracking a transacted file are the following ## Universal Windows Driver Compliant -This sample builds a Universal Windows Driver. It uses only APIs and DDIs that are included in OneCoreUAP. +This sample builds a Universal Windows Driver. It uses only APIs and DDIs that are included in OneCoreUAP. \ No newline at end of file diff --git a/filesys/miniFilter/ctx/README.md b/filesys/miniFilter/ctx/README.md index 19cd94f8e..904a35686 100644 --- a/filesys/miniFilter/ctx/README.md +++ b/filesys/miniFilter/ctx/README.md @@ -28,4 +28,4 @@ This sample builds a Universal Windows Driver. It uses only APIs and DDIs that a The *Ctx* minifilter demonstrates how to attach and remove contexts from instances, files, steams, and stream handles. *Ctx* attaches a context whenever one of these objects is created. While attaching a context to a file, the sample also creates a stream and stream handle context. All contexts are ultimately deleted by the filter manager using the callback function that the *Ctx* minifilter provides. -For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide. +For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide. \ No newline at end of file diff --git a/filesys/miniFilter/delete/README.md b/filesys/miniFilter/delete/README.md index e2c5a5ef2..96e91cdc2 100644 --- a/filesys/miniFilter/delete/README.md +++ b/filesys/miniFilter/delete/README.md @@ -30,4 +30,4 @@ The *delete* minifilter illustrates how to detect deletion of files and streams. **Note** Because of the way in which the Windows operating system deletes files, it is not possible for the minifilter to detect in advance that a file or stream will be deleted. The minifilter can only detect operations that may cause a deletion, and then determine if the deletion took place after the operation completes. -For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide. +For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide. \ No newline at end of file diff --git a/filesys/miniFilter/minispy/README.md b/filesys/miniFilter/minispy/README.md index 522b10805..aff8825a7 100644 --- a/filesys/miniFilter/minispy/README.md +++ b/filesys/miniFilter/minispy/README.md @@ -30,4 +30,4 @@ Minispy consists of both user-mode and kernel-mode components. The kernel-mode c To observe I/O activity on a device, you must explicitly attach Minispy to that device by using the Minispy user-mode component. Similarly, you can request Minispy to stop logging data for a particular device. -For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide. +For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide. \ No newline at end of file diff --git a/filesys/miniFilter/nullFilter/README.md b/filesys/miniFilter/nullFilter/README.md index 803ef8ce1..b7e52d445 100644 --- a/filesys/miniFilter/nullFilter/README.md +++ b/filesys/miniFilter/nullFilter/README.md @@ -28,4 +28,4 @@ This sample builds a Universal Windows Driver. It uses only APIs and DDIs that a The *NullFilter* minifilter is a simple minifilter that registers itself with the filter manager for no callback operations. -For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide. +For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide. \ No newline at end of file diff --git a/filesys/miniFilter/passThrough/README.md b/filesys/miniFilter/passThrough/README.md index 88481c69e..2e319a68c 100644 --- a/filesys/miniFilter/passThrough/README.md +++ b/filesys/miniFilter/passThrough/README.md @@ -28,4 +28,4 @@ This sample builds a Universal Windows Driver. It uses only APIs and DDIs that a The *PassThrough* minifilter does not have any real functionality. For each type of I/O operation, the same pre and post callback functions are called. These callback functions simply forward the I/O request to the next filter on the stack. -For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide. +For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide. \ No newline at end of file diff --git a/filesys/miniFilter/scanner/README.md b/filesys/miniFilter/scanner/README.md index 8bc56be87..da01b38ef 100644 --- a/filesys/miniFilter/scanner/README.md +++ b/filesys/miniFilter/scanner/README.md @@ -30,4 +30,4 @@ The Scanner minifilter comprises both kernel-mode and user-mode components. The The kernel-mode component scans files with specific extensions only. The file is first scanned on a successful open. If the file was opened with write access, it is scanned again before a close. Scanning is also performed on data that is about to be written to a file. Writes will be rejected if any occurrences of a "foul" string are found in the data. If a "foul" string is detected during the closing of a file, a debug message is printed. -For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide. +For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide. \ No newline at end of file diff --git a/filesys/miniFilter/simrep/README.md b/filesys/miniFilter/simrep/README.md index b6775082b..366818ed7 100644 --- a/filesys/miniFilter/simrep/README.md +++ b/filesys/miniFilter/simrep/README.md @@ -32,4 +32,4 @@ SimRep decides to reparse according to a mapping. The mapping is made up of a "N It is important to note that SimRep does not take long and short names into account. It literally does a string comparison to detect overlap with the mapping paths. SimRep also handles IRP\_MJ\_NETWORK\_QUERY\_OPEN. Because network query opens are FastIo operations, they cannot be reparsed. This means network query opens which need to be redirected must be failed with FLT\_PREOP\_DISALLOW\_FASTIO. This will cause the Io Manager to reissue the open as a regular IRP based open. To prevent performance regression, SimRep only fails network query opens which need to be reparsed. -For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide. \ No newline at end of file +For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide. diff --git a/filesys/miniFilter/swapBuffers/README.md b/filesys/miniFilter/swapBuffers/README.md index ae73c5898..729e79661 100644 --- a/filesys/miniFilter/swapBuffers/README.md +++ b/filesys/miniFilter/swapBuffers/README.md @@ -28,4 +28,4 @@ This sample builds a Universal Windows Driver. It uses only APIs and DDIs that a The *SwapBuffers* minifilter introduces a new buffer before a read/write or directory control operations. The corresponding operation is then performed on the new buffer instead of the buffer that was originally provided. After the operation completes, the contents of the new buffer are copied back in to the original buffer. -For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide. \ No newline at end of file +For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide. diff --git a/general/DCHU/README.md b/general/DCHU/README.md index 65ca524d7..ce107bb11 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 432f53b21..bc1c1de3e 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 4e2dbab6e..23315a124 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 1ccabb8b7..1d44f0609 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 d74cd255e..ff53246bb 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 ` -**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 8a4acf4b6..9dcdf601d 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 4d8cbbe4c..c1ae545f7 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 2ce91193e..1a46cc349 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 a3c60afaa..579013e19 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 3af1d8455..0730c1565 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 <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 2e87f94bd..43daa06e8 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 ed04bc3b7..edfc3651e 100644 --- a/general/ioctl/kmdf/README.md +++ b/general/ioctl/kmdf/README.md @@ -74,4 +74,4 @@ KmdfService = \, \ -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 e1f9cf7cb..76717ec81 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 75e12d1ac..70434d2a4 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 5b575667f..94881da70 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 fc916e556..347dc1bc0 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 e01af91d8..141c1238a 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 846180c8f..423d258b7 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 b3ada6323..a66cfe76f 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 7b6eb8fb5..b5cfa5f7b 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 437f194c8..a1a18c9c9 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 ba3dcd65f..13c9542fe 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 67e27fc2a..400452fd7 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 5191bafba..6936cfdf0 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. diff --git a/gnss/ReadMe.md b/gnss/ReadMe.md index 6d37480d8..a40b6d0c5 100644 --- a/gnss/ReadMe.md +++ b/gnss/ReadMe.md @@ -85,14 +85,14 @@ Customer should validate their driver after customizing it. ### Test method 3 -* Test the [Windows Geolocation API](https://docs.microsoft.com/en-us/windows/desktop/locationapi/windows-location-api-portal) layer on real apps. +* Test the [Windows Geolocation API](https://docs.microsoft.com/windows/desktop/locationapi/windows-location-api-portal) layer on real apps. * Get current location by clicking on "Show my location" from the In-box Windows Maps app. * Run the tracking scenario from the [Geolocation Sample app](https://github.com/Microsoft/Windows-universal-samples/tree/master/Samples/Geolocation). * Get current location by clicking on "Start" from GPS Satellite app in Windows Store. ## Resources -* [GNSS DDI reference](https://docs.microsoft.com/en-us/windows-hardware/drivers/ddi/content/gnssdriver/index) -* [Getting started with Windows drivers](https://docs.microsoft.com/en-us/windows-hardware/drivers/gettingstarted) -* [Windows Driver Kit documentation](https://docs.microsoft.com/en-us/windows-hardware/drivers) +* [GNSS DDI reference](https://docs.microsoft.com/windows-hardware/drivers/ddi/content/gnssdriver/index) +* [Getting started with Windows drivers](https://docs.microsoft.com/windows-hardware/drivers/gettingstarted) +* [Windows Driver Kit documentation](https://docs.microsoft.com/windows-hardware/drivers) * [NMEA format documentation](http://navspark.mybigcommerce.com/content/NMEA_Format_v0.1.pdf) \ No newline at end of file diff --git a/gpio/samples/README.md b/gpio/samples/README.md index d404819a8..f5c4fdfac 100644 --- a/gpio/samples/README.md +++ b/gpio/samples/README.md @@ -27,4 +27,4 @@ Minifilter | Sample Description SimGpio | The files in this sample contain the source code for a GPIO controller driver that communicates with GpioClx through the GpioClx device driver interface (DDI). The GPIO controller driver is written for a hypothetical memory-mapped GPIO controller (simgpio). The code is meant to be purely instructional. An ASL file illustrates how to specify a GPIO interrupt and I/O descriptor in the ACPI firmware. SimGpio_I2C | The files in this sample contain the source code for a GPIO controller driver that communicates with GpioClx through the GpioClx DDI. In contrast to the SimGpio sample, the GPIO controller in this sample is not memory-mapped. The GPIO controller driver is written for a hypothetical GPIO controller that resides on an I2C bus (simgpio_i2c). The code is meant to be purely instructional. An ASL file illustrates how to specify a GPIO interrupt and I/O descriptor in the ACPI firmware. SimDevice\kmdf | The purpose of this sample is to show how a driver opens a device and performs I/O operations on a GPIO controller in kernel mode. Additionally, this sample demonstrates how the driver connects to a GPIO interrupt resource. The ASL file illustrates how to specify a GPIO interrupt and I/O descriptor in the ACPI firmware. -SimDevice\umdf | The purpose of this sample is to show how a driver opens a device and performs I/O operations on a GPIO controller in user mode. Additionally, this sample demonstrates how the driver connects to a GPIO interrupt resource. The ASL file illustrates how to specify a GPIO interrupt and I/O descriptor in the ACPI firmware. +SimDevice\umdf | The purpose of this sample is to show how a driver opens a device and performs I/O operations on a GPIO controller in user mode. Additionally, this sample demonstrates how the driver connects to a GPIO interrupt resource. The ASL file illustrates how to specify a GPIO interrupt and I/O descriptor in the ACPI firmware. \ No newline at end of file diff --git a/hid/firefly/README.md b/hid/firefly/README.md index 2a5e4aa85..d5db239db 100644 --- a/hid/firefly/README.md +++ b/hid/firefly/README.md @@ -90,4 +90,4 @@ The sample consists of: - Driver (firefly.sys): The Firefly driver is an upper device filter driver for the mouse driver (mouhid.sys). Firefly is a generic filter driver based on the toaster filter driver sample available in the WDK. During start device, the driver registers a WMI class (FireflyDeviceInformation). The user mode application connects to the WMI namespace (root\\wmi) and opens this class using COM interfaces. Then the application can make requests to read ("get") or change ("set") the current value of the TailLit data value from this class. In response to a set WMI request, the driver opens the HID collection using IoTarget and sends [**IOCTL\_HID\_GET\_COLLECTION\_INFORMATION**](http://msdn.microsoft.com/en-us/library/windows/hardware/ff541092) and [**IOCTL\_HID\_GET\_COLLECTION\_DESCRIPTOR**](http://msdn.microsoft.com/en-us/library/windows/hardware/ff541089) requests to get the preparsed data. The driver then calls [**HidP\_GetCaps**](http://msdn.microsoft.com/en-us/library/windows/hardware/ff539715) using the preparsed data to retrieve the capabilities of the device. After getting the capabilities of the device, the driver creates a feature report to set or clear the feature that causes the light to toggle. - Library (luminous.lib): The sources for this file are located in the \\hid\\firefly\\lib folder. You will need to build the library before using it. This library is shared by the WDM and WDF samples. All the interfaces required to access the WMI is defined in this library and exposed as CLuminous class. - Application (flicker.exe): The sources for this file are located in the \\hid\\firefly\\app folder. You will need to build the application before using it. This application is shared by the WDM and WDF samples. The application links to luminous.lib to open the WMI interfaces and send set requests to toggle the light. -- Sauron (sauron.dll): The sources for this file are located in the \\hid\\firefly\\sauron folder. You will need to build this dll before using it. The library is shared by the WDM and WDF samples. Sauron is a Windows Media Player visualization DLL, and is based on a sample from the Windows Media Player SDK kit. By using this DLL, you can cause the mouse lights to blink to the beats of the music. \ No newline at end of file +- Sauron (sauron.dll): The sources for this file are located in the \\hid\\firefly\\sauron folder. You will need to build this dll before using it. The library is shared by the WDM and WDF samples. Sauron is a Windows Media Player visualization DLL, and is based on a sample from the Windows Media Player SDK kit. By using this DLL, you can cause the mouse lights to blink to the beats of the music. diff --git a/hid/hclient/README.md b/hid/hclient/README.md index 5ee07fa30..bff1f89b6 100644 --- a/hid/hclient/README.md +++ b/hid/hclient/README.md @@ -26,4 +26,4 @@ You will find this sample useful if you need to develop an application that comm [Human Input Devices Design Guide](http://msdn.microsoft.com/en-us/library/windows/hardware/ff539952) -[Human Input Devices Reference](http://msdn.microsoft.com/en-us/library/windows/hardware/ff539956) \ No newline at end of file +[Human Input Devices Reference](http://msdn.microsoft.com/en-us/library/windows/hardware/ff539956) diff --git a/hid/hidusbfx2/README.md b/hid/hidusbfx2/README.md index 983b051f7..3bb3e4c49 100644 --- a/hid/hidusbfx2/README.md +++ b/hid/hidusbfx2/README.md @@ -275,4 +275,4 @@ Hidusbfx2.rc | Resource file for the driver Hidusbfx2.inx | INX file for the driver Sources | WDK sources file Makefile | WDK build environment make file -Makefile.inc | A makefile that defines custom build actions, including the conversion of the .INX file into a .INF file \ No newline at end of file +Makefile.inc | A makefile that defines custom build actions, including the conversion of the .INX file into a .INF file diff --git a/hid/vhidmini2/README.md b/hid/vhidmini2/README.md index dae9decf5..b99eb796f 100644 --- a/hid/vhidmini2/README.md +++ b/hid/vhidmini2/README.md @@ -30,4 +30,4 @@ The sample demonstrates how to communicate with an HID minidriver from an HID cl [Human Input Devices Reference](http://msdn.microsoft.com/en-us/library/windows/hardware/ff539956) -[UMDF HID Minidriver IOCTLs](http://msdn.microsoft.com/en-us/library/windows/hardware/hh463977) \ No newline at end of file +[UMDF HID Minidriver IOCTLs](http://msdn.microsoft.com/en-us/library/windows/hardware/hh463977) diff --git a/input/kbfiltr/README.md b/input/kbfiltr/README.md index 84ab12ef5..0343f7660 100644 --- a/input/kbfiltr/README.md +++ b/input/kbfiltr/README.md @@ -117,4 +117,4 @@ Testing To use the test application provided with the sample, it must be copied to the target computer manually. Save the kbftest.exe file from the folder where the build result is placed (for example, exe\\Debug). This file is copied somewhere on the target, possibly where the driver package files are located. The test application is the executed on the target computer in a Command Prompt using **kbftest** as the command. -**Tip** To avoid DLL dependencies for kbftext.exe, and the need to copy additional files, select the statically linked run-time library when building. \ No newline at end of file +**Tip** To avoid DLL dependencies for kbftext.exe, and the need to copy additional files, select the statically linked run-time library when building. diff --git a/input/layout/README.md b/input/layout/README.md index 0d1a4d7cd..52af37c76 100644 --- a/input/layout/README.md +++ b/input/layout/README.md @@ -95,4 +95,4 @@ Loading the Sample In order to load the layout DLLs, you may need to turn to the Regional and Language Options application in Control Panel and add input locales that use the keyboard layouts you installed. -You may also choose to do it programmatically. LoadKeyboardLayout API can be used to load the keyboard layouts. To activate the keyboard layout, you may choose to specify KLF\_ACTIVATE flag to LoadKeyboardLayout API, or you may need to call ActivateKeyboardLayout API. \ No newline at end of file +You may also choose to do it programmatically. LoadKeyboardLayout API can be used to load the keyboard layouts. To activate the keyboard layout, you may choose to specify KLF\_ACTIVATE flag to LoadKeyboardLayout API, or you may need to call ActivateKeyboardLayout API. diff --git a/input/moufiltr/README.md b/input/moufiltr/README.md index d97ac21a0..3a8483c6f 100644 --- a/input/moufiltr/README.md +++ b/input/moufiltr/README.md @@ -34,4 +34,4 @@ This sample is installed via an .inf file. The .inf file included in this sample The .inf file must install the class driver (Mouclass) and the port driver (i8042prt, Mouhid, Sermouse, etc.) by using Msmouse.inf and the INF directives "Needs" and "Include". -The .inf file must add the correct registry values for the class and port driver, as well as using the new directives. \ No newline at end of file +The .inf file must add the correct registry values for the class and port driver, as well as using the new directives. diff --git a/network/config/bindview/README.md b/network/config/bindview/README.md index 641a4398d..fdb27529b 100644 --- a/network/config/bindview/README.md +++ b/network/config/bindview/README.md @@ -20,4 +20,4 @@ products: The Bindview sample demonstrates how to use INetCfg APIs to enumerate, install, uninstall, bind and unbind network components. -For more information on the INetCfg interface, see [Network Configuration Interfaces](http://msdn.microsoft.com/en-us/library/windows/hardware/ff559080). \ No newline at end of file +For more information on the INetCfg interface, see [Network Configuration Interfaces](http://msdn.microsoft.com/en-us/library/windows/hardware/ff559080). diff --git a/network/modem/fakemodem/README.md b/network/modem/fakemodem/README.md index 2cedd97bb..aa1399589 100644 --- a/network/modem/fakemodem/README.md +++ b/network/modem/fakemodem/README.md @@ -22,4 +22,4 @@ The Fakemodem sample demonstrates a simple controller-less modem driver. This dr ## Universal Windows Driver Compliant -This sample builds a Universal Windows Driver. It uses only APIs and DDIs that are included in OneCoreUAP. \ No newline at end of file +This sample builds a Universal Windows Driver. It uses only APIs and DDIs that are included in OneCoreUAP. diff --git a/network/ndis/extension/README.md b/network/ndis/extension/README.md index 305579278..554f4af0b 100644 --- a/network/ndis/extension/README.md +++ b/network/ndis/extension/README.md @@ -32,4 +32,4 @@ MsForwardExt is a basic forwarding extension filter driver that is implemented b Use the *install.cmd* script provided with each extension filter driver. The *install.cmd* uses **netcfg** to install the extension and **mofcomp** to register any required mof files. The PowerShell cmdlet *Enable-VmSwitchExtension* can then be used to enable the extension filter driver on a Hyper-V Extensible Switch. -For more information on Hyper-V Extensible Switch extensions, see [Hyper-V Extensible Switch](http://msdn.microsoft.com/en-us/library/windows/hardware/hh598161). \ No newline at end of file +For more information on Hyper-V Extensible Switch extensions, see [Hyper-V Extensible Switch](http://msdn.microsoft.com/en-us/library/windows/hardware/hh598161). diff --git a/network/ndis/filter/README.md b/network/ndis/filter/README.md index 1163fda16..69be489f2 100644 --- a/network/ndis/filter/README.md +++ b/network/ndis/filter/README.md @@ -117,4 +117,4 @@ What the Ndislwf sample driver does: 5. All requests and sends coming from overlying drivers for the Ndislwf filter driver are repackaged if necessary and sent down to NDIS, to be passed to the underlying NDIS driver. 6. All indications arriving from an underlying NDIS driver are forwarded up by Ndislwf filter driver. 7. NDIS calls the filter's [*FilterPause*](http://msdn.microsoft.com/en-us/library/windows/hardware/ff549957) handler when NDIS needs to detach the filter from the stack or there is some configuration changes in the stack. In processing the pause request from NDIS, the Ndislwf driver waits for all its own outstanding requests to be completed before it completes the pause request. -8. NDIS calls the Ndislwf driver's [*FilterDetach*](http://msdn.microsoft.com/en-us/library/windows/hardware/ff549918) entry point when NDIS needs to detach a filter module from NDIS stack. The *FilterDetach* handler should free all the memory allocation done in [*FilterAttach*](http://msdn.microsoft.com/en-us/library/windows/hardware/ff549905), and undo the operations it did in *FilterAttach* Handler. \ No newline at end of file +8. NDIS calls the Ndislwf driver's [*FilterDetach*](http://msdn.microsoft.com/en-us/library/windows/hardware/ff549918) entry point when NDIS needs to detach a filter module from NDIS stack. The *FilterDetach* handler should free all the memory allocation done in [*FilterAttach*](http://msdn.microsoft.com/en-us/library/windows/hardware/ff549905), and undo the operations it did in *FilterAttach* Handler. diff --git a/network/ndis/mux/README.md b/network/ndis/mux/README.md index 710ab13b4..215bed62b 100644 --- a/network/ndis/mux/README.md +++ b/network/ndis/mux/README.md @@ -191,7 +191,7 @@ Mux.rc | Resource file for the MUX driver Muxp.inf | Installation INF for the service (protocol side installation) Mux_mp.inf | Installation INF for the miniport (virtual device installation) Precomp.h | Precompile header file -Protocol.c | Protocol related routines for the MUX driver +Protocol.c | Protocol related routines for the MUX driver Public.h | Contains the common declarations shared by driver and user applications For more information, see [NDIS Intermediate Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff565773) in the network devices design guide. \ No newline at end of file diff --git a/network/ndis/ndisprot/6x/README.md b/network/ndis/ndisprot/6x/README.md index 92e52464a..5fa812181 100644 --- a/network/ndis/ndisprot/6x/README.md +++ b/network/ndis/ndisprot/6x/README.md @@ -75,4 +75,4 @@ ndisprot.inf | INF file for installing NDISPROT ntdisp.c | NT Entry points and dispatch routines for NDISPROT protuser.h | IOCTL and associated structure definitions recv.c | NDIS protocol entry points for receiving data, and IRP_MJ_READ processing -send.c | NDIS protocol routines for sending data, and IRP_MJ_WRITE processing \ No newline at end of file +send.c | NDIS protocol routines for sending data, and IRP_MJ_WRITE processing \ No newline at end of file diff --git a/network/ndis/ndisprot_kmdf/README.md b/network/ndis/ndisprot_kmdf/README.md index 9fba66be0..339e25531 100644 --- a/network/ndis/ndisprot_kmdf/README.md +++ b/network/ndis/ndisprot_kmdf/README.md @@ -129,4 +129,4 @@ File | Description Common.hpp | Header file containing the common include files for the project dllmain.cpp | Handles loading/unloading of Wdf Coinstaller and the notify object dll ProtNotify.idl | Defines the interfaces for the notify object dll -ProtNotify.rc | Resource file for the notify object dll \ No newline at end of file +ProtNotify.rc | Resource file for the notify object dll diff --git a/network/ndis/netvmini/6x/README.md b/network/ndis/netvmini/6x/README.md index 2a46b3d32..5ce68d7a0 100644 --- a/network/ndis/netvmini/6x/README.md +++ b/network/ndis/netvmini/6x/README.md @@ -28,4 +28,4 @@ To test the miniport driver, install more than one miniport driver instance. You **Note** This sample provides an example of minimal driver intended for education purposes. The driver and its sample test programs are not intended for use in a production environment. -For more information on creating NDIS Miniport Drivers, see [NDIS Miniport Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff565949). \ No newline at end of file +For more information on creating NDIS Miniport Drivers, see [NDIS Miniport Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff565949). diff --git a/network/radio/HidSwitchDriverSample/README.md b/network/radio/HidSwitchDriverSample/README.md index a150b0cae..812fd66c9 100644 --- a/network/radio/HidSwitchDriverSample/README.md +++ b/network/radio/HidSwitchDriverSample/README.md @@ -67,4 +67,4 @@ In this mode the radio switch (switch 8 on the switch pack) represents an A-B sl ### Mode 5 LED only -In this mode the radio switch (switch 8 on the switch pack) is ignored. The LED array will reflect the state of the Radio LED: either all on or all off (note that the top 2 LEDs never illuminate as these are not wired in). \ No newline at end of file +In this mode the radio switch (switch 8 on the switch pack) is ignored. The LED array will reflect the state of the Radio LED: either all on or all off (note that the top 2 LEDs never illuminate as these are not wired in). diff --git a/network/radio/RadioManagerSample/README.md b/network/radio/RadioManagerSample/README.md index 4c38c2e37..575e26dfc 100644 --- a/network/radio/RadioManagerSample/README.md +++ b/network/radio/RadioManagerSample/README.md @@ -114,4 +114,4 @@ Simply change the values in the registry. For example, change the radio state fr ### Removing a Radio Instance ### -Delete the corresponding registry key. \ No newline at end of file +Delete the corresponding registry key. diff --git a/network/trans/WFPSampler/README.md b/network/trans/WFPSampler/README.md index fa808b2bf..7e45796a9 100644 --- a/network/trans/WFPSampler/README.md +++ b/network/trans/WFPSampler/README.md @@ -194,4 +194,4 @@ If you want to test whether your TraceView.exe session is working, you can enter For more information, see [Creating a Trace Session with a PDB File](http://msdn.microsoft.com/en-us/library/windows/hardware/ff543582). -Tracing for the sample driver can be started at any time before the driver is started or while the driver is already running. \ No newline at end of file +Tracing for the sample driver can be started at any time before the driver is started or while the driver is already running. diff --git a/network/trans/ddproxy/README.md b/network/trans/ddproxy/README.md index bbc3f1257..224bc026f 100644 --- a/network/trans/ddproxy/README.md +++ b/network/trans/ddproxy/README.md @@ -80,4 +80,4 @@ Packet modification is done out-of-band by a system worker thread by using the r Ddproxy.sys acts as a redirector for both Internet Protocol version 4 (IPv4) and Internet Protocol version 6 (IPv6) traffic. -For more information on creating a Windows Filtering Platform Callout Driver, see [Windows Filtering Platform Callout Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff571068). \ No newline at end of file +For more information on creating a Windows Filtering Platform Callout Driver, see [Windows Filtering Platform Callout Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff571068). diff --git a/network/trans/inspect/README.md b/network/trans/inspect/README.md index d1dcac7f5..7480bace4 100644 --- a/network/trans/inspect/README.md +++ b/network/trans/inspect/README.md @@ -69,4 +69,4 @@ On the target computer, open a Command Prompt window as Administrator, and enter Remarks ------- -For more information on creating a Windows Filtering Platform Callout Driver, see [Windows Filtering Platform Callout Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff571068). \ No newline at end of file +For more information on creating a Windows Filtering Platform Callout Driver, see [Windows Filtering Platform Callout Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff571068). diff --git a/network/trans/msnmntr/README.md b/network/trans/msnmntr/README.md index ad71a788a..14cedd3b1 100644 --- a/network/trans/msnmntr/README.md +++ b/network/trans/msnmntr/README.md @@ -92,4 +92,4 @@ As an alternative to building the WFP MSN Messenger Monitor Sample in Visual Stu **msbuild /p:configuration="Release" /p:platform="Win32" msnmntr.sln** -For more information about using [MSBuild](http://go.microsoft.com/fwlink/p/?linkID=262804) 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](http://go.microsoft.com/fwlink/p/?linkID=262804) to build a driver package, see [Building a Driver](http://msdn.microsoft.com/en-us/library/windows/hardware/ff554644). diff --git a/network/trans/stmedit/README.md b/network/trans/stmedit/README.md index 75cf70604..2c1d83e15 100644 --- a/network/trans/stmedit/README.md +++ b/network/trans/stmedit/README.md @@ -81,4 +81,4 @@ On the target computer, open a Command Prompt window as Administrator, and enter Remarks ------- -For more information on creating a Windows Filtering Platform Callout Driver, see [Windows Filtering Platform Callout Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff571068). \ No newline at end of file +For more information on creating a Windows Filtering Platform Callout Driver, see [Windows Filtering Platform Callout Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff571068). diff --git a/network/wlan/WDI/README.md b/network/wlan/WDI/README.md index e825b1b5b..c9327a9c0 100644 --- a/network/wlan/WDI/README.md +++ b/network/wlan/WDI/README.md @@ -18,4 +18,4 @@ products: # WDI samples -This sample demonstrates use of the WLAN WDI. \ No newline at end of file +This sample demonstrates use of the WLAN WDI. diff --git a/network/wlan/ihvsampleui/README.md b/network/wlan/ihvsampleui/README.md index 94f623816..db537b917 100644 --- a/network/wlan/ihvsampleui/README.md +++ b/network/wlan/ihvsampleui/README.md @@ -18,4 +18,4 @@ products: # IHV Sample UI -This sample demonstrates the WLAN IHV UI. \ No newline at end of file +This sample demonstrates the WLAN IHV UI. diff --git a/network/wsk/echosrv/README.md b/network/wsk/echosrv/README.md index a5300b051..3ab0360cb 100644 --- a/network/wsk/echosrv/README.md +++ b/network/wsk/echosrv/README.md @@ -71,4 +71,4 @@ Install and run this sample driver by using the following steps: After the driver is installed and started, it will listen for incoming TCP connection requests on port 40007 over both IPv4 and IPv6 protocols until the driver is stopped. On each connection, the driver will echo all the received data back to the peer until the connection is closed by the peer. -For more information on the usage of the Winsock Kernel (WSK) programming interface, see [Winsock Kernel](http://msdn.microsoft.com/en-us/library/windows/hardware/ff571084). \ No newline at end of file +For more information on the usage of the Winsock Kernel (WSK) programming interface, see [Winsock Kernel](http://msdn.microsoft.com/en-us/library/windows/hardware/ff571084). diff --git a/nfc/NfcCxSample/README.md b/nfc/NfcCxSample/README.md index 85437cbbb..a3af8add7 100644 --- a/nfc/NfcCxSample/README.md +++ b/nfc/NfcCxSample/README.md @@ -40,4 +40,4 @@ This sample builds a Universal Windows Driver. It uses only APIs and DDIs that a - `DeviceContext::ReadNciPacket` - Demonstrates calling [`NfcCxNciReadNotification`](https://docs.microsoft.com/windows-hardware/drivers/ddi/content/nfccx/nf-nfccx-nfccxncireadnotification). - [Device.h](windows-drivertemplate-nfc/Device.h) - - `DeviceContext` - The class that stores the device instance's state. \ No newline at end of file + - `DeviceContext` - The class that stores the device instance's state. diff --git a/nfp/net/inc/README.md b/nfp/net/inc/README.md index 3c8e994b7..814eaf336 100644 --- a/nfp/net/inc/README.md +++ b/nfp/net/inc/README.md @@ -24,4 +24,4 @@ Typically, a near-field proximity driver would use near-field technologies such ## Related technologies -[User-Mode Driver Framework](http://msdn.microsoft.com/en-us/library/windows/hardware/ff560456) \ No newline at end of file +[User-Mode Driver Framework](http://msdn.microsoft.com/en-us/library/windows/hardware/ff560456) diff --git a/pofx/PEP/README.md b/pofx/PEP/README.md index fb399a21c..ece35c049 100644 --- a/pofx/PEP/README.md +++ b/pofx/PEP/README.md @@ -24,4 +24,4 @@ Use the PEP ACPI interface if: * You want to write peripheral (off-SoC) device power management in C rather than in ACPI Source Language (ASL). * You need to override an ACPI method which exists in a platform's DSDT or SSDT firmware tables. -* Shipping, maintaining, and updating a driver binary suits your platform better than firmware updates (note that you will still need FADT, MADT, DBG2, and so on in firmware - this interface is only for runtime methods). \ No newline at end of file +* Shipping, maintaining, and updating a driver binary suits your platform better than firmware updates (note that you will still need FADT, MADT, DBG2, and so on in firmware - this interface is only for runtime methods). diff --git a/pofx/UMDF2/README.md b/pofx/UMDF2/README.md index 64092ecf1..b73aadea6 100644 --- a/pofx/UMDF2/README.md +++ b/pofx/UMDF2/README.md @@ -67,4 +67,4 @@ As an alternative to building the driver sample in Visual Studio, you can build **msbuild /p:configuration="Release" /p:platform="Win32" PoFx.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/pofx/WDF/README.md b/pofx/WDF/README.md index 9c10e060b..d689c2819 100644 --- a/pofx/WDF/README.md +++ b/pofx/WDF/README.md @@ -124,4 +124,4 @@ The code to implement S0-idle power management support for the device is conditi Additional Information ---------------------- -For detailed information about implementing F-state-based power management for a multiple component device, see [Supporting Multiple Functional Power States for Multiple-Component Devices](http://msdn.microsoft.com/en-us/library/windows/hardware/hh451028). \ No newline at end of file +For detailed information about implementing F-state-based power management for a multiple component device, see [Supporting Multiple Functional Power States for Multiple-Component Devices](http://msdn.microsoft.com/en-us/library/windows/hardware/hh451028). diff --git a/pos/drivers/MagneticStripeReader/README.md b/pos/drivers/MagneticStripeReader/README.md index e386515c1..36e1bd778 100644 --- a/pos/drivers/MagneticStripeReader/README.md +++ b/pos/drivers/MagneticStripeReader/README.md @@ -22,4 +22,4 @@ This sample serves as a template for creating a new Magnetic Stripe Reader drive This sample uses UMDF 2.0 and enables basic functionality such as claiming and enabling the device for exclusive access. -It serves as an example of how to include the libraries necessary to develop a PointOfService driver. Once a driver is developed using this template it can be compiled for, deployed, and used on x86, amd64, and ARM platforms. \ No newline at end of file +It serves as an example of how to include the libraries necessary to develop a PointOfService driver. Once a driver is developed using this template it can be compiled for, deployed, and used on x86, amd64, and ARM platforms. diff --git a/pos/drivers/barcodescanner/README.md b/pos/drivers/barcodescanner/README.md index bf041f448..d5934f8f2 100644 --- a/pos/drivers/barcodescanner/README.md +++ b/pos/drivers/barcodescanner/README.md @@ -22,4 +22,4 @@ This sample serves as a template for creating a new Barcode Scanner driver. This sample uses UMDF 2.0 and enables basic functionality such as claiming and enabling the device for exclusive access. -It serves as an example of how to include the libraries necessary to develop a PointOfService driver. Once a driver is developed using this template it can be compiled for, deployed, and used on x86, amd64, and ARM platforms. \ No newline at end of file +It serves as an example of how to include the libraries necessary to develop a PointOfService driver. Once a driver is developed using this template it can be compiled for, deployed, and used on x86, amd64, and ARM platforms. diff --git a/print/OEM Printer Customization Plug-in Samples/README.md b/print/OEM Printer Customization Plug-in Samples/README.md index 3807f9e6c..430353af3 100644 --- a/print/OEM Printer Customization Plug-in Samples/README.md +++ b/print/OEM Printer Customization Plug-in Samples/README.md @@ -102,7 +102,7 @@ This sample has the following limitations: When preanalysis is enabled in the GPD (for more details about preanalysis, see the WDK documentation), Unidrv defines the surface as a banding surface but causes the first playback (that is, the first band) to be of the entire page. Unidrv performs this definition by setting the GDI clip window to the entire page. Unidrv enables all drawing commands to be hooked but returns before any drawing can be done. On the subsequent passes, Unidrv resets the clip window back to the original band size and bands normally. -In order for plugins to also take part in preanalysis, they can enable OEM preanalysis by specifying the `"*PreAnalysisOptions: 8"` parameter in the GPD. The OEM rendering plug-in must hook both `DrvStartBanding` and `DrvNextBand` when this mode is enabled in the GPD. The OEM rendering plug-in must test the `pptl` parameter of the `OEMStartBanding` call to determine whether preanalysis has been enabled on this page. If the `pptl` parameter is `NULL`, preanalysis has been enabled, and the OEM rendering plug-in should consider all drawing calls up to the first call to `OEMNextBand` to be part of preanalysis. +In order for plugins to also take part in preanalysis, they can enable OEM preanalysis by specifying the `"*PreAnalysisOptions: 8"` parameter in the GPD. The OEM rendering plug-in must hook both `DrvStartBanding` and `DrvNextBand` when this mode is enabled in the GPD. The OEM rendering plug-in must test the `pptl` parameter of the `OEMStartBanding` call to determine whether preanalysis has been enabled on this page. If the `pptl` parameter is `NULL`, preanalysis has been enabled, and the OEM rendering plug-in should consider all drawing calls up to the first call to `OEMNextBand` to be part of preanalysis. During these preanalysis phase drawing calls, the plug-in should not draw on the surface. The plug-in should also not call back into unidrv. You should use this phase only for analysis of the objects on the page. For example, certain printers need to handle black objects that intersect with color objects differently from black objects that appear by themselves. Other printers might need to halftone `StretchBlt` objects differently from `BitBlt` objects. You should be aware that after preanalysis, you might get more calls than you saw in the normal rendering, because primitives that cross band boundaries yield two or more DDI calls after the preanalysis pass. diff --git a/print/SampleOpenXPS/README.md b/print/SampleOpenXPS/README.md index 3e50790a2..7ece34424 100644 --- a/print/SampleOpenXPS/README.md +++ b/print/SampleOpenXPS/README.md @@ -20,4 +20,4 @@ products: This sample contains a set of documents that were generated from a variety of sources, including those generated from the Windows Presentation Foundation in the .NET Framework, from Office 2007, and from the Microsoft XPS Document Writer (MXDW). A few of the documents were either hand-built from scratch or hand-modified from another source. They have been included to provide you with a few documents that exercise a variety of features of the XML Paper Specification. -In addition, a few high-quality documents have been provided in the Showcase directory to highlight some of the XPS advantages in terms of screen-to-print fidelity. We've also created some documents that are intended to fail, by violating at least one conformance rule. These are in the ConformanceViolations directory. For information about OpenXPS in Windows, see [Improvements in XPSDrv](http://msdn.microsoft.com/en-us/library/windows/hardware/jj218730(v=vs.85).aspx) and [OpenXPS Support in Windows](http://msdn.microsoft.com/en-us/library/windows/hardware/br259130.aspx). \ No newline at end of file +In addition, a few high-quality documents have been provided in the Showcase directory to highlight some of the XPS advantages in terms of screen-to-print fidelity. We've also created some documents that are intended to fail, by violating at least one conformance rule. These are in the ConformanceViolations directory. For information about OpenXPS in Windows, see [Improvements in XPSDrv](http://msdn.microsoft.com/en-us/library/windows/hardware/jj218730(v=vs.85).aspx) and [OpenXPS Support in Windows](http://msdn.microsoft.com/en-us/library/windows/hardware/br259130.aspx). diff --git a/print/SampleXPS/README.md b/print/SampleXPS/README.md index b9c49330f..edc8f7a11 100644 --- a/print/SampleXPS/README.md +++ b/print/SampleXPS/README.md @@ -20,4 +20,4 @@ products: This sample is a set of documents that were generated from a variety of sources, including those generated from the Windows Presentation Foundation in the .NET Framework, from Office 2007, and from the Microsoft XPS Document Writer (MXDW). The set of documents also includes documents that were either hand-built from scratch or hand-modified from another source. They have been included to provide you with a few documents that exercise a variety of features of the XML Paper Specification. -In addition, a few high-quality documents have been provided in the Showcase directory to highlight some of the XPS advantages in terms of screen-to-print fidelity. There are also some documents that are intended to fail by violating at least one conformance rule. These are in the ConformanceViolations directory. For information about XPS in Windows, see [XPS Printing Features](http://msdn.microsoft.com/en-us/library/windows/hardware/ff564299(v=vs.85).aspx). \ No newline at end of file +In addition, a few high-quality documents have been provided in the Showcase directory to highlight some of the XPS advantages in terms of screen-to-print fidelity. There are also some documents that are intended to fail by violating at least one conformance rule. These are in the ConformanceViolations directory. For information about XPS in Windows, see [XPS Printing Features](http://msdn.microsoft.com/en-us/library/windows/hardware/ff564299(v=vs.85).aspx). diff --git a/print/SimplePipelineFilter/README.md b/print/SimplePipelineFilter/README.md index 23227ccea..945586705 100644 --- a/print/SimplePipelineFilter/README.md +++ b/print/SimplePipelineFilter/README.md @@ -22,4 +22,4 @@ The printing system supports a print filter pipeline. The pipeline is run when a This sample shows how to use the print pipeline's filter interfaces. -The filters in the print pipeline consume a certain data type and produce a certain data type. This information is specified in the pipeline configuration file on a per printer driver basis. The WDK print filter sample contains two filter samples: one that consumes and produces XPS data type, and the other one consumes and produces opaque byte stream. For more information, see the [XpsDrv](http://msdn.microsoft.com/en-us/windows/hardware/gg463364) whitepaper. \ No newline at end of file +The filters in the print pipeline consume a certain data type and produce a certain data type. This information is specified in the pipeline configuration file on a per printer driver basis. The WDK print filter sample contains two filter samples: one that consumes and produces XPS data type, and the other one consumes and produces opaque byte stream. For more information, see the [XpsDrv](http://msdn.microsoft.com/en-us/windows/hardware/gg463364) whitepaper. diff --git a/print/autoconfig/README.md b/print/autoconfig/README.md index e50b45b70..2085dd722 100644 --- a/print/autoconfig/README.md +++ b/print/autoconfig/README.md @@ -50,4 +50,4 @@ For more information about how to build a driver solution using Microsoft Visual ## Run the sample -To run the auto-configuration sample, you must install this driver to support a printer which is installed against either a WSD port, or TCP/IP port. Additionally, USB printers may be supported if the driver is updated to incorporate USB Bidi Javascript, as described here: [Print Driver USB Monitor and Bidi Sample](https://github.com/Microsoft/Windows-driver-samples/tree/master/print/v4PrintDriverSamples/v4PrintDriver-USBMon-Bidi-Extension). \ No newline at end of file +To run the auto-configuration sample, you must install this driver to support a printer which is installed against either a WSD port, or TCP/IP port. Additionally, USB printers may be supported if the driver is updated to incorporate USB Bidi Javascript, as described here: [Print Driver USB Monitor and Bidi Sample](https://github.com/Microsoft/Windows-driver-samples/tree/master/print/v4PrintDriverSamples/v4PrintDriver-USBMon-Bidi-Extension). diff --git a/print/cpsuisam/README.md b/print/cpsuisam/README.md index f7859ae78..5bb6676bf 100644 --- a/print/cpsuisam/README.md +++ b/print/cpsuisam/README.md @@ -26,4 +26,4 @@ The application then creates an additional property sheet page to illustrate som CPSUI is a user-mode DLL that enables you to create property sheet pages that have a standard appearance. -CPSUIAM causes CPSUI to call the Windows print spooler to create property sheet pages for the system's default printer. The application then creates an additional property sheet page to illustrate some of the techniques that you can use when you are using CPSUI to create a new page. For more information, see [Common Property Sheet User Interface](http://msdn.microsoft.com/en-us/library/windows/hardware/ff546163(v=vs.85).aspx). \ No newline at end of file +CPSUIAM causes CPSUI to call the Windows print spooler to create property sheet pages for the system's default printer. The application then creates an additional property sheet page to illustrate some of the techniques that you can use when you are using CPSUI to create a new page. For more information, see [Common Property Sheet User Interface](http://msdn.microsoft.com/en-us/library/windows/hardware/ff546163(v=vs.85).aspx). diff --git a/print/v4PrintDriverSamples/PrinterExtensionSample/README.md b/print/v4PrintDriverSamples/PrinterExtensionSample/README.md index 5595036d5..d022fcad3 100644 --- a/print/v4PrintDriverSamples/PrinterExtensionSample/README.md +++ b/print/v4PrintDriverSamples/PrinterExtensionSample/README.md @@ -26,4 +26,4 @@ This sample demonstrates how to use .NET to build a customized, desktop UI for a [Building a Driver](http://msdn.microsoft.com/en-us/library/windows/hardware/ff554644) -[v4 Print Driver Interfaces and Enumerations](http://msdn.microsoft.com/en-us/library/hh464103(v=vs.85).aspx) \ No newline at end of file +[v4 Print Driver Interfaces and Enumerations](http://msdn.microsoft.com/en-us/library/hh464103(v=vs.85).aspx) diff --git a/print/v4PrintDriverSamples/v4PrintDriver-ConstraintScript/README.md b/print/v4PrintDriverSamples/v4PrintDriver-ConstraintScript/README.md index de67b0138..cc3ba3074 100644 --- a/print/v4PrintDriverSamples/v4PrintDriver-ConstraintScript/README.md +++ b/print/v4PrintDriverSamples/v4PrintDriver-ConstraintScript/README.md @@ -35,4 +35,4 @@ This sample does not demonstrate **ConvertPrintTicketToDevMode** or **ConvertDev [IPrintSchemaCapabilities](http://msdn.microsoft.com/en-us/library/hh451256(v=vs.85).aspx) -[IPrintSchemaTicket](http://msdn.microsoft.com/en-us/library/hh451398(v=vs.85).aspx) \ No newline at end of file +[IPrintSchemaTicket](http://msdn.microsoft.com/en-us/library/hh451398(v=vs.85).aspx)