http://bugs.winehq.org/show_bug.cgi?id=11811
--- Comment #34 from RBEmerson n5470@pinefields.com 2008-03-20 08:12:46 --- A few thoughts on the COM port issue...
First, the Keyspan driver is bundled with most Linux distros (but not all, Ubuntu and Debian do not include it because of, I think, GPL issues). Put another way, this is not a driver or module I added to my initial system installation, it's a default item.
Second, in testing the application just now, the error messages didn't show up at all. I selected a number of different rates up to 38400 and down to 110 (hint: very much not recommended for the CPU-bound!). Without a terminal to watch the serial output, it's dangerous to assume the data was sent properly. However, the status light on the converter changed its blink rate consistent with moving from 4800 to 38400 and down from 4800 to 300 and 110. More importantly, the gripes about get and set serial rates didn't show up.
Third, further testing shows that the message is related to the automatic port detection process. The problem arises when testing COM3 (a legacy of the native SERIALCOMM keys). Since COM3 is a "nonsense" port (not tied to any existing hardware), the error message is, in fact, appropriate (i.e., COM3 won't allow a get or set rate because it's not really there). Removing COM3 from the SERIALCOMM key and doing an autodetect shows the problem is fixed: no (bogus) port, no error message.
Finally, it appears that "all" that's needed to support the creation of the needed transient COM port entries in SERIALCOMM and this bug can be closed out.