I guess this is more a question than an issue, but anyway: when I move an USB 3.0 (a normal 128gb pen drive for example) to USBIP, it works perfect and I can access it's content, it appears in the file system as a drive and everything perfect.
But, in terms of connections, it's not located in any COM port. And that's a problem for some softwares that exclusively look at COM ports (or physical ports, let's say), instead of virtual ports (vhci ports). Is there any way to make that pen drive appear as a COM1 port in Windows 10? Like, is that an available feature of usbip-win?
That being said, how does attach -s works? I don't see that anywhere in any doc or readme or any blog, it just says "overwrite serial number"... I'm not sure if that's related to my issue (seeing the usbip pen drive as a COM port).
Hope somebody can help me :)
If it's not related to the project, then my apologies and I'll try to look somewhere else... (if you can suggest me any way to achieve that, i'll be thankful)
I guess this is more a question than an issue, but anyway: when I move an USB 3.0 (a normal 128gb pen drive for example) to USBIP, it works perfect and I can access it's content, it appears in the file system as a drive and everything perfect. But, in terms of connections, it's not located in any COM port. And that's a problem for some softwares that exclusively look at COM ports (or physical ports, let's say), instead of virtual ports (vhci ports). Is there any way to make that pen drive appear as a COM1 port in Windows 10? Like, is that an available feature of usbip-win? That being said, how does attach -s works? I don't see that anywhere in any doc or readme or any blog, it just says "overwrite serial number"... I'm not sure if that's related to my issue (seeing the usbip pen drive as a COM port). Hope somebody can help me :) If it's not related to the project, then my apologies and I'll try to look somewhere else... (if you can suggest me any way to achieve that, i'll be thankful)