Search results for query: *

Stan, You are exactly correct. I didn't find this article in SCO's knowledgebase but came to the same conclusion. /etc/rc2.d/S85tcp had excess "net1" entries which had to be edited out as well. Of course replacing a bad NIC with a bad NIC didn't help my stress level either. The network...

Oh, an addendum to the previous. This was the the way the reinstall problem began. The remove process fails leaving the card partially removed and config files in a mess. Then the re-install "succeeds" and it looks like we have two NICs and redundant function calls in /etc/strcf.d/10tcp and...

New problem now. I started to remove the old 3Com driver via Scoadmin/Network Manager. I selected the 3Com hardware and then "remove hardware". The remove process failed with a message "/usr/lib/netconfig/remove/sco_tcp: Unknown operator 192.100.0.1" That IP address was on the system long...

The Lucent chip on both are the same number, 40-0336-004. The "bad" card was a rev-B and the replacement card was a rev-A. I will try a driver install. Can't hurt, and at this point I'm willing to try almost anything. My hair is sparse and I can't afford to lose any more.

Long story... First the facts. SCO Open Server v.5.04, 3COM, 3c905-tx NIC. The SCO server app is accessed by FacetWin apps on the Win desktops. This has worked well for several years. This is primarily a Win environment with a legacy SCO server supporting the original filePro data...