Okay, this might be a bit esoteric since it concerns Windows 3 drivers, but here goes:
The Basics: DOS wants to load a hardware driver from a particular IO address, but the Windows-based configuration utility for the driver doesn't allow me to select that address.
The Details: I've got a ThinkPad 701c - the "butterfly" keyboard model. I've got a nice, snappy install of Windows for Workgroups 3.11 on it. PCMCIA support is installed, as is the driver for the IBM credit card ethernet adapter I have.
When the computer boots, it turns on power to the IBM card. And my network router indicates that it "sees" the 701c on the network. TCP/IP is installed on the computer, bound to the IBM card, and seet up for DHCP. All is well - almost...
But - every time the driver starts to load in DOS (before the C:\ prompt comes up), it says that the "hardware failed to respond" and it unloads the driver as soon as it's been loaded. Network services are loaded correctly, and the PCMCIA slots are detected properly - it's just that the PC card's driver fails when it attempts to initialize/communicate with the PC card. (FYI the PC card and PCMCIA slots are confirmed fully functional, and I've tried it in both of the computer's PCMCIA slots, with the same results.)
So I've got an OS properly configured for TCP/IP with DHCP; and I've got a laptop that physically and electrically interacts with the PCMCIA ethernet card. But I can't get the OS to "talk" to the card.
Now, here, finally, is my question. Googling seems to reveal that DOS Card and Socket Service drivers look for PCMCIA controllers at IO address 0x03E0 (see for example http://www.cardupdate.com/support/pcic3eo.php). In the network setup under Windows, however, I cannot select that IO address for the IBM card - the highest address is 0x03A0. After triple-checking IRQ and extended memory settings for this card, I conclude that it must be that the DOS drivers are looking for the card at 0x03E0, while the braindead Windows-based configuration utility is setting the IO address to a different location.
I know this is a pretty specific issue - but perhaps it rings a bell for someone on these forums? Perhaps you've experienced or heard about IO address problems before, even if not in this exact context?