Yes, my son owns the server so he set that up.
Use the Windows drivers for your stick, which produces a serial COM port. You can then map that port to your VM, assuming the driver baud rate, etc. are configured correctly. I am using a Debian VM currently.
I was with you right up to:
How would you go about mapping that port? The stick shows up in Device Manager as Ports (COM & LPT) > UZB (COM4). I don’t see anything in Hyper-V manager that lets me map a com port to a VM.
Everything I’ve googled on the subject is very discouraging, and implies it just can’t be done. If you and your son are doing it, I’d appreciate some more detail.
I understand what a named pipe is conceptually, but it’s not something I’ve ever messed with. I found this: GitHub - tdhoward/COMpipe: Links a serial COM port to a named pipe but not sure if that is the right way to approach this.
Thanks!
I found this. Does it help?