Windows Equivalent for lspci?

Question

Anyone know if an equivalent of lspci exists for Windows?

lspci is a really nice Linux command to list all the device info on the pci bus. This tells you exactly what chipsets are present in video, network, and audio devices. Since companies like Dell allow you to choose from a couple of different network and video options it would really help when trying to figure out how the system you're working on is configured when the system is missing drivers.

Answer 1

I don't know about a command that will do this, but there are a number of programs that will do this. My favorite is SIW. They have an installable version as well as a standalone version.

Answer 2

SIW is a front end for WMIC - WMIC /? should get you started on it.

Answer 3

If I want the PCI ID's I just use Windows's built in Device Manager:

Right click an item, choose the details tab and then choose the 'Device Instance Id' dropdown.

You'll see a string like:

PCI\VEN_14E4&DEV_170C&SUBSYS_30A2103C&REV_02\4&........

The vendor ID is 14E4 & device ID 170C in the above example.

---

If its not specifically the ID's I want, and I'd just like a general list, check out Speccy.

Answer 4

I've never used SIW before, it's quite nice.

Another one that you might want to take a look at is Filewut. You download the client software here and it will identify your PCI and USB devices via a wikipedia-style site:

Answer 5

You can also look at CPUID's PC-Wizard, which can retrieve complete information about your system. PC-Wizard can also be used to perform a variety of benchmarks on your computer.

I am not affiliated with CPUID.

Answer 6

If you really want exactly what lspci gives you – a list of devices gathered more-or-less directly from PCI configuration space – you may as well just use lspci. Yes, that's right, pciutils (the package providing lspci) works on Windows! (See README.Windows.)

Unfortunately, Windows doesn't (seem to) have any API for reading from PCI configuration space, so pciutils must use direct port IO via the inb/inw and outb/outw CPU instructions, which it can only do with the permission of a kernel-mode driver, which must be loaded/installed by an Administrator. (Presently, it uses the WinIO driver from http://www.internals.com/, though there's no shortage of such drivers, and nothing to prevent pciutils from being ported to any of the others.)

(Admittedly, you will probably have to build it yourself, and the build-system support tends to bitrot over time, but it's not usually too hard to fix...)