Ignore the USB aspect of the connection. At either end of the USB link you are simply dealing with an RS232 serial port - everything else should be taken care of 'under the hood'. That said, the 'under the hood' stuff is tricky and it may be that you have been bitten by a bad implementation.
More likely however: "invalid COMMPROP block length" sounds like a Windows API related error (COMMPROP is a structure used by the serial port API calls). It may be that the API has moved on since Win32::SerialPort was last worked on and dodgy stuff that used to work now fails on newer versions of Windows. You could use Win32::API and effectively reinvent the Win32API::CommPort wheel, or you could try to track down the bug in Win32API::CommPort / Win32::SerialPort. Unless you are somewhat familiar with the Win32 API either option is likely to entail something of a steep learning curve. Otherwise, I suspect you are a bit stuffed!
In reply to Re: Connecting to a USB Serial Device on Windows
by GrandFather
in thread Connecting to a USB Serial Device on Windows
by slloyd
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |