diff options
Diffstat (limited to 'storage')
| -rw-r--r-- | storage/class/cdrom/README.md | 13 | ||||
| -rw-r--r-- | storage/msdsm/README.md | 20 |
2 files changed, 7 insertions, 26 deletions
diff --git a/storage/class/cdrom/README.md b/storage/class/cdrom/README.md index eb895521..56e68f15 100644 --- a/storage/class/cdrom/README.md +++ b/storage/class/cdrom/README.md @@ -8,17 +8,6 @@ products: - windows-wdk --- - - -<!--- - name: CDROM Storage Class Driver - platform: KMDF - language: cpp - category: Storage - description: Provide access to CD, DVD and Blu-ray drives, supports Plug and Play, Power Management, and AutoRun (media change notification). - samplefwlink: http://go.microsoft.com/fwlink/p/?LinkId=617971 ----> - # CDROM Storage Class Driver The CD ROM driver is used to provide access to CD, DVD and Blu-ray drives. It supports Plug and Play, Power Management, and AutoRun (media change notification). @@ -65,4 +54,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.
\ No newline at end of file +For more information, see [CD-ROM Drivers](https://docs.microsoft.com/windows-hardware/drivers/storage/cd-rom-drivers) in the storage technologies design guide. diff --git a/storage/msdsm/README.md b/storage/msdsm/README.md index 483df7d4..06fa8759 100644 --- a/storage/msdsm/README.md +++ b/storage/msdsm/README.md @@ -8,17 +8,6 @@ products: - windows-wdk --- - - -<!--- - name: Multipath I/O (MPIO) DSM Sample - platform: WDM - language: cpp - category: Storage - description: Provides a sample for building vendor-specific device-specific modules (DSM), supports iSCSI and Fibre Channel devices. - samplefwlink: http://go.microsoft.com/fwlink/p/?LinkId=620203 ----> - # Multipath I/O (MPIO) DSM Sample The MPIO DSM Sample is intended to serve as an example to follow when building your own vendor specific device specific modules (DSM). This sample DSM supports iSCSI and Fibre Channel devices. @@ -105,7 +94,8 @@ AddReg = mydsm_addreg This next section contains the Hardware ID strings for your devices. You can have more than one. Sample format: "VENDOR PRODUCT " - remember to use spaces in a field (vendor, product ID) to pad this to be eight characters for the vendor name (as registered with STA) and sixteen for the product ID (unless the supported devices share a common prefix, in which case the product ID can be less than 16 characters). -**Note** Underscores that are part of the inquiry string (applies to vendor ID as well as product ID fields) must NOT be replaced with spaces. +> [!NOTE] +> Underscores that are part of the inquiry string (applies to vendor ID as well as product ID fields) must NOT be replaced with spaces. In this sample, there are two different strings: @@ -211,6 +201,8 @@ You should be aware of the following when you install the MPIO DSM sample: It is expected that the adapter that hosts the system volumes (boot/paging) will not restart, but that should not be problem if you are not multipathing the boot volume. However, if you are multipathing the boot volume, you will need to restart the system. -**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] +> 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.
\ No newline at end of file +> [!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. |