Just wanted to add some info in case anyone might have an idea what's going on. As mentioned, the card acts like it can't be seen on any port when trying to initialize it. However, I've found that I can use the Program.bat file in the Eeprom folder of the installed software to write to the eeprom. Program.bat won't work when I specify the wrong port, but it does work when I match the port the jumpers.

This seems to mean that the card does exist in some capacity on the port specified with the jumpers. However, even though I can use Program.bat in DOS, pincfg.exe still won't initialize the card in DOS at the same port.

Is it the DSP that is busted?

Have you tried getting it working in Windows?

I have tried to get it working in Windows. Here is a summary of how it went:

Windows 95: Digital Audio driver installs, but upon restart, pindsp.vxd complains that the hardware cannot be found on the port. Also, manually changing the control port or the DSP port in Device Manager causes a blue screen. The card also isn't found by Windows 95 in PnP mode.

Windows 98SE: Windows 98SE blue screens immediately after the digital audio driver is selected, and the driver is not installed. Not found in PnP mode either.

Windows NT 4.0 & Windows 2000: The driver install errors with "The PnP Board address is wrong" regardless of what settings are selected.

This all occurs with everything removed from the computers besides a video card and practically everything disabled in the BIOS. The 290-297 port range that the card wants by default for the DSP conflicts with the PCI bus, but it also doesn't work when I attempt a valid port with no conflicts.

It really seems strange to me that the card just won't talk. I was expecting that if the card had a problem, it would half work instead of nothing at all.