You probably can find something to list resources occupied by PCI (including PCIe), AGP, and ISAPNP devices.

But there's no universal way to find resources used by non-PNP ISA cards, no way to create a trustworthy utility for that.

Grzyb wrote on 2024-06-28, 22:34:

But there's no universal way to find resources used by non-PNP ISA cards, no way to create a trustworthy utility for that.

Ok thanks for that, I thought maybe I was overlooking something obvious.

I usually see what MSD, Norton Sysinfo and Snooper say, then harmonise the results with an amethyst crystal pendant, then guess.

Even IRQs/DMAs, you can't actually interrogate the cards in any standard way and determine what is being used.

For IRQs, you could look and see whether an interrupt vector is installed or whether it's just pointing to an iret, or an EOI and an iret.

A better way is a program, like HWiNFO from Mumak here at vogons, that has a database of ISA cards inside it and probes all the ones that can be probed safely to see if there is a card there. That would have probably helped with your issue, too. Compiled-in ISA drivers to the Linux kernel worked like that, too.

BitWrangler wrote on 2024-06-29, 01:27:

I usually see what MSD, Norton Sysinfo and Snooper say, then harmonise the results with an amethyst crystal pendant, then guess.

😆 Yep totally get it.

Thanks for the tip on Snooper, I'll defintely try it out. My "UTILS" directory currently contains:

- CHECKIT
- HWINFO
- MSD of course
- NICSCAN
- CONFIG (PC Config)
- PCICFG
- SPEEDSYS

Favorites are MSD & HWINFO so far. Speedsys is nice too, but I find myself going to HWINFO first.

jakethompson1 wrote on 2024-06-29, 01:31:

A better way is a program, like HWiNFO from Mumak here at vogons, that has a database of ISA cards inside it and probes all the ones that can be probed safely to see if there is a card there.

Agreed! Love HWiNFO

Somewhere either in the linux kernel tree or old Slackware release notes, I bet you can find a list of "dangerous" ISA cards that will lock up the machine when probed by another driver that scans that same I/O port