Mumak wrote on 2022-02-12, 17:10:

Thanks for the data, it's useful for me!
Yes, the check for GUS can happen if there's a NE2000 card present. I haven't figured out yet a reliable way to avoid this.

I have pulled the ethernet card. Here is the updated log file (I think that it is appended to the old one?)

Thanks, yes it's appended to the end of LOG. I will fix the IRQ list on pre-AT systems and need to figure out somehow how to solve the GUS hang with NE2000.

Released version 1.8:
- Fixed IRQ/DMA list on XT systems
- Removed GUS detection which was causing issues with NE2000 cards
- Minor improvements to CPU and video adapter detection

See initial post for download.

Mumak wrote on 2022-02-13, 17:32:

Released version 1.8: - Fixed IRQ/DMA list on XT systems - Removed GUS detection which was causing issues with NE2000 cards - Mi […]
Show full quote

Released version 1.8:
- Fixed IRQ/DMA list on XT systems
- Removed GUS detection which was causing issues with NE2000 cards
- Minor improvements to CPU and video adapter detection

See initial post for download.

I have tested the new version. There is some good news and some maybe not so good news. First: the IRQ overview seems to be in agreement with the computer type:

The not-so-good news is that the detection of devices still will hang the computer, this time on CD-ROM detection on port 310. Now this happens only after a certain sequence of events, so I am not quite sure what triggers this. I will do some more testing tomorrow to see if I can reproduce the error.

I ran HWINFO16 v18 on two computers.

The first is a true blue 5151 IBM XT with a stock 4KB IBM MDA adapter
The second is an XT clone ( DTK motherboard, 64kb Suntek hercules clone display )

HWInfo16 identifies both display adapters as :
º Video Chipset: Hercules Graphics
º Video Card: Unknown
º Video Memory Size: 4 KBytes
º Video Card Bus: Unknown
º Video RAMDAC: ???
º Video BIOS Manufacturer: Unknown
º Video BIOS Version: Unknown

Reports and debug files attached.

douglar wrote on 2022-02-18, 17:58:

I ran HWINFO16 v18 on two computers. […]
Show full quote

I ran HWINFO16 v18 on two computers.

The first is a true blue 5151 IBM XT with a stock 4KB IBM MDA adapter
The second is an XT clone ( DTK motherboard, 64kb Suntek hercules clone display )

HWInfo16 identifies both display adapters as :
º Video Chipset: Hercules Graphics
º Video Card: Unknown
º Video Memory Size: 4 KBytes
º Video Card Bus: Unknown
º Video RAMDAC: ???
º Video BIOS Manufacturer: Unknown
º Video BIOS Version: Unknown

Reports and debug files attached.

Thanks. I will adjust this to report MDA instead, however on such really retro systems it's not possible to detect the exact adapter as it doesn't feature any registers that could be used for differentiation. I'm also not aware how to properly detect display memory size in this case.

douglar wrote on 2021-12-26, 19:49:

I have a 12Mhz Packard Bell 286. The system has a 1MB Trident 8900c HWinfo16 v1.7 says: […]
Show full quote

I have a 12Mhz Packard Bell 286. The system has a 1MB Trident 8900c HWinfo16 v1.7 says:

Copy code to clipboard

1                             HWiNFO16 v1.7
2  ┌─────────────────────────────Video Information─────────────────────────┐
3  │ Video Chipset:            Trident 9000i A/B/C                     │

Mumak wrote on 2022-01-05, 22:17:

Thank you. This issue will be fixed in the next build.

I checked out v1.8 and it looks good. Thanks for the fix.

Mumak wrote on 2022-02-18, 18:39:

Thanks. I will adjust this to report MDA instead, however on such really retro systems it's not possible to detect the exact adapter as it doesn't feature any registers that could be used for differentiation. I'm also not aware how to properly detect display memory size in this case.

Can you use this code?

http://www.pennelynn.com/Documents/CUJ/HTML/9 … ML/199001B5.HTM

If an MDA card is detected, however, you can also distinguish between an MDA card and the Hercules cards. To do this, the vertical sync bit is sampled and then for a certain time interval, is continually and frequently re-sampled. If no change is observed, the video card is assumed to be an MDA card. If the vertical sync bit changes, the video card is one of the Hercules graphics cards. The specific card is identified by examining bits 4-6 of the status port; a pattern of 001 indicates a Hercules Graphics Card Plus, a pattern of 101 indicates a Hercules In-Color Card, and any other pattern is a Hercules Graphics Card.

douglar wrote on 2022-02-18, 18:44:

Can you use this code? […]
Show full quote

Mumak wrote on 2022-02-18, 18:39:

Thanks. I will adjust this to report MDA instead, however on such really retro systems it's not possible to detect the exact adapter as it doesn't feature any registers that could be used for differentiation. I'm also not aware how to properly detect display memory size in this case.

Can you use this code?

http://www.pennelynn.com/Documents/CUJ/HTML/9 … ML/199001B5.HTM

If an MDA card is detected, however, you can also distinguish between an MDA card and the Hercules cards. To do this, the vertical sync bit is sampled and then for a certain time interval, is continually and frequently re-sampled. If no change is observed, the video card is assumed to be an MDA card. If the vertical sync bit changes, the video card is one of the Hercules graphics cards. The specific card is identified by examining bits 4-6 of the status port; a pattern of 001 indicates a Hercules Graphics Card Plus, a pattern of 101 indicates a Hercules In-Color Card, and any other pattern is a Hercules Graphics Card.

That's interesting, thanks! Going to use that and will post a new test version shortly.

douglar wrote on 2022-02-18, 18:44:

Can you use this code? […]
Show full quote

Mumak wrote on 2022-02-18, 18:39:

Thanks. I will adjust this to report MDA instead, however on such really retro systems it's not possible to detect the exact adapter as it doesn't feature any registers that could be used for differentiation. I'm also not aware how to properly detect display memory size in this case.

Can you use this code?

http://www.pennelynn.com/Documents/CUJ/HTML/9 … ML/199001B5.HTM

If an MDA card is detected, however, you can also distinguish between an MDA card and the Hercules cards. To do this, the vertical sync bit is sampled and then for a certain time interval, is continually and frequently re-sampled. If no change is observed, the video card is assumed to be an MDA card. If the vertical sync bit changes, the video card is one of the Hercules graphics cards. The specific card is identified by examining bits 4-6 of the status port; a pattern of 001 indicates a Hercules Graphics Card Plus, a pattern of 101 indicates a Hercules In-Color Card, and any other pattern is a Hercules Graphics Card.

Actually I had this already implemented but it seems the test wasn't performed properly.
Here's a new version, please try and let me know the results. ANew LOG+DBG files will be needed so I can verify if it works as expected.

Looking better-- MDA detected correctly.

For the Hercules cards, maybe you could default to 64KBytes memory size
º Video Chipset: Hercules Graphics
º Video Card: Unknown
º Video Memory Size: 4 KBytes

douglar wrote on 2022-02-19, 01:52:

Looking better-- MDA detected correctly. […]
Show full quote

Looking better-- MDA detected correctly.

For the Hercules cards, maybe you could default to 64KBytes memory size
º Video Chipset: Hercules Graphics
º Video Card: Unknown
º Video Memory Size: 4 KBytes

Thanks. Yes, that will work, but it looks like the Hercules detection didn't work properly in v1.9.
Here's a new version, please run again and let me know the result with new report+DBG:

Not as good this time

douglar wrote on 2022-02-19, 22:35:

Not as good this time

Thanks for the results. Please try again with

I attached the results for v21 .

I alos reviewed and noticed that I attached the wrong files for the prodata on v19. I have attached those files here.

douglar wrote on 2022-02-20, 19:42:

I attached the results for v21 .

I alos reviewed and noticed that I attached the wrong files for the prodata on v19. I have attached those files here.

Thank you for the results and patience! I think I have finally found the bug(s), it was not obvious. Posting a new version that I'm quite confident should finally work. Please let me know..

I knew I should have scripted this process back on v19

Results look good--

IBMXT:

1                             HWiNFO16 v2.2
2  º Video Chipset:            MDA Mono
3  º Video Card:               Unknown
4  º Video Memory Size:        4 KBytes

ProData:

1                                HWiNFO16 v2.2
2  º Video Chipset:            MDA Mono
3  º Video Card:               Hercules Graphics Card
4  º Video Memory Size:        64 KBytes

Finally 😀 It's perfect now. Thanks for all testing!

Greetings!

My 5160 was out of work for some time due to the HDD failure. I bought a new one so can continue with the tests.
I have past some releases but the latest version still crashes on video test, now it crashes after the checking Compaq, see screen attached as well a debug info. Another issue is that in this version only one FDD was detected not two.
Will try to swap adapter to CGA and redo the test.

Susanin79 wrote on 2022-02-22, 21:13:

Greetings! […]
Show full quote

Greetings!

My 5160 was out of work for some time due to the HDD failure. I bought a new one so can continue with the tests.
I have past some releases but the latest version still crashes on video test, now it crashes after the checking Compaq, see screen attached as well a debug info. Another issue is that in this version only one FDD was detected not two.
Will try to swap adapter to CGA and redo the test.

Thanks for the results. What is your current video adapter?