Unsupported settings do not SetLastError() under Windows (XP?)
hparra opened this issue · comments
from asquared: "In other news, Windows (XP at least) is brain dead. From the looks of things, if you pass a baud rate or other DCB settings which happen to be unsupported by the hardware, SetCommState returns zero but doesn't SetLastError( ) in the process. This in turn causes the Ruby interpreter to crash..."
The same exact behavior needs to be confirmed for Vista/7. I would like to confirm whose fault this is (OS? Ruby?)