Something interesting happening here: When i run old AIDA32 or current version AIDA64 and then Hwinfo32, all voltages and fan speeds are detected by Hwinfo32. It looks like AIDA somewhat reconfigure LM79 monitoring chip. After computer has been power off and on again, everything with sensors are again broken until i run AIDA. In attached ZIP file are new set of log files after "repair" with AIDA and sensor dump from AIDA64.

hasat wrote on 2024-04-21, 11:19:

Something interesting happening here: When i run old AIDA32 or current version AIDA64 and then Hwinfo32, all voltages and fan speeds are detected by Hwinfo32. It looks like AIDA somewhat reconfigure LM79 monitoring chip. After computer has been power off and on again, everything with sensors are again broken until i run AIDA. In attached ZIP file are new set of log files after "repair" with AIDA and sensor dump from AIDA64.

Thanks! I think I know what the problem is. Will be fixed in the next build.

MAC address is 48-bit, but HWINFO displays 64 bits:

Grzyb wrote on 2024-04-27, 10:54:

MAC address is 48-bit, but HWINFO displays 64 bits:
1.png
2.png

Thanks, will be fixed.

Not sure if this is the best place to report it - I found a minor bug in Windows version of HWiNFO, present in freshly downloaded HWiNFO32.exe from hwi_804.zip.
When HWiNFO32 is run on Win98 (probably any Win9x, due to their non-unicode nature?) from a folder that contains non-ASCII characters it will keep complaining about not being able to install its driver, and abort. Example:

D:\Problem\HWiNFO\HWiNFO32.exe

In this case Problem contains non-ASCII characters. This can be solved by moving the entire HWiNFO folder to D: for example, but it took me 10 minutes to realize.

I'm not really expecting this to be fixed, I will move HWiNFO to a permanent location that does not contain any non-ASCII characters in the name, but I figured a report might help somebody else.
Also, a question for DOS version: Is it possible to add a printout of PCI IDs (VEN/DEV) in the device list or details? Preferably with SUBSYS value too if possible.

Yes, this is a limitation of the non-Unicode version but it has to stay in ANSI to maintain compatibility with older systems.
And I'm really not keen on building a Unicode version of legacy HWiNFO32 and maintaining that given the very low usage.

Does the AM386DX have the POPAD bug? I'm running HWINFO in DOS and it's saying that the errata is present on my CPU.

The Am386 design was licensed from Intel (back when companies played nice with each other), so it stands to reason that the same errors would be present for the same stepping.

There's a bug that been around for a while, on W2K and earlier.

On the main window, if you click on the Memory icon, (between Sensors and About), it makes a window with information about the selected memory stick.

At DIMM, there's a dropdown list of all the memory sticks. This dropdown doesn't work on W2K and Win9x (maybe more), you only get to see the first stick.

The other memory dropdowns in other places work fine, it's just in this particular window where there's a problem.

Robbbert wrote on 2024-11-04, 22:52:

There's a bug that been around for a while, on W2K and earlier. […]
Show full quote

There's a bug that been around for a while, on W2K and earlier.

On the main window, if you click on the Memory icon, (between Sensors and About), it makes a window with information about the selected memory stick.

At DIMM, there's a dropdown list of all the memory sticks. This dropdown doesn't work on W2K and Win9x (maybe more), you only get to see the first stick.

The other memory dropdowns in other places work fine, it's just in this particular window where there's a problem.

Thanks, I will try to fix this in the next build.

Before I go cracking open the lid on my PC, could i ask. How reliable HWiNFO is at reporting CPU speeds? Only it's reporting my 66mhz DX2 as running at 58mhz.

Hiddenevil wrote on 2024-11-07, 00:15:

Before I go cracking open the lid on my PC, could i ask. How reliable HWiNFO is at reporting CPU speeds? Only it's reporting my 66mhz DX2 as running at 58mhz.

Measuring CPU clock on such legacy systems can sometimes be not reliable. It depends on several factors, especially the CPU model and environment run under.

I’ll post a screen grab of hwinfo so you can see.

I bought this system a while ago and only now have come to use it properly, so I can’t even confirm if the jumpers are set for 66mhz as I don’t have a motherboard manual. The bios DOES post 66mhz speed.

FWIW, seems to properly measure my 486DX2-66:

I'm going to start a separate thread, get some insight on the motherboard I have. See if anyone can identify it and tell me if the jumpers are set right. I have no motherboard and the last time i dealt with a 486 was 2001-2.

Mumak wrote on 2024-11-05, 06:09:

Thanks, I will try to fix this in the next build.

Looks like it's fixed in release 8.16, at least for 98SE (haven't tried anything else as yet).

I meant to report another bug, but I kept forgetting to. On the same 98SE machine, in the Motherboard section, there's an indicator that lights up green if the board is UEFI capable, otherwise it says Legacy. For some reason, this indicator says UEFI, even though the board was made in 1999. The main summary screen though is correct, it says it is not UEFI capable.

Although it's a trivial bug, do you think it could be fixed?

Robbbert wrote on 2024-11-26, 03:56:

Looks like it's fixed in release 8.16, at least for 98SE (haven't tried anything else as yet). […]
Show full quote

Mumak wrote on 2024-11-05, 06:09:

Thanks, I will try to fix this in the next build.

Looks like it's fixed in release 8.16, at least for 98SE (haven't tried anything else as yet).

I meant to report another bug, but I kept forgetting to. On the same 98SE machine, in the Motherboard section, there's an indicator that lights up green if the board is UEFI capable, otherwise it says Legacy. For some reason, this indicator says UEFI, even though the board was made in 1999. The main summary screen though is correct, it says it is not UEFI capable.

Although it's a trivial bug, do you think it could be fixed?

I will look at the UEFI flag issue but please provide the HWiNFO Report and Debug Files so I can check the details.

I've left that location now, so it will be a few days before I return. In the meantime, how do I get the files you requested? I forgot how.

Robbbert wrote on 2024-11-26, 07:01:

I've left that location now, so it will be a few days before I return. In the meantime, how do I get the files you requested? I forgot how.

https://www.hwinfo.com/forum/threads/read-thi … g-a-report.241/

I have attached the Debug info.

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