HWiNFO32 and HWiNFO64 v3.90 released

[Mumak]

HWiNFO32 v3.90 and HWiNFO64 v3.90 available.
Changes:

• Improved sensor monitoring on multi-threaded systems.
• Enhanced support of systems with multiple CPU groups.
• Enhanced support of Nehalem-EX.
• Added preliminary support of Ivy Bridge-EP/EX.
• Extended new clock measurement method to AMD 10h and 15h families.
• Enhanced NVAPI GPU fan speed monitoring.
• Minor bugfixes and improvements.
• Added support of XMP 1.3.
• Added AMD PITCAIRN XT/PRO, WIMBLEDON XT.
• Improved reporting of GPU Memory clock on later AMD GPUs (R700 and above).
• Raised sensor limits.
• Added reporting of system memory usage in sensors.

[cesariuth]

"Added preliminary support of Ivy Bridge-EP/EX."

this is new info?

[PatRaceTin]

wow that big improvement

[Mumak]

Ivy Bridge? that's oooold
I'm currently working on Haswell support

[bamtan2]

Ivy Bridge? that's oooold
I'm currently working on Haswell support

He means the EP/EX version, which we haven't heard about before. I guess this confirms its existence.

Can I ask about your job? Because I really have no idea. How do you support things that don't exist? Is there a way to pay Intel to tell you secrets? I don't understand.

[El Mano]

Yeah I'm curious too, how are you already working on Haswell?

[Mumak]

IVB-EP/EX existence is logical, I thought it's already public..
Besides HWiNFO, my primary job is low-level software engineering - drivers, firmware, partial BIOS, etc.. Such jobs often involve early access to systems which are under development.
Of course all preliminary/early access information (and advanced information) is kept under strict NDAs so I cannot give our any further details about such things (I believe that saying that I'm working on next-gen stuff doesn't violate it).
Things like CPUs for example start development several years before the actual release. First internal-only, later strategic customers and early-access engineers step-in to prepare their platforms to support these components in advance (HW engineers - layout, SW engineers - BIOS/firmware). They have a need-to-know things in advance. So when the first limited samples are available (~1 year before launch; there are several stages like ES0/1/2/QS) they can test their early platforms and hunt bugs; this is a close relationship with hardware vendors. When the public gets access to first samples (illegal leaks), the external development is already several months in progress and many things are finalized. The same goes to documentation and technical details - it's available years before launch (often even before the first samples are ready), which allows to start working on future gens in advance...
To bring a new CPU to market is a big process, if often starts as a request from biggest partners and the whole development cycle involves participation of several external players. There are relationships between several levels of internal/external people and that implies a big information exchange.
There's no straight way that you pay those companies (like Intel) to get information in advance. You must have a need-to-know and support from their side. The best need-to-know is to be an early-access engineer or even better - a strategic partner. Sometimes not even a good need-to-know and support is enough to get required approvals.. Everything is driven by $$$ in today's world, there are only few exceptions to this

[El Mano]

Thanks for the post Mumak!

[iMacmatician]

IVB-EP/EX existence is logical, I thought it's already public..

Yeah, PC Watch mentioned Ivy Bridge-EX-A/-B and I think -EP over a year ago.