Chances are, when you installed Windows for Workgroups, you may not have bothered with the
I installed Windows for Workgroups as it was a later version of the then-popular Windows 3.1 and it was, in my experience, more reliable. I also figured paying a little extra for the peer to peer networking wasn't that big a thing, as it was useful to have if needed.
It was almost a decade later that I put the networking components into use!
First...You will have a group in program manager called Network. Open it, then double-click on the icon Set up network.
Click the lower of the three options, to set up your adaptors...
If all else fails, try the NE2000 driver and hope for the best!
If you bought a new card, it should have suitable instructions...
Once you have installed your adaptor, you can install your protocols. If you do not have IPX/SPX
and NetBEUI installed, then click the Add protocol button and install them.
Do not waste time looking for TCP/IP, you don't have it...yet...
When you have done that, click on Close (it will appear at the top right, it isn't on my window as I had not modified anything when I took this screenshot).
You are now back at the window with the three options. Click on the middle button to decide what you wish to share.
You will now be back at the window with the three options. You can ignore the top option. It is only of relevence if you are setting up multi-protocol or non-standard networks. By default, the options are set to work with a MicroSoft compatible network. That suits us fine...
Click on the Accept icon and prepare for loads of disc swapping!
You will then see...
Your drivers and protocols installed, you will want to set the basic configuration. Open the Control Panel and click on Network...
Windows for Workgroups seems a bit 'odd' with it's user authentication. Simply give yourself a user name (I chose MOM) and don't bother with a password. Windows will probably ask you to confirm your username/password at some later date. Simply check the username and don't bother with the password. It will stop asking.
Click the Startup icon in the options list...
In the performance priority, set up the running and sharing tradeoff as you prefer. The PC is not currently being used as anything other than a file server, but that is expected to change quite soon, so I have set it to run it's own tasks at maximum speed; thus meaning it pays much less attention to the network.
Some timings to illustrate...
It is a 486DX/4 66MHz processor, 8Mb RAM, running Windows for Workgroups 3.11 LanMan via TCP/IP. The settings were for applications to run fastest.
My RISC OS 3.7 machine is a 40MHz ARM710 machine running OmniClient 2.04 and Samba 0.07a.
Transferring 6 files each 738358 bytes, deleting the originals, took 73 seconds.
That's a total transfer of 4430148 bytes of data, plus whatever overheads for deleting the files and the TCP/IP packets etc. As far as the data itself is concerned, it went from there to here at approximately 60K a second.
Too slow for you? Play with the performance settings. Get your preferred trade-off between share speed and application speed. Knocking the slider to resources shared fastest had a dramatic effect on the speed of networking between the two machines. Play around with it, the results are instant (no rebooting required), and see what feels best.
Click OK; and in the options list click Event log.
While it is restarting, we can think about setting up TCP/IP.
That is the next step...