Hello Mumak, here are report from my latest 386/486 build. Your last update something messed up with CPU and cache detection:
HWINFO 6.2.0

• Cyrix Cx486DLC 33.3 MHz
• IIT 4C87DLC 34.9 MHz
• L1 - 1 kB
• L2 - 128 kB

HWINFO 6.2.1

• NexGen Nx586 21.6 MHz
• NexGen Nx587
• L1 - 16+16 kB
• L2 nothing

Real CPU + FPU in my board is TX486DLC/E-40GA (yes, i have it downclocked to match FPU speed) and IIT 3C87-33
Motherboard is DTK PEM-4036YB with Symphony Labs SL82C460 (Haydn II [Cache]) chipset and 128 kB cache (motherboard and chipset not detected)
VGA is Cirrus Logic CL-GD5422 (detected as CL-GD5424)
Network card is SMC 8216C (detected as Unknown SMC LAN Adapter)

In attached zip are DBG and LOG files from both versions.

Thanks for your support.

Thanks!
I tried to address the false Nx586 detection and SMSC adapter and released v6.2.2. It can be downloaded in the OP HWiNFO for DOS resurrected !
Note that TX486DLC cannot be distinguished from Cx486 using software AFAIK so it should appear as Cx486DLC.

Mumak wrote on 2022-10-30, 16:44:

Thanks!
I tried to address the false Nx586 detection and SMSC adapter and released v6.2.2. It can be downloaded in the OP HWiNFO for DOS resurrected !
Note that TX486DLC cannot be distinguished from Cx486 using software AFAIK so it should appear as Cx486DLC.

I did extensive research into CPUID some years ago, and from my notes, the only TI CPUs that can be determined separately from any Cyrix CPU are the DX4, DX2 stepping eB0, potomac (SXL(C))

debs3759 wrote on 2022-10-30, 19:28:

Mumak wrote on 2022-10-30, 16:44:

Thanks!
I tried to address the false Nx586 detection and SMSC adapter and released v6.2.2. It can be downloaded in the OP HWiNFO for DOS resurrected !
Note that TX486DLC cannot be distinguished from Cx486 using software AFAIK so it should appear as Cx486DLC.

I did extensive research into CPUID some years ago, and from my notes, the only TI CPUs that can be determined separately from any Cyrix CPU are the DX4, DX2 stepping eB0, potomac (SXL(C))

Yes, Potomac can be recognized by its 8K/4-way cache. But many other TI don't feature any software-recognizable differences.

Thanks Mumak, with version 6.2.2 everything now properly detected.

Hey Mumak,

I have an Intel 486 DX33 that doesn't play ball with HWINFO (first tried 6.2, then the latest 6.2.2, same result).
When going into the "Motherboard info" tab it crashes with a "Fatal Error" - Cannot Continue red error box, with the only option to quit.
I did run it again with the -d switch, and it crashes straightaway to prompt. The .DBG file content is as follows:

1VidMode=3
2DispComb=8
3HWiNFO v6.2.2 
4Flushing disk caches ...
5
6Reading Data ...
7
8DetectCPU - 486
9FPUtest=3
10Check Cx
11Check IBM
12Not IBM
13Get freq

Let me know if you want me to test anything else! Cheers

Boohyaka wrote on 2023-01-05, 18:57:

Hey Mumak, […]
Show full quote

Hey Mumak,

I have an Intel 486 DX33 that doesn't play ball with HWINFO (first tried 6.2, then the latest 6.2.2, same result).
When going into the "Motherboard info" tab it crashes with a "Fatal Error" - Cannot Continue red error box, with the only option to quit.
I did run it again with the -d switch, and it crashes straightaway to prompt. The .DBG file content is as follows:

Copy code to clipboard

1VidMode=3
2DispComb=8
3HWiNFO v6.2.2 
4Flushing disk caches ...
5
6Reading Data ...
7
8DetectCPU - 486
9FPUtest=3
10Check Cx
11Check IBM
12Not IBM
13Get freq

Let me know if you want me to test anything else! Cheers

Is that the full content of DBG file? Are you running in plain DOS or some extenders perhaps? Try to free more system memory if that will help.

well I'm afraid it's weirder than that 😀

Yes that is the full DBG content. Running plain DOS, pure conventional mem, even skipped whole startup files. Ended up with 578kb free and it still doesn't like the "Mainboard info" menu entry. Everything else is fine, though.

Hmm, it seems to crash during a normal loop measuring the CPU clock. I'm wondering whether the system runs stable otherwise and no issues in other applications... How about NSSI or similar tools?

Yes system is stable and quite heavily used with no issue. I will try NSSI when I'm back from work later today and report back!

Rebooted to pure DOS 6.22, bypassing startup files, 578kb of conventional memory.

CheckIt Pro: no problem
NSSI: no problem
HWINFO: I did run it again with the -d switch and get a crash to DOS prompt after pressing "OK". Debug file is attached. It shows more than yesterday.
What's maybe strange to me is that it checks for cache 256k...system BIOS reports 128k and NSSI as well (not sure how to find the cache info in CKPro).
In any case I hope it makes more sense to you because it doesn't make much to me 😀 happy and available to run more tests if it helps you!

VidMode=3 DispComb=8 HWiNFO v6.2.2 Flushing disk caches ... […]
Show full quote

VidMode=3
DispComb=8
HWiNFO v6.2.2
Flushing disk caches ...

Reading Data ...

DetectCPU - 486
FPUtest=3
Check Cx
Check IBM
Not IBM
Get freq
FreqCPU: 1378-30

Cache 1K: 31.3 -> 31.3
Cache 2K: 60.1 -> 60.1 = 1.92x
Cache 4K: 117.8 -> 117.8 = 1.96x
Cache 8K: 238.7 -> 238.7 = 2.03x
Cache 16K: 920.7 -> 920.7 = 3.86x *L1*
Cache 32K: 1839.0 -> 1839.0 = 2.00x
Cache 64K: 3675.0 -> 3675.0 = 2.00x
Cache 128K: 7352.0 -> 7352.0 = 2.00x
Cache 256K: 29492.0

Hmm. Both crashes (during CPU clock measurement and L2 cache timing) involve timers. So I'm wondering whether there might be some issue with system timers, but really not sure what exactly.

Not sure if is related to card (as is weird in construction) or hwinfo but during checking info about Matrox VLB then I get artifacts.
3Dbench doesnt produce them so thats why I post it.

mt777 wrote on 2023-03-10, 13:51:

Not sure if is related to card (as is weird in construction) or hwinfo but during checking info about Matrox VLB then I get artifacts.
3Dbench doesnt produce them so thats why I post it.

Please attach the HWiNFO report and debug files so I can have a deeper look (hwinfo .exe-r -d)

HWINFO 6.2.2

When I click on Info=>Motherboard, It simply hang (Resetting CPU [Method 1])

CPU is a Cyrix 5x86 (BTB OFF, Optimized safe settings)
Chipset is ALI1429G

I also tried to run it with -r -d to generate the report

Rav wrote on 2023-07-18, 17:51:

HWINFO 6.2.2 […]
Show full quote

HWINFO 6.2.2

When I click on Info=>Motherboard, It simply hang (Resetting CPU [Method 1]) hwinfo_crash.jpeg

CPU is a Cyrix 5x86 (BTB OFF, Optimized safe settings)
Chipset is ALI1429G

I also tried to run it with -r -d to generate the report with_debug.jpeg

Disable Reset Method 1 in menu "Setup" > "Configuration".

Mumak wrote on 2023-07-18, 18:19:

Rav wrote on 2023-07-18, 17:51:

HWINFO 6.2.2 […]
Show full quote

HWINFO 6.2.2

When I click on Info=>Motherboard, It simply hang (Resetting CPU [Method 1]) hwinfo_crash.jpeg

CPU is a Cyrix 5x86 (BTB OFF, Optimized safe settings)
Chipset is ALI1429G

I also tried to run it with -r -d to generate the report with_debug.jpeg

Disable Reset Method 1 in menu "Setup" > "Configuration".

Oh well, thanks, it work.
Should have inspected the other menu before...

No problem. It's impossible to know in advance if a certain Reset Method will work or cause issues. There are few systems/configurations where it doesn't play well.

Mumak wrote on 2023-07-18, 18:26:

No problem. It's impossible to know in advance if a certain Reset Method will work or cause issues. There are few systems/configurations where it doesn't play well.

System seam to "hang" when I go on "Peripherals Informations"
But it seam to be just the keyboard that stop working. I initially thought it hanged but...

I managed to do the -r -d this time.
And did it fully and quitted, back to prompt but I can't type anything.

Here the misdetections from the report
* BUS frequency is not detected properly it seam, most other program give ~40Mhz for the BUS (it's set to 40). But in this case I get 36.1.
* Sound card is wrong, it's a PAS16 SCSI, Not a sound blaster.

I did attach the report and debug.

Report :

Debug :

Rav wrote on 2023-07-18, 18:42:

System seam to "hang" when I go on "Peripherals Informations" But it seam to be just the keyboard that stop working. I initially […]
Show full quote

Mumak wrote on 2023-07-18, 18:26:

No problem. It's impossible to know in advance if a certain Reset Method will work or cause issues. There are few systems/configurations where it doesn't play well.

System seam to "hang" when I go on "Peripherals Informations"
But it seam to be just the keyboard that stop working. I initially thought it hanged but...

I managed to do the -r -d this time.
And did it fully and quitted, back to prompt but I can't type anything.

Here the misdetections from the report
* BUS frequency is not detected properly it seam, most other program give ~40Mhz for the BUS (it's set to 40). But in this case I get 36.1.
* Sound card is wrong, it's a PAS16 SCSI, Not a sound blaster.

I did attach the report and debug.

Report : HWINFO.LOG
Debug : debug.log

I suppose the CPU clock is wrong too and should be 120 MHz ?
What SCSI controller is there?