On 4/23/21 7:45 PM, karl@aspodata.se wrote:
> Grant:
I think you are conflating me for the OP. Easy to do with the same
first name. ;-)
> In that case, your usb-connection (or anything) will probably be a
> borderline case to, since that is also a network... But I guess the
> thing fobidden is anything makeing the ms-win box recognize and use
> somthing to communicate outwards.
I agree and that such is a possibility and is something that Grant
/Edwards/ -- the OP -- will need to make a judgement call on.
> Don't know much about the windows side, but I found this:
> https://stackoverflow.com/questions/766912/raw-ethernet-frames-using-winsock
> https://www.winpcap.org/
> https://hacked10bits.blogspot.com/2011/12/sending-raw-ethernet-frames-in-6-easy.html
> seems to be some programming involved.
That's about what I had expected. Not many, if any, ready built tools
for transferring raw Ethernet frames. Though plenty of scaffolding to
create it.
> Seems it never was, though there were patches:
> https://flylib.com/books/en/3.151.1.29/1/
That's about what I remember.
> 4.18-rc1 it seems.
Thank you for finding and sharing that milestone.
Aside: I don't like using "milestone" to describe the point that was
removed. Particularly something I think is good.
> Ah, forgot that one.
;-)
> About the original question. Here what a few thing I dig up.
>
> https://www.amazon.com/Laplink-High-Speed-Transfer-Cable-PCmover/dp/B0093H83DW
This is the USB version of the Laplink cable concept.
Decidedly different than the old serial & parallel versions of which
I've used many times. LapLink, INTERLNK.EXE & INTERSVR.EXE, and '95's
Direct Cable Connection used them. I suspect there may have been more
that I'm not aware of.
> https://sourceforge.net/projects/lptransfer/
Interesting.
I'm not sure why a separate program was needed. Maybe it didn't
monopolize the server side the same way that INTERSVR.EXE did.
Because INTERLNK.EXE would map a drive to the server and return control
to the command prompt / batch script allowing use of the new drive letter.
> https://github.com/viveris/uMTP-Responder
Interesting.
This is most likely to be the lease problematic considering that it
turns the Linux end into a /special/ USB flash drive.
> It is usually simple to setup and use a serial null-modem cable and
> run kermit or somthing on the MS-Win side and add a getty (I've used
> mgetty) handling the serial port on the linux side.
Is it wrong that the first thing that came to mind when reading the OP's
post is UUCP with as high speed serial as possible?
I wonder if the USB LapLink (type) cable or USB On The Go gadget cables
could present as a multi-megabit serial interface.
--
Grant. . . .
unix || die