tk7k
Active
Posts: 9
|
Post by tk7k on Jan 25, 2022 4:00:18 GMT
Current SIV Version: V5.62 Background: I love SIV and have been using it issue free for several years to display system metrics using the RainMeter plugin. Recently I built a new computer for the 12 Series CPUs with an ASUS Maximus z690 Hero. When I pull info from Sentest.exe anything returning a temperature value show a unicode "lightshade"(░) where possibly SIV is trying to use a degree symbol. See Sentest_Output.txt (23.78 KB) for examples or see below: T\CPU-0-T CPU-0 Temperature 22░C,23░C,19░C,79░C
T\CPU-2-T CPU-2 Temperature 21░C,22░C,19░C,69░C
T\CPU-4-T CPU-4 Temperature 22░C,25░C,20░C,77░C
T\CPU-6-T CPU-6 Temperature 22░C,23░C,17░C,80░C
T\CPU-8-T CPU-8 Temperature 22░C,24░C,19░C,78░C Since the RainMeter plugin just pulls anything like it appears in sentest.ese that symbol comes through and turns it into an Ä which doesn't look to pretty on my displays. I'm aware this could possibly be an early adopter issue on my end with either the Mobo Bios. I am currently on the latest v811 bios. Within SIV64x's Cooling Status section all the temperatures display correctly with the degree symbol. I wanted to get your thoughts on the issue and see if you had any ideas to help me troubleshoot.
|
|
|
Post by siv on Jan 25, 2022 8:45:57 GMT
Welcome to the forum, I expect the effect is only in Command Windows. Below you can see that when the output from SENTEST in piped to a file such as notepad display °.  Looking in your output then I see: T\CPU-0-T CPU-0 Temperature 22â–‘C,23â–‘C,19â–‘C,79â–‘C T\CPU-2-T CPU-2 Temperature 21â–‘C,22â–‘C,19â–‘C,69â–‘C T\CPU-4-T CPU-4 Temperature 22â–‘C,25â–‘C,20â–‘C,77â–‘C T\CPU-6-T CPU-6 Temperature 22â–‘C,23â–‘C,17â–‘C,80â–‘C So your default codepage must use a MBCS, what is it (post the English (Neutral) line of Menu->Help->SIV Languages). I also suspect that if you look at your Sentest_Output.txt using notepad on your system it will look OK, does it? As you are using SIV64X which is a unicode build SIV should save unicode °s (U+00B0) to HKEY_LOCAL_MACHINE\HARDWARE\SIV\T does it? (use regedit modify binary data to check). Assuming so then if RainMeter fails to correctly render °s this is an issue in either RainMeter or it's plugin.
|
|
tk7k
Active
Posts: 9
|
Post by tk7k on Jan 25, 2022 17:15:41 GMT
looks like my SIV Language was set on "Latin 1252 (ANSI - Latin I)"(Lang ID 768) when I checked those settings. I switched it over to "English (Neutral) 1252 (ANSI - Latin I) [0]"(Lang ID 0) and did the Notepad Test below. No changes the RainMeter output either after refreshing. CMD & NotePad:  Rainmeter (work in progress):  RainMeter can render °s if I pass them through a text string on the latest version using my current system Like I've done above. With my previous system I was only getting the value without a degree, A umlaut, or light shade. I may not have been on the very latest versions of either app for the old system though.. Next, I checked the Reg path you mentioned, but I didn't have a SIV entry under Hardware so I ran SIV64x.exe as Admin and those registries were created. No change to Rainmeter after refreshing, but I suspect I'll need to restart for the reg changes to take effect.  I will be right back after my restart to report the results.
|
|
tk7k
Active
Posts: 9
|
Post by tk7k on Jan 25, 2022 17:24:49 GMT
Back from the restart, but no change on the RainMeter display side. Since Rainmeter can render other "°" characters if I put them in a string it starts to seem as though the plugin is the root cause. It's still strange though because this same plugin version worked on my old system although my Rainmenter and SIV versions could have been a year+ older than current.
|
|
tk7k
Active
Posts: 9
|
Post by tk7k on Jan 25, 2022 20:54:40 GMT
After doing some more research I think this might be an issue with how I saved My Rainmeter ini file. I'll need to make sure that I am saving it with the correct encoding. I will test this after work and report back.
|
|
tk7k
Active
Posts: 9
|
Post by tk7k on Jan 25, 2022 22:17:51 GMT
Yep.. Simply saving my Rainmeter INI file that contained the SIV sensor variables with an ANSI encoding is what fixed it. It was UTF-8 by for some reason and I didn't think to check. I saved and refreshed my meters and all was good. Thanks for your help recently and for developing an amazing tool! This one is resolved.
|
|
|
Post by siv on Jan 25, 2022 23:43:57 GMT
Thank you for the running updates and I am pleased to hear you resolved your issue.
|
|