diff options
| author | Den Delimarsky <[email protected]> | 2019-03-13 13:01:43 -0700 |
|---|---|---|
| committer | Den Delimarsky <[email protected]> | 2019-03-13 13:01:43 -0700 |
| commit | b376cda09e60215ea229d55e19ade907d84cdf81 (patch) | |
| tree | aad88b2816ac5c59b67be032361eef955052dc20 | |
| parent | f70a523e2345250a2e6daa3a51babc2b0a08818f (diff) | |
Testing samples browser integration
24 files changed, 22 insertions, 28 deletions
diff --git a/audio/sysvad/README.md b/audio/sysvad/README.md index 137dd489..3e5cfa79 100644 --- a/audio/sysvad/README.md +++ b/audio/sysvad/README.md @@ -41,7 +41,6 @@ KeywordDetectorAdapter | Sample Keyword Detector Adapter. For more information about the Windows audio engine, see [Exposing Hardware-Offloaded Audio Processing in Windows](http://msdn.microsoft.com/en-us/windows/hardware/br259116), and note that audio hardware that is offload-capable replicates the architecture that is presented in the diagram shown in the topic. - Build the sample ---------------- diff --git a/avstream/avscamera/README.md b/avstream/avscamera/README.md index 8a76bfc4..9ab30cfe 100644 --- a/avstream/avscamera/README.md +++ b/avstream/avscamera/README.md @@ -31,4 +31,4 @@ This sample builds a Universal Windows Driver. It uses only APIs and DDIs that a ## Building the sample -The AvsCamera sample can be built by opening the AvsCamera.sln solution file. A successful build produces AvsCamera.sys, AvsCameraMft0.dll, AvsCamera.inf and AvsCamera.cat. +The AvsCamera sample can be built by opening the AvsCamera.sln solution file. A successful build produces AvsCamera.sys, AvsCameraMft0.dll, AvsCamera.inf and AvsCamera.cat.
\ No newline at end of file diff --git a/avstream/avscamera/mft0/README.md b/avstream/avscamera/mft0/README.md index 8a76bfc4..9ab30cfe 100644 --- a/avstream/avscamera/mft0/README.md +++ b/avstream/avscamera/mft0/README.md @@ -31,4 +31,4 @@ This sample builds a Universal Windows Driver. It uses only APIs and DDIs that a ## Building the sample -The AvsCamera sample can be built by opening the AvsCamera.sln solution file. A successful build produces AvsCamera.sys, AvsCameraMft0.dll, AvsCamera.inf and AvsCamera.cat. +The AvsCamera sample can be built by opening the AvsCamera.sln solution file. A successful build produces AvsCamera.sys, AvsCameraMft0.dll, AvsCamera.inf and AvsCamera.cat.
\ No newline at end of file diff --git a/avstream/avshws/README.md b/avstream/avshws/README.md index 4571ce5e..a7d3ad23 100644 --- a/avstream/avshws/README.md +++ b/avstream/avshws/README.md @@ -88,7 +88,7 @@ Code tour ### File Manifest -File | Description +File | Description -----|------------ Avshws.h | Main header file for the sample Avshws.inf | Sample installation file diff --git a/avstream/avssamp/README.md b/avstream/avssamp/README.md index ec5b07e4..51c23a50 100644 --- a/avstream/avssamp/README.md +++ b/avstream/avssamp/README.md @@ -65,5 +65,4 @@ Purecall.h | _purecall stub necessary for virtual function usage in drivers. Video.cpp | Video capture pin implementation. Video.h | Video capture pin header. Wave.cpp | Wave object implementation -Wave.h | Wave object header - +Wave.h | Wave object header
\ No newline at end of file diff --git a/avstream/sampledevicemft/README.md b/avstream/sampledevicemft/README.md index ecb5e9c6..e00a9bd4 100644 --- a/avstream/sampledevicemft/README.md +++ b/avstream/sampledevicemft/README.md @@ -45,4 +45,4 @@ Related topics [Device app for camera sample](http://go.microsoft.com/fwlink/p/?linkid=249442) -[Camera Capture UI sample](http://go.microsoft.com/fwlink/p/?linkid=249441%20) +[Camera Capture UI sample](http://go.microsoft.com/fwlink/p/?linkid=249441%20)
\ No newline at end of file diff --git a/avstream/samplemft0/README.md b/avstream/samplemft0/README.md index f7be80e5..9c059455 100644 --- a/avstream/samplemft0/README.md +++ b/avstream/samplemft0/README.md @@ -43,4 +43,4 @@ Related topics [Device app for camera sample](http://go.microsoft.com/fwlink/p/?linkid=249442) -[Camera Capture UI sample](http://go.microsoft.com/fwlink/p/?linkid=249441%20) +[Camera Capture UI sample](http://go.microsoft.com/fwlink/p/?linkid=249441%20)
\ No newline at end of file diff --git a/biometrics/README.md b/biometrics/README.md index f7debb2e..e6f8bfb8 100644 --- a/biometrics/README.md +++ b/biometrics/README.md @@ -92,4 +92,4 @@ WinBio Adapters are plug-in components that provide a standard interface layer b For many simple biometric devices, it will only be necessary to write a WBDI driver for the device plus an Engine Adapter to perform matching operations. Consult the programming guidelines in the WinBio Service documentation for more details. -Each Adapter sample contains a well-known interface-discovery function, whose job is to return the address of a function dispatch table. When the WinBio Service loads an Adapter plug-in, it uses the interface-discovery function to locate the dispatch table, and then calls various methods in the table to communicate with the biometric device. The purpose, arguments, and return codes of each Adapter method are described in the WinBio Service programming guidelines. More information on adapter plug-ins is available at [WBDI Plug-in Reference](https://docs.microsoft.com/windows/desktop/SecBioMet/plug-in-reference). +Each Adapter sample contains a well-known interface-discovery function, whose job is to return the address of a function dispatch table. When the WinBio Service loads an Adapter plug-in, it uses the interface-discovery function to locate the dispatch table, and then calls various methods in the table to communicate with the biometric device. The purpose, arguments, and return codes of each Adapter method are described in the WinBio Service programming guidelines. More information on adapter plug-ins is available at [WBDI Plug-in Reference](https://docs.microsoft.com/windows/desktop/SecBioMet/plug-in-reference).
\ No newline at end of file diff --git a/bluetooth/bthecho/bthsrv/README.md b/bluetooth/bthecho/bthsrv/README.md index 6d3c7215..22b969f7 100644 --- a/bluetooth/bthecho/bthsrv/README.md +++ b/bluetooth/bthecho/bthsrv/README.md @@ -226,6 +226,4 @@ One transition to note here is that if disconnect is received in the connecting **Sending and receiving data from server**: When application writes data to the client, client sends this data to server on the connection opened for the given handle. Server would echo back this data. This data is retrieved by the application using a read operation. Echo Sample Client doesn't do any draining of echoed data on its own. Application read/write are handled using a parallel WDF I/O queue. -**Shutdown**: Client doesn't need any specific shutdown code as connection open/close and read/write are done within the context of application's handle open. - - +**Shutdown**: Client doesn't need any specific shutdown code as connection open/close and read/write are done within the context of application's handle open.
\ No newline at end of file diff --git a/bluetooth/serialhcibus/README.md b/bluetooth/serialhcibus/README.md index 8e585493..9a8fe7cb 100644 --- a/bluetooth/serialhcibus/README.md +++ b/bluetooth/serialhcibus/README.md @@ -75,4 +75,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 +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 ff09194b..ee5744c3 100644 --- a/filesys/cdfs/README.md +++ b/filesys/cdfs/README.md @@ -24,5 +24,5 @@ The CD-ROM file system driver (cdfs) sample is a sample file system driver that Cdfs is a read-only file system that addresses various issues such as accessing data on disk, interacting with the cache manager, and handling various I/O operations such as opening files, performing reads on a file, retrieving information on a file, and performing various control operations on the file system. The Cdfs file system is included with the Microsoft Windows operating system. ## Universal Windows Driver Compliant -This sample builds a Universal Windows Driver. It uses only APIs and DDIs that are included in OneCoreUAP. +This sample builds a Universal Windows Driver. It uses only APIs and DDIs that are included in OneCoreUAP.
\ No newline at end of file diff --git a/filesys/fastfat/README.md b/filesys/fastfat/README.md index 6988b362..d8964077 100644 --- a/filesys/fastfat/README.md +++ b/filesys/fastfat/README.md @@ -58,4 +58,4 @@ You can build a driver from the command line using the Visual Studio Command Pro Installation ------------ -No INF file is provided with this sample because the *fastfat* file system driver (fastfat.sys) is already part of the Windows operating system. You can build a private version of this file system and use it as a replacement for the native driver. +No INF file is provided with this sample because the *fastfat* file system driver (fastfat.sys) is already part of the Windows operating system. You can build a private version of this file system and use it as a replacement for the native driver.
\ No newline at end of file diff --git a/filesys/miniFilter/MetadataManager/README.md b/filesys/miniFilter/MetadataManager/README.md index 31676011..19b4703e 100644 --- a/filesys/miniFilter/MetadataManager/README.md +++ b/filesys/miniFilter/MetadataManager/README.md @@ -35,4 +35,4 @@ Similarly, the minifilter might close its metadata file if it sees an explicit F The metadata minifilter also handles the case when a snapshot of its volume object is being taken. In this scenario, the minifilter acquires a shared exclusive lock on the metadata resource object while calling the callback that corresponds to the pre-device control operation for IOCTL\_VOLSNAP\_FLUSH\_AND\_HOLD\_WRITES. The lock is later released in the callback that corresponds to the post-device control operation for IOCTL\_VOLSNAP\_FLUSH\_AND\_HOLD\_WRITES. The lock is acquired to prevent any modifications on the metadata file while the snapshot is being taken. -For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide. +For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide.
\ No newline at end of file diff --git a/filesys/miniFilter/NameChanger/README.md b/filesys/miniFilter/NameChanger/README.md index b4257d91..78a46165 100644 --- a/filesys/miniFilter/NameChanger/README.md +++ b/filesys/miniFilter/NameChanger/README.md @@ -101,4 +101,3 @@ F:\\X\\Y After the minifilter attaches, the "B" subdirectory of F:\\A is no longer visible. Its contents now appear under the "Y" subdirectory of F:\\X. For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide. - diff --git a/filesys/miniFilter/avscan/README.md b/filesys/miniFilter/avscan/README.md index 2086c987..70032b20 100644 --- a/filesys/miniFilter/avscan/README.md +++ b/filesys/miniFilter/avscan/README.md @@ -22,5 +22,4 @@ 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. - +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 93aebaaa..fbb25f2a 100644 --- a/filesys/miniFilter/cancelSafe/README.md +++ b/filesys/miniFilter/cancelSafe/README.md @@ -29,4 +29,4 @@ Design and Operation The *CancelSafe* minifilter initializes a cancel-safe queue when it is attached to a volume. When the minifilter is deployed, it monitors read operations that are passing through the I/O stack. If the read operation is being performed on a file named csqdemo.txt, it is queued onto the cancel-safe queue. Queued operations are completed after a brief pause through a separate worker thread that is running in system context. -For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide. +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/cdo/README.md b/filesys/miniFilter/cdo/README.md index bdbea50d..f9badb52 100644 --- a/filesys/miniFilter/cdo/README.md +++ b/filesys/miniFilter/cdo/README.md @@ -32,4 +32,4 @@ Design and Operation When the CDO minifilter is deployed, it creates a CDO object named "FileSystem\\Filters\\CdoSample" in the Microsoft Windows object namespace and enables applications to open it and perform certain operations on it. -For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide. +For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide.
\ No newline at end of file diff --git a/filesys/miniFilter/change/README.md b/filesys/miniFilter/change/README.md index 8a2e39ad..b3ab7303 100644 --- a/filesys/miniFilter/change/README.md +++ b/filesys/miniFilter/change/README.md @@ -32,4 +32,4 @@ The primary tasks of the filter for tracking a transacted file are the following ## Universal Windows Driver Compliant -This sample builds a Universal Windows Driver. It uses only APIs and DDIs that are included in OneCoreUAP. +This sample builds a Universal Windows Driver. It uses only APIs and DDIs that are included in OneCoreUAP.
\ No newline at end of file diff --git a/filesys/miniFilter/ctx/README.md b/filesys/miniFilter/ctx/README.md index e01f1e3b..c6b76ef5 100644 --- a/filesys/miniFilter/ctx/README.md +++ b/filesys/miniFilter/ctx/README.md @@ -29,4 +29,4 @@ This sample builds a Universal Windows Driver. It uses only APIs and DDIs that a The *Ctx* minifilter demonstrates how to attach and remove contexts from instances, files, steams, and stream handles. *Ctx* attaches a context whenever one of these objects is created. While attaching a context to a file, the sample also creates a stream and stream handle context. All contexts are ultimately deleted by the filter manager using the callback function that the *Ctx* minifilter provides. -For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide. +For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide.
\ No newline at end of file diff --git a/filesys/miniFilter/delete/README.md b/filesys/miniFilter/delete/README.md index 70ebf09f..83129954 100644 --- a/filesys/miniFilter/delete/README.md +++ b/filesys/miniFilter/delete/README.md @@ -31,4 +31,4 @@ The *delete* minifilter illustrates how to detect deletion of files and streams. **Note** Because of the way in which the Windows operating system deletes files, it is not possible for the minifilter to detect in advance that a file or stream will be deleted. The minifilter can only detect operations that may cause a deletion, and then determine if the deletion took place after the operation completes. -For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide. +For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide.
\ No newline at end of file diff --git a/filesys/miniFilter/minispy/README.md b/filesys/miniFilter/minispy/README.md index e487235b..92d73723 100644 --- a/filesys/miniFilter/minispy/README.md +++ b/filesys/miniFilter/minispy/README.md @@ -31,4 +31,4 @@ Minispy consists of both user-mode and kernel-mode components. The kernel-mode c To observe I/O activity on a device, you must explicitly attach Minispy to that device by using the Minispy user-mode component. Similarly, you can request Minispy to stop logging data for a particular device. -For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide. +For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide.
\ No newline at end of file diff --git a/filesys/miniFilter/nullFilter/README.md b/filesys/miniFilter/nullFilter/README.md index 8a2f1a04..d5896b50 100644 --- a/filesys/miniFilter/nullFilter/README.md +++ b/filesys/miniFilter/nullFilter/README.md @@ -29,4 +29,4 @@ This sample builds a Universal Windows Driver. It uses only APIs and DDIs that a The *NullFilter* minifilter is a simple minifilter that registers itself with the filter manager for no callback operations. -For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide. +For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide.
\ No newline at end of file diff --git a/filesys/miniFilter/passThrough/README.md b/filesys/miniFilter/passThrough/README.md index f7f2a520..d35f70a9 100644 --- a/filesys/miniFilter/passThrough/README.md +++ b/filesys/miniFilter/passThrough/README.md @@ -29,4 +29,4 @@ This sample builds a Universal Windows Driver. It uses only APIs and DDIs that a The *PassThrough* minifilter does not have any real functionality. For each type of I/O operation, the same pre and post callback functions are called. These callback functions simply forward the I/O request to the next filter on the stack. -For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide. +For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide.
\ No newline at end of file diff --git a/filesys/miniFilter/scanner/README.md b/filesys/miniFilter/scanner/README.md index fa2559e2..872b98d6 100644 --- a/filesys/miniFilter/scanner/README.md +++ b/filesys/miniFilter/scanner/README.md @@ -31,4 +31,4 @@ The Scanner minifilter comprises both kernel-mode and user-mode components. The The kernel-mode component scans files with specific extensions only. The file is first scanned on a successful open. If the file was opened with write access, it is scanned again before a close. Scanning is also performed on data that is about to be written to a file. Writes will be rejected if any occurrences of a "foul" string are found in the data. If a "foul" string is detected during the closing of a file, a debug message is printed. -For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide. +For more information on file system minifilter design, start with the [File System Minifilter Drivers](http://msdn.microsoft.com/en-us/library/windows/hardware/ff540402) section in the Installable File Systems Design Guide.
\ No newline at end of file |