Robbbert wrote on 2024-12-02, 03:26:

I have attached the Debug info.

There's nothing in your link of how I can get the HWINFO Report for you.

The attachment HWiNFO32.7z is no longer available

Thanks. You can create the Report file from the main window by pressing the Report icon.
Does "UEFI" or "UEFI Boot" show green? Could you please also attach a screenshot?

Here's the files you requested.

You can see the UEFI things in the BMP file.

EDIT: i was just reading the report and noticed that the AWE64 DMA numbers both show 0; they should be 1 and 5.

Also, the memory module CAS Latency is missing; I think it probably should be 3.

Robbbert wrote on 2024-12-02, 09:39:

Here's the files you requested. […]
Show full quote

Here's the files you requested.

You can see the UEFI things in the BMP file.

The attachment ip101.7z is no longer available

EDIT: i was just reading the report and noticed that the AWE64 DMA numbers both show 0; they should be 1 and 5.

Also, the memory module CAS Latency is missing; I think it probably should be 3.

Thanks. Looks like the problem is because HWiNFO can't access the BIOS here.
I will try to fix this in the next build.
The AWE64 DMA numbers are reported by Windows.
CAS Latency reported is 2.

Here's another one. This is a WIN98FE machine running (rather slowly) on a Pentium 2.

It has the same UEFI issue, and the memory view says the machine is fitted with 2x 128MB RAM sticks, however the System applet claims it has 384MB.

(see attached)

Robbbert wrote on 2024-12-08, 14:04:

Here's another one. This is a WIN98FE machine running (rather slowly) on a Pentium 2. […]
Show full quote

The attachment IP102.7z is no longer available

Here's another one. This is a WIN98FE machine running (rather slowly) on a Pentium 2.

It has the same UEFI issue, and the memory view says the machine is fitted with 2x 128MB RAM sticks, however the System applet claims it has 384MB.

(see attached)

Try the latest Beta version 8.17 if it fixes the UEFI reporting issue.
The 3rd memory module wasn't found because it's SPD doesn't contain a correct checksum. I'll try to workaround this in the next build.

I don't normally use betas, but I tried for this test and yes it does now say Legacy on both machines.

Robbbert wrote on 2024-12-09, 00:14:

I don't normally use betas, but I tried for this test and yes it does now say Legacy on both machines.

Thanks. I also found a problem in the latest build which caused inability to read the BIOS under Win9x. That will be fixed in the next (Beta) build too.

Problem with BIOS readout on Win9x should be resolved in v8.17-5615 Beta

Just tried that beta on IP102, the bios date now shows 05/11/98 instead of blank. Not sure of the date format, is it M/D/Y, or D/M/Y, or is it just a string out of the bios rom? The version and motherboard fields are still blank though.

Also, it now detects the extra ram stick, which shows as unknown. Given that there's a problem with that stick, and the fact that the machine takes forever to boot first time (it's ok after a reboot), I'm going to try replacing that RAM stick. I'll also see if the stick has any identifying info on it.

The unknown RAM has no brand, it has a AST Warranty sticker, another sticker with PC-100 128MB on it, and one more that says LIFETIME WARRANTY. It has 16x V54C365804VCT8PC chips.

Where does HWINFO get the descriptions from? I ask because the RAM that shows as KGM100x64C2/128 is actually KTD-OPGX1N/128 (with 8x HYB39S128800CT-7)

So I changed slot 0 to 256MB, and used the Samsung module in slot 2. If I try to put 512MB in, the bios can only see 384MB, windows gives a protection error, and freezes in safe mode. So lo0ks like 384MB is all it can handle. Even then, the main bios screen can't see anything in slot 0, even though the initial memory count can see it, windows sees it, as does HWINFO. I guess there's a bug in this bios.

BIOS date format should be MM/DD/YY.
HWiNFO detects the RAM module name from SPD integrated in the DIMM that must be properly programmed by the vendor. But it's quite common that legacy vendors didn't want to pay JEDEC to become a member and get an unique ID, so in such case the vendor can't be reliably determined. The rules for SPD back then weren't so strict.

Looks like v8.14 and up aren't showing GPU sensors in Windows 98. CPU sensors also disappeared (but that may not be related). The GPU sensors were working perfectly in v8.12. The motherboard is a Tyan S1854 (Apollo Pro 133A) https://theretroweb.com/motherboards/s/tyan-s1854 and the GPU is a Nvidia Geforce 2 Ultra.

v8.14 and v8.16 shows the GPU but no sensors

v8.17 beta doesn't show the GPU at all

Both HWiNFO for DOS and Windows are not showing it's an Ultra. It's like the word has been cut off.

zuldan wrote on 2025-01-05, 05:33:

Looks like v8.14 and up aren't showing GPU sensors in Windows 98. CPU sensors also disappeared (but that may not be related). Th […]
Show full quote

Looks like v8.14 and up aren't showing GPU sensors in Windows 98. CPU sensors also disappeared (but that may not be related). The GPU sensors were working perfectly in v8.12. The motherboard is a Tyan S1854 (Apollo Pro 133A) https://theretroweb.com/motherboards/s/tyan-s1854 and the GPU is a Nvidia Geforce 2 Ultra.

v8.14 and v8.16 shows the GPU but no sensors

The attachment 20.JPG is no longer available

v8.17 beta doesn't show the GPU at all

The attachment 10.JPG is no longer available

Both HWiNFO for DOS and Windows are not showing it's an Ultra. It's like the word has been cut off.

The attachment 30.JPG is no longer available

I found a bug in latest versions running on legacy systems, it will be fixed in the next Beta build (8.17).

Mumak wrote on 2025-01-05, 09:04:

I found a bug in latest versions running on legacy systems, it will be fixed in the next Beta build (8.17).

Fantastic!

Any chance of identifying the GF2 Ultra correctly? At the moment it’s showing “NVIDIA Geforce2 GTS: Unknown”. It should be “NVIDIA Geforce2 GTS Ultra” or even just “NVIDIA Geforce2 Ultra”.

zuldan wrote on 2025-01-05, 09:13:

Mumak wrote on 2025-01-05, 09:04:

I found a bug in latest versions running on legacy systems, it will be fixed in the next Beta build (8.17).

Fantastic!

Any chance of identifying the GF2 Ultra correctly? At the moment it’s showing “NVIDIA Geforce2 GTS: Unknown”. It should be “NVIDIA Geforce2 GTS Ultra” or even just “NVIDIA Geforce2 Ultra”.

Please post the HWiNFO Debug File from older version like 8.14 and I will check that.

zuldan wrote on 2025-01-05, 09:13:

Mumak wrote on 2025-01-05, 09:04:

I found a bug in latest versions running on legacy systems, it will be fixed in the next Beta build (8.17).

Fantastic!

Any chance of identifying the GF2 Ultra correctly? At the moment it’s showing “NVIDIA Geforce2 GTS: Unknown”. It should be “NVIDIA Geforce2 GTS Ultra” or even just “NVIDIA Geforce2 Ultra”.

New v8.17-5630 Beta should fix this.

Mumak wrote on 2025-01-07, 18:50:

zuldan wrote on 2025-01-05, 09:13:

Mumak wrote on 2025-01-05, 09:04:

I found a bug in latest versions running on legacy systems, it will be fixed in the next Beta build (8.17).

Fantastic!

Any chance of identifying the GF2 Ultra correctly? At the moment it’s showing “NVIDIA Geforce2 GTS: Unknown”. It should be “NVIDIA Geforce2 GTS Ultra” or even just “NVIDIA Geforce2 Ultra”.

New v8.17-5630 Beta should fix this.

Thank you very much for fixing that.

I have 3 machines with CPU related sensor issues. 2 machines where the CPU sensor has disappeared and 1 machine where the sensor value is displayed correctly in the system tray but not on the main sensor page.

[Machine 1] See Debug Logs.zip -> Tyan S1854 Trinity 400 - Apollo Pro 133A - HWiNFO32.DBG. CPU sensor has randomly disappeared. This is the machine you fixed the issue with the GPU sensor not showing (above). Issue occurs in 7.6 -> 8.17

[Machine 2] See Debug Logs.zip -> AOpen AX6BC - 440BX - HWiNFO32.DBG. CPU sensor has randomly disappeared. Issue occurs in 7.6 -> 8.17

[Machine 3] See Debug Logs.zip -> ABIT AB-BX6 - 440BX - HWiNFO32.DBG. Sensor value is displayed correctly in the system tray but not on the main sensor page (sorry phone didn't get a good picture of the system tray) but the value is "40", which is correct. This CPU sensor is also delayed. It takes about 60 seconds for it to appear.

zuldan wrote on 2025-01-08, 09:35:

Thank you very much for fixing that. […]
Show full quote

Mumak wrote on 2025-01-07, 18:50:

zuldan wrote on 2025-01-05, 09:13:

Fantastic!

Any chance of identifying the GF2 Ultra correctly? At the moment it’s showing “NVIDIA Geforce2 GTS: Unknown”. It should be “NVIDIA Geforce2 GTS Ultra” or even just “NVIDIA Geforce2 Ultra”.

New v8.17-5630 Beta should fix this.

Thank you very much for fixing that.

The attachment Fixed.JPG is no longer available

I have 3 machines with CPU related sensor issues. 2 machines where the CPU sensor has disappeared and 1 machine where the sensor value is displayed correctly in the system tray but not on the main sensor page.

The attachment Debug Logs.zip is no longer available

[Machine 1] See Debug Logs.zip -> Tyan S1854 Trinity 400 - Apollo Pro 133A - HWiNFO32.DBG. CPU sensor has randomly disappeared. This is the machine you fixed the issue with the GPU sensor not showing (above). Issue occurs in 7.6 -> 8.17

[Machine 2] See Debug Logs.zip -> AOpen AX6BC - 440BX - HWiNFO32.DBG. CPU sensor has randomly disappeared. Issue occurs in 7.6 -> 8.17

The attachment AOpen AX6BC - 440BX.JPG is no longer available

[Machine 3] See Debug Logs.zip -> ABIT AB-BX6 - 440BX - HWiNFO32.DBG. Sensor value is displayed correctly in the system tray but not on the main sensor page (sorry phone didn't get a good picture of the system tray) but the value is "40", which is correct. This CPU sensor is also delayed. It takes about 60 seconds for it to appear.

The attachment ABIT AB-BX6 - 440BX.JPG is no longer available

Thanks, will try to fix those issues in the next build.

Mumak wrote on 2019-09-05, 21:56:

Hi Martin. I'm not going to read 36 pages of posts to see if this issue has already been reported, and I do not have any logs to send you as I've uninstalled HWINFO, but I have some feedback for you.

I used HWINFO on my Windows XP machine, and a persistent issue I encountered, was that when I had the program open, at some point, the program would no longer properly read my RAM details. I would get two sets of records of blank readings. And this then prevented my machine from shutting down or restarting. I had to do a hard shutdown every time.

Thank you.

Michael

Barley wrote on 2025-02-04, 22:49:

Hi Martin. I'm not going to read 36 pages of posts to see if this issue has already been reported, and I do not have any logs to […]
Show full quote

Mumak wrote on 2019-09-05, 21:56:

Hi Martin. I'm not going to read 36 pages of posts to see if this issue has already been reported, and I do not have any logs to send you as I've uninstalled HWINFO, but I have some feedback for you.

I used HWINFO on my Windows XP machine, and a persistent issue I encountered, was that when I had the program open, at some point, the program would no longer properly read my RAM details. I would get two sets of records of blank readings. And this then prevented my machine from shutting down or restarting. I had to do a hard shutdown every time.

Thank you.

Michael

I'd have to see at least the HWiNFO Debug File of the issue to look into that.