kishy
Veteran Member
I KNOW these types of topics exist but the search is obviously broken or something, I either get a whole bunch of nonrelevant posts or nothing at all, so here goes...
I have a 286, as many know, and I've placed a D-Link DE220 16-bit ISA Ethernet card in it. I want to get this machine up and "talking" on my network hopefully with the ability to share files with my Windows XP computers, and definitely with the ability to access the internet, either by TUI or GUI browser, I'm not picky in that regard. The machine does have the original implementation of VGA as it is a PS/2 30 286. It would be nice to have it lease an address via DHCP from my router but static is fine too (probably a bit less overhead at startup this way).
I've installed Windows for Workgroups 3.1 (not 3.11; I do not want to try to modify it to work on a 286). I've found a DOS driver (and WFW 3.1 driver - are these one in the same though?) for this card and it appears to initialize correctly on bootup.
Apparently this is a "packet driver", so I still need a TCP/IP stack. The commonly available Microsoft one needs 3.11 and is 32 bit, apparently (according to itself).
The D-Link drivers claimed to include their own, but when I added it with a device= line in config.sys, I found it just loaded a second instance of the driver...
Can anyone point me in the right direction here? I'd like a TCP/IP stack that will fully integrate into the operating system so that when an application wants out, out it will go.
Thanks!
I have a 286, as many know, and I've placed a D-Link DE220 16-bit ISA Ethernet card in it. I want to get this machine up and "talking" on my network hopefully with the ability to share files with my Windows XP computers, and definitely with the ability to access the internet, either by TUI or GUI browser, I'm not picky in that regard. The machine does have the original implementation of VGA as it is a PS/2 30 286. It would be nice to have it lease an address via DHCP from my router but static is fine too (probably a bit less overhead at startup this way).
I've installed Windows for Workgroups 3.1 (not 3.11; I do not want to try to modify it to work on a 286). I've found a DOS driver (and WFW 3.1 driver - are these one in the same though?) for this card and it appears to initialize correctly on bootup.
Apparently this is a "packet driver", so I still need a TCP/IP stack. The commonly available Microsoft one needs 3.11 and is 32 bit, apparently (according to itself).
The D-Link drivers claimed to include their own, but when I added it with a device= line in config.sys, I found it just loaded a second instance of the driver...
Can anyone point me in the right direction here? I'd like a TCP/IP stack that will fully integrate into the operating system so that when an application wants out, out it will go.
Thanks!
Last edited: