Windows Compatible Products List

The Windows Compatible Products List is a comprehensive list of certified devices and systems. The Windows Compatible Products list has the following features and restrictions:

• You can find devices and systems by filtering the list or by running a search for a specific product name.
• You can search across all certified devices and systems for the entire catalog.
• If you need an OEM system report for RFPs, you can search for the product/marketing name and receive a verification report, which you can download.
• The Compatible Products List displays Declarative & Universal status for all Device Classes.

System search does not support the D & U status field. Therefore, you must set the D & U Status search field dropdown to All to see system results.

Searching for Marketing and Product names for systems or devices

If you search using the Marketing/Product Name box, the Compatible Products List returns matches in the product name, submission name, and marketing name fields. Consider these:

• Limit your search to plain text, without quotes or wildcards.
• Any spaces between words are treated as AND expressions.
• Do not use any special characters or search-limiting terms. For example, do not use (OR, AND, ””, *, ?, etc.).

Searching for a Company Name

Limit your searches to plain text, without quotes or wildcards. For example, do not use (OR, AND, ””, *, ?, etc.).

The search function will auto-complete results after you type five letters.

You may find that some companies are listed twice. This is a result of merging the previous database with Hardware Dev Center. Each entry is different, so it’s best to search using the Marketing/Product Name field.

CM_Get_Device_ID_ListA function (cfgmgr32.h)

The CM_Get_Device_ID_List function retrieves a list of device instance IDs for the local computer’s device instances.

Syntax

Parameters

Caller-supplied pointer to a character string that is either set to a subset of the computer’s device instance identifiers (IDs), or to NULL. See the following description of ulFlags.

Address of a buffer to receive a set of NULL-terminated device instance identifier strings. The end of the set is terminated by an extra NULL. The required buffer size should be obtained by calling CM_Get_Device_ID_List_Size.

Caller-supplied length, in characters, of the buffer specified by Buffer.

One of the following caller-supplied bit flags that specifies search filters:

CM_GETIDLIST_FILTER_BUSRELATIONS

If this flag is set, pszFilter must specify a device instance identifier. The function returns device instance IDs for the bus relations of the specified device instance.

CM_GETIDLIST_FILTER_CLASS (Windows 7 and later versions of Windows)

If this flag is set, pszFilter contains a string that specifies a device setup class GUID. The returned list contains device instances for which the property (referenced by the CM_DRP_CLASSGUID constant) matches the specified device setup class GUID.

The CM_DRP_CLASSGUID constant is defined in Cfgmgr32.h.

CM_GETIDLIST_FILTER_PRESENT (Windows 7 and later versions of Windows)

If this flag is set, the returned list contains only device instances that are currently present on the system. This value can be combined with other ulFlags values, such as CM_GETIDLIST_FILTER_CLASS.

CM_GETIDLIST_FILTER_TRANSPORTRELATIONS (Windows 7 and later versions of Windows)

If this flag is set, pszFilter must specify the device instance identifier of a composite device node (devnode).

The function returns the device instance identifiers of the devnodes that represent the transport relations of the specified composite devnode.

For more information about composite devnodes and transport relations, see the following Remarks section.

CM_GETIDLIST_DONOTGENERATE

Used only with CM_GETIDLIST_FILTER_SERVICE. If set, and if the device tree does not contain a devnode for the specified service, this flag prevents the function from creating a devnode for the service.

CM_GETIDLIST_FILTER_EJECTRELATIONS

If this flag is set, pszFilter must specify a device instance identifier. The function returns device instance IDs for the ejection relations of the specified device instance.

CM_GETIDLIST_FILTER_ENUMERATOR

If this flag is set, pszFilter must specify the name of a device enumerator, optionally followed by a device ID. The string format is EnumeratorName\ , such as ROOT or ROOT\*PNP0500.

If pszFilter supplies only an enumerator name, the function returns device instance IDs for the instances of each device associated with the enumerator. Enumerator names can be obtained by calling CM_Enumerate_Enumerators.

If pszFilter supplies both an enumerator and a device ID, the function returns device instance IDs only for the instances of the specified device that is associated with the enumerator.

CM_GETIDLIST_FILTER_NONE

If this flag is set, pszFilter is ignored, and a list of all devices on the system is returned.

CM_GETIDLIST_FILTER_POWERRELATIONS

If this flag is set, pszFilter must specify a device instance identifier. The function returns device instance IDs for the power relations of the specified device instance.

CM_GETIDLIST_FILTER_REMOVALRELATIONS

If this flag is set, pszFilter must specify a device instance identifier. The function returns device instance IDs for the removal relations of the specified device instance.

CM_GETIDLIST_FILTER_SERVICE

If this flag is set, pszFilter must specify the name of a Microsoft Windows service (typically a driver). The function returns device instance IDs for the device instances controlled by the specified service.

Note that if the device tree does not contain a devnode for the specified service, this function creates one by default. To inhibit this behavior, also set CM_GETIDLIST_DONOTGENERATE.

If no search filter flag is specified, the function returns all device instance IDs for all device instances.

Return value

If the operation succeeds, the function returns CR_SUCCESS. Otherwise, it returns one of the CR_-prefixed error codes defined in Cfgmgr32.h.

Remarks

Starting with Windows 7, a device that supports multiple transport paths for packet-based data is referred to as a composite device and is represented by a composite devnode. A composite devnode logically represents the composite device to the user and applications as a single device, even though the composite devnode can have multiple paths to the physical device.

Each active transport path to the physical device is represented by a transport devnode and is referred to as a transport relation for the composite device.

The composite devnode (but not the related transport devnodes) exposes device interfaces to applications and the system. When an application uses these public device interfaces, the composite device routes the packet-based data to one or more of these transport devnodes, which then transport the data to the physical device.

For example, if a physical cell phone is simultaneously connected to the computer on the USB and the Bluetooth buses, each bus enumerates a child transport devnode on that bus to represent the device’s physical connection.

In this case, if you set the CM_GETIDLIST_FILTER_TRANSPORTRELATIONS flags in ulFlags and specify the device instance ID of the cell phone’s composite devnode in pszFilter, the function returns the device instance IDs for the two transport devnodes in the Buffer parameter.

For more information about device instance IDs, see Device Identification Strings.

The cfgmgr32.h header defines CM_Get_Device_ID_List as an alias which automatically selects the ANSI or Unicode version of this function based on the definition of the UNICODE preprocessor constant. Mixing usage of the encoding-neutral alias with code that not encoding-neutral can lead to mismatches that result in compilation or runtime errors. For more information, see Conventions for Function Prototypes.

QueryDosDeviceW function (fileapi.h)

Retrieves information about MS-DOS device names. The function can obtain the current mapping for a particular MS-DOS device name. The function can also obtain a list of all existing MS-DOS device names.

MS-DOS device names are stored as junctions in the object namespace. The code that converts an MS-DOS path into a corresponding path uses these junctions to map MS-DOS devices and drive letters. The QueryDosDevice function enables an application to query the names of the junctions used to implement the MS-DOS device namespace as well as the value of each specific junction.

Syntax

Parameters

An MS-DOS device name string specifying the target of the query. The device name cannot have a trailing backslash; for example, use «C:», not «C:\».

This parameter can be NULL. In that case, the QueryDosDevice function will store a list of all existing MS-DOS device names into the buffer pointed to by lpTargetPath.

A pointer to a buffer that will receive the result of the query. The function fills this buffer with one or more null-terminated strings. The final null-terminated string is followed by an additional NULL.

If lpDeviceName is non-NULL, the function retrieves information about the particular MS-DOS device specified by lpDeviceName. The first null-terminated string stored into the buffer is the current mapping for the device. The other null-terminated strings represent undeleted prior mappings for the device.

If lpDeviceName is NULL, the function retrieves a list of all existing MS-DOS device names. Each null-terminated string stored into the buffer is the name of an existing MS-DOS device, for example, \Device\HarddiskVolume1 or \Device\Floppy0.

The maximum number of TCHARs that can be stored into the buffer pointed to by lpTargetPath.

Return value

If the function succeeds, the return value is the number of TCHARs stored into the buffer pointed to by lpTargetPath.

If the function fails, the return value is zero. To get extended error information, call GetLastError.

If the buffer is too small, the function fails and the last error code is ERROR_INSUFFICIENT_BUFFER.

Remarks

The DefineDosDevice function enables an application to create and modify the junctions used to implement the MS-DOS device namespace.

Windows ServerВ 2003 and WindowsВ XP:В В QueryDosDevice first searches the Local MS-DOS Device namespace for the specified device name. If the device name is not found, the function will then search the Global MS-DOS Device namespace.

When all existing MS-DOS device names are queried, the list of device names that are returned is dependent on whether it is running in the «LocalSystem» context. If so, only the device names included in the Global MS-DOS Device namespace will be returned. If not, a concatenation of the device names in the Global and Local MS-DOS Device namespaces will be returned. If a device name exists in both namespaces, QueryDosDevice will return the entry in the Local MS-DOS Device namespace.

For more information on the Global and Local MS-DOS Device namespaces and changes to the accessibility of MS-DOS device names, see Defining an MS DOS Device Name.

In WindowsВ 8 and Windows ServerВ 2012, this function is supported by the following technologies.

Technology	Supported
Server Message Block (SMB) 3.0 protocol	No
SMB 3.0 Transparent Failover (TFO)	No
SMB 3.0 with Scale-out File Shares (SO)	No
Cluster Shared Volume File System (CsvFS)	Yes
Resilient File System (ReFS)	Yes

В

SMB does not support volume management functions.

How to get a list of all Device Drivers using Command Prompt

Device Drivers are one of the main reasons why your computer is running at the optimal performance today; they can also be one of the reasons why your computer is running slowly. When things are running well, computer users might want to view a list of the drivers that are operational. This can be a difficult process, which is why we are going to talk about how to view a list of all device drivers via the Command Prompt by using the driverquery command.

First we need to kick start the Command Prompt app, and for this to happen, users may open the WinX menu in Windows 10 or Windows 8.1 and click on Command Prompt. Another way of doing it is to press the Windows Key along with R, and then type CMD in the text box. Hit enter and watch as the Command Prompt launches.

Generate a list of Drivers using driverquery command

In the Command Prompt, enter the command driverquery . This should bring up a list of drivers installed on the system. Depending on the number of drivers installed, it may take a while for the screen to fully populate. A relatively fast computer should perform these tasks within just a few seconds after the user hits the enter button.

Using the driverquery command will show the module name of the driver, along with the display name, driver type, and link date. However, that is not all, because it is possible to generate more information about these drivers just by using a different parameter.

Type driverquery /v to generate the list similar to the one below:

To generate an even more detailed list, use driverquery /FO list /v .

It shows a lot more, including information on whether or not a driver is running. We understand that this one should be more adequate for advanced users, so we would recommend starting things off with driverquery /FO list /v instead of driverquery .

While using the Command Prompt removes the need for installing another app, some users might not feel right at home, so we suggest using an app called DriverView. It does almost everything driverquery does and more. It is a powerful app, and as such, we recommend it to novices since it is more straightforward than using the Command Prompt.

Date: July 30, 2018 Tags: CMD, Drivers

Related Posts

The Realtek Network Controller not found in Device Manager

How to uninstall a program using Command Prompt in Windows 10

How to remove virus from USB Flash Drive using Command Prompt or Batch File in Windows 10

[email protected]

Vamien McKalin possesses the awesome power of walking on water like a boss. He’s also a person who enjoys writing about technology, comics, video games, and anything related to the geek world.

Primary Sidebar

report this ad