The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: corey@lod.com (Corey Lindsly)
Subject: [TUHS] AT+T UNIX PC Information needed
Date: Mon, 20 Feb 2006 20:52:26 -0800 (PST)	[thread overview]
Message-ID: <20060221045226.0461F5D85F@lod.com> (raw)
In-Reply-To: <200602210346.WAA21487@cuzuco.com>


> Duncan Anderson asks:
> > Thanks for that bit of information. I had been under the impression that it
> > was V3. Is the lack of streams the main difference between the 2 and 3? If
> > there is no streams interface, can the machine be part of a TCP/IP network?
> 
> SVR3 also added shared libraries and RFS. As for TCP/IP the popular
> implementation was from Wollongong. But wouldn't you need ethernet
> hardware support too? It's been a long time but I only remember
> StarLAN hardware for it.

There is indeed an ethernet interface for 
the UNIXpc, but they are exceedingly difficult 
to come by. It's separate from the StarLAN card.

From the 3b1 FAQ:

"If you want to connect your UNIX PC to a *real* Ethernet,
you'll need to hunt down the AT&T UNIX PC Ethernet board.  This board
runs a version of the TCP/IP drivers developed by Wollogong.  The
board will require the proper cables, as well as a transceiver.  This
increases the cost of Ethernet interconnectability.  The Wollogong
TCP/IP drivers are an older version not supported by Wollogong
anymore.  It's generally acknowledged that there are many bugs, and
the throughput of the board is nowhere near what Ethernet should be
getting.  (People report that throughput with the Starlan-1 board was
better than the TCP/IP Ethernet board, which shouldn't be the case.)"

http://www.faqs.org/faqs/3b1-faq/part2/

There are also information and schematics pertaining
to the UNIXpc ethernet interface in the Technical Reference
manual, which I am in the process of scanning & PDFing
for interested parties.

Regards,

---corey




  reply	other threads:[~2006-02-21  4:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-21  3:46 Brian S Walden
2006-02-21  4:52 ` Corey Lindsly [this message]
2006-02-21  8:58   ` Duncan Anderson
2006-02-21  8:56 ` Duncan Anderson
2006-02-21 17:00 ` Sven Mascheck
  -- strict thread matches above, loose matches on Subject: below --
2006-02-18 15:44 Mike Haertel
2006-02-18 16:48 ` Michael Davidson
2006-02-20 10:03 ` Duncan Anderson
2006-02-18  8:48 Duncan Anderson
2006-02-18 14:34 ` Brantley Coile
2006-02-18 15:25   ` Duncan Anderson
2006-02-18 15:32 ` Corey Lindsly
2006-02-18 20:19 ` Robert Tillyard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060221045226.0461F5D85F@lod.com \
    --to=corey@lod.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).