1 |
On 4/23/21 7:45 PM, karl@××××××××.se wrote: |
2 |
> Grant: |
3 |
|
4 |
I think you are conflating me for the OP. Easy to do with the same |
5 |
first name. ;-) |
6 |
|
7 |
> In that case, your usb-connection (or anything) will probably be a |
8 |
> borderline case to, since that is also a network... But I guess the |
9 |
> thing fobidden is anything makeing the ms-win box recognize and use |
10 |
> somthing to communicate outwards. |
11 |
|
12 |
I agree and that such is a possibility and is something that Grant |
13 |
/Edwards/ -- the OP -- will need to make a judgement call on. |
14 |
|
15 |
> Don't know much about the windows side, but I found this: |
16 |
> https://stackoverflow.com/questions/766912/raw-ethernet-frames-using-winsock |
17 |
> https://www.winpcap.org/ |
18 |
> https://hacked10bits.blogspot.com/2011/12/sending-raw-ethernet-frames-in-6-easy.html |
19 |
> seems to be some programming involved. |
20 |
|
21 |
That's about what I had expected. Not many, if any, ready built tools |
22 |
for transferring raw Ethernet frames. Though plenty of scaffolding to |
23 |
create it. |
24 |
|
25 |
> Seems it never was, though there were patches: |
26 |
> https://flylib.com/books/en/3.151.1.29/1/ |
27 |
|
28 |
That's about what I remember. |
29 |
|
30 |
> 4.18-rc1 it seems. |
31 |
|
32 |
Thank you for finding and sharing that milestone. |
33 |
|
34 |
Aside: I don't like using "milestone" to describe the point that was |
35 |
removed. Particularly something I think is good. |
36 |
|
37 |
> Ah, forgot that one. |
38 |
|
39 |
;-) |
40 |
|
41 |
> About the original question. Here what a few thing I dig up. |
42 |
> |
43 |
> https://www.amazon.com/Laplink-High-Speed-Transfer-Cable-PCmover/dp/B0093H83DW |
44 |
|
45 |
This is the USB version of the Laplink cable concept. |
46 |
|
47 |
Decidedly different than the old serial & parallel versions of which |
48 |
I've used many times. LapLink, INTERLNK.EXE & INTERSVR.EXE, and '95's |
49 |
Direct Cable Connection used them. I suspect there may have been more |
50 |
that I'm not aware of. |
51 |
|
52 |
> https://sourceforge.net/projects/lptransfer/ |
53 |
|
54 |
Interesting. |
55 |
|
56 |
I'm not sure why a separate program was needed. Maybe it didn't |
57 |
monopolize the server side the same way that INTERSVR.EXE did. |
58 |
|
59 |
Because INTERLNK.EXE would map a drive to the server and return control |
60 |
to the command prompt / batch script allowing use of the new drive letter. |
61 |
|
62 |
> https://github.com/viveris/uMTP-Responder |
63 |
|
64 |
Interesting. |
65 |
|
66 |
This is most likely to be the lease problematic considering that it |
67 |
turns the Linux end into a /special/ USB flash drive. |
68 |
|
69 |
> It is usually simple to setup and use a serial null-modem cable and |
70 |
> run kermit or somthing on the MS-Win side and add a getty (I've used |
71 |
> mgetty) handling the serial port on the linux side. |
72 |
|
73 |
Is it wrong that the first thing that came to mind when reading the OP's |
74 |
post is UUCP with as high speed serial as possible? |
75 |
|
76 |
I wonder if the USB LapLink (type) cable or USB On The Go gadget cables |
77 |
could present as a multi-megabit serial interface. |
78 |
|
79 |
|
80 |
|
81 |
-- |
82 |
Grant. . . . |
83 |
unix || die |