diff options
| author | Den Delimarsky <[email protected]> | 2019-03-13 19:15:06 -0700 |
|---|---|---|
| committer | Den Delimarsky <[email protected]> | 2019-03-13 19:15:06 -0700 |
| commit | dbc7785c3a7ced56ecac6b5a9dfb81ef45dedac6 (patch) | |
| tree | 2a8e1a39358b66cc2bc0d85e163956aafd5ccd16 | |
| parent | ffeacc14932f98db4e7926825909a37d2b6d332f (diff) | |
Update manifests
154 files changed, 148 insertions, 169 deletions
diff --git a/TrEE/README.md b/TrEE/README.md index 077a8fb8..9c20a059 100644 --- a/TrEE/README.md +++ b/TrEE/README.md @@ -18,4 +18,4 @@ products: # TrEE sample -The Trusted Execution Environment (TrEE) sample. +The Trusted Execution Environment (TrEE) sample.
\ No newline at end of file diff --git a/audio/sysvad/README.md b/audio/sysvad/README.md index 5c20b3eb..33fa79fd 100644 --- a/audio/sysvad/README.md +++ b/audio/sysvad/README.md @@ -165,5 +165,4 @@ On the target computer, in a Command Prompt window, enter **devmgmt** to open De On the target computer, open Control Panel and navigate to **Hardware and Sound** \> **Manage audio devices**. In the Sound dialog box, select the speaker icon labeled as *Microsoft Virtual Audio Device (WDM) - Tablet Audio Sample*, then click **Set Default**, but do not click **OK**. This will keep the Sound dialog box open. -Locate an MP3 or other audio file on the target computer and double-click to play it. Then in the Sound dialog box, verify that there is activity in the volume level indicator associated with the *Microsoft Virtual Audio Device (WDM) - Tablet Audio Sample* driver. - +Locate an MP3 or other audio file on the target computer and double-click to play it. Then in the Sound dialog box, verify that there is activity in the volume level indicator associated with the *Microsoft Virtual Audio Device (WDM) - Tablet Audio Sample* driver.
\ No newline at end of file diff --git a/avstream/avscamera/README.md b/avstream/avscamera/README.md index 4dcc24bb..81f0d3c4 100644 --- a/avstream/avscamera/README.md +++ b/avstream/avscamera/README.md @@ -19,7 +19,7 @@ products: # AvsCamera - AVStream Camera Sample Driver -The AvsCamera sample provides a pin-centric AVStream capture driver for a simulated front and back camera. The driver performs simulated captures at 320x240 or 640x480 in RGB24, RGB32, YUY2 and NV12 formats at various frame rates. The purpose of the sample is to demonstrate how to write a fully functional AVStream camera driver. +The AvsCamera sample provides a pin-centric AVStream capture driver for a simulated front and back camera. The driver performs simulated captures at 320x240 or 640x480 in RGB24, RGB32, YUY2 and NV12 formats at various frame rates. The purpose of the sample is to demonstrate how to write a fully functional AVStream camera driver. This sample features strong parameter validation and overflow detection. It provides validation and simulation logic for all advanced camera controls in the CCaptureFilter class. A real camera driver would replace the filter automation table and CSensor and CSynthesizer class hierarchies to produce a new camera driver. diff --git a/avstream/avscamera/mft0/README.md b/avstream/avscamera/mft0/README.md index 3064837e..b492a3b2 100644 --- a/avstream/avscamera/mft0/README.md +++ b/avstream/avscamera/mft0/README.md @@ -18,7 +18,7 @@ products: # AvsCamera: AVStream Camera Sample Driver -The AvsCamera sample provides a pin-centric AVStream capture driver for a simulated front and back camera. The driver performs simulated captures at 320x240 or 640x480 in RGB24, RGB32, YUY2 and NV12 formats at various frame rates. The purpose of the sample is to demonstrate how to write a fully functional AVStream camera driver. +The AvsCamera sample provides a pin-centric AVStream capture driver for a simulated front and back camera. The driver performs simulated captures at 320x240 or 640x480 in RGB24, RGB32, YUY2 and NV12 formats at various frame rates. The purpose of the sample is to demonstrate how to write a fully functional AVStream camera driver. This sample features strong parameter validation and overflow detection. It provides validation and simulation logic for all advanced camera controls in the CCaptureFilter class. A real camera driver would replace the filter automation table and CSensor and CSynthesizer class hierarchies to produce a new camera driver. diff --git a/avstream/avshws/README.md b/avstream/avshws/README.md index 5413a2c0..5768e521 100644 --- a/avstream/avshws/README.md +++ b/avstream/avshws/README.md @@ -90,4 +90,4 @@ Code tour File | Description -----|------------ Avshws.h | Main header file for the sample -Avshws.inf | Sample installation file +Avshws.inf | Sample installation file
\ No newline at end of file diff --git a/avstream/avssamp/README.md b/avstream/avssamp/README.md index 12e38b7e..91c25824 100644 --- a/avstream/avssamp/README.md +++ b/avstream/avssamp/README.md @@ -20,7 +20,6 @@ products: The AVStream filter-centric simulated capture sample driver (Avssamp) provides a filter-centric [AVStream](http://msdn.microsoft.com/en-us/library/windows/hardware/ff554240) capture driver with functional audio. This streaming media driver performs video captures at 320 x 240 pixel resolution in RGB24 or YUV422 format while playing a user-provided Pulse Code Modulation (PCM) wave audio file in a loop. The sample demonstrates how to write a filter-centric AVStream minidriver. - Installation instructions ------------------------- diff --git a/avstream/sampledevicemft/README.md b/avstream/sampledevicemft/README.md index 25d5991e..2998e966 100644 --- a/avstream/sampledevicemft/README.md +++ b/avstream/sampledevicemft/README.md @@ -26,7 +26,6 @@ In this sample, the Device Transform , when enabled, will replicate a photo sequ This sample is designed to be used with a specific camera. To run the sample, you need the your camera's device ID and device metadata package. - Related topics -------------- diff --git a/avstream/samplemft0/README.md b/avstream/samplemft0/README.md index 4370517b..3e97e680 100644 --- a/avstream/samplemft0/README.md +++ b/avstream/samplemft0/README.md @@ -24,7 +24,6 @@ In this sample, the driver MFT, when enabled, replaces a portion of the captured This sample is designed to be used with a specific camera. To run the sample, you need the your camera's device ID and device metadata package. - Related topics -------------- diff --git a/biometrics/README.md b/biometrics/README.md index f62da26a..97b2e07f 100644 --- a/biometrics/README.md +++ b/biometrics/README.md @@ -28,7 +28,6 @@ This sample implements the Windows Biometric Driver Interface (WBDI). It contain *Windows Biometric Service Adapters* These samples provide skeleton code that developers can use as a basis for writing Sensor, Engine, and Storage Adapters for the Windows Biometric Service. Note that the stubs in these samples are non-functional, and Adapter writers will need to follow the programming guidelines in the WinBio Service documentation in order produce a working Adapter component. - Build the sample ---------------- diff --git a/bluetooth/bthecho/bthsrv/README.md b/bluetooth/bthecho/bthsrv/README.md index a839b7ef..dedc6646 100644 --- a/bluetooth/bthecho/bthsrv/README.md +++ b/bluetooth/bthecho/bthsrv/README.md @@ -155,7 +155,7 @@ The device tree for echo client device is similar to the one shown for the echo Run BthEcho.exe on the client machine. You should see client sending data to the server and receiving the same data echoed back. Press Ctrl+c to terminate the application. You will see output similar to below: -``` +```batch D:\bth\wdfcli>BthEcho.exe DevicePath: \\?\bthenum#{c07508f2-b970-43ca-b5dd-cc4f2391bef4}_localmfg&000a#7&3 62d0a3&0&000c55ff727a_c00000001#{fc71b33d-d528-4763-a86c-78777c7bcd7b} diff --git a/bluetooth/serialhcibus/README.md b/bluetooth/serialhcibus/README.md index a81e5f83..460b3923 100644 --- a/bluetooth/serialhcibus/README.md +++ b/bluetooth/serialhcibus/README.md @@ -74,4 +74,4 @@ device.h - header file for device.c driver.rc - driver version and name -SerialBusWdk.inx - device specific INF file to install this driver. The vendor will need to add the hardware ID to match the "\_HID" for the Serial Bus Device (Bluetooth) in the DSDT.asl file. For example, in SerialBusWDK.inx, the hardware ID is "ACPI\\<*vendor*\>\_BTH0" where <*vendor*\> could be a 4 digit vendor name
\ No newline at end of file +SerialBusWdk.inx - device specific INF file to install this driver. The vendor will need to add the hardware ID to match the "\_HID" for the Serial Bus Device (Bluetooth) in the DSDT.asl file. For example, in SerialBusWDK.inx, the hardware ID is "ACPI\\<*vendor*\>\_BTH0" where <*vendor*\> could be a 4 digit vendor name.
\ No newline at end of file diff --git a/filesys/cdfs/README.md b/filesys/cdfs/README.md index 9a70e049..d7e5b86c 100644 --- a/filesys/cdfs/README.md +++ b/filesys/cdfs/README.md @@ -1,6 +1,6 @@ --- topic: sample -description: The CD-ROM file system driver (cdfs) sample is a file system driver for removable media. +description: The CD-ROM file system driver (CDFS) sample is a file system driver for removable media. languages: - cpp products: diff --git a/filesys/fastfat/README.md b/filesys/fastfat/README.md index eb0e879e..5994fe0a 100644 --- a/filesys/fastfat/README.md +++ b/filesys/fastfat/README.md @@ -23,6 +23,7 @@ The *fastfat* sample is file system driver that you can use as a model to write *fastfat* is a complete file system that addresses various issues such as storing data on disk, interacting with the cache manager, and handling various I/O operations such as file creation, performing read/writes on a file, setting information on a file, and performing control operations on the file system. ## Universal Windows Driver Compliant + This sample builds a Universal Windows Driver. It uses only APIs and DDIs that are included in OneCoreUAP. Build the sample diff --git a/filesys/miniFilter/MetadataManager/README.md b/filesys/miniFilter/MetadataManager/README.md index dd7bf6df..b8838c3c 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.
\ 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/NameChanger/README.md b/filesys/miniFilter/NameChanger/README.md index e56a22b4..210eff25 100644 --- a/filesys/miniFilter/NameChanger/README.md +++ b/filesys/miniFilter/NameChanger/README.md @@ -20,7 +20,6 @@ products: The *NameChanger* minifilter grafts a directory from one part of a volume's namespace to another part using a mapping. The minifilter maintains this illusion by acting as a name provider, injecting entries into directory enumerations and forwarding directory change notifications. - Build the sample ---------------- diff --git a/filesys/miniFilter/avscan/README.md b/filesys/miniFilter/avscan/README.md index e8b232c6..6fbfa116 100644 --- a/filesys/miniFilter/avscan/README.md +++ b/filesys/miniFilter/avscan/README.md @@ -21,4 +21,5 @@ products: The AvScan minifilter is a transaction-aware file scanner. This is an example for developers who intend to write filters that examine data in files. Typically, anti-virus products fall into this category. ## 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 diff --git a/filesys/miniFilter/cancelSafe/README.md b/filesys/miniFilter/cancelSafe/README.md index e35f429b..cdebf8fc 100644 --- a/filesys/miniFilter/cancelSafe/README.md +++ b/filesys/miniFilter/cancelSafe/README.md @@ -21,6 +21,7 @@ products: The CancelSafe filter is a sample minifilter that you use if you want to use cancel-safe queues. ## Universal Windows Driver Compliant + This sample builds a Universal Windows Driver. It uses only APIs and DDIs that are included in OneCoreUAP. Design and Operation diff --git a/filesys/miniFilter/cdo/README.md b/filesys/miniFilter/cdo/README.md index 8feba54e..41379efa 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.
\ 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/change/README.md b/filesys/miniFilter/change/README.md index 12e8e17a..38c00468 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.
\ 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/ctx/README.md b/filesys/miniFilter/ctx/README.md index 904a3568..19cd94f8 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.
\ 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/delete/README.md b/filesys/miniFilter/delete/README.md index 96e91cdc..e2c5a5ef 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.
\ 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/minispy/README.md b/filesys/miniFilter/minispy/README.md index aff8825a..522b1080 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.
\ 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/nullFilter/README.md b/filesys/miniFilter/nullFilter/README.md index b7e52d44..803ef8ce 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.
\ 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/passThrough/README.md b/filesys/miniFilter/passThrough/README.md index 2e319a68..88481c69 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.
\ 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/scanner/README.md b/filesys/miniFilter/scanner/README.md index da01b38e..8bc56be8 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.
\ 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/simrep/README.md b/filesys/miniFilter/simrep/README.md index 366818ed..b6775082 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. +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/swapBuffers/README.md b/filesys/miniFilter/swapBuffers/README.md index 729e7966..ae73c589 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. +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/general/DCHU/README.md b/general/DCHU/README.md index ce107bb1..65ca524d 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. +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 diff --git a/general/PLX9x5x/README.md b/general/PLX9x5x/README.md index bc1c1de3..432f53b2 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. +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 diff --git a/general/SystemDma/wdm/README.md b/general/SystemDma/wdm/README.md index 23315a12..4e2dbab6 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. +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 diff --git a/general/WinHEC 2017 Lab/README.md b/general/WinHEC 2017 Lab/README.md index 1d44f060..1ccabb8b 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.
\ No newline at end of file +Toaster samples from the WinHEC 2017 Lab: Toaster Driver, PlugInToaster, and Toaster Support App. diff --git a/general/cancel/README.md b/general/cancel/README.md index ff53246b..d74cd255 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. +**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 diff --git a/general/echo/kmdf/README.md b/general/echo/kmdf/README.md index 9dcdf601..8a4acf4b 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. +Generic file that lists source files and all the build options.
\ No newline at end of file diff --git a/general/echo/umdf/README.md b/general/echo/umdf/README.md index c1ae545f..4d8cbbe4 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. +- These GUIDs must remain in sync with the trace control GUIDs defined in internal.h.
\ No newline at end of file diff --git a/general/echo/umdf2/README.md b/general/echo/umdf2/README.md index 1a46cc34..2ce91193 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). +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 diff --git a/general/echo/umdfSocketEcho/README.md b/general/echo/umdfSocketEcho/README.md index 579013e1..a3c60afa 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). +**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 diff --git a/general/event/README.md b/general/event/README.md index 0730c156..3af1d845 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. +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 diff --git a/general/filehistory/README.md b/general/filehistory/README.md index 43daa06e..2e87f94b 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. +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 diff --git a/general/ioctl/kmdf/README.md b/general/ioctl/kmdf/README.md index edfc3651..ed04bc3b 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" +For example, for V1.0 KmdfLibraryVersion is "1.0"
\ No newline at end of file diff --git a/general/ioctl/wdm/README.md b/general/ioctl/wdm/README.md index 76717ec8..e1f9cf7c 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. +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 diff --git a/general/obcallback/README.md b/general/obcallback/README.md index 70434d2a..75e12d1a 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 94881da7..5b575667 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). +TEST | Contains source of test application (MYPING).
\ No newline at end of file diff --git a/general/perfcounters/kcs/README.md b/general/perfcounters/kcs/README.md index 347dc1bc..fc916e55 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. +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 diff --git a/general/registry/regfltr/README.md b/general/registry/regfltr/README.md index 141c1238..e01af91d 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. +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 diff --git a/general/toaster/toastDrv/README.md b/general/toaster/toastDrv/README.md index 423d258b..846180c8 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 +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 diff --git a/general/toaster/toastpkg/README.md b/general/toaster/toastpkg/README.md index a66cfe76..b3ada632 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 +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 diff --git a/general/toaster/umdf2/README.md b/general/toaster/umdf2/README.md index b5cfa5f7..7b6eb8fb 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). +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 diff --git a/general/tracing/SystemTraceControl/README.md b/general/tracing/SystemTraceControl/README.md index a1a18c9c..437f194c 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. +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 diff --git a/general/tracing/evntdrv/README.md b/general/tracing/evntdrv/README.md index 13c9542f..ba3dcd65 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). +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 diff --git a/general/tracing/tracedriver/README.md b/general/tracing/tracedriver/README.md index 400452fd..67e27fc2 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). +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 diff --git a/general/umdfSkeleton/README.md b/general/umdfSkeleton/README.md index 6936cfdf..5191bafb 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. +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 diff --git a/gnss/ReadMe.md b/gnss/ReadMe.md index 0e382a34..6d37480d 100644 --- a/gnss/ReadMe.md +++ b/gnss/ReadMe.md @@ -95,4 +95,4 @@ Customer should validate their driver after customizing it. * [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) -* [NMEA format documentation](http://navspark.mybigcommerce.com/content/NMEA_Format_v0.1.pdf) +* [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 f5c4fdfa..d404819a 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.
\ No newline at end of file +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. diff --git a/hid/firefly/README.md b/hid/firefly/README.md index d5db239d..2a5e4aa8 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. +- 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 diff --git a/hid/hclient/README.md b/hid/hclient/README.md index bff1f89b..5ee07fa3 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) +[Human Input Devices Reference](http://msdn.microsoft.com/en-us/library/windows/hardware/ff539956)
\ No newline at end of file diff --git a/hid/hidusbfx2/README.md b/hid/hidusbfx2/README.md index 8c16f094..983b051f 100644 --- a/hid/hidusbfx2/README.md +++ b/hid/hidusbfx2/README.md @@ -275,5 +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 - +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 diff --git a/hid/vhidmini2/README.md b/hid/vhidmini2/README.md index b99eb796..dae9decf 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) +[UMDF HID Minidriver IOCTLs](http://msdn.microsoft.com/en-us/library/windows/hardware/hh463977)
\ No newline at end of file diff --git a/input/kbfiltr/README.md b/input/kbfiltr/README.md index 0343f766..84ab12ef 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. +**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 diff --git a/input/layout/README.md b/input/layout/README.md index 52af37c7..0d1a4d7c 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. +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 diff --git a/input/moufiltr/README.md b/input/moufiltr/README.md index 3a8483c6..d97ac21a 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. +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 diff --git a/network/config/bindview/README.md b/network/config/bindview/README.md index fdb27529..641a4398 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). +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 diff --git a/network/modem/fakemodem/README.md b/network/modem/fakemodem/README.md index aa139958..2cedd97b 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. +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/network/ndis/extension/README.md b/network/ndis/extension/README.md index 554f4af0..30557927 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). +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 diff --git a/network/ndis/filter/README.md b/network/ndis/filter/README.md index 4d65740f..1163fda1 100644 --- a/network/ndis/filter/README.md +++ b/network/ndis/filter/README.md @@ -117,6 +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. - - +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 diff --git a/network/ndis/mux/README.md b/network/ndis/mux/README.md index fbe8ae91..710ab13b 100644 --- a/network/ndis/mux/README.md +++ b/network/ndis/mux/README.md @@ -194,5 +194,4 @@ Precomp.h | Precompile header file 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. - +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 ecb51586..92e52464 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 +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 4d40fadc..9fba66be 100644 --- a/network/ndis/ndisprot_kmdf/README.md +++ b/network/ndis/ndisprot_kmdf/README.md @@ -129,5 +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 - +ProtNotify.rc | Resource file for the notify object dll
\ No newline at end of file diff --git a/network/ndis/netvmini/6x/README.md b/network/ndis/netvmini/6x/README.md index 5ce68d7a..2a46b3d3 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). +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 diff --git a/network/radio/HidSwitchDriverSample/README.md b/network/radio/HidSwitchDriverSample/README.md index 812fd66c..a150b0ca 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). +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 diff --git a/network/radio/RadioManagerSample/README.md b/network/radio/RadioManagerSample/README.md index 5abdb866..4c38c2e3 100644 --- a/network/radio/RadioManagerSample/README.md +++ b/network/radio/RadioManagerSample/README.md @@ -114,5 +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. - +Delete the corresponding registry key.
\ No newline at end of file diff --git a/network/trans/WFPSampler/README.md b/network/trans/WFPSampler/README.md index bf8a630e..fa808b2b 100644 --- a/network/trans/WFPSampler/README.md +++ b/network/trans/WFPSampler/README.md @@ -194,5 +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. - +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 diff --git a/network/trans/ddproxy/README.md b/network/trans/ddproxy/README.md index 636aeb68..bbc3f125 100644 --- a/network/trans/ddproxy/README.md +++ b/network/trans/ddproxy/README.md @@ -80,5 +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). - +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 diff --git a/network/trans/inspect/README.md b/network/trans/inspect/README.md index 9b15b02c..d1dcac7f 100644 --- a/network/trans/inspect/README.md +++ b/network/trans/inspect/README.md @@ -69,5 +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). - +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 diff --git a/network/trans/msnmntr/README.md b/network/trans/msnmntr/README.md index 91bf1356..ad71a788 100644 --- a/network/trans/msnmntr/README.md +++ b/network/trans/msnmntr/README.md @@ -92,5 +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). - +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 diff --git a/network/trans/stmedit/README.md b/network/trans/stmedit/README.md index 17fdff98..75cf7060 100644 --- a/network/trans/stmedit/README.md +++ b/network/trans/stmedit/README.md @@ -81,5 +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). - +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 diff --git a/network/wlan/WDI/README.md b/network/wlan/WDI/README.md index c9327a9c..e825b1b5 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. +This sample demonstrates use of the WLAN WDI.
\ No newline at end of file diff --git a/network/wlan/ihvsampleui/README.md b/network/wlan/ihvsampleui/README.md index db537b91..94f62381 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. +This sample demonstrates the WLAN IHV UI.
\ No newline at end of file diff --git a/network/wsk/echosrv/README.md b/network/wsk/echosrv/README.md index 8c5e8323..a5300b05 100644 --- a/network/wsk/echosrv/README.md +++ b/network/wsk/echosrv/README.md @@ -71,5 +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). - +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 diff --git a/nfc/NfcCxSample/README.md b/nfc/NfcCxSample/README.md index a3af8add..85437cbb 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. + - `DeviceContext` - The class that stores the device instance's state.
\ No newline at end of file diff --git a/nfp/net/inc/README.md b/nfp/net/inc/README.md index 814eaf33..3c8e994b 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) +[User-Mode Driver Framework](http://msdn.microsoft.com/en-us/library/windows/hardware/ff560456)
\ No newline at end of file diff --git a/pofx/PEP/README.md b/pofx/PEP/README.md index ece35c04..fb399a21 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). +* 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 diff --git a/pofx/UMDF2/README.md b/pofx/UMDF2/README.md index b73aadea..64092ecf 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). +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 diff --git a/pofx/WDF/README.md b/pofx/WDF/README.md index 70dbedf7..9c10e060 100644 --- a/pofx/WDF/README.md +++ b/pofx/WDF/README.md @@ -124,5 +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). - +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 diff --git a/pos/drivers/MagneticStripeReader/README.md b/pos/drivers/MagneticStripeReader/README.md index 36e1bd77..e386515c 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. +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 diff --git a/pos/drivers/barcodescanner/README.md b/pos/drivers/barcodescanner/README.md index d5934f8f..bf041f44 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. +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 diff --git a/print/OEM Printer Customization Plug-in Samples/README.md b/print/OEM Printer Customization Plug-in Samples/README.md index b6bd5675..3807f9e6 100644 --- a/print/OEM Printer Customization Plug-in Samples/README.md +++ b/print/OEM Printer Customization Plug-in Samples/README.md @@ -121,4 +121,4 @@ The plug-in implements the `ExpandIntentOptions` method of the `IPrintOemPrintTi This sample shows how a plug-in for a Unidrv-based driver can replace the default UI. It provides new property sheets for the printer property and printing preferences pages. Use this sample as an example of implementing full UI replacement in a Unidrv-based plugin. It also demonstrates the use of the new `IPrintCoreHelper` interface. -This sample is only provided for educational purposes and should not be used in a production environment. +This sample is only provided for educational purposes and should not be used in a production environment.
\ No newline at end of file diff --git a/print/SampleOpenXPS/README.md b/print/SampleOpenXPS/README.md index 7ece3442..3e50790a 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). +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 diff --git a/print/SampleXPS/README.md b/print/SampleXPS/README.md index edc8f7a1..b9c49330 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). +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 diff --git a/print/SimplePipelineFilter/README.md b/print/SimplePipelineFilter/README.md index 94558670..23227cce 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. +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 diff --git a/print/XPSDrvSmpl/README.md b/print/XPSDrvSmpl/README.md index 01a6735f..75a5ca81 100644 --- a/print/XPSDrvSmpl/README.md +++ b/print/XPSDrvSmpl/README.md @@ -247,4 +247,4 @@ When a property page receives a message for a control, it looks up the relevant The sample Print Ticket Provider plug-in is intended to demonstrate how to validate and map driver settings from a DevMode description to a Print Ticket description and back again. The driver allows configuration of custom settings through a custom user interface. These custom settings are represented as either GPD options or in the OEM private DevMode and are mapped to and from the Print Ticket using an XML schema. -To support Print Ticket handling, the Unidrv UI Plug-in Print Ticket Provider Interface is utilized. The Unidrv UI Plug-in interface includes methods that allow mapping of DevMode to and from a Print Ticket Schema. A collection of feature conversion objects are stored at the plug-in interface level, each of which is responsible for the conversion of a specific feature (Color, Watermark, Booklet, Scaling, and NUp). Whenever the Unidrv core calls through the external interface of the plug-in to convert from DevMode to Print Ticket or Print Ticket to DevMode, the collection is iterated through calling each conversion object in turn; each then perform its own DevMode/Print Ticket mapping via the appropriate get and set functions. The sample get and set functions provide an interface to read and write the GPD options, OEM private DevMode, and Print Ticket keyword value pairs. +To support Print Ticket handling, the Unidrv UI Plug-in Print Ticket Provider Interface is utilized. The Unidrv UI Plug-in interface includes methods that allow mapping of DevMode to and from a Print Ticket Schema. A collection of feature conversion objects are stored at the plug-in interface level, each of which is responsible for the conversion of a specific feature (Color, Watermark, Booklet, Scaling, and NUp). Whenever the Unidrv core calls through the external interface of the plug-in to convert from DevMode to Print Ticket or Print Ticket to DevMode, the collection is iterated through calling each conversion object in turn; each then perform its own DevMode/Print Ticket mapping via the appropriate get and set functions. The sample get and set functions provide an interface to read and write the GPD options, OEM private DevMode, and Print Ticket keyword value pairs.
\ No newline at end of file diff --git a/print/XpsRasFilter/README.md b/print/XpsRasFilter/README.md index a4b6447a..481a1896 100644 --- a/print/XpsRasFilter/README.md +++ b/print/XpsRasFilter/README.md @@ -39,4 +39,4 @@ The default parameters in this sample are as follows: - Letter-sized physical page (can override in print ticket). - 0.25-inch margins (creating an 8-inch by 10.5-inch imageable area). - Scaling is set to FitApplicationBleedSizeToImageableSize. -- Destination resolution set to 96 dpi (can override in print ticket). +- Destination resolution set to 96 dpi (can override in print ticket).
\ No newline at end of file diff --git a/print/autoconfig/README.md b/print/autoconfig/README.md index 2085dd72..e50b45b7 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). +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 diff --git a/print/cpsuisam/README.md b/print/cpsuisam/README.md index 5bb6676b..f7859ae7 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). +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 diff --git a/print/v4PrintDriverSamples/PrinterExtensionSample/README.md b/print/v4PrintDriverSamples/PrinterExtensionSample/README.md index d022fcad..5595036d 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) +[v4 Print Driver Interfaces and Enumerations](http://msdn.microsoft.com/en-us/library/hh464103(v=vs.85).aspx)
\ No newline at end of file diff --git a/print/v4PrintDriverSamples/v4PrintDriver-ConstraintScript/README.md b/print/v4PrintDriverSamples/v4PrintDriver-ConstraintScript/README.md index cc3ba307..de67b013 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) +[IPrintSchemaTicket](http://msdn.microsoft.com/en-us/library/hh451398(v=vs.85).aspx)
\ No newline at end of file diff --git a/print/v4PrintDriverSamples/v4PrintDriver-HostBasedSampleDriver/README.md b/print/v4PrintDriverSamples/v4PrintDriver-HostBasedSampleDriver/README.md index c72c4082..584f3cb8 100644 --- a/print/v4PrintDriverSamples/v4PrintDriver-HostBasedSampleDriver/README.md +++ b/print/v4PrintDriverSamples/v4PrintDriver-HostBasedSampleDriver/README.md @@ -66,4 +66,4 @@ For information and instructions about how to test and deploy drivers, see [Deve ## Run the sample -To understand how to run this sample as a Windows driver, see the [v4 Printer Driver](http://msdn.microsoft.com/en-us/library/windows/hardware/hh706306(v=vs.85).aspx) collection of topics. +To understand how to run this sample as a Windows driver, see the [v4 Printer Driver](http://msdn.microsoft.com/en-us/library/windows/hardware/hh706306(v=vs.85).aspx) collection of topics.
\ No newline at end of file diff --git a/print/v4PrintDriverSamples/v4PrintDriver-USBMon-Bidi-Extension/README.md b/print/v4PrintDriverSamples/v4PrintDriver-USBMon-Bidi-Extension/README.md index cba0ed54..303107fc 100644 --- a/print/v4PrintDriverSamples/v4PrintDriver-USBMon-Bidi-Extension/README.md +++ b/print/v4PrintDriverSamples/v4PrintDriver-USBMon-Bidi-Extension/README.md @@ -50,4 +50,4 @@ var cleanArray = []; for ( i = 0; i < readBytes; i++ ) { cleanArray[i] = readBuffer.shift(); } -``` +```
\ No newline at end of file diff --git a/print/v4PrintDriverSamples/v4PrintDriver-WSDMon-Bidi-Extension/README.md b/print/v4PrintDriverSamples/v4PrintDriver-WSDMon-Bidi-Extension/README.md index 8f4755fc..0a852373 100644 --- a/print/v4PrintDriverSamples/v4PrintDriver-WSDMon-Bidi-Extension/README.md +++ b/print/v4PrintDriverSamples/v4PrintDriver-WSDMon-Bidi-Extension/README.md @@ -58,4 +58,4 @@ WSDMON supports the following Xcv commands: **Note** This sample is for the v4 print driver model. -For more information, see [V4 Driver Connectivity Architecture](http://msdn.microsoft.com/en-us/library/windows/hardware/) and [Bidirectional Communication Schema](http://msdn.microsoft.com/en-us/library/windows/hardware/ff545169(v=vs.85).aspx). +For more information, see [V4 Driver Connectivity Architecture](http://msdn.microsoft.com/en-us/library/windows/hardware/) and [Bidirectional Communication Schema](http://msdn.microsoft.com/en-us/library/windows/hardware/ff545169(v=vs.85).aspx).
\ No newline at end of file diff --git a/sd/miniport/sdhc/README.md b/sd/miniport/sdhc/README.md index 73a239cf..29962ad9 100644 --- a/sd/miniport/sdhc/README.md +++ b/sd/miniport/sdhc/README.md @@ -28,4 +28,4 @@ This driver, sdhc.sys, provides a functional miniport implementation for a stand - UHS-I speed modes. - HS400 -- SD 4.0 +- SD 4.0
\ No newline at end of file diff --git a/security/elam/README.md b/security/elam/README.md index 0495be42..3916c0e0 100644 --- a/security/elam/README.md +++ b/security/elam/README.md @@ -122,4 +122,4 @@ ElamSample: 93 29 d5 f2 e2 7a c9 79 41 b2 6d c0 78 35 2a d3 ElamSample: da 2d 7e 72 f0 05 5f 8b 63 8c 7b a2 6b 37 5c 4f ElamSample reports that all Boot Start drivers have been initialized and that ElamSample is about to be unloaded ElamSample is being unloaded. -``` +```
\ No newline at end of file diff --git a/sensors/ADXL345Acc/readme.md b/sensors/ADXL345Acc/readme.md index a9e88e1b..d240d066 100644 --- a/sensors/ADXL345Acc/readme.md +++ b/sensors/ADXL345Acc/readme.md @@ -18,4 +18,4 @@ products: # ADXL345 Accelerometer Sample Driver -The ADXL345 accelerometer sample shows how to write a UMDF v2 driver to control an ADXL345 accelerometer chip. +The ADXL345 accelerometer sample shows how to write a UMDF v2 driver to control an ADXL345 accelerometer chip.
\ No newline at end of file diff --git a/sensors/Activity/readme.md b/sensors/Activity/readme.md index 5024f481..b95d577c 100644 --- a/sensors/Activity/readme.md +++ b/sensors/Activity/readme.md @@ -18,4 +18,4 @@ products: # Activity Sensor Driver Sample -The Activity sample shows how to write a UMDF v2 driver to control an activity sensor. +The Activity sample shows how to write a UMDF v2 driver to control an activity sensor.
\ No newline at end of file diff --git a/sensors/CustomSensors/readme.md b/sensors/CustomSensors/readme.md index 6f1a6081..f6c613fe 100644 --- a/sensors/CustomSensors/readme.md +++ b/sensors/CustomSensors/readme.md @@ -18,4 +18,4 @@ products: # Custom Sensor Driver Sample -The CustomSensor sample shows how to write a UMDF v2 driver to control a custom sensor. +The CustomSensor sample shows how to write a UMDF v2 driver to control a custom sensor.
\ No newline at end of file diff --git a/sensors/Fusion/readme.md b/sensors/Fusion/readme.md index 6d378428..13438cba 100644 --- a/sensors/Fusion/readme.md +++ b/sensors/Fusion/readme.md @@ -18,4 +18,4 @@ products: # Fusion Sensor Driver Sample -The FusionSensor sample shows how to write a UMDF v2 driver to control a virtual FusionSensor sensor. +The FusionSensor sample shows how to write a UMDF v2 driver to control a virtual FusionSensor sensor.
\ No newline at end of file diff --git a/sensors/SensorsComboDriver/readme.md b/sensors/SensorsComboDriver/readme.md index 23ee0a61..a06edd94 100644 --- a/sensors/SensorsComboDriver/readme.md +++ b/sensors/SensorsComboDriver/readme.md @@ -18,4 +18,4 @@ products: # Sensors Combo Driver Sample -The sensors combo driver sensor sample shows how to write UMDF v2 drivers to control various types of virtual sensors such as Ambient Light, Barometer, Gyroscope, Magnetometer, Geomagnetic, Gravity Vector, Proximity, Linear Accelerometer and Relative Fusion. +The sensors combo driver sensor sample shows how to write UMDF v2 drivers to control various types of virtual sensors such as Ambient Light, Barometer, Gyroscope, Magnetometer, Geomagnetic, Gravity Vector, Proximity, Linear Accelerometer and Relative Fusion.
\ No newline at end of file diff --git a/sensors/SimpleDeviceOrientationSensor/readme.md b/sensors/SimpleDeviceOrientationSensor/readme.md index cd1e72c5..d21d502c 100644 --- a/sensors/SimpleDeviceOrientationSensor/readme.md +++ b/sensors/SimpleDeviceOrientationSensor/readme.md @@ -18,4 +18,4 @@ products: # Simple Device Orientation Sensor Sample -The SimpleDeviceOrientationSensor sample shows how to write a UMDF v2 sensor driver to output Simple Device Orientation values. +The SimpleDeviceOrientationSensor sample shows how to write a UMDF v2 sensor driver to output Simple Device Orientation values.
\ No newline at end of file diff --git a/serial/VirtualSerial/README.md b/serial/VirtualSerial/README.md index b24ecaaf..342d1c5c 100644 --- a/serial/VirtualSerial/README.md +++ b/serial/VirtualSerial/README.md @@ -65,4 +65,4 @@ For more information, see [Serial Controller and Device Drivers](http://msdn.mic ### VirtualSerial.inf / FakeModem.inf -- INF file that contains installation information for this driver. +- INF file that contains installation information for this driver.
\ No newline at end of file diff --git a/serial/VirtualSerial2/README.md b/serial/VirtualSerial2/README.md index c3b9220a..e42b8bdc 100644 --- a/serial/VirtualSerial2/README.md +++ b/serial/VirtualSerial2/README.md @@ -66,4 +66,4 @@ For more information, see [Serial Controller and Device Drivers](http://msdn.mic ### VirtualSerial.inf / FakeModem.inf -- INF file that contains installation information for this driver. +- INF file that contains installation information for this driver.
\ No newline at end of file diff --git a/serial/serenum/README.md b/serial/serenum/README.md index 79d1cf35..b2767887 100644 --- a/serial/serenum/README.md +++ b/serial/serenum/README.md @@ -43,4 +43,4 @@ Serenum.h | Local header with defines, prototypes String.c | String handling support; mainly ASCII to UNICODE functionality Serenum.rc | Resource script -For more information, see [Features of Serial and Serenum](http://msdn.microsoft.com/en-us/library/windows/hardware/ff546505). +For more information, see [Features of Serial and Serenum](http://msdn.microsoft.com/en-us/library/windows/hardware/ff546505).
\ No newline at end of file diff --git a/serial/serial/README.md b/serial/serial/README.md index b97575a8..d5a92722 100644 --- a/serial/serial/README.md +++ b/serial/serial/README.md @@ -50,4 +50,4 @@ If you have other hardware such as an add-in card, then you must add the hardwar %PNP0500.DevDesc%= Serial_Inst, *PNP0500, *PNP0501 ; Communications Port %PNP0501.DevDesc%= Serial_Inst, *PNP0501, *PNP0500 ; Communications Port %PNP0501.DevDesc%= Serial_Inst, MF\PCI9710_COM ; Communications Port -``` +```
\ No newline at end of file diff --git a/setup/devcon/README.md b/setup/devcon/README.md index 3d67a9ec..1a603e75 100644 --- a/setup/devcon/README.md +++ b/setup/devcon/README.md @@ -139,4 +139,4 @@ DumpDeviceDriverNodes DumpDeviceStack -- This function determines class and device upper and lower filters. +- This function determines class and device upper and lower filters.
\ No newline at end of file diff --git a/simbatt/README.md b/simbatt/README.md index de5aeeed..360936fe 100644 --- a/simbatt/README.md +++ b/simbatt/README.md @@ -18,4 +18,4 @@ products: # SimBatt: Simulated Battery Driver Sample -SimBatt is simulated battery device driver, this source code is intended to demonstrate implementation of Windows battery driver interfaces. This is a KMDF based sample. You may use this sample as a starting point to implement a battery miniport specific to your needs. +SimBatt is simulated battery device driver, this source code is intended to demonstrate implementation of Windows battery driver interfaces. This is a KMDF based sample. You may use this sample as a starting point to implement a battery miniport specific to your needs.
\ No newline at end of file diff --git a/smartcrd/README.md b/smartcrd/README.md index bfdcd0a3..23bdc5fc 100644 --- a/smartcrd/README.md +++ b/smartcrd/README.md @@ -50,4 +50,4 @@ The driver will not unload as long as you have Ifdtest.exe running and connected ISO 7816 Part 3 describes smart cards and smart card protocols in detail. Refer to the PC99 Handbook for smart card reader requirements. -For more information about Windows smart card reader drivers, see [Smart Card Reader Devices Design Guide](http://msdn.microsoft.com/en-us/library/windows/hardware/). +For more information about Windows smart card reader drivers, see [Smart Card Reader Devices Design Guide](http://msdn.microsoft.com/en-us/library/windows/hardware/).
\ No newline at end of file diff --git a/spb/SkeletonI2C/README.md b/spb/SkeletonI2C/README.md index a9fbb672..647cfa11 100644 --- a/spb/SkeletonI2C/README.md +++ b/spb/SkeletonI2C/README.md @@ -125,4 +125,4 @@ Handles processing for both normal and error condition interrupts. Invokes `Cont `ControllerCompleteTransfer` -Invoked when an I/O completes or an error is detected. If this I/O is part of a sequence, `PbcRequestConfigureForIndex`() is called to prepare the next I/O; otherwise, the request is marked for completion. +Invoked when an I/O completes or an error is detected. If this I/O is part of a sequence, `PbcRequestConfigureForIndex`() is called to prepare the next I/O; otherwise, the request is marked for completion.
\ No newline at end of file diff --git a/spb/SpbTestTool/README.md b/spb/SpbTestTool/README.md index 242f09f4..2fafe026 100644 --- a/spb/SpbTestTool/README.md +++ b/spb/SpbTestTool/README.md @@ -122,4 +122,4 @@ internal.h | Common includes and function definitions main.cpp | Application entry point, input parsing, and main execution loop. Also contains the interrupt notification thread. makefile | Redirects to the real makefile that is shared by all components of the WDK. sources | Lists source files and build options. -util.cpp | Helper functions +util.cpp | Helper functions
\ No newline at end of file diff --git a/storage/class/cdrom/README.md b/storage/class/cdrom/README.md index 5a6f366a..dee04bf0 100644 --- a/storage/class/cdrom/README.md +++ b/storage/class/cdrom/README.md @@ -62,4 +62,4 @@ The in-box CD ROM driver is protected by the system, and thus a normal device dr 1. Click "Next" to complete the driver upgrade. 1. After installation completes successfully, "mycdrom.sys" will be the effective driver for the device, "cdrom.sys" will no longer be used. -For more information, see [CD-ROM Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff551391) in the storage technologies design guide. +For more information, see [CD-ROM Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff551391) in the storage technologies design guide.
\ No newline at end of file diff --git a/storage/class/classpnp/README.md b/storage/class/classpnp/README.md index 60f92316..8e6b4687 100644 --- a/storage/class/classpnp/README.md +++ b/storage/class/classpnp/README.md @@ -28,4 +28,4 @@ This sample builds a Universal Windows Driver. It uses only APIs and DDIs that a The storage class drivers are used to interact with mass storage devices along with appropriate port driver. The class drivers are layered above the port drivers and manage mass storage devices of a specific class, regardless of their bus type. The classpnp sample contains the common routines that are required for all storage class drivers such as PnP and power management. It also provides I/O and error handling support. -For more information, see [Introduction to Storage Class Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff559215) in the storage technologies design guide. +For more information, see [Introduction to Storage Class Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff559215) in the storage technologies design guide.
\ No newline at end of file diff --git a/storage/class/disk/README.md b/storage/class/disk/README.md index 82a08ba6..90e76d00 100644 --- a/storage/class/disk/README.md +++ b/storage/class/disk/README.md @@ -44,4 +44,4 @@ You can build a driver from the command line using the Visual Studio Command Pro The disk class driver is used to interact with disk devices along with the appropriate port driver. The disk class driver is layered above the port driver and manages disk devices regardless of their bus type. This driver attaches to the disk devices that are enumerated by all of the storage port drivers. This driver exposes the required functionality to the file system drivers to access the disk devices. -For more information, see [Introduction to Storage Class Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff559215) in the storage technologies design guide. +For more information, see [Introduction to Storage Class Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff559215) in the storage technologies design guide.
\ No newline at end of file diff --git a/storage/filters/addfilter/README.md b/storage/filters/addfilter/README.md index 47f41838..b0168809 100644 --- a/storage/filters/addfilter/README.md +++ b/storage/filters/addfilter/README.md @@ -38,4 +38,4 @@ The following is the command line usage for addfilter: **addfilter [/listdevices] [/device device\_name] [/add filter] [/remove filter]** -If the device name is not supplied, settings will apply to all devices. If there is no /add or /remove argument, a list of currently installed drivers will be printed. +If the device name is not supplied, settings will apply to all devices. If there is no /add or /remove argument, a list of currently installed drivers will be printed.
\ No newline at end of file diff --git a/storage/iscsi/README.md b/storage/iscsi/README.md index 53edf7da..16d38d0e 100644 --- a/storage/iscsi/README.md +++ b/storage/iscsi/README.md @@ -22,4 +22,4 @@ WMI Implementation in an iSCSI miniport can be tested using the iSCSICLI.exe too ## Installation and Operation -The iSCSI WMI sample uses the iSCSI WMI Class, and MOF definitions described at [iSCSI WMI Classes](http://msdn.microsoft.com/en-us/library/windows/hardware/ff561578) in the storage WMI classes reference. Their corresponding class structure details are described at [iSCSI Structures](http://msdn.microsoft.com/en-us/library/windows/hardware/ff561569). +The iSCSI WMI sample uses the iSCSI WMI Class, and MOF definitions described at [iSCSI WMI Classes](http://msdn.microsoft.com/en-us/library/windows/hardware/ff561578) in the storage WMI classes reference. Their corresponding class structure details are described at [iSCSI Structures](http://msdn.microsoft.com/en-us/library/windows/hardware/ff561569).
\ No newline at end of file diff --git a/storage/miniports/lsi_u3/README.md b/storage/miniports/lsi_u3/README.md index 6d2cb740..1e602832 100644 --- a/storage/miniports/lsi_u3/README.md +++ b/storage/miniports/lsi_u3/README.md @@ -31,4 +31,4 @@ The operation of this sample requires one of the following hardware items: - Parallel SCSI Host Bus Adapter - On-motherboard solution that uses the LSI 53C1010 SCSI ASIC -For more information, see [Storport Miniport Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff567562) in the storage technologies design guide. +For more information, see [Storport Miniport Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff567562) in the storage technologies design guide.
\ No newline at end of file diff --git a/storage/miniports/storahci/README.md b/storage/miniports/storahci/README.md index 3ecb3c2f..771b11a2 100644 --- a/storage/miniports/storahci/README.md +++ b/storage/miniports/storahci/README.md @@ -22,4 +22,4 @@ The StorAhci sample is a Storport ACHI miniport driver. ## 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/storage/msdsm/README.md b/storage/msdsm/README.md index 992992ef..b1b3e4d1 100644 --- a/storage/msdsm/README.md +++ b/storage/msdsm/README.md @@ -210,4 +210,4 @@ It is expected that the adapter that hosts the system volumes (boot/paging) will **Note** Other filter drivers installed as port filters may interfere with the proper operation of the MPIO port filter. Microsoft does not recommend the use of such filter drivers which may be supplied by HBA miniport vendors. -**Note** Since your DSM binary is not signed, you will get Unsigned Driver Pop-Ups. Ignore these and accept the installation of the new driver. Once your package has been successfully qualified by WHQL, your binaries will get signed and your customers will not get unsigned driver popups. +**Note** Since your DSM binary is not signed, you will get Unsigned Driver Pop-Ups. Ignore these and accept the installation of the new driver. Once your package has been successfully qualified by WHQL, your binaries will get signed and your customers will not get unsigned driver popups.
\ No newline at end of file diff --git a/storage/sfloppy/README.md b/storage/sfloppy/README.md index 70ffbc43..ae75294d 100644 --- a/storage/sfloppy/README.md +++ b/storage/sfloppy/README.md @@ -28,4 +28,4 @@ This sample builds a Universal Windows Driver. It uses only APIs and DDIs that a This sample sits a level above the port driver (ATAPI, USB, and so on) in the driver stack and controls communication between the application level and the port driver. The floppy driver takes requests from file system drivers and then sends the appropriate [**SCSI\_REQUEST\_BLOCK**](http://msdn.microsoft.com/en-us/library/windows/hardware/ff565393) (SRB) to the port driver. -For more information, see [Introduction to Storage Class Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff559215) in the storage technologies design guide. +For more information, see [Introduction to Storage Class Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff559215) in the storage technologies design guide.
\ No newline at end of file diff --git a/storage/tools/spti/README.md b/storage/tools/spti/README.md index bc1ee132..034a49b7 100644 --- a/storage/tools/spti/README.md +++ b/storage/tools/spti/README.md @@ -24,4 +24,4 @@ The SCSI Pass Through Interface sample demonstrates how to communicate with a SC The storage port drivers provide an interface for Win32 applications to send SCSI CBDs (Command Descriptor Block) to SCSI devices. The interfaces are [**IOCTL\_SCSI\_PASS\_THROUGH**](http://msdn.microsoft.com/en-us/library/windows/hardware/ff560519) and [**IOCTL\_SCSI\_PASS\_THROUGH\_DIRECT**](http://msdn.microsoft.com/en-us/library/windows/hardware/ff560521). Applications can build a pass-through request and send it to the device by using this IOCTL. -Two command line parameters can be used with *SPTI.EXE*. The first parameter is mandatory. It is the name of the device to be opened. Typical values for this are drive letters such as "C:", or device names as defined by a class driver such as Scanner0, or the SCSI port driver name, ScsiN:, where N = 0, 1, 2, etc. The second parameter is optional and is used to set the share mode (note that access mode and share mode are different things) and sector size. The default share mode is (FILE\_SHARE\_READ | FILE\_SHARE\_WRITE) and the default sector size is 512. A parameter of "r" changes the share mode to only FILE\_SHARE\_READ. A parameter of "w" changes the share mode to only FILE\_SHARE\_WRITE. A parameter of "c" changes the share mode to only FILE\_SHARE\_READ and also changes the sector size to 2048. Typically, a CD-ROM device would use the "c" parameter. +Two command line parameters can be used with *SPTI.EXE*. The first parameter is mandatory. It is the name of the device to be opened. Typical values for this are drive letters such as "C:", or device names as defined by a class driver such as Scanner0, or the SCSI port driver name, ScsiN:, where N = 0, 1, 2, etc. The second parameter is optional and is used to set the share mode (note that access mode and share mode are different things) and sector size. The default share mode is (FILE\_SHARE\_READ | FILE\_SHARE\_WRITE) and the default sector size is 512. A parameter of "r" changes the share mode to only FILE\_SHARE\_READ. A parameter of "w" changes the share mode to only FILE\_SHARE\_WRITE. A parameter of "c" changes the share mode to only FILE\_SHARE\_READ and also changes the sector size to 2048. Typically, a CD-ROM device would use the "c" parameter.
\ No newline at end of file diff --git a/thermal/simsensor/README.md b/thermal/simsensor/README.md index c8e6994a..56fbcaad 100644 --- a/thermal/simsensor/README.md +++ b/thermal/simsensor/README.md @@ -26,4 +26,4 @@ This sample builds a Universal Windows Driver. It uses only APIs and DDIs that a A hardware platform designer can strategically place temperature sensors in various thermal zones around the platform. The operating system gets the temperature readings from the temperature sensor drivers and uses these readings to regulate the temperatures across the platform. Regulation can be either passive or active. For more information, see [Device-Level Thermal Management](http://msdn.microsoft.com/en-us/library/windows/hardware/hh698236). -The SimSensor sample provides the source code for a specialized sensor driver that supports platform-wide thermal management by the operating system. This driver does not make the temperature sensor accessible to applications through the [Sensor API](http://msdn.microsoft.com/en-us/library/windows/hardware/dd318953). +The SimSensor sample provides the source code for a specialized sensor driver that supports platform-wide thermal management by the operating system. This driver does not make the temperature sensor accessible to applications through the [Sensor API](http://msdn.microsoft.com/en-us/library/windows/hardware/dd318953).
\ No newline at end of file diff --git a/thermal/thermalclient/README.md b/thermal/thermalclient/README.md index 7c00733c..641ea12c 100644 --- a/thermal/thermalclient/README.md +++ b/thermal/thermalclient/README.md @@ -24,4 +24,4 @@ This sample is a driver for a simulated device that is a client of Windows therm This sample builds a Universal Windows Driver. It uses only APIs and DDIs that are included in OneCoreUAP. -For more information, see [Device-Level Thermal Management](http://msdn.microsoft.com/en-us/library/windows/hardware/hh698236). +For more information, see [Device-Level Thermal Management](http://msdn.microsoft.com/en-us/library/windows/hardware/hh698236).
\ No newline at end of file diff --git a/tools/dv/samples/DV-FailDriver-WDM/README.md b/tools/dv/samples/DV-FailDriver-WDM/README.md index 30d56cc7..27ae700b 100644 --- a/tools/dv/samples/DV-FailDriver-WDM/README.md +++ b/tools/dv/samples/DV-FailDriver-WDM/README.md @@ -36,4 +36,4 @@ See [Deploying a Driver to a Test Computer](https://msdn.microsoft.com/en-us/lib See [How to test a driver at runtime](https://msdn.microsoft.com/en-us/library/windows/hardware/ff554820) for details on how to run tests on the Toastmon driver. -To observe the injected defect being caught by DV, you should enable DV on the Toastmon driver, and then run the "DF - PNP Surprise Remove (Development and Integration)" test on the Toastmon sample driver and device. +To observe the injected defect being caught by DV, you should enable DV on the Toastmon driver, and then run the "DF - PNP Surprise Remove (Development and Integration)" test on the Toastmon sample driver and device.
\ No newline at end of file diff --git a/tools/sdv/samples/SDV-FailDriver-KMDF/README.md b/tools/sdv/samples/SDV-FailDriver-KMDF/README.md index 06fb7e58..746210f3 100644 --- a/tools/sdv/samples/SDV-FailDriver-KMDF/README.md +++ b/tools/sdv/samples/SDV-FailDriver-KMDF/README.md @@ -57,4 +57,4 @@ The SDV-FailDriver-KMDF sample driver contains intentional code errors that are As the static analysis proceeds, SDV reports the status of the analysis. When the analysis is complete, SDV reports the results and statistics. If the driver fails to satisfy a DDI usage rule, the result is reported as a defect. SDV finds 8 defects in this sample. -On the **Main** tab, under **Results**, click the **Rules** tab. This tab displays the name of each rule that was verified in the last run and the results of the analysis. To view the reported defects, click the **Defect** link in the **Results** column. This opens the [Static Driver Verifier Report Page](http://msdn.microsoft.com/en-us/library/windows/hardware/ff552834) and the [Trace Viewer](http://msdn.microsoft.com/en-us/library/windows/hardware/ff544659), which displays a trace of the code path to the rule violation. For more information, see [Interpreting Static Driver Verifier Results](http://msdn.microsoft.com/en-us/library/windows/hardware/ff547228). +On the **Main** tab, under **Results**, click the **Rules** tab. This tab displays the name of each rule that was verified in the last run and the results of the analysis. To view the reported defects, click the **Defect** link in the **Results** column. This opens the [Static Driver Verifier Report Page](http://msdn.microsoft.com/en-us/library/windows/hardware/ff552834) and the [Trace Viewer](http://msdn.microsoft.com/en-us/library/windows/hardware/ff544659), which displays a trace of the code path to the rule violation. For more information, see [Interpreting Static Driver Verifier Results](http://msdn.microsoft.com/en-us/library/windows/hardware/ff547228).
\ No newline at end of file diff --git a/tools/sdv/samples/SDV-FailDriver-NDIS/README.md b/tools/sdv/samples/SDV-FailDriver-NDIS/README.md index f87bf56a..2ac33b70 100644 --- a/tools/sdv/samples/SDV-FailDriver-NDIS/README.md +++ b/tools/sdv/samples/SDV-FailDriver-NDIS/README.md @@ -50,4 +50,4 @@ The SDV-FailDriver-NDIS sample driver contains intentional code errors that are As the static analysis proceeds, SDV reports the status of the analysis. When the analysis is complete, SDV reports the results and statistics. If the driver fails to satisfy a DDI usage rule, the result is reported as a defect. SDV finds 5 defects in this sample. -On the **Main** tab, under **Results**, click the **Rules** tab. This tab displays the name of each rule that was verified in the last run and the results of the analysis. To view the reported defects, click the **Defect** link in the **Results** column. This opens the [Static Driver Verifier Report Page](http://msdn.microsoft.com/en-us/library/windows/hardware/ff552834) and the [Trace Viewer](http://msdn.microsoft.com/en-us/library/windows/hardware/ff544659), which displays a trace of the code path to the rule violation. For more information, see [Interpreting Static Driver Verifier Results](http://msdn.microsoft.com/en-us/library/windows/hardware/ff547228). +On the **Main** tab, under **Results**, click the **Rules** tab. This tab displays the name of each rule that was verified in the last run and the results of the analysis. To view the reported defects, click the **Defect** link in the **Results** column. This opens the [Static Driver Verifier Report Page](http://msdn.microsoft.com/en-us/library/windows/hardware/ff552834) and the [Trace Viewer](http://msdn.microsoft.com/en-us/library/windows/hardware/ff544659), which displays a trace of the code path to the rule violation. For more information, see [Interpreting Static Driver Verifier Results](http://msdn.microsoft.com/en-us/library/windows/hardware/ff547228).
\ No newline at end of file diff --git a/tools/sdv/samples/SDV-FailDriver-STORPORT/README.md b/tools/sdv/samples/SDV-FailDriver-STORPORT/README.md index ce1ec925..e012e461 100644 --- a/tools/sdv/samples/SDV-FailDriver-STORPORT/README.md +++ b/tools/sdv/samples/SDV-FailDriver-STORPORT/README.md @@ -52,4 +52,4 @@ The SDV-FailDriver-Storport sample driver contains intentional code errors that As the static analysis proceeds, SDV reports the status of the analysis. When the analysis is complete, SDV reports the results and statistics. If the driver fails to satisfy a DDI usage rule, the result is reported as a defect. SDV finds 7 defects in this sample. -On the **Main** tab, under **Results**, click the **Rules** tab. This tab displays the name of each rule that was verified in the last run and the results of the analysis. To view the reported defects, click the **Defect** link in the **Results** column. This opens the [Static Driver Verifier Report Page](http://msdn.microsoft.com/en-us/library/windows/hardware/ff552834) and the [Trace Viewer](http://msdn.microsoft.com/en-us/library/windows/hardware/ff544659), which displays a trace of the code path to the rule violation. For more information, see [Interpreting Static Driver Verifier Results](http://msdn.microsoft.com/en-us/library/windows/hardware/ff547228). +On the **Main** tab, under **Results**, click the **Rules** tab. This tab displays the name of each rule that was verified in the last run and the results of the analysis. To view the reported defects, click the **Defect** link in the **Results** column. This opens the [Static Driver Verifier Report Page](http://msdn.microsoft.com/en-us/library/windows/hardware/ff552834) and the [Trace Viewer](http://msdn.microsoft.com/en-us/library/windows/hardware/ff544659), which displays a trace of the code path to the rule violation. For more information, see [Interpreting Static Driver Verifier Results](http://msdn.microsoft.com/en-us/library/windows/hardware/ff547228).
\ No newline at end of file diff --git a/tools/sdv/samples/SDV-FailDriver-WDM/README.md b/tools/sdv/samples/SDV-FailDriver-WDM/README.md index 0b824e1e..7c6be291 100644 --- a/tools/sdv/samples/SDV-FailDriver-WDM/README.md +++ b/tools/sdv/samples/SDV-FailDriver-WDM/README.md @@ -50,4 +50,4 @@ The SDV-FailDriver-WDM sample driver contains intentional code errors that are d As the static analysis proceeds, SDV reports the status of the analysis. When the analysis is complete, SDV reports the results and statistics. If the driver fails to satisfy a DDI usage rule, the result is reported as a defect. SDV finds 5 defects in this sample. -To view specific defects in the [Static Driver Verifier Report](http://msdn.microsoft.com/en-us/library/windows/hardware/ff552834), click the Defect in the **Results** pane. This opens the [Trace Viewer](http://msdn.microsoft.com/en-us/library/windows/hardware/ff544659), which displays a trace of the code path to the rule violation. For more information, see [Interpreting Static Driver Verifier Results](http://msdn.microsoft.com/en-us/library/windows/hardware/ff547228). +To view specific defects in the [Static Driver Verifier Report](http://msdn.microsoft.com/en-us/library/windows/hardware/ff552834), click the Defect in the **Results** pane. This opens the [Trace Viewer](http://msdn.microsoft.com/en-us/library/windows/hardware/ff544659), which displays a trace of the code path to the rule violation. For more information, see [Interpreting Static Driver Verifier Results](http://msdn.microsoft.com/en-us/library/windows/hardware/ff547228).
\ No newline at end of file diff --git a/usb/UcmCxUcsi/README.md b/usb/UcmCxUcsi/README.md index c9d64f14..aec7f7f1 100644 --- a/usb/UcmCxUcsi/README.md +++ b/usb/UcmCxUcsi/README.md @@ -68,4 +68,4 @@ The remainder of the files perform operations for UCSI and WDF, non-specific to ## When to write a UcmCx client driver -UcmCx is intended for system port controller drivers. If you are bringing up a USB Type-C peripheral, you do not need to write a USB Type-C specific driver; a regular USB client driver will suffice. Refer to [Developing Windows client drivers for USB devices](https://msdn.microsoft.com/en-us/library/windows/hardware/hh406260(v=vs.85).aspx) to determine what type of driver, if any, you need to write to make your USB device work with Windows. You may look at [Do I need to write a driver for my USB Type-C hardware?](https://blogs.msdn.microsoft.com/usbcoreblog/2016/06/20/do-i-need-to-write-a-driver-for-my-usb-type-c-hardware/) for a more detailed overview. +UcmCx is intended for system port controller drivers. If you are bringing up a USB Type-C peripheral, you do not need to write a USB Type-C specific driver; a regular USB client driver will suffice. Refer to [Developing Windows client drivers for USB devices](https://msdn.microsoft.com/en-us/library/windows/hardware/hh406260(v=vs.85).aspx) to determine what type of driver, if any, you need to write to make your USB device work with Windows. You may look at [Do I need to write a driver for my USB Type-C hardware?](https://blogs.msdn.microsoft.com/usbcoreblog/2016/06/20/do-i-need-to-write-a-driver-for-my-usb-type-c-hardware/) for a more detailed overview.
\ No newline at end of file diff --git a/usb/UcmTcpciCxClientSample/README.md b/usb/UcmTcpciCxClientSample/README.md index 2dfab641..5919ee07 100644 --- a/usb/UcmTcpciCxClientSample/README.md +++ b/usb/UcmTcpciCxClientSample/README.md @@ -219,4 +219,4 @@ Microsoft USB Test Tools Tracelog Command Syntax -<https://msdn.microsoft.com/en-us/library/windows/hardware/ff553012(v=vs.85).aspx> +<https://msdn.microsoft.com/en-us/library/windows/hardware/ff553012(v=vs.85).aspx>
\ No newline at end of file diff --git a/usb/UcmUcsiAcpiSample/README.md b/usb/UcmUcsiAcpiSample/README.md index f2ac668b..fc163389 100644 --- a/usb/UcmUcsiAcpiSample/README.md +++ b/usb/UcmUcsiAcpiSample/README.md @@ -61,4 +61,4 @@ The remainder of the files perform operations for UCSI and WDF, non-specific to ## When to write a UcmUcsiCx client driver -UcmUcsiCx is intended to abstract UCSI protocol from UCSI based driver support. If you have a system that implements PPM logic in an Embedded controller which is connected to the system over a non ACPI transport - e.g. USB, PCI, I2C or UART, it is advised that you write a UcmUcsiCx client driver that implements the necessary transport. Ideally, you would just need to replace Acpi class and implement your way to talk to the PPM. Please note, UcmUcsiCx client is the power policy owner. The class extension does handle S0 idling if you chose to enable it in the client driver. +UcmUcsiCx is intended to abstract UCSI protocol from UCSI based driver support. If you have a system that implements PPM logic in an Embedded controller which is connected to the system over a non ACPI transport - e.g. USB, PCI, I2C or UART, it is advised that you write a UcmUcsiCx client driver that implements the necessary transport. Ideally, you would just need to replace Acpi class and implement your way to talk to the PPM. Please note, UcmUcsiCx client is the power policy owner. The class extension does handle S0 idling if you chose to enable it in the client driver.
\ No newline at end of file diff --git a/usb/kmdf_enumswitches/README.md b/usb/kmdf_enumswitches/README.md index c22cfa8f..1d4e0319 100644 --- a/usb/kmdf_enumswitches/README.md +++ b/usb/kmdf_enumswitches/README.md @@ -58,4 +58,4 @@ Here is the overview of the device: - Device moves data from IN endpoint to OUT endpoint. - Device does not change the values of the data it receives nor does it internally create any data. - Endpoints are always double buffered. - - Maximum packet size depends on speed (64 Full speed, 512 High speed). + - Maximum packet size depends on speed (64 Full speed, 512 High speed).
\ No newline at end of file diff --git a/usb/kmdf_fx2/README.md b/usb/kmdf_fx2/README.md index f2c90029..a31a908d 100644 --- a/usb/kmdf_fx2/README.md +++ b/usb/kmdf_fx2/README.md @@ -383,5 +383,3 @@ To trace, you can use the in-box tools, logman and tracerpt, or download XPerf ( 4. View the trace file using Xperf: `xperfview OSRUSBFX2.etl` - - diff --git a/usb/ufxclientsample/README.md b/usb/ufxclientsample/README.md index 7d8b65f0..3197795f 100644 --- a/usb/ufxclientsample/README.md +++ b/usb/ufxclientsample/README.md @@ -39,4 +39,4 @@ This sample is not a functional driver. It is a skeleton driver intended to illu ## Installation Note -Installation on Windows 10 Mobile requires the creation of a package. To properly interact with the USB UI on Windows 10 Mobile, the package must include a Security Element that specifies the ID_CAP_USB capability with DEVICE_READ and DEVICE_WRITE rights. +Installation on Windows 10 Mobile requires the creation of a package. To properly interact with the USB UI on Windows 10 Mobile, the package must include a Security Element that specifies the ID_CAP_USB capability with DEVICE_READ and DEVICE_WRITE rights.
\ No newline at end of file diff --git a/usb/umdf2_fx2/README.md b/usb/umdf2_fx2/README.md index 4a486fd0..ce1742cd 100644 --- a/usb/umdf2_fx2/README.md +++ b/usb/umdf2_fx2/README.md @@ -67,4 +67,4 @@ As an alternative to building the driver sample in Visual Studio, you can build **msbuild /p:configuration=Win8 Release /p:platform=Win32 umdf2\_fx2.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). +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 diff --git a/usb/umdf_filter_kmdf/README.md b/usb/umdf_filter_kmdf/README.md index a5a8af0d..e938c44a 100644 --- a/usb/umdf_filter_kmdf/README.md +++ b/usb/umdf_filter_kmdf/README.md @@ -64,4 +64,4 @@ You can test this sample either by using the [Custom driver access](http://go.mi | Folder | Description | | --- | --- | | usb\umdf_filter_kmdf\kmdf_driver | This directory contains source code for the kmdf_fx2 sample driver. | -| usb\umdf_filter_kmdf\umdf_filter | This directory contains the UMDF filter driver. |
\ No newline at end of file +| usb\umdf_filter_kmdf\umdf_filter | This directory contains the UMDF filter driver. | diff --git a/usb/umdf_filter_umdf/README.md b/usb/umdf_filter_umdf/README.md index ace83811..f9db0a44 100644 --- a/usb/umdf_filter_umdf/README.md +++ b/usb/umdf_filter_umdf/README.md @@ -48,4 +48,4 @@ You can test this sample either by using the [Custom driver access](http://go.mi | Folder | Description | | --- | --- | | usb\umdf_filter_umdf\umdf_driver | This directory contains source code for the umdf_fx2 sample driver. | -| usb\umdf_filter_umdf\umdf_filter | This directory contains the UMDF filter driver. | +| usb\umdf_filter_umdf\umdf_filter | This directory contains the UMDF filter driver. |
\ No newline at end of file diff --git a/usb/umdf_fx2/README.md b/usb/umdf_fx2/README.md index 0b57018e..89c7cadf 100644 --- a/usb/umdf_fx2/README.md +++ b/usb/umdf_fx2/README.md @@ -341,5 +341,4 @@ This directory contains a test application that can be used to drive the UMDF dr usb\\umdf\_fx2\\deviceMetadata -This directory contains the device metadata package for the sample. You must copy the device metadata to the system before installing the device. For information on how to update and deploy device metadata, see [Custom driver access sample](http://go.microsoft.com/fwlink/p/?LinkID=248288). - +This directory contains the device metadata package for the sample. You must copy the device metadata to the system before installing the device. For information on how to update and deploy device metadata, see [Custom driver access sample](http://go.microsoft.com/fwlink/p/?LinkID=248288).
\ No newline at end of file diff --git a/usb/usbsamp/README.md b/usb/usbsamp/README.md index b9d13ad8..54a9f860 100644 --- a/usb/usbsamp/README.md +++ b/usb/usbsamp/README.md @@ -151,4 +151,4 @@ The sample includes a test application, usbsamp.exe. This console application en - To skip validation of the data to be read or written in a particular request, use the command with **-x** option as follows: - **usbsamp.exe -r 1024 -w 1024 -c 100 -x** + **usbsamp.exe -r 1024 -w 1024 -c 100 -x**
\ No newline at end of file diff --git a/usb/usbview/README.md b/usb/usbview/README.md index 688800bc..5e06c913 100644 --- a/usb/usbview/README.md +++ b/usb/usbview/README.md @@ -86,4 +86,4 @@ The file Enum.c contains the routines that enumerate the USB bus and populate th 1. Enumerate Hubs (Root Hubs and External Hubs). Given the name of a hub, use CreateFile() to open the hub. Send the hub an IOCTL\_USB\_GET\_NODE\_INFORMATION request to get info about the hub, such as the number of downstream ports. Create a node in the tree view to represent each hub. 1. Enumerate Downstream Ports. Given a handle to an open hub and the number of downstream ports on the hub, send the hub an IOCTL\_USB\_GET\_NODE\_CONNECTION\_INFORMATION request for each downstream port of the hub to get info about the device (if any) attached to each port. If there is a device attached to a port, send the hub an IOCTL\_USB\_GET\_NODE\_CONNECTION\_NAME request to get the symbolic link name of the hub attached to the downstream port. If there is a hub attached to the downstream port, recurse to step (2). Create a node in the tree view to represent each hub port and attached device. USB configuration and string descriptors are retrieved from attached devices in GetConfigDescriptor() and GetStringDescriptor() by sending an IOCTL\_USB\_GET\_DESCRIPTOR\_FROM\_NODE\_CONNECTION() to the hub to which the device is attached. -The file Display.c contains routines that display information about selected devices in the application edit control. Information about the device was collected during the enumeration of the device tree. This information includes USB device, configuration, and string descriptors and connection and configuration information that is maintained by the USB stack. The routines in this file simply parse and print the data structures for the device that were collected when it was enumerated. The file Dispaud.c parses and prints data structures that are specific to USB audio class devices. +The file Display.c contains routines that display information about selected devices in the application edit control. Information about the device was collected during the enumeration of the device tree. This information includes USB device, configuration, and string descriptors and connection and configuration information that is maintained by the USB stack. The routines in this file simply parse and print the data structures for the device that were collected when it was enumerated. The file Dispaud.c parses and prints data structures that are specific to USB audio class devices.
\ No newline at end of file diff --git a/usb/wdf_osrfx2_lab/README.md b/usb/wdf_osrfx2_lab/README.md index 5455a8c7..e244b09b 100644 --- a/usb/wdf_osrfx2_lab/README.md +++ b/usb/wdf_osrfx2_lab/README.md @@ -382,6 +382,4 @@ The most basic step. The source file contains a minimal amount of code to get th </ol></td> </tr> </tbody> -</table> - - +</table>
\ No newline at end of file diff --git a/video/KMDOD/README.md b/video/KMDOD/README.md index c17df323..111053c3 100644 --- a/video/KMDOD/README.md +++ b/video/KMDOD/README.md @@ -69,4 +69,4 @@ Text This new code provides generic identifiers for ACPI hardware. -You can optionally delete the original lines of code within these sections of the INF file. +You can optionally delete the original lines of code within these sections of the INF file.
\ No newline at end of file diff --git a/video/pixlib/README.md b/video/pixlib/README.md index a307dd21..af19cbf1 100644 --- a/video/pixlib/README.md +++ b/video/pixlib/README.md @@ -20,4 +20,4 @@ products: The PixLib sample demonstrates how to implement the **CPixel** class for use by a display driver. -For more information, see the WDK documentation topic, [CPixel Support Methods for Lightweight MIP Maps](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540585). +For more information, see the WDK documentation topic, [CPixel Support Methods for Lightweight MIP Maps](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540585).
\ No newline at end of file diff --git a/wia/README.md b/wia/README.md index f20504d6..d02b4f3f 100644 --- a/wia/README.md +++ b/wia/README.md @@ -56,4 +56,4 @@ Previous versions of the WDK used the Windows Build utility (Build.exe) and prov ## Run the sample -Run the "copywia.cmd” batch file to gather all of the binaries into a subdirectory named “wiabins”. The WIA driver sample can be installed by using the Add Device icon in the Scanners and Cameras control panel. Use the Have Disk button to point to the wiabins\\drivers or wiabins\\drivers folder. Wiatest.exe (from the WDK Tools\\Wia directory), MS Paint, the Scanner and Camera Wizard, or any TWAIN application (through the WIA TWAIN compatibility layer) can be used to test the samples. +Run the "copywia.cmd” batch file to gather all of the binaries into a subdirectory named “wiabins”. The WIA driver sample can be installed by using the Add Device icon in the Scanners and Cameras control panel. Use the Have Disk button to point to the wiabins\\drivers or wiabins\\drivers folder. Wiatest.exe (from the WDK Tools\\Wia directory), MS Paint, the Scanner and Camera Wizard, or any TWAIN application (through the WIA TWAIN compatibility layer) can be used to test the samples.
\ No newline at end of file diff --git a/wmi/wmiacpi/README.md b/wmi/wmiacpi/README.md index e70e9a2d..d3eb3338 100644 --- a/wmi/wmiacpi/README.md +++ b/wmi/wmiacpi/README.md @@ -44,4 +44,4 @@ To add the sample code to your ACPI bios and access through WMI: 1. Copy *Acpimof.dll* to %windir%\\system32 and add a value named "MofImagePath" under the HKEY\_LOCAL\_MACHINE\\CurrentControlSet\\Services\\WmiAcpi key. The contents of the value should be a path to the *Acpimof.dll* file. 1. Restart your computer. When Plug and Play (PnP) recognizes the new device with a pnpid of pnp0c14, it will install *Wmiacpi.sys* automatically and make the MOF resource in Acpimof.dll available to the WMI schema. -Note that you do not need an INF file because Windows supplies an INF for the ACPI-WMI mapping driver device as part of the operating system. +Note that you do not need an INF file because Windows supplies an INF for the ACPI-WMI mapping driver device as part of the operating system.
\ No newline at end of file diff --git a/wmi/wmisamp/README.md b/wmi/wmisamp/README.md index fd8f3df4..e6960cde 100644 --- a/wmi/wmisamp/README.md +++ b/wmi/wmisamp/README.md @@ -47,4 +47,4 @@ WmiMofCk validates that the classes, properties, methods and events specified in - If the -x parameter is specified, a text file is created that contains the text representation of the binary .mof data. This can be included in the source of the driver if the driver supports reporting the binary .mof via a WMI query rather than a resource on the driver image file. - Usage: wmimofck -h\<C Header output file\> -x\<Hexdump output file\> -t\<VBScript test output file\> \<binary mof input file\> -**Note** A byproduct of compiling the .mof file is a .vbs file. This is a VBScript file that is run from the command line on the target machine running the new device driver. It will cause WMI to query all data blocks and properties, and put the results into a .log file. This can be very useful for testing WMI support in your driver. For more sophisticated testing, the VBScript can be extended by hand. +**Note** A byproduct of compiling the .mof file is a .vbs file. This is a VBScript file that is run from the command line on the target machine running the new device driver. It will cause WMI to query all data blocks and properties, and put the results into a .log file. This can be very useful for testing WMI support in your driver. For more sophisticated testing, the VBScript can be extended by hand.
\ No newline at end of file diff --git a/wpd/WpdBasicHardwareDriver/README.md b/wpd/WpdBasicHardwareDriver/README.md index 5b8837ce..56c803d4 100644 --- a/wpd/WpdBasicHardwareDriver/README.md +++ b/wpd/WpdBasicHardwareDriver/README.md @@ -53,4 +53,4 @@ To install the WpdBasicHardwareDriver sample, do the following: 1. Navigate to the directory that contains the INF file and binaries (for example, cd /d c:\\wpdbasichardwaredriver), and run DevCon.exe as follows: **devcon.exe install wpdbasichardwaredriver.inf WUDF\\WpdBasicHardware** - You can find DevCon.exe in the \\tools directory of the WDK (for example, \\tools\\devcon\\i386\\devcon.exe). + You can find DevCon.exe in the \\tools directory of the WDK (for example, \\tools\\devcon\\i386\\devcon.exe).
\ No newline at end of file diff --git a/wpd/WpdHelloWorldDriver/README.md b/wpd/WpdHelloWorldDriver/README.md index 13e40cce..6eb2028a 100644 --- a/wpd/WpdHelloWorldDriver/README.md +++ b/wpd/WpdHelloWorldDriver/README.md @@ -83,4 +83,4 @@ For a complete description of this sample and its underlying code and functional [WPD Driver Development Tools](http://msdn.microsoft.com/en-us/library/windows/hardware/ff597568) -[WPD Programming Guide](https://msdn.microsoft.com/en-us/library/windows/hardware/ff597898) +[WPD Programming Guide](https://msdn.microsoft.com/en-us/library/windows/hardware/ff597898)
\ No newline at end of file diff --git a/wpd/WpdMultiTransportDriver/README.md b/wpd/WpdMultiTransportDriver/README.md index bc4943b3..3d42cd0a 100644 --- a/wpd/WpdMultiTransportDriver/README.md +++ b/wpd/WpdMultiTransportDriver/README.md @@ -30,4 +30,4 @@ For a complete description of this sample and its underlying code and functional [WPD Driver Development Tools](http://msdn.microsoft.com/en-us/library/windows/hardware/ff597568) -[WPD Programming Guide](https://msdn.microsoft.com/en-us/library/windows/hardware/ff597898) +[WPD Programming Guide](https://msdn.microsoft.com/en-us/library/windows/hardware/ff597898)
\ No newline at end of file diff --git a/wpd/WpdWudfSampleDriver/README.md b/wpd/WpdWudfSampleDriver/README.md index d0898cb4..b11d7f85 100644 --- a/wpd/WpdWudfSampleDriver/README.md +++ b/wpd/WpdWudfSampleDriver/README.md @@ -32,4 +32,4 @@ For a complete description of this sample and its underlying code and functional [WPD Driver Development Tools](http://msdn.microsoft.com/en-us/library/windows/hardware/ff597568) -[WPD Programming Guide](https://msdn.microsoft.com/en-us/library/windows/hardware/ff597898) +[WPD Programming Guide](https://msdn.microsoft.com/en-us/library/windows/hardware/ff597898)
\ No newline at end of file |