![]() | This redirect does not require a rating on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||
|
discuss the benefit of dcc in building small networks and where we can decide to use it and where should not use — Preceding unsigned comment added by 84.11.131.222 ( talk • contribs) 16:56, 18 January 2008
This may be a stub now and need supporting documentation, but I found this information to be useful and the writing to be clear. So, please keep this Wikipedia entry, and (hopefully) someone with more knowledge about this subject will expand. -- Blumrosen ( talk) 20:50, 27 November 2011 (UTC)
What data rate is achieved? Which wire carries a clock signal? How many data bits are sent on each clock cycle? Which wires carry data? DriveByWire ( talk) 18:10, 21 June 2012 (UTC)
This article is a veiled advertisement for laplink.
Come on.
There is nothing notable about a "laplink" cable -- it's just a generic crossover cable.
This article is bullshit. — Preceding unsigned comment added by 68.183.100.27 ( talk) 15:32, 4 October 2013 (UTC)
There's still a stub for Laplink. It would make sense to change this to just redirect to this page. DFH ( talk) 17:15, 3 October 2016 (UTC)
This page is the only one which mentions 17(Select in) to be connected to 19 on the other side. 19 is normally an extra ground, common with 18‥24 and probably 25, the mandatory ground, and not connected with shielding. From the description, it is unclear whether 19 here is supposed to be common ground or just pin-to-pin.
However, it’s very improbable that 17 should be connected to 19. All other reference materials mandate a 17-17 straight-through (e.g. Linux, Crynwr) or suggest it to be not connected (FreeBSD). Recent NetBSD tests indicate 17-17 may be necessary to communicate with at the very least Linux. mirabilos ( talk) 22:11, 25 March 2023 (UTC)
![]() | This redirect does not require a rating on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||
|
discuss the benefit of dcc in building small networks and where we can decide to use it and where should not use — Preceding unsigned comment added by 84.11.131.222 ( talk • contribs) 16:56, 18 January 2008
This may be a stub now and need supporting documentation, but I found this information to be useful and the writing to be clear. So, please keep this Wikipedia entry, and (hopefully) someone with more knowledge about this subject will expand. -- Blumrosen ( talk) 20:50, 27 November 2011 (UTC)
What data rate is achieved? Which wire carries a clock signal? How many data bits are sent on each clock cycle? Which wires carry data? DriveByWire ( talk) 18:10, 21 June 2012 (UTC)
This article is a veiled advertisement for laplink.
Come on.
There is nothing notable about a "laplink" cable -- it's just a generic crossover cable.
This article is bullshit. — Preceding unsigned comment added by 68.183.100.27 ( talk) 15:32, 4 October 2013 (UTC)
There's still a stub for Laplink. It would make sense to change this to just redirect to this page. DFH ( talk) 17:15, 3 October 2016 (UTC)
This page is the only one which mentions 17(Select in) to be connected to 19 on the other side. 19 is normally an extra ground, common with 18‥24 and probably 25, the mandatory ground, and not connected with shielding. From the description, it is unclear whether 19 here is supposed to be common ground or just pin-to-pin.
However, it’s very improbable that 17 should be connected to 19. All other reference materials mandate a 17-17 straight-through (e.g. Linux, Crynwr) or suggest it to be not connected (FreeBSD). Recent NetBSD tests indicate 17-17 may be necessary to communicate with at the very least Linux. mirabilos ( talk) 22:11, 25 March 2023 (UTC)