🚀 go-pugleaf

In article <1992Jul20.081403.1@ptavv.llnl.gov> oberman@ptavv.llnl.gov writes:
>In article <1992Jul17.190752.21847@midway.uchicago.edu>, chris@gargoyle.uchicago.edu (Chris Johnston) writes:
>> 
>> I always turn SQE/Heartbeat OFF for every transceiver.  
>
>This sort of thing really frustrates me.
>SQE IS THERE FOR A REASON! TURNING IT OFF IS ASKING FOR TROUBLE!
> [several paragraphs deleted]
>
>R. Kevin Oberman			Lawrence Livermore National Laboratory
>Internet: koberman@llnl.gov		(510) 422-6955

802.3 standard lawyers not withstanding, using the same signal to
indicate both "Collision" and "Transceiver OK" is a MAJOR DESIGN FLAW.

I'm still waiting for someone to tell me exactly why turning SQE off
on every transceiver is a bad idea...  I am relieved to learn that
most, if not all, software/firmware ignores SQE even when it is
enabled.  

For now SQE stays disabled on my net.  The risk of losing one computer
is trivial compared to the risk of losing the entire network.  (I'm
always open to and invite arguements against this policy.)

IMPORTANT: Remember, the standard does say turn off SQE/Heartbeat/Jam
when connecting a transceiver to a repeater or hub.  If you forget
this your throughput will be very poor.

cj

Chris Johnston AM Investors work312-786-4889 home312-761-0091

If you are "humor challenged" please ignore the following.
Standards?  We don't need no stinking standards.
...and remember, please don't try this at home I'm a professional. :-)