diff options
| -rw-r--r-- | input/kbfiltr/README.md | 65 | ||||
| -rw-r--r-- | input/layout/README.md | 53 | ||||
| -rw-r--r-- | input/moufiltr/README.md | 10 | ||||
| -rw-r--r-- | network/ndis/filter/README.md | 11 | ||||
| -rw-r--r-- | network/ndis/mux/README.md | 11 | ||||
| -rw-r--r-- | network/ndis/ndisprot/6x/README.md | 11 | ||||
| -rw-r--r-- | network/ndis/ndisprot_kmdf/README.md | 11 | ||||
| -rw-r--r-- | network/radio/RadioManagerSample/README.md | 11 | ||||
| -rw-r--r-- | network/trans/WFPSampler/README.md | 11 | ||||
| -rw-r--r-- | network/trans/ddproxy/README.md | 11 | ||||
| -rw-r--r-- | network/trans/inspect/README.md | 11 | ||||
| -rw-r--r-- | network/trans/msnmntr/README.md | 11 | ||||
| -rw-r--r-- | network/wsk/echosrv/README.md | 11 | ||||
| -rw-r--r-- | pofx/UMDF2/README.md | 10 | ||||
| -rw-r--r-- | pofx/WDF/README.md | 10 | ||||
| -rw-r--r-- | print/OEM Printer Customization Plug-in Samples/README.md | 11 | ||||
| -rw-r--r-- | print/XPSDrvSmpl/README.md | 11 |
17 files changed, 48 insertions, 232 deletions
diff --git a/input/kbfiltr/README.md b/input/kbfiltr/README.md index 90b59f79..6bbbe933 100644 --- a/input/kbfiltr/README.md +++ b/input/kbfiltr/README.md @@ -8,16 +8,6 @@ products: - windows-wdk --- - -<!--- - name: Keyboard Input WDF Filter Driver (Kbfiltr) - platform: KMDF - language: cpp - category: HID WDF - description: A WDF example of a keyboard input filter driver. - samplefwlink: http://go.microsoft.com/fwlink/p/?LinkId=620194 ----> - # Keyboard Input WDF Filter Driver (Kbfiltr) The Kbdfltr sample is an example of a keyboard input filter driver. @@ -35,20 +25,18 @@ This driver filters input for a particular keyboard on the system. If you want t This sample builds a Universal Windows Driver. It uses only APIs and DDIs that are included in OneCoreUAP. -Set the hardware ID in the inx file ------------------------------------ +## Set the hardware ID in the inx file This step is required for automatic deployment (described later) to work properly. In the kbfiltr.inx file (located with the driver source files), find the [DDK\_Ex.Mfg.NT\$ARCH\$] section. Change the hardware ID in the %DDK\_Ex% entry from the dummy value to the hardware ID of the PS/2 keyboard on the target computer. The following example shows the hardware ID change. -``` +```INF ; For XP and above [DDK_Ex.Mfg.NT$ARCH$] ;%DDK_Ex% = kbfiltr, *PNP0BAAD %DDK_Ex% = kbfiltr, ACPI\VEN_PNP&DEV_0303 ``` -Build the sample using Visual Studio ------------------------------------- +## Build the sample using Visual Studio In Visual Studio, on the **Build** menu, choose **Build Solution**. @@ -56,33 +44,30 @@ For more information about using Visual Studio to build a driver package, see [B The test application, *kbftest.exe* is also built as part of the solution under the 'exe' folder. -Locate the built driver package -------------------------------- +## Locate the built driver package In File Explorer, navigate to the folder that contains your built driver package. The location of this folder varies depending on what you set for configuration and platform. For example, if your settings are **Debug** and **x64**, the package is your solution folder under \\Debug\\Package. The package contains these files: -File | Description ------|------------ -Kmdfsamples.cat | A signed catalog file, which serves as the signature for the entire package. -kbfiltr.inf | An information (INF) file that contains information needed to install the driver. -WdfCoinstaller010xx.dll | The coinstaller for version 1.xx of KMDF. -kbfiltr.sys | The driver file. +| File | Description | +| --- | --- | +| Kmdfsamples.cat | A signed catalog file, which serves as the signature for the entire package. | +| kbfiltr.inf | An information (INF) file that contains information needed to install the driver. | +| WdfCoinstaller010xx.dll | The coinstaller for version 1.xx of KMDF. | +| kbfiltr.sys | The driver file. | -Using MSBuild -------------- +## Using MSBuild As an alternative to building the Kbfiltr Filter Driver sample in Visual Studio, you can build it in a Visual Studio Command Prompt window. In Visual Studio, on the **Tools** menu, choose **Visual Studio Command Prompt**. In the Visual Studio Command Prompt window, navigate to the folder that has the solution file, kbfiltr.sln. Use the [MSBuild](http://go.microsoft.com/fwlink/p/?linkID=262804) command to build the solution. Here are some examples: -**msbuild /p:configuration="Debug" /p:platform="x64" kbfiltr.sln** +- **msbuild /p:configuration="Debug" /p:platform="x64" kbfiltr.sln** -**msbuild /p:configuration="Release" /p:platform="Win32" kbfiltr.sln** +- **msbuild /p:configuration="Release" /p:platform="Win32" kbfiltr.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). -Run the sample --------------- +## Run the sample The computer where you install the driver is called the *target computer* or the *test computer*. Typically this is a separate computer from where you develop and build the driver package. The computer where you develop and build the driver is called the *host computer*. @@ -92,16 +77,19 @@ The process of moving the driver package to the target computer and installing t Before you automatically deploy a driver, you must provision the target computer. For instructions, see [Configuring a Computer for Driver Deployment, Testing, and Debugging](http://msdn.microsoft.com/en-us/library/windows/hardware/). -1. On the host computer, in Visual Studio, in Solution Explorer, right click **package** (lower case), and choose **Properties**. Navigate to **Configuration Properties \> Driver Install \> Deployment**. -2. Check **Enable deployment**, and check **Remove previous driver versions before deployment**. For **Target Computer Name**, select the name of a target computer that you provisioned previously. Select **Install and Verify**, and choose **Default Driver Package Installation Task** in the list. Click **OK**. -3. On the **Build** menu, choose **Deploy Package** or **Build Solution**. +1. On the host computer, in Visual Studio, in Solution Explorer, right click **package** (lower case), and choose **Properties**. Navigate to **Configuration Properties \> Driver Install \> Deployment**. + +1. Check **Enable deployment**, and check **Remove previous driver versions before deployment**. For **Target Computer Name**, select the name of a target computer that you provisioned previously. Select **Install and Verify**, and choose **Default Driver Package Installation Task** in the list. Click **OK**. + +1. On the **Build** menu, choose **Deploy Package** or **Build Solution**. ### Manual deployment Before you manually deploy a driver, you must turn on test signing and install a certificate on the target computer. You also need to copy the [DevCon](http://msdn.microsoft.com/en-us/library/windows/hardware/ff544707) tool to the target computer. For instructions, see [Preparing a Computer for Manual Driver Deployment](https://docs.microsoft.com/en-us/windows-hardware/drivers/develop/preparing-a-computer-for-manual-driver-deployment). -1. Copy all of the files in your driver package to a folder on the target computer (for example, c:\\KbfiltrDriverPackage). -2. On the target computer, open a Command Prompt window as Administrator. Navigate to your driver package folder, and enter the Devcon command with the correct hardware ID, such as: +1. Copy all of the files in your driver package to a folder on the target computer (for example, c:\\KbfiltrDriverPackage). + +1. On the target computer, open a Command Prompt window as Administrator. Navigate to your driver package folder, and enter the Devcon command with the correct hardware ID, such as: **Devcon install kbfiltr.inf ACPI\\VEN\_PNP&DEV\_0303** @@ -109,14 +97,13 @@ Before you manually deploy a driver, you must turn on test signing and install a Using Device Manager, update the driver for the PS/2 Keyboard by manually selecting kbfiltr.inf from the location where you copied the driver files. -View the installed driver in Device Manager -------------------------------------------- +## View the installed driver in Device Manager On the target computer, in a Command Prompt window, enter **devmgmt** to open Device Manager. In Device Manager, on the **View** menu, choose **Devices by type**. In the device tree, locate **DDK Example Device that needs filtering** under the **Keyboards** node. -Testing -------- +## 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] +> Optional information to help a user be more successfulTo avoid DLL dependencies for kbftext.exe, and the need to copy additional files, select the statically linked run-time library when building. diff --git a/input/layout/README.md b/input/layout/README.md index 32fb84c6..eb654d31 100644 --- a/input/layout/README.md +++ b/input/layout/README.md @@ -8,66 +8,59 @@ products: - windows-wdk --- - -<!--- - name: Keyboard Layout Samples - platform: Application - language: cpp - category: HID - description: Demonstrates how to generate layouts for various keyboards and locales. - samplefwlink: https://aka.ms/rapjms ----> - # Keyboard Layout Samples The keyboard layout samples demonstrate how to generate layouts for various keyboards and locales. -Build the sample ----------------- +## Build the sample Starting in the WDK, you can build the sample in two ways: using the Visual Studio Integrated Development Environment (IDE) or from the command line using the Visual Studio Command Prompt window and the Microsoft Build Engine (MSBuild.exe). ### Building the sample using Visual Studio -1. Open Visual Studio. From the **File** menu, select **Open Project/Solution**. Within your WDK installation, navigate to src\\input\\layout and open the kbd.sln project file. -2. Right-click the solution in the **Solution Explorer** and select **Configuration Manager**. -3. From the **Configuration Manager**, select the **Active Solution Configuration** (for example, Windows 8.1 Debug or Windows 8.1 Release) and the **Active Solution Platform** (for example, Win32) that correspond to the type of build you are interested in. -4. From the **Build** menu, click **Build Solution** (Ctrl+Shift+B). +1. Open Visual Studio. From the **File** menu, select **Open Project/Solution**. Within your WDK installation, navigate to src\\input\\layout and open the kbd.sln project file. + +1. Right-click the solution in the **Solution Explorer** and select **Configuration Manager**. + +1. From the **Configuration Manager**, select the **Active Solution Configuration** (for example, Windows 8.1 Debug or Windows 8.1 Release) and the **Active Solution Platform** (for example, Win32) that correspond to the type of build you are interested in. + +1. From the **Build** menu, click **Build Solution** (Ctrl+Shift+B). Previous versions of the WDK used the Windows Build utility (Build.exe) and provided separate build environment windows for each of the supported build configurations. Starting in the WDK, you can use the Visual Studio Command Prompt window for all build configurations. ### Building the sample using the command line (MSBuild) -1. Open a Visual Studio Command Prompt window. Click **Start** and search for **Developer Command Prompt**. If your project is under %PROGRAMFILES%, you need to open the command prompt window using elevated permissions (**Run as administrator**). From this window you can use MsBuild.exe to build any Visual Studio project by specifying the project (.VcxProj) or solutions (.Sln) file. -2. Navigate to the project directory and enter the **MSbuild** command for your target. For example, to perform a clean build of a Visual Studio driver project called kbdus.vcxproj, navigate to the project directory and enter the following MSBuild command: **msbuild /t:clean /t:build .\\kbdus.vcxproj**. -3. If the build succeeds, you will find the driver (kbdus.dll) in the binary output directory corresponding to the target platform, for example src\\input\\layout\\kbdus\\Windows 8.1 Debug. +1. Open a Visual Studio Command Prompt window. Click **Start** and search for **Developer Command Prompt**. If your project is under %PROGRAMFILES%, you need to open the command prompt window using elevated permissions (**Run as administrator**). From this window you can use MsBuild.exe to build any Visual Studio project by specifying the project (.VcxProj) or solutions (.Sln) file. + +1. Navigate to the project directory and enter the **MSbuild** command for your target. For example, to perform a clean build of a Visual Studio driver project called kbdus.vcxproj, navigate to the project directory and enter the following MSBuild command: **msbuild /t:clean /t:build .\\kbdus.vcxproj**. + +1. If the build succeeds, you will find the driver (kbdus.dll) in the binary output directory corresponding to the target platform, for example src\\input\\layout\\kbdus\\Windows 8.1 Debug. -Design and Operation --------------------- +## Design and Operation -### Keyboard Layout Samples +### Keyboard Layout Samples details The layout DLL is loaded by the window manager when needed. One of the examples is the logon. The default set of the input locales is set in the HKCU registry, according to user's preference, which can be customized by the Regional and Language Options application in Control Panel. The window manager reads the HKCU registry and loads the keyboard layouts accordingly. The samples under input/layout include the following keyboard layouts: -- kbdus +- kbdus US-English keyboard layout -- kbdfr +- kbdfr French keyboard layout -- kbdgr +- kbdgr German keyboard layout -- kbd101 +- kbd101 Japanese 101 keyboard layout -- kbd106 +- kbd106 Japanese 106 keyboard layout @@ -87,13 +80,11 @@ The layout DLLs export one or more entry points, which are called by the window For the East Asian keyboard layouts, the keyboard layout DLL has to provide language-specific entry points. Those additional entries expose the language-specific information, such as the kana conversion table, or the special conversion rule, including the VK\_KANJI generation. -Installation ------------- +## Installation To install a customized version of a layout DLL, it is recommended to substitute the existing DLL installed by the operating system with the customized DLL. The layout DLLs should be installed in the %windir%\\system32 directory (exceptions may apply on 64-bit platforms). You may need to disable the System File Protection (SFP) before replacing the layout DLLs. After the layout DLLs are installed, you may need to reboot the system to ensure the new layouts are used.. -Loading the Sample ------------------- +## 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. diff --git a/input/moufiltr/README.md b/input/moufiltr/README.md index d25da692..210a7198 100644 --- a/input/moufiltr/README.md +++ b/input/moufiltr/README.md @@ -8,16 +8,6 @@ products: - windows-wdk --- - -<!--- - name: Mouse Input WDF Filter Driver (Moufiltr) - platform: KMDF - language: cpp - category: HID WDF - description: A WDF example of a mouse input filter driver. - samplefwlink: http://go.microsoft.com/fwlink/p/?LinkId=620195 ----> - # Mouse Input WDF Filter Driver (Moufiltr) The Moufiltr sample is an example of a mouse input filter driver. diff --git a/network/ndis/filter/README.md b/network/ndis/filter/README.md index 8580c269..a7093842 100644 --- a/network/ndis/filter/README.md +++ b/network/ndis/filter/README.md @@ -8,17 +8,6 @@ products: - windows-wdk --- - - -<!--- - name: NDIS 6.0 Filter Driver - platform: WDM - language: cpp - category: Network - description: A pass-through NDIS 6 filter driver demonstrating the basic principles of an NDIS 6.0 Filter driver. - samplefwlink: http://go.microsoft.com/fwlink/p/?LinkId=617915 ----> - # NDIS 6.0 Filter Driver The Ndislwf sample is a do-nothing pass-through NDIS 6 filter driver that demonstrates the basic principles underlying an NDIS 6.0 Filter driver. The sample replaces the NDIS 5 Sample Intermediate Driver (Passthru driver). diff --git a/network/ndis/mux/README.md b/network/ndis/mux/README.md index 480f934f..681158f0 100644 --- a/network/ndis/mux/README.md +++ b/network/ndis/mux/README.md @@ -8,17 +8,6 @@ products: - windows-wdk --- - - -<!--- - name: NDIS MUX Intermediate Driver and Notify Object - platform: WDM - language: cpp - category: Network - description: An NDIS 6.0 driver that demonstrates the operation of an N:1 MUX driver. - samplefwlink: http://go.microsoft.com/fwlink/p/?LinkId=617916 ----> - # NDIS MUX Intermediate Driver and Notify Object The MUX Intermediate Miniport (IM) driver is an NDIS 6.0 driver that demonstrates the operation of an "N:1" MUX driver.The sample demonstrates creating multiple virtual network devices on top of a single lower adapter. Protocols bind to these virtual adapters as if they are real adapters. Examples of Intermediate Miniport drivers that can use this framework are Virtual LAN (VLAN) drivers. Included in the project is a sample Notify Object that demonstrates how to write a notify object for installing and configuring an NDIS MUX intermediate miniport (IM) driver that implements an N:1 relationship between upper and lower bindings, for example, it creates multiple virtual network devices on top of a single lower adapter. Protocols bind to these virtual adapters as if they are real adapters. Examples of Intermediate Miniport drivers that can use this type of notify object are Virtual LAN (VLAN) drivers. diff --git a/network/ndis/ndisprot/6x/README.md b/network/ndis/ndisprot/6x/README.md index f895ab8b..2ac81988 100644 --- a/network/ndis/ndisprot/6x/README.md +++ b/network/ndis/ndisprot/6x/README.md @@ -8,17 +8,6 @@ products: - windows-wdk --- - - -<!--- - name: NDIS Connection-less Protocol WDM Driver Sample - platform: WDM - language: cpp - category: Network - description: Demonstrates a connection-less NDIS 6.0 protocol WDM driver. - samplefwlink: http://go.microsoft.com/fwlink/p/?LinkId=617917 ----> - # NDIS Connection-less Protocol WDM Driver Sample This sample demonstrates a connection-less NDIS 6.0 protocol WDM driver. The driver supports sending and receiving raw Ethernet frames using `ReadFile`/`WriteFile` calls from user-mode. It only receives frames with a specific EtherType field. As an NDIS protocol, it illustrates how to establish and tear down bindings to Ethernet adapters, i.e. those that export medium type **NdisMedium802\_3**. It shows how to set a packet filter, send and receive data, and handle plug-and-play events. diff --git a/network/ndis/ndisprot_kmdf/README.md b/network/ndis/ndisprot_kmdf/README.md index 2109281f..cd1b9bfb 100644 --- a/network/ndis/ndisprot_kmdf/README.md +++ b/network/ndis/ndisprot_kmdf/README.md @@ -8,17 +8,6 @@ products: - windows-wdk --- - - -<!--- - name: Connection-less NDIS 6.0 Protocol KMDF Sample Driver - platform: KMDF - language: cpp - category: Network - description: Demonstrates a connection-less NDIS 6.0 protocol KMDF driver. - samplefwlink: http://go.microsoft.com/fwlink/p/?LinkId=620197 ----> - # Connection-less NDIS 6.0 Protocol KMDF Sample Driver This sample demonstrates a connection-less NDIS 6.0 protocol KMDF driver. diff --git a/network/radio/RadioManagerSample/README.md b/network/radio/RadioManagerSample/README.md index 155d66c7..9a5f0e1e 100644 --- a/network/radio/RadioManagerSample/README.md +++ b/network/radio/RadioManagerSample/README.md @@ -8,17 +8,6 @@ products: - windows-wdk --- - - -<!--- - name: Windows Radio Management Sample - platform: WDM - language: cpp - category: Network Radio - description: Demonstrates how to structure a Radio Manager for use with the Windows Radio Management APIs. - samplefwlink: http://go.microsoft.com/fwlink/p/?LinkId=617920 ----> - # Windows Radio Management Sample The Radio Manager sample demonstrates how to structure a Radio Manager for use with the Windows Radio Management APIs. diff --git a/network/trans/WFPSampler/README.md b/network/trans/WFPSampler/README.md index d357ab57..68f86e87 100644 --- a/network/trans/WFPSampler/README.md +++ b/network/trans/WFPSampler/README.md @@ -8,17 +8,6 @@ products: - windows-wdk --- - - -<!--- - name: Windows Filtering Platform Sample - platform: KMDF - language: cpp - category: Network - description: A sample firewall that has a command-line interface which allows adding filters at various WFP layers. - samplefwlink: http://go.microsoft.com/fwlink/p/?LinkId=620198 ----> - # Windows Filtering Platform Sample The WFPSampler sample driver is a sample firewall. It has a command-line interface which allows adding filters at various WFP layers with a wide variety of conditions. Additionally it exposes callout functions for injection, basic action, proxying, and stream inspection. diff --git a/network/trans/ddproxy/README.md b/network/trans/ddproxy/README.md index 89d972b4..ee021020 100644 --- a/network/trans/ddproxy/README.md +++ b/network/trans/ddproxy/README.md @@ -8,17 +8,6 @@ products: - windows-wdk --- - - -<!--- - name: Windows Filtering Platform Packet Modification Sample - platform: KMDF - language: cpp - category: Network - description: Demonstrates the packet modification capabilities of the Windows Filtering Platform (WFP). - samplefwlink: http://go.microsoft.com/fwlink/p/?LinkId=617930 ----> - # Windows Filtering Platform Packet Modification Sample The sample driver demonstrates the packet modification capabilities of the Windows Filtering Platform (WFP). diff --git a/network/trans/inspect/README.md b/network/trans/inspect/README.md index ddf7be8b..cc294fb1 100644 --- a/network/trans/inspect/README.md +++ b/network/trans/inspect/README.md @@ -8,17 +8,6 @@ products: - windows-wdk --- - - -<!--- - name: Windows Filtering Platform Traffic Inspection Sample - platform: KMDF - language: cpp - category: Network - description: Demonstrates the traffic inspection capabilities of the Windows Filtering Platform (WFP). - samplefwlink: http://go.microsoft.com/fwlink/p/?LinkId=617931 ----> - # Windows Filtering Platform Traffic Inspection Sample This sample driver demonstrates the traffic inspection capabilities of the Windows Filtering Platform (WFP). diff --git a/network/trans/msnmntr/README.md b/network/trans/msnmntr/README.md index 4ff840b8..ef3f073a 100644 --- a/network/trans/msnmntr/README.md +++ b/network/trans/msnmntr/README.md @@ -8,17 +8,6 @@ products: - windows-wdk --- - - -<!--- - name: Windows Filtering Platform MSN Messenger Monitor Sample - platform: KMDF - language: cpp - category: Network - description: Demonstrates the stream inspection capabilities of the Windows Filtering Platform (WFP). - samplefwlink: http://go.microsoft.com/fwlink/p/?LinkId=617932 ----> - # Windows Filtering Platform MSN Messenger Monitor Sample This sample application and driver demonstrate the stream inspection capabilities of the Windows Filtering Platform (WFP). diff --git a/network/wsk/echosrv/README.md b/network/wsk/echosrv/README.md index b4851683..fe1c4dcd 100644 --- a/network/wsk/echosrv/README.md +++ b/network/wsk/echosrv/README.md @@ -8,17 +8,6 @@ products: - windows-wdk --- - - -<!--- - name: WSK TCP Echo Server - platform: WDM - language: cpp - category: Network - description: A minimal sample driver to demonstrate the usage of the Winsock Kernel (WSK) programming interface. - samplefwlink: http://go.microsoft.com/fwlink/p/?LinkId=617935 ----> - # WSK TCP Echo Server This sample driver is a minimal driver meant to demonstrate the usage of the Winsock Kernel (WSK) programming interface. diff --git a/pofx/UMDF2/README.md b/pofx/UMDF2/README.md index d3fa2da1..c526f412 100644 --- a/pofx/UMDF2/README.md +++ b/pofx/UMDF2/README.md @@ -8,16 +8,6 @@ products: - windows-wdk --- - -<!--- - name: Power Framework (PoFx) Sample (UMDF Version 2) - platform: UMDF2 - language: cpp - category: Power - description: Demonstrates how a UMDF version 2 driver can implement F-state-based power management. - samplefwlink: http://go.microsoft.com/fwlink/p/?LinkId=617936 ----> - # Power Framework (PoFx) Sample (UMDF Version 2) This solution demonstrates how a User-Mode Driver Framework (UMDF) version 2 driver can implement F-state-based power management. The SingleComp project demonstrates how a UMDF version 2 driver can implement F-state-based power management for a device that has only a single component. diff --git a/pofx/WDF/README.md b/pofx/WDF/README.md index 731550ed..c4503eee 100644 --- a/pofx/WDF/README.md +++ b/pofx/WDF/README.md @@ -8,16 +8,6 @@ products: - windows-wdk --- - -<!--- - name: KMDF Power Framework (PoFx) Sample - platform: KMDF - language: cpp - category: Power - description: Demonstrate how a KMDF driver can implement F-state-based power management. - samplefwlink: http://go.microsoft.com/fwlink/p/?LinkId=617937 ----> - # KMDF Power Framework (PoFx) Sample This solution consists of two samples that demonstrate how a KMDF driver can implement F-state-based power management. The SingleComp sample demonstrates how a KMDF driver can implement F-state-based power management for a device that has only a single component. The MultiComp sample demonstrates how a KMDF driver can implement F-state-based power management for a device that has an arbitrary number of components that can be individually power-managed. diff --git a/print/OEM Printer Customization Plug-in Samples/README.md b/print/OEM Printer Customization Plug-in Samples/README.md index 7609e269..4d50703d 100644 --- a/print/OEM Printer Customization Plug-in Samples/README.md +++ b/print/OEM Printer Customization Plug-in Samples/README.md @@ -8,17 +8,6 @@ products: - windows-wdk --- - - -<!--- - name: OEM Printer Customization Plug-in Samples - platform: DLL - language: cpp - category: Print - description: Provides examples of how to build OEM printer customization plug-ins. - samplefwlink: https://go.microsoft.com/fwlink/?linkid=862105 ----> - # OEM Printer Customization Plug-in Samples The OEMDLL samples are an illustration of OEM customization plug-ins. The BITMAP, OEMPS, OEMUI, OEMUNI, OEMPREAN, CUSTHLP, SyncSet, ThemeUI, PSUIRep, and Watermark samples do not affect the printer output. They are only examples of how to build OEM Customization DLLs of various types. diff --git a/print/XPSDrvSmpl/README.md b/print/XPSDrvSmpl/README.md index d0eb6734..3b609f11 100644 --- a/print/XPSDrvSmpl/README.md +++ b/print/XPSDrvSmpl/README.md @@ -8,17 +8,6 @@ products: - windows-wdk --- - - -<!--- - name: XPSDrv Driver and Filter Sample - platform: DLL - language: cpp - category: Print - description: Provide a starting point for developing XPSDrv printer drivers and to illustrate the facility and potential of an XPSDrv print driver. - samplefwlink: http://go.microsoft.com/fwlink/p/?LinkId=617950 ----> - # XPSDrv Driver and Filter Sample This sample is intended to provide a starting point for developing XPSDrv printer drivers and to illustrate the facility and potential of an XPSDrv print driver. This goal is accomplished by implementing a number of real-world features within a set of XPS print pipeline filters that are configured through a configuration plug-in that supports custom UI content and PrintTicket handling. |