No sorry Martin, it's not doing that, it's just that it permanently sits on top of the oter HWiNFO window so it can't be switched to.
Closing the sensor window closes the whole thing, but you can minimize it, which is the only way I've found of using the other window.
Maybe that is expected...
Hi again Martin, just a quick note to say that I've now decided a better way to go is to remove the artificial extra delay added to HWiNFO's startup, and simply disable the performance monitoring system on XP completely, as I never actually use it!
I've done that now and removed the startup...
Hi again Martin!
I've set Startup Delayer to delay the startup of HWiNFO by 3 seconds, and that seems to have made the error message go away.
With 2 seconds, it still appeared.
I suppose I should investigate why the Server service is taking so long to start that HWiNFO is causing it to throw...
It seems to load faster in that configuration!
The longest pause is on "Detecting CPU #0".
I have a dual processor system if you remember.
I don't see "Detecting CPU #1", but it may be too quick to register of course!
Actually if I stop it and start it manually again, it seems very slow indeed!
There's a good 25 seconds between me running it and the icons appearing in the system tray.
Interesting about the driver, when I first looked Persistent Driver was checked, and the start type was set to "Demand".
Ah right, I just wondered.
Are the new functions the reason why version 7.12 is apparently so much slower starting up than previous versions, at least on XP?
I already have the Startup Delayer program installed for other reasons, so adding HWiNFO to it won't be a problem.
Just one other query...
Thanks for the fast reply Martin!
Yes, that would make sense. The Server service is set to automatic and is running fine, but as you say if it's not up and running before HWiNFO expects it to be, that could well generate that error. It also disappears of course if I disable the PerfNet...
I recently noticed errors being logged in my Windows XP Application log on every boot.
They are from PerfNet.
I didn't make the connection straight away, but after a lot of head scratching and experimentation, I found that the start of the messages coincided with my update to version 7.12 of...
It certainly is useful, it's exactly what I wanted, as the only way to get a single overall temperature before for each processor was to use the "CPU1" and "CPU2" options in the W83793 section, which from what HWiNFO says about them, are very possibly not actually average temperatures at all...
Ah, so the opposite of what I thought "run-time average" meant! D'oh! :D
So it is an average, the "live" temperatures of all four cores (in my case) added up and divided by four?
That's what I understand an aggregate to be in this context.
Sorry, can I just clarify this.
The info tip says that the core temperature values are aggregated into one value, but it's not a "run-time average".
Does that mean that it's an average value of all the core temperatures for the processor since the start of that session, rather than a real time...