If you have a lot of drivers then you could use a cmd script to load each INF file in turn (but you probably only need to load 2 or 3 of them). To find obtain the chipset uses the easiest thing to do is download them from the manufacturers website and expand them (if in cab files). install the drivers as follows drvload /inf xxx.inf where xxx.inf is the name of each inf file inf and all all other driver files) on a USB key (or hard disk folder that you can access under WinPE)ģ. Find the **Vista** chipset drivers for your mainboard and put them all (inc. You can use this to dynamically load drivers.ġ. Under WinPE v2 there is the drvload command. My guess is that when the Windows chipset drivers are loaded, it changes the PCI registers in some way and HWMonitor works OK. I suspect that HWMonitor and CPUZ have direct I/O code which accesses ports on the chipset registers directly.
Hard disk drive temp and CPU core temp is not obtained via the SMBUS so this often works under WinPE when other sensors don't. some Vista drivers will return DIMM SPD information via the chipset driver and via WMI) and some graphics drivers have driver support for fan speed/temperature, etc. Some drivers have this hardware support (e.g. In some cases, executable files can damage your computer.
#Cpuid hwmonitor pro full .exe
exe extension of a file name displays an executable file. Access to this must be directly via hardware I/O ports as there is no BIOS or OS support for this. What is hwmonitor.exe hwmonitor.exe is an executable file that is part of the CPUID HWMonitor 1.21 program developed by CPUID, Inc.The software is usually about 2.44 MB in size. Most sensor info is obtained via the SMBUS or I/O ports directly. Some mainboards show this issue and others don't.
It is not WMI as I have WinPe v2 with WMI components added and I get the same result on some mainboards under WinPE v2.