HDTenEightyP/NetNews huggingface dataset:
From: olson@anchor.esd.sgi.com (Dave Olson)
Newsgroups: comp.dcom.lans.misc,comp.protocols.misc,comp.sources.wanted,comp.sys.misc
Subject: Re: Multi-drop Serial Protocol Wanted (RS-232)
Date: 24 Jan 93 22:18:25 GMT
Organization: Silicon Graphics, Inc.  Mountain View, CA

In <1993Jan24.181433.26225@rosevax.rosemount.com> bill@texan.rosemount.com (William Hawkins) writes:

| >jdc@isis.cs.wayne.edu (Jon Cardwell) writes:
| >+---------------
| >| We're looking for sources or references for a "multi-drop serial protocol"
| >| i.e. one that allows multiple devices to be attached to the same serial line.
| 
| RS-232 is not a multi-drop protocol *electrically* because it holds
| the line at the mark (or space) state.  You need the RS-485 protocol
| to multi-drop devices, because it lets the line float if a device
| has nothing to say.  There are 232 to 485 converters available (or
| there were 7 years ago).  Then you can implement a master-slave
| software protocol for the universe of devices attached to the line.
| 
| In ISO terms, RS-232/485 is barely a physical layer specification.
| You get to do anything you want with the rest of the layers.

Wyse makes (made?) both 485 terminals, and 485 drops to rs232 protocol
boxes (2 and 8 232 ports per box).  I don't remember if they ever made
the controller boards.  This was done about 5 years back, originally as
a joint project with Altos.  I did a lot of the driver work, and it
worked pretty well (we ran 64 terminals at full speed both directions
off a 286 box).  As I recall, the datarate was about 1.4 Mbits/sec on
the multidrop wire. 
--
Let no one tell me that silence gives consent,  |   Dave Olson
because whoever is silent dissents.             |   Silicon Graphics, Inc.
    Maria Isabel Barreno                        |   olson@sgi.com
Newsgroups: comp.dcom.lans.misc,comp.protocols.misc,comp.sources.wanted,comp.sys.misc
From: burke@seachg.uucp (Michael Burke)
Subject: Re: Multi-drop Serial Protocol Wanted (RS-232)
Reply-To: burke@seachg.UUCP (Michael Burke)
Organization: Sea Change Corporation, Mississauga, Ontario, Canada
Date: Thu, 28 Jan 93 14:28:38 GMT

In article <1993Jan24.181433.26225@rosevax.rosemount.com> bill@texan.rosemount.com (William Hawkins) writes:
>>jdc@isis.cs.wayne.edu (Jon Cardwell) writes:
>>+---------------
>>| We're looking for sources or references for a "multi-drop serial protocol"
>>| i.e. one that allows multiple devices to be attached to the same serial line.
>
>RS-232 is not a multi-drop protocol *electrically* because it holds
>the line at the mark (or space) state.  

Hogwash...

RS232 has been used for years with BSC 3270 multi-drop circuits. Generally,
the trick is to use the fastest modem turn around time possible to get best
results. The "poll-ack" protocols are above this physical standard.

Remember, multi-drop does not mean a "bus architecture" in the strictest
sense. One orders a multi-drop circuit from the Telco. I have not been
involved with BSC 3270 circuits for many years (about 15) so I have no idea
how one would go about building an in-house multi-drop circuit....


-- 
---
Michael Burke

Sea Change Corporation
6695 Millcreek Drive, Unit 8 
Mississauga, Ontario, Canada L5N 5R8
Tel: 416-542-9484  Fax: 416-542-9479
UUCP: ...!uunet!uunet.ca!seachg!burke
From: atkinson@itd.nrl.navy.mil (Randall Atkinson)
Newsgroups: comp.dcom.lans.misc
Subject: Re: building wiring
Date: 24 Jan 93 23:26:23 GMT
Followup-To: comp.dcom.lans.misc
Distribution: na
Organization: Naval Research Laboratory, DC

[ redirected discussion from comp.protocols.tcp-ip :-]

In article <1993Jan24.231044.16138@xenitec.on.ca> merce@xenitec.on.ca (Jim Mercer) writes:

>for new buildings, [coax is] dead, except for the possibiliy of backbone 
>pulls of thick coax to connect wiring centres, but then you might consider 
>fiber.

  Actually, I happen to be planning for a 1995 building and we are
sure that our backbones will be fiber.  However, we expect to continue
to have a large installed base of workstations that want a thin-net
Ethernet coax connection and do not plan that twisted pair will be
enough.

  The harder question is which kind of fiber to install.  So our
backbone plans have both single-mode and multi-mode fiber.  The
distribution within the floors will be decided upon later so we have
time to figure out what we want.

>for existing buildings, if you are pulling new cable, pull UTP.  you
>will probably save some money on media.  you will spend it later in hubs.

  Actually most of the cost of cabling installation is in the labor,
so it would be much wiser to put in Shielded Twisted Pair (STP), with
2 pair of wires per outlet.  NB: Anything that will run over UTP will
also run over STP, but the reverse is NOT true.  STP is wisest and
gives the most flexibility, with little real cost difference from UTP
when you figure in installation costs.

>2) What options are available for small (less than a dozen nodes) networks
>currently running coax and wanting to move to 10BaseT?  

  If really small, then why not just use continue to use what you have
where you have it, move to STP for new locations and add
tranceivers/T-joints where there are new drops in existing coax
locations.
Newsgroups: comp.dcom.lans.misc
From: sjl@panix.com (Steve Lewis)
Subject: Converting WP mini -> lan
Keywords: wp conversion
Organization: PANIX Public Access Unix, NYC
Date: Fri, 22 Jan 1993 15:29:52 GMT


We are about to convert from a Wang mini environment to Novell LAN.  We
currently keep about 150,000 live WP documents and are trying to figure
out a reasonable scheme for converting these documents to our new editor
(Word for Windows).

In general, how many documents do we convert off the bat, and how do we
choose them?  By age?  By user request?

After the initial large conversion, do we restrict who can do future
conversions?  (500+ users, with WP strictly controlled by document
management.)

Any advice from folks who have already been through this?

Thanks, Steve Lewis.
Newsgroups: comp.dcom.lans.misc
From: mfroedge@lunatix.uucp (Maxwell Froedge)
Subject: Token Ring Networks
Organization: Lexington Public Access Unix. -KY- (606) 255-9121
Date: Wed, 27 Jan 1993 02:44:57 GMT

I am looking for information on IBM Token Ring Networks.
Unfortunately I do not know the proper newsgroup to post this to.
I really need basic information on the system.  Probablely a FAQ would
answer about 90% of my questions at this point.  However I donot know
how to get my hands on it.  There does not appear to be a
Comp.sys.ibm.tokenring or some variant of it at my location.

Any infomation would be appreciated.

Maxwell K. Froedge
lunatix!mfroedge@ukma.UUCP


Newsgroups: comp.dcom.lans.misc
From: bert@penril.com (Bert Robbins)
Subject: Re: building wiring
Organization: Penril DataComm Networks
X-Newsreader: TIN [version 1.1 PL8]
Date: Tue, 26 Jan 1993 13:53:40 GMT

John K. Scoggin, Jr. (scoggin@delmarva.com) wrote:
: In article 9AF@ra.nrl.navy.mil, atkinson@itd.nrl.navy.mil (Randall Atkinson) writes:
: > [ redirected discussion from comp.protocols.tcp-ip :-]
: > 
: > In article <1993Jan24.231044.16138@xenitec.on.ca> merce@xenitec.on.ca (Jim Mercer) writes:
: >   Actually most of the cost of cabling installation is in the labor,
: > so it would be much wiser to put in Shielded Twisted Pair (STP), with
: > 2 pair of wires per outlet.  NB: Anything that will run over UTP will
: > also run over STP, but the reverse is NOT true.  STP is wisest and
: > gives the most flexibility, with little real cost difference from UTP
: > when you figure in installation costs.
: > 

: This is NOT true.  STP has a different impedance than UTP.  We made the mistake
: of wiring two large buildings with IBM Type 2 (STP) cable.  We have had problems
: running 10BaseT over long (75-100 meters) distances as a result.  Believe me,
: there is a BIG difference in cost between UTP and STP if you have to use plenum-
: rated cable (Teflon)...


We have recently acquired space that IBM had been leasing and had placed
Type 2 wiring in. We were very glad to have the existing wiring to use.
We are running 10BaseT on the piggy-backed 4 twisted-pairs of the Type 2
wiring, some lengths are 75-100 meters, and have experienced no problems
at all.  The existing TR connections have been used to connect up serial
links to various equipment throught the building and works great.

BTW, the twisted-pair runs through two punch blocks from the ethernet
HUB, Penril S2000 Router, to the workstations and PCs.


--
Bert Robbins                          Penril DataComm Networks
bert@penril.com                       1300 Quince Orchard Blvd
301/921-8600 x8856                    Gaithersburg, MD   20872
Newsgroups: comp.dcom.lans.misc,comp.protocols.ibm,comp.protocols.misc
From: skl@wimsey.bc.ca (Samuel Lam)
Subject: Re: 802.2 frames with DSAP 0xE0
Reply-To: skl@wimsey.bc.ca (Samuel Lam)
Date: Tue, 26 Jan 1993 12:19:41 GMT

In article <1993Jan21.203623.7308@nobeltech.se>, ppan@nobeltech.se
 (Per Andersson) wrote:
>I have read RFC1340, which has a list off known DSAPs and SSAPs,
>and 'E0' is not one of them.

It's for Novell's IPX protocol.  Typically used between Novell NetWare
file servers and their PC clients.

...Sam
-- 
<skl@wimsey.bc.ca> -- Connectivity Technology Inc.
Newsgroups: comp.dcom.lans.misc
From: mreese@nyx.cs.du.edu (Mike Reese)
Subject: Re: 2nd RFD: comp.os.nos.lanman
X-Disclaimer: Nyx is a public access Unix system run by the University
	of Denver for the Denver community.  The University has neither
	control over nor responsibility for the opinions of users.
Organization: Nyx, Public Access Unix at U. of Denver Math/CS dept.
Date: Fri, 22 Jan 93 03:19:35 GMT


I think the creation of this newsgroup would be very beneficial.
--
###############################################################################
#  Mike Reese  #  Mail:  mzr@detrick-hsc.army.mil  #  "Make it so!"           #
#  US Army     #  Phone: (301)619-2081             #       --Jean Luc Picard  #
###############################################################################
Newsgroups: comp.dcom.lans.misc
From: birk@zebra.technion.ac.il (Yitzhak (Tsahi) Birk)
Subject: Info on smart hubs (switches)
Organization: TECHNION - Israel Institute of Technology
Date: Wed, 27 Jan 1993 19:27:18 GMT
Keywords: smart hubs, switch, Ethernet, 

I am trying to gather information about products and research prototypes of
"smart hubs", which permit concurrent communication among computers that
have standard LAN adapters (E.g. Ethernet, token ring and FDDI).  These hubs
are actually switches, but appear to the computers as conventional, 
lightly-utilized LANs.

Any info, pointers to vendors, etc. will appreciated.

Yitzhak Birk
birk@ee.technion.ac.il
Newsgroups: comp.dcom.lans.misc
From: gjseo@june.kotel.co.kr (Seo GeunJoo)
Subject: 3C503 card question
Organization: SNU SSLAB.
Date: Mon, 25 Jan 93 07:40:52 GMT


I have a problem with 3-com 503 ethernet cards.

I want to make ethernet bridge with two 3-com 503 cards on IBM PC

,but can't find software which support 3-com 503 card.


Pcbridge v 1.2 support 3c-507 card and wd cards, but does not support 3c-503 card.


please , help me ..



		  THANKS IN ADVANCE ...
From: harvey@indyvax.iupui.edu
Newsgroups: comp.dcom.lans.misc
Subject: Re: 802.2 frames with DSAP 0xE0
Date: 21 Jan 93 22:00:31 -0500
Followup-To: comp.dcom.lans.misc
Organization: Indiana University-Purdue University at Indianapolis

In article <1993Jan21.203623.7308@nobeltech.se>, ppan@nobeltech.se (Per Andersson) writes:
>
> Hi.
>
> I have started to monitor our Token-Ring traffic in addition
> to the ethernet, and in the process I have had start modifying
> tcpdump for recognising 802.2 frames. SNAP-frames seems quite
> easy, but there are some other frames on the net I can`t find
> out what they are. Most of them have a DSAP and SSAP that has
> a value of 'E0'. That is - the first two bytes in the 802.2
> frame are E0E0. I have read RFC1340, which has a list off known
> DSAPs and SSAPs, and 'E0' is not one of them. Anybody able to
> help me ?

These are IPX packets (Novell NetWare).  Check the first two bytes of the
packet data; it will always be FFFF (IPX checksumming disabled).

Novell's new ODI drivers support SNAP encapsulation for IPX.  It's not very
common though (for example, I know Cisco routers don't support it).
--
James Harvey    IUPUI/OIT Technical Support/VMS & Networks
harvey@iupui.edu  uucp:iugate!harvey  bitnet:harvey@indyvax
From: scoggin@delmarva.com (John K. Scoggin, Jr.)
Newsgroups: comp.dcom.lans.misc
Subject: Re: building wiring
Date: 25 Jan 1993 12:53:36 GMT
Organization: Delmarva Power & Light Company
Distribution: world
Reply-To: scoggin@delmarva.com
NNTP-Posting-Host: mercury.delmarva.com

In article 9AF@ra.nrl.navy.mil, atkinson@itd.nrl.navy.mil (Randall Atkinson) writes:
> [ redirected discussion from comp.protocols.tcp-ip :-]
> 
> In article <1993Jan24.231044.16138@xenitec.on.ca> merce@xenitec.on.ca (Jim Mercer) writes:
> 
> >for new buildings, [coax is] dead, except for the possibiliy of backbone 
> >pulls of thick coax to connect wiring centres, but then you might consider 
> >fiber.
> 
>   Actually, I happen to be planning for a 1995 building and we are
> sure that our backbones will be fiber.  However, we expect to continue
> to have a large installed base of workstations that want a thin-net
> Ethernet coax connection and do not plan that twisted pair will be
> enough.
> 
>   The harder question is which kind of fiber to install.  So our
> backbone plans have both single-mode and multi-mode fiber.  The
> distribution within the floors will be decided upon later so we have
> time to figure out what we want.
> 
> >for existing buildings, if you are pulling new cable, pull UTP.  you
> >will probably save some money on media.  you will spend it later in hubs.
> 
>   Actually most of the cost of cabling installation is in the labor,
> so it would be much wiser to put in Shielded Twisted Pair (STP), with
> 2 pair of wires per outlet.  NB: Anything that will run over UTP will
> also run over STP, but the reverse is NOT true.  STP is wisest and
> gives the most flexibility, with little real cost difference from UTP
> when you figure in installation costs.
> 

This is NOT true.  STP has a different impedance than UTP.  We made the mistake
of wiring two large buildings with IBM Type 2 (STP) cable.  We have had problems
running 10BaseT over long (75-100 meters) distances as a result.  Believe me,
there is a BIG difference in cost between UTP and STP if you have to use plenum-
rated cable (Teflon)...

> >2) What options are available for small (less than a dozen nodes) networks
> >currently running coax and wanting to move to 10BaseT?  
> 
>   If really small, then why not just use continue to use what you have
> where you have it, move to STP for new locations and add
> tranceivers/T-joints where there are new drops in existing coax
> locations.
> 



---
+---------------------------------------------------------------------+    
|  John K. Scoggin, Jr.			Email: scoggin@delmarva.com   |
|  Supervisor, Network Operations       Phone: (302) 451-5200         |
|  Delmarva Power & Light Company       Fax:   (302) 451-5321         |
|  500 N. Wakefield Drive               NOC:   (800) 388-7076         |
|  Newark, DE 19714-6066		                              |
|  The opinions expressed are not those of Delmarva Power, simply the |
|  product of an over-active imagination...                           |
+---------------------------------------------------------------------+

Newsgroups: comp.dcom.lans.misc,comp.protocols.misc,comp.sources.wanted,comp.sys.misc
From: peterd@pjd.dev.cdx.mot.com (Peter Desnoyers)
Subject: Re: Multi-drop Serial Protocol Wanted (RS-232)
Organization: Motorola Codex, Canton, Massachusetts
Date: Sun, 24 Jan 1993 03:15:29 GMT

jdc@isis.cs.wayne.edu (Jon Cardwell) writes:
+---------------
| We're looking for sources or references for a "multi-drop serial protocol"
| i.e. one that allows multiple devices to be attached to the same serial line.
| Our goal is to have data exchanged between a host cpu and any number of
| ( well ok, 8 :) attached slave devices. ... Any help (even remote references
| from 15 years ago) would be most welcome.
+---------------

If you can run sync instead of async and you're willing to do some
coding, Localtalk would be a good protocol for this sort of thing -
it's fast (in comparison to async), it only needs an 8530 and some
simple driver hardware, and you can take advantage of an existing base
of machines that talk it.

If you need to do async (e.g. your host only has async ports) then any
poll-response protocol would do - you just need to ensure that each
poll has an address in it, and require that slave devices only
transmit in response to a poll.

				Peter Desnoyers
-- 
Xref: sparky comp.dcom.lans.misc:1139 comp.dcom.lans.ethernet:3063
From: harvey@indyvax.iupui.edu
Newsgroups: comp.dcom.lans.misc,comp.dcom.lans.ethernet
Subject: Re: Clarkson 11.x drivers
Date: 22 Jan 93 16:35:05 -0500
Distribution: na
Organization: Indiana University-Purdue University at Indianapolis

In article <1993Jan22.201508.1@stimpy.enet.dec.com>, quodling@stimpy.enet.dec.com writes:
> In article <1993Jan19.232708.9907@asns.tredydev.Unisys.COM>, mkain@asns.tredydev.unisys.com (Mike Kain) writes:
>> Questions:  Are the Clarkson 11.x drivers available yet?  I have a device
>> driver for an Exos 205, and I need one for an exos 105-t.  I've heard that
>> it is in the 11 version (and the two obviously aren't compatible).
>>
>
> Or for that matter, Clarkson drivers with 3C509 support?

Russell Nelson recently posted the following article in comp.protocols.tcp-ip.

Please note that Clarkson University no longer has anything to do with the
packet drivers that were formerly called the "Clarkson collection of packet
drivers."  As I recall, this has been the case since version 10.  Russell's
company Crynwr Software (that's creh-NOOR) maintains the collection and sells
support for them.

>X-NEWS: ivax comp.protocols.tcp-ip: 1225
>Relay-Version: VMS News - V6.0-3 14/03/90 VAX/VMS V5.5; site indyvax.iupui.edu
>Path: indyvax.iupui.edu!usenet.ucs.indiana.edu!sol.ctr.columbia.edu!zaphod.mps.ohio-state.edu!cs.utexas.edu!sun-barr!olivea!uunet!psinntp!crynwr!nelson
>Newsgroups: comp.protocols.tcp-ip
>Subject: 3C509 pkt. drivers ?
>Message-ID: <727586398snx@crynwr.com>
>From: nelson@crynwr.com (Russell Nelson)
>Date: 21 Jan 93 03:19:58 GMT
>References: <20JAN93.17562179@skyfox>
>Organization: Crynwr Software
>Lines: 14
>
>In article <20JAN93.17562179@skyfox> keele@skyfox writes:
>
>   Does anyone know if there are packet drivers around for the new
>   3C509 Etherlink III cards ? I have not seen them in the usual
>   DRIVERS.ZIP file.
>
>They're in beta test, but you're welcome to try using it.  No guarantees,
>of course.  It's ftp.msen.com:pub/vendor/crynwr/3c509g.zip.  Please tell
>me if it doesn't work for you.
>
>-russ <nelson@crynwr.com> What canst *thou* say?
>Crynwr Software           Crynwr Software sells packet driver support.
>11 Grant St.              315-268-1925 Voice  |  LPF member - ask me about
>Potsdam, NY 13676         315-268-9201 FAX    |  the harm software patents do.
--
James Harvey    IUPUI/OIT Technical Support/VMS & Networks
harvey@iupui.edu  uucp:iugate!harvey  bitnet:harvey@indyvax
Newsgroups: comp.dcom.lans.misc,comp.protocols.misc,comp.sources.wanted,comp.sys.misc
From: bill@texan.rosemount.com (William Hawkins)
Subject: Re: Multi-drop Serial Protocol Wanted (RS-232)
Organization: Rosemount, Inc. Mpls, MN
Date: Sun, 24 Jan 1993 18:14:33 GMT

>jdc@isis.cs.wayne.edu (Jon Cardwell) writes:
>+---------------
>| We're looking for sources or references for a "multi-drop serial protocol"
>| i.e. one that allows multiple devices to be attached to the same serial line.

RS-232 is not a multi-drop protocol *electrically* because it holds
the line at the mark (or space) state.  You need the RS-485 protocol
to multi-drop devices, because it lets the line float if a device
has nothing to say.  There are 232 to 485 converters available (or
there were 7 years ago).  Then you can implement a master-slave
software protocol for the universe of devices attached to the line.

In ISO terms, RS-232/485 is barely a physical layer specification.
You get to do anything you want with the rest of the layers.

Bill Hawkins
Xref: sparky comp.dcom.lans.misc:1133 comp.protocols.ibm:890 comp.protocols.misc:957
From: ppan@nobeltech.se (Per Andersson)
Newsgroups: comp.dcom.lans.misc,comp.protocols.ibm,comp.protocols.misc
Subject: 802.2 frames with DSAP 0xE0
Date: 21 Jan 93 20:36:23 GMT
Followup-To: comp.dcom.lans.misc
Organization: NobelTech AB


Hi.

I have started to monitor our Token-Ring traffic in addition
to the ethernet, and in the process I have had start modifying
tcpdump for recognising 802.2 frames. SNAP-frames seems quite
easy, but there are some other frames on the net I can`t find
out what they are. Most of them have a DSAP and SSAP that has
a value of 'E0'. That is - the first two bytes in the 802.2
frame are E0E0. I have read RFC1340, which has a list off known
DSAPs and SSAPs, and 'E0' is not one of them. Anybody able to
help me ?

/Per
-- 
-----------------------------------------------------------------------------
Per Andersson - ppan@nobeltech.se (perand@stacken.kth.se on free time)
Managing networks at, but not speaking for Nobeltech AB, J{rf{lla, Sweden
-----------------------------------------------------------------------------
Newsgroups: comp.dcom.lans.fddi
From: dmadsen@stpaul.ncr.com (Dan Madsen)
Subject: Conectors
Summary: What is the relation between MCI and ST connectors?
Keywords: FDDI MCI ST
Organization: Internetworking
Date: Tue, 26 Jan 1993 18:51:14 GMT

I would like to set up a small network using NPI's FDDI adapter.  Their 
literature indicates they use a media interface connector (MIC).  My Anixter 
catalog lists ST I, ST II, SMA, and miniMNC connectors.  Are any of the 
types listed by Anixter equivalent to MIC?

Thanks.
Dan Madsen Att/NCR Network Hardware Development
dan.madsen@stpaul.ncr.com
From: marc@piglet.uni-paderborn.de (Marc Gumbold)
Newsgroups: comp.dcom.lans.fddi
Subject: 2 questions (SMT status?, SMF specs?)
Date: 23 Jan 1993 16:02:47 +0100
Organization: Universitaet Paderborn, Germany
NNTP-Posting-Host: piglet.uni-paderborn.de

Hi folks,

sorry to steal you some of your precious news reading cycles again,
but whom should I ask else? 

First question: What is the precise status of SMT?  

	(Mike Yip wrote in this group on December 3, citing an ANSI 
	mailing, that "X3 Public Review ends 1/93". What is going to 
	happen next? When will the standard be published?)

Second question: What are the exact specifications (max. fiber length,
max. link length, max. # of links, max. # of stations) of the SMF-PMD?

	(When reading about it, e.g. both 60 and 100 km are mentioned as
	max. link length values. What should I believe?)


Thanks for any answer,
Marc

-- 
  Marc Gumbold                                       Universitaet-GH Paderborn
  Email: marc@hni.uni-paderborn.de                   Heinz Nixdorf Institut
  Phone: +49 5251 60 3382                            Pohlweg 47-49
  Fax:   +49 5251 60 3426                            W-4790 Paderborn, Germany
Xref: sparky comp.dcom.lans.fddi:921 comp.dcom.lans.ethernet:3081
From: jessea@u013.me.vp.com (Jesse W. Asher)
Newsgroups: comp.dcom.lans.fddi,comp.dcom.lans.ethernet
Subject: SDDI (FDDI over twisted pair)?
Date: 24 Jan 93 21:31:57 GMT
Organization: Varco-Pruden Buildings

I'm interested in hearing the latest with regard to SDDI - FDDI over twisted
pair.  We have quite a bit of twisted pair installed and would like to
retain all of it, but we may need to upgrade from 10baseT to something like
SDDI.  What's the status of SDDI as far as a specification is concerned? 
Does it exist, and if so are there any products out for it?  I'd like to
look into getting a SDDI hub, if possible.  Thanks.

-- 
      Jesse W. Asher                                          (901)762-6000
                             Varco-Pruden Buildings
                 6000 Poplar Ave., Suite 400, Memphis, TN  38119
    Internet: jessea@vpbuild.vp.com                   UUCP: vpbuild!jessea