Talk:LapLink cable

message: 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‎
: With a LabLink cable the connection between two PCs was faster than via a Nullmodem-cable because it used the faster Parallel Port and it was easily affordable for every PC owner, because every PC had a built in Parallel Port interface and no other hardware was required, except the cable itself. Compared to real 10 MBit/s BNC based Ethernet cards it was also a cheap and affordable solution, to connect two PCs at that time. Real Network cards were rather expensive at that time and it was required to buy them additional to the PC, so they were very uncommon in private usage at that time. --109.192.197.21 (talk) 00:08, 3 April 2015 (UTC)
thread_title: Benefits

message: 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)
replies: text: I agree. --109.192.197.21 (talk) 00:08, 3 April 2015 (UTC)
thread_title:  Information to add to the article 

message: 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)
replies: text: No, it might be a generic crossover cable for the parallel port, but as its time, it was known as LapLink cable and if you wanted to transfer Data between two PCs over the Parallel Port, you asked for a LapLink cable. --109.192.197.21 (talk) 23:58, 2 April 2015 (UTC)

text: It's an interesting snippet of PC history, remembering which just brought me here today. DFH (talk) 17:17, 3 October 2016 (UTC)
thread_title:  Commercial 

message: 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)
replies: text: No, not at all. That is software that can use a USB adhoc networking cable, or a null-modem cable. And it can do remote desktop takeover in its later versions. The laplink cable itself was used by non-Laplink software as well. The software is notable, and should be able to be built out. The cable is notable separately, because of its use by other non-laplink software. -- 70.31.205.108 (talk) 06:53, 16 January 2021 (UTC)
thread_title:  Change the Laplink stub to a redirect? 

message: 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)
thread_title:  Pin 17 citation needed