Welcome to the Lounge

2-Nov-23 5:27

...not knowing your CPU's core temperature?

Having two utilities that read it, and display wildly different results.

I might as well not know at all.

Richard Deeming2-Nov-23 5:33

2-Nov-23 5:33

Assuming they're both using the same units (°C vs °F vs °K), get a third utility so you can find out which one is correct.

Of course, if the third utility displays yet another wildly different temperature, then you're stuffed. Laugh | :laugh:

"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer

Nelek2-Nov-23 5:36

Nelek

2-Nov-23 5:36

Richard Deeming wrote:
Of course, if the third utility displays yet another wildly different temperature

Average? Median? Roll eyes | :rolleyes:

M.D.V.

If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.

Richard Deeming2-Nov-23 5:42

2-Nov-23 5:42

Does the wisdom of crowds[^] apply to buggy hardware monitoring utilities? Big Grin | :-D

"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer

dandy722-Nov-23 5:52

2-Nov-23 5:52

See the XKCD comic about having 14 standards. Smile | :)

Richard Andrew x642-Nov-23 5:41

Richard Andrew x64

2-Nov-23 5:41

May I ask which CPU you're talking about? And what chipset?

The difficult we do right away...
...the impossible takes slightly longer.

dandy722-Nov-23 6:03

2-Nov-23 6:03

Sure. The machine is an antique at this point, it's an Acer Aspire easyStore H340 - shipped with Windows Home Server (so, 2007 or so!), which has been repurposed and running Windows 7 essentially as a headless NAS. Still works great for the job that's been assigned to it, so I've never looked into replacing it.

Core Temp reports the CPU as an Intel Atom (Diamondville), socket 437 (FCBGA437).

Open Hardware Monitor reports it as an Intel Atom 230.

Core Temp reports the temperature floating around 67C.

Open Hardware Monitor says 32C.

jschell3-Nov-23 5:22

jschell

3-Nov-23 5:22

dandy72 wrote:
... around 67C...says 32C.

You should be able to use your hand to figure out which of those is right. Hopefully the second.

Presuming that there is only one temperature sensor and if the same utility keeps getting it wrong then discard it.

Of course if there are two sensors then one of those could be bad.

dandy723-Nov-23 5:42

3-Nov-23 5:42

jschell wrote:
You should be able to use your hand to figure out which of those is right.

True.

What I prefer with Open Hardware Monitor is that it writes its data to WMI, which I then read back with another tool to display a graph of temperature over time (and combine with the same data from other systems). Core Temp only exports its data to a log file (although I could still work with that if I really, really wanted to)...

But if the data's inaccurate, being able to plot pretty graphs with it is kinda useless. Smile | :)

Christian Graus2-Nov-23 7:38

Christian Graus

2-Nov-23 7:38

This is why single source of data is important. If you have two sources of truth, what if they don't agree?

dandy722-Nov-23 9:21

2-Nov-23 9:21

I've always said, if I have a watch, I can probably tell you the time. If I have two watches...I'll be less certain of the accuracy of my response.

Christian Graus2-Nov-23 9:23

Christian Graus

2-Nov-23 9:23

Exactly!!!

Outdated?

Eddy Vluggen2-Nov-23 4:30

2-Nov-23 4:30

So, I fire up VS2019 today to write a small console app; then you choose a framework, and all my choices have this nice prefix "no longer supported". There's that new-fangled .NET Core 3, and it is already no longer supported.

You mean 5 years is too long to support your product? Why would I even look at the new products then, as they are already on their way to being unsupported?

Bastard Programmer from Hell Suspicious | :suss:

"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.

jschell2-Nov-23 4:35

jschell

2-Nov-23 4:35

Apparently.

.NET and .NET Core official support policy[^]

Though it is rather difficult to release new versions and support old versions at the same time. If one supposes 10 years then they would need to support 10 different versions (from that list.)

This becomes more problematic if one of those versions has a security problem and fixing it would require significant work and/or a refactor.

fgs19632-Nov-23 4:44

fgs1963

2-Nov-23 4:44

I rarely code at all any more and never using MS stuff, so please help me understand that chart from your link.

Using the .NET Core 3 that Eddy mentioned...

Original Release Date: September 23, 2019
Last patch version (v3.0.3): February 18, 2020 (148 days since original release)
End of support: March 3, 2020 (162 days since original release)

162 days!?!?!?!?!?

What am I missing?

Richard Deeming2-Nov-23 4:54

2-Nov-23 4:54

fgs1963 wrote:
What am I missing?

3.1 has just over two years support.

I think they didn't formalise the STS/LTS cycle until .NET 5, which was the first version to have precisely 18 months support.

"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer

Eddy Vluggen2-Nov-23 5:12

2-Nov-23 5:12

A good thing they don't build pacemakers.

Bastard Programmer from Hell Suspicious | :suss:

"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.

Richard Deeming2-Nov-23 5:25

2-Nov-23 5:25

Or bionic implants:
Bionic Implants Can Go Obsolete And Unsupported, Too | Hackaday[^]

"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer

Eddy Vluggen2-Nov-23 6:55

2-Nov-23 6:55

I am glad you don't read my bedtime stories Smile | :)

Bastard Programmer from Hell Suspicious | :suss:

"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.

Eddy Vluggen2-Nov-23 4:54

2-Nov-23 4:54

fgs1963 wrote:
What am I missing?

I blame marketing.

Ever since Windows was invented, buttons had to look "newer" with every version. Change, for changes sake, to prove things "improved".

Bastard Programmer from Hell Suspicious | :suss:

"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.

Eddy Vluggen2-Nov-23 4:51

2-Nov-23 4:51

You know why JavaScript has that many equality operaters? Because it would break a lot of existing code if they simply changed it and called it outdated; a big part of the internet would break down. I dislike JavaScript, but it is reliable.

Do new idea's have to break the principle of reliability? No, they don't. Unreliable means exactly that.

jschell wrote:
This becomes more problematic if one of those versions has a security problem and fixing it would require significant work and/or a refactor.

Maybe stop introducing new crap every three months that introduces more bugs and security riscs? Smile | :)

Bastard Programmer from Hell Suspicious | :suss:

"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.

dandy722-Nov-23 5:33

2-Nov-23 5:33

I blame Linux for that. 5 years is considered "LTS" (Long-Term Support). Somehow Microsoft thought that was a great idea and adopted that schedule.

Phones are even worse.

Eddy Vluggen2-Nov-23 6:48

2-Nov-23 6:48

Phones aren't required.

Bastard Programmer from Hell Suspicious | :suss:

"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.

dandy722-Nov-23 9:25