I have not returned to this topic for awhile but in this time I've learned much from the replies here and on my own I've read about important working details of the ibm-pc hardware.
To start off with, this thread is about a socket 5 mother board I got that didn't come with on board support for a mouse, floppy, or hard drive.
I found, to my shock, correct all who explained that there were some motherboards from the Socket 5 years didn't have built in I/O and IDE (floppy being part of the ATA-1/IDE specs). I've been shopping for a new motherboard and noticed many small business/distributor motherboards - they seem brandless. Most OEM boards do without on board interfaces.
I was at first unable to use anything even with an IDE card. But I had a 1999 E Series Aptiva. One lone ISA slot had my Acculogic sIDE-3 and floppies, IDE Hdd, and cd-rom worked. This Aptiva had on board interfaces and none were used during the test.
My next move was reading the datasheet for the GoldStar IC on the interface. That showed that they use one IRQ line connected to the bus. I have seen on fdc/ IDE interface that auto assigns IRQ numbers. My guess is my interface must be auto assigning and address that conflicts - because my BIOS is anemic.
Initially information I located about jumpers was about a different interface not at all like mine. Later when I located the correct info I discovered the interface IDE had no jumper at all on a block to activate IRQ 14 to make it primary. Floppy remained unusable.
I warn folks that cf cards and modern windows involve safe guards that prevent windows 95 from accessing the cf card. Most likely because I'm using virtualbox which is a "hosted" hypervisor - it's like using a windows application to access the bootsector of a virtual hard drive on the cf card. I could not make this work. I know imaging is the next route here because it cuts out the hypervisor. I did try imaging a floppy and got a win 95 boot disk but needed the Aptiva to make it. Hard drives would need VHD and could image there. But no plans for that now.
I want to add that a cheap USB 2.0 cf card reader was ruining my cf cards and making them unusable. I replaced the USB 2.0 with USB 3.x. My USB 3.x reader used a 3.x cable with a USB C connected to my laptop running windows 11 and at the other end a type micro a/b which has extra pins for power.
I got past my cf problem by I trying a IDE to USB cable to employ the process of using virtualbox on a 3.8 GB UltraATA/33 hard drive and there was no problem issued from windows 95 format command.
But the 16-bit controller only deals in FAT16. My handiwork was FAT32.
This weekend I installed in my SOYO SY-033A disks and interface consisting of:
EIDE UltaATA 33 3.4 GB disk initialized on the APTIVA, using on board EIDE headers.
A Promise Technology PCI controller - also UltraATA 33.
The interface auto configures the settings but no luck. The BIOS had user defined CHD for the disk. You can't turn off an interface because there is none. I am pretty sure BIOS was detecting my older IDE disk on the acculogic controller. Maybe in their cheapness they only ordered BIOS that supported older cheaper IDE-1.
I agree with Sphere's idea of using a PCI based SATA interface and SATA to m.2 adapter. It's just a great idea because it's disk based which are easier to use than CF cards.
The MobRules takes the route of using motherboard supported manufacturer for a SCSI interface as he mentioned in his post above. This is essentially the way out. My motherboard also mentions NCR in the docs. But I have yet to deal with floppy and how to initialize steps. There's a USB adapter for 50 pin SCSI but it's rare - that's code for expensive.