Hi Martin,
I was just running hwinfo on a Windows NT 4 machine. It crashed and the debug file said there was an error writing the driver - the fix it simple, the C:\TEMP directory didn't exist - all worked after I created it.
thanks for the nice tool!

muro wrote on 2025-03-07, 18:22:

Hi Martin,
I was just running hwinfo on a Windows NT 4 machine. It crashed and the debug file said there was an error writing the driver - the fix it simple, the C:\TEMP directory didn't exist - all worked after I created it.
thanks for the nice tool!

If you could attach DBG file of the crash, I will look at that.

Getting duplication of data with a Gigabyte GA-7VT600. Also, the CPU fan speed should be in the 2000's. I can work around it by using the divider but just thought I should mention it.

In relation to my post above, these sensors values from another application match what's in the BIOS.

Maybe HWinfo for win 3.1 ? 😁

While my Pentium 4 isn't exactly vintage, I still thought I'd give HWiNFO a shot on it.

The CPU and motherboard are detected properly; however, HWiNFO 8.24 fails to display most of the GPU specs. I've attached an additional screenshot and report from HWiNFO 8.00, which does not exhibit this issue.

The program reports that my RAM runs at 6-9-9-15 timings, which seem a bit strange for DDR. It also lists a 500 GB HDD connected over SATA; while I do have one attached to the machine, it's plugged into a USB port.

GemCookie wrote on 2025-04-21, 12:57:

The program reports that my RAM runs at 6-9-9-15 timings, which seem a bit strange for DDR.

I looked in the .DBG file and it contains as below, so it's not reading it correctly or the hardware has an issue, what does my SIV utility report?

1MCHBARset[0:0:0_44]=1
2MCHBAR:
3MCHBARmap
4      00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F   0123456789ABCDEF
5------------------------------------------------------------------------
60000: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF   ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
70010: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF   ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ

red-ray wrote on 2025-04-21, 18:54:

I looked in the .DBG file and it contains as below, so it's not reading it correctly or the hardware has an issue, what does my SIV utility report?

SIV reports 3-4-4-8 timings for the RAM, as expected.

Hi, can you please name me last version that is fully compatible with win vista without any dependencies? Tried last one, but caught requirements. In current case it’s easier to use old version rather then install updates. Thx.

GemCookie wrote on 2025-04-22, 13:25:

SIV reports 3-4-4-8 timings for the RAM, as expected.

Good, this means your hardware is OK, I wonder how long HWiNFO has been wonky...

I noted the SIO voltages and temperatures reported by SIV need adjusting, if you PM/Post/E-Mail me the two Menu->File->Save Local files I will adjust them.

vorob wrote on 2025-04-22, 17:00:

Hi, can you please name me last version that is fully compatible with win vista without any dependencies?

It will be very very old, we have had to use SHA2 since around 2015, the last SHA1 signed SIV Driver is Version 4.53 released on 14-Mar-2015

You could boot with driver signature enforcement disabled or install the KB.

It's much easier to install the KB, only takes a few moments.

Sorry folks, I wasn't getting any notifications about new posts, so I missed the reports. Going to look into that now...

zuldan wrote on 2025-03-08, 00:28:

Getting duplication of data with a Gigabyte GA-7VT600. Also, the CPU fan speed should be in the 2000's. I can work around it by using the divider but just thought I should mention it.

The attachment HWiNFO.png is no longer available

The attachment Gigabyte GA-7VT600 Debug.zip is no longer available

This will be fixed in the next (Beta) build.

GemCookie wrote on 2025-04-21, 12:57:

While my Pentium 4 isn't exactly vintage, I still thought I'd give HWiNFO a shot on it.

The CPU and motherboard are detected properly; however, HWiNFO 8.24 fails to display most of the GPU specs. I've attached an additional screenshot and report from HWiNFO 8.00, which does not exhibit this issue.

The program reports that my RAM runs at 6-9-9-15 timings, which seem a bit strange for DDR. It also lists a 500 GB HDD connected over SATA; while I do have one attached to the machine, it's plugged into a USB port.

This will be fixed in the next build too.

XboXC wrote on 2025-03-11, 19:36:

Maybe HWinfo for win 3.1 ? 😁

I'm not such a masochist 😁

I started doing testing on my Asus P4C800-E Deluxe again after nearly two years of not doing anything with it, and I noticed under Windows XP that after I use HWINFO to probe for system sensors and try to restart the system, the board gets stuck at POST code do. I am running XP Pro SP3 fully-updated, default services, latest Intel chipset drivers (not that they matter much), and have accounted for effectively all the hardware (with both the motherboard and video cards tested being fully-recapped).

I did not have any issues with HWINFO back when I tested this board two years ago, and sure enough, the version from around the time I was doing testing on the board (v7.22) worked without issue. I then went version-by-version to find the culprit - v7.40, the first version to display this behavior. Turning-off SMBus support does prevent the issue from occurring, but I'd think that's less than ideal.

I generated reports and then generated debug files from opening in "sensors-only" mode for 10 seconds for 7.36, 7.40, and the latest 8.24, both with and without SMBus support enabled and with resets in-between, attached to this post.

ultra_code wrote on 2025-04-28, 12:32:

I started doing testing on my Asus P4C800-E Deluxe again after nearly two years of not doing anything with it, and I noticed under Windows XP that after I use HWINFO to probe for system sensors and try to restart the system, the board gets stuck at POST code do. I am running XP Pro SP3 fully-updated, default services, latest Intel chipset drivers (not that they matter much), and have accounted for effectively all the hardware (with both the motherboard and video cards tested being fully-recapped).

I did not have any issues with HWINFO back when I tested this board two years ago, and sure enough, the version from around the time I was doing testing on the board (v7.22) worked without issue. I then went version-by-version to find the culprit - v7.40, the first version to display this behavior. Turning-off SMBus support does prevent the issue from occurring, but I'd think that's less than ideal.

I generated reports and then generated debug files from opening in "sensors-only" mode for 10 seconds for 7.36, 7.40, and the latest 8.24, both with and without SMBus support enabled and with resets in-between, attached to this post.

Thanks for the detailed report. Can you please try to enable SMBus Support back and tick the boxes belonging to 0x61 and 0x62 in the "SMBus Device Exclusion" table and let me know if that fixed the problem.

Mumak wrote on 2025-04-28, 18:43:

Thanks for the detailed report. Can you please try to enable SMBus Support back and tick the boxes belonging to 0x61 and 0x62 in the "SMBus Device Exclusion" table and let me know if that fixed the problem.

Unfortunately, with the following settings, it did not fix the problem, both with v7.40 and v8.24. 😔

If you want me to perform any more testing, let me know.

ultra_code wrote on 2025-04-28, 23:40:

Mumak wrote on 2025-04-28, 18:43:

Thanks for the detailed report. Can you please try to enable SMBus Support back and tick the boxes belonging to 0x61 and 0x62 in the "SMBus Device Exclusion" table and let me know if that fixed the problem.

Unfortunately, with the following settings, it did not fix the problem, both with v7.40 and v8.24. 😔

If you want me to perform any more testing, let me know.

I think you should tick these 2 instead?

roytam1 wrote on 2025-04-29, 02:33:

I think you should tick these 2 instead?

The attachment untitled.png is no longer available

pfffft I'm dumb. You are correct. Thanks!

Disabling x16 and x26 and enabling x61 and x62 did solve the problem! Can confirm with both v7.40 and v8.24.