Re: HWiNFO support of vintage hardware
Posted on 2020-04-29, 15:36
Scratching my head.... is the clock wrong also if you disable Reset Methods 1-3 ? Changing CPU detection methods doesn't correct anything
Re: HWiNFO support of vintage hardware
Posted on 2020-04-29, 14:19
Mumak wrote on 2020-04-29, 13:39: Sorry, I meant CHKCPU 😀 Would be interesting to know what it reports right after HWiNFO reporting low clock. Just to prove whether HWiNFO does perhaps mess-up something with the clock. I have already checked it, and I'm sorry, CHKCPU is always correct 🙁
Re: HWiNFO support of vintage hardware
Posted on 2020-04-29, 13:27
This is totally weird. HWiNFO measures the execution time of a certain instruction set, so if it reports wrong there can be 2 reasons only: either the clock has really changed or something messed-up with the timers. And if you exit HWiNFO right after it reporting low clock and launch CHECKIT does …
Re: HWiNFO support of vintage hardware
Posted on 2020-04-29, 12:57
Mumak wrote on 2020-04-29, 11:48: What happens if you close the Mainboard info screen and open again a few times? Will it still show the low clock? Still no changes. Every time the clock shown is too low Also a question regarding #10: this one had an ALG2228 card, what's its exact name, some SPEA ? …
Re: HWiNFO support of vintage hardware
Posted on 2020-04-29, 09:56
I downloaded latest version (6.1.0), and retested a FIC board fror CPU sped issue. I have also dug yet another old 486 board (Shuttle HOT-409) and ran some tests with it. Results are: FIC 486-GVT-2 - Still have an issue displaying incorrect CPU speed on the screen (report is however OK.) SHUTTLE HOT …
Re: HWiNFO support of vintage hardware
Posted on 2020-04-27, 08:02
Hello I have retested both Soyo and FIC boards, with manually stepping through the screens. Results: - FIC: no changes, Am486DX4-100 CPU in report, DX2-80 CPU on the screen (always, nevertheless the what was done first (report. On the screen mode, what screen was first, CPU detection method) - Soyo: …
Re: HWiNFO support of vintage hardware
Posted on 2020-04-22, 15:19
I wish I could know the answers. I croschecked it with CHKCPU, which gave me correct results, but I don't remember if I had done it directly after the HWiNFO report run. What more wonders me is why report, and on screen display differs from each other? regards P. S. I wish 486 had a SpeedStep 😁
Re: HWiNFO support of vintage hardware
Posted on 2020-04-22, 12:09
I did tests again. IDE controllers are detected with no problems. Found some issues though: - On FIC board, report detects Am486DX4-100 CPU (which is ok.), but on the screen is displayed a DX2-80 CPU (that’s how motherboard sees it). - On the Soyo board things are reversed - on the screen CPU is ok …
Re: HWiNFO support of vintage hardware
Posted on 2020-04-21, 19:50
Quick Update I managed to revive another 486 VLB board, that I thought was dead - Soyo Sy-025K2, based on SiS chipset SIS 85C471. I tested it with "Check Keyboard Controller and Super IO" option Enabled, and with the same boards as above, except VLSIOVX VLB Promise PDC20230C board, that refused to …
Re: HWiNFO support of vintage hardware
Posted on 2020-04-21, 07:56
As far as I know, this board doas not have any SIO chip, but relies on external cards. It uses VIA chipset VIA VT82C486A, and has an additional chip VIA VT82C482.
Re: HWiNFO support of vintage hardware
Posted on 2020-04-21, 07:04
Back again I did some tests with “Check Keyboard Controller and Super IO” option enabled, and disabled. Testbed remains the same (FIC 486-GVT-2 + Cirrus Logic CL-GD5428 VLB card + 486DX2-66), except IO cards. I have tested following cards - Octek VL-Combo VLB Promise PDC20230C - VLSIOVX VLB Promise …
Re: HWiNFO support of vintage hardware
Posted on 2020-04-20, 13:23
P.S. Sorry for size of attachment. Next time I will lower the resolution
Re: HWiNFO support of vintage hardware
Posted on 2020-04-20, 13:22
Ok. 1. I486SX is detected correctly, logfile attached 2. I have tested again 486DX2-66 on FIC 486-GVT-2 with 2 VLB I/O cards (QD6500 and Promise PDC20230C), but sadly both make program crash. I have taken photo of both adapters, and screenshot when system freezes. Promise was shot twice – firs time …
Re: HWiNFO support of vintage hardware
Posted on 2020-04-16, 16:59
I'll do all that, but not until Monday (no time tomorrow, and no hardware on weekend) 🙁
Re: HWiNFO support of vintage hardware
Posted on 2020-04-16, 13:34
Found nothing I put the same CPU to another board (FIC 486-GVT-2), and is recognizable properly using all 3 methods. Program however hangs if trying to make report (on peripherals). I checked another CPU - the same. Maybe the problem is controller& I/O card, but I can check it in the next week. You …
Re: HWiNFO support of vintage hardware
Posted on 2020-04-16, 12:15
Sorry, still the same - 486DX
Re: HWiNFO support of vintage hardware
Posted on 2020-04-16, 06:59
Mumak wrote on 2020-04-16, 06:43: As for the 486SX - does the machine perhaps have an FPU ? In the previous test HWiNFO reported no FPU, now it looks as if there was one. Quake definitely claim there is no FPU, and refuses tu run
Re: HWiNFO support of vintage hardware
Posted on 2020-04-16, 05:54
I have repeated Intel i486SX-25 test. Program does work using all CPU detection method (with this specific CPU), but still is identified as DX25. I also pulled off the storage another old CPU – Cyrix DX 40, and tested it using revised version of HWinfo, but in this case program behaved like before – …
Re: HWiNFO support of vintage hardware
Posted on 2020-04-15, 15:31
Mumak wrote on 2020-04-15, 14:23: 486SX can be distinguished from 486DX only by CPU ID value AFAIK. And since the reset methods didn't work to obtain the ID, it wasn't correctly identified. I thought, that such old CPU does not support CPU ID?
Re: HWiNFO support of vintage hardware
Posted on 2020-04-15, 15:29
ad3. I guess I wasn't precise enough. I know that I can specify filename after - r switch, but this is not, that I was thinking about. What I was thinking of is another parameter (-p for example), after using which, program would asked to enter log filename BEFORE running the tests. What would it do …
Page 2 of 3