s900387@minyos.xx.rmit.oz.au (Craig Macbride) (03/16/91)
My first problem, that of the PC's networking software dying, seems to be over.
Now that I am using the w3pktdr2 (MSWindows) 3c503 driver from NCSA, everything
seems to be working great. I haven't had a chance to test this fully yet, but
when I left the PC (a 20MHz 386) it was running 5 xterms, 6 xeyes, 1 xclock, 1
xload and 2 mazes. 4 of the 5 xterms are getting sent output every second by
shell scripts. The PC is also being ping'ed constantly. It was able to run
Microsoft Word and Project out of Windows at the same time as all this was
happening, without the system falling down! It is incredibly slow, but the
point is that real users will never make demands on the system this bad.
As an aside, particularly heavy activity (eg. starting a Windows application or
a maze) may cause ping to time out up to 30 (!!) times in succession, but the
system does not crash. (As yet ... I'll see if it's still up after the weekend.)
The Clarkson stuff we got with PC/TCP didn't have anything about the -n
switch in any documentation I came across, but a number of people pointed this
out to me. Apparently the driver I got from NCSA supports it as well, so
hopefully I can get this thing talking to Novell servers, too.
--
_--_|\ Craig Macbride <uni: s900387@minyos.xx.rmit.oz.au>
/ \ <work: craig@bacchus.esa.oz.au>
\_.--.*/ VUT (RMIT) is responsible for the equipment, not the opinions!
v