286 and network

I am a junkie. I have a wardrobe full of old iron. From Boolean IC chips in DIP packages to Voodoo5. Of course, all this is of no practical value, but some people enjoy the pleasure of messing with old pieces of iron. If you are one of them, I invite you under the cat, where I will tell you how the computer based on the AMD 286 processor “was friends” with the modern network, and what came of it.

The idea of ​​screwing the network to the 286th was born a long time ago, since it is easiest to transfer data to a computer over the network, and in general, this is interesting. Does TCP / IP work? Does the web browser earn money? Although browsers under Dos, people on 286m have already repeatedly launched, but I have never seen 286go under Windows on the Internet. Well, the main goal is to connect to a home NAS, which stores all the software for my old hardware. And the NAS is more or less modern, and only TCP / IP can do it.

I already had experience connecting to this drive of old computers. Including while writing previous articles about old iron. But in previous articles I only considered 32-bit processors, and everything is pretty easy there: even on 386SX-16, Windows 95 runs (yes, terribly slow, yes, the installation takes more than 9 hours, but it works), which has a native TCP stack / IP and a bunch of drivers for all kinds of network cards included. If you want to be quicker, that is, Windows for Workgroups 3.11, onto which, after installing Win32s, you can roll your own TCP / IP stack. And, although it will not be able to log in to a modern file server, open folders without a password become quite accessible to the PC even in this configuration. And Internet Explorer 5 runs even on 386SX, it would be enough memory!
')

image pulled from google

But alas, by 286 all this does not apply. The main difficulty is that the 286 processor is 16-bit, and Windows for Workgroups 3.11 is not available for it, since the Standard mode, which allowed its predecessor 3.1 to run on 16-bit processors, was cut out of 3.11. Unsatisfied at 286 and the Win32s extension (for obvious reasons), and, accordingly, it will not be possible to install the native Microsoft TCP / IP stack.

Thus, we return to DOS.

After a brief, thoughtful googling, the DOS TCP / IP picture became much less clear than it was before. Basically, it all came down to the fact that the application normally running under DOS itself has its own stack, and all it needs is a packet driver for the network card. But I could not find an application that allows you to mount remote disks.
However, I came across as many as 2 different network clients for DOS from Microsoft itself (MS Client and MS LAN Manager), and another very strange beast called Windows for Workgroups 3.1. Yes, it was 3.1, not 3.11, and this meant that everything might work in the standard mode.
What would be extremely interesting. Of course, I did not expect to see TCP / IP stack 3.1, but also on Google I came across a description of the 16-bit TCP / IP stack from Microsoft. Interesting.
Having bought the distribution kit 3.1 on eBay, I proceeded to the installation.


image pulled from google

The system turned out to be a slightly modified 3.1 with a built-in network interface under DOS, very similar to the stripped-down MS LAN Manager. All the difference from the traditional 3.1 was reduced to the presence of the “mount network drive” button in the File Manager and the corresponding dialog box. Network configuration from under Windows itself was impossible. How to perform the setup from under DOS was not clear. Although after installing the system, she identified my network card as NE1000 or compatible, which was not far from the truth, because the Genius GR1222 card I used was true. But I had a native driver disc for this card, including under DOS. It remained unclear, however, how to configure the driver for the interrupt and the address of the I / O card.

Moreover, after reading Google it turned out that the driver for MS LAN Manager and the packet driver are two different things.

The situation with the drivers under DOS began to clear up a bit.

So, there were 3 big standards:

1. Odi. This driver model used Novell to communicate with its Netware servers. I do not have Netvari, so it will not work.
2. NDIS. This is a Microsoft model, for their LAN Manager and Windows. In theory, that is necessary.
3. A batch driver that many DOS applications use.

, . MS Client MS LAN Manager , . , , TCP/IP MS Client Windows for Workgroups, MS LAN Manager.

NE1000, , .



2.2 TCP/IP!!! . , 5-7 286. . DHCP, .

. .

PROTOCOL.INI
. , , LAN Manager IP , , :

192 168 1 101

, , , LAN Manager , . , ping, NET USE . .
, , , , .
.INI , , - . . . .
.
, , Windows for Workgroups .
, Windows, .



, : . , , - , Windows NT . , , Windows for Workgroups , .

.



.

, . , D-Link DE-220P. MS LAN Manager , :



DHCP. , .

:





NET USE Z: \\HOSTNAME\SHARENAME



! ?

DIR Z:



, , …

, . - . , . .

. , : EMM386 LAN Managera 640, :



Windows , Netscape Navigator, MS Internet Explorer 286, NCSA Mosaic TCP/IP LAN Manager'. , , , , . , 286. , .

, , 286 «» , , . , , «» 386 , 286 1 … 16- , , , 286 . , 20 , , , , 286 «» 640 , : , , . , Windows - , Windows. , , , . , 6.22 . .

3 :

1. . «» . .
2. NDIS. , Windows .
3. .

, . D-Link DE220 , , , ISA. - . NE2000, , .

, TCP/IP , - TCP/IP. , , mTCP, Windows — Trumpet Winsock, 1 .

, , . , NCSA Mosaic TCP/IP , , .




16- TCP/IP Windows. . WFWG 3.11, 3.1 - Windows. - , .

, Windows. ( , NE2000-, ), … « »



16- … . . : , Windows TCP/IP . .

, , . , . , , 286. 386, Headland , SIMM, 16 , , Intel 286 12 . , 24 , 12 … , . . . , , DIP. , 1 , Windows …



Windows:



Windows 286 . , - Windows Windows. 16 .