home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   alt.comp.os.windows-xp      Actually wasn't too bad for a M$-OS      17,273 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 16,617 of 17,273   
   R.Wieser to All   
   Re: How to get all possible baudrates fo   
   11 Oct 23 17:31:25   
   
   From: address@is.invalid   
      
   JJ,   
      
   > It's not a coincidence. It's based on experience.   
      
   I would have liked to have read that.   
      
   Pardon me, but I've had to many people tell me stuff as if they where facts,   
   only to later discover that their "facts" where conjured outof thin air (had   
   no basis).   Documentation still trumps experience, but I will take the   
   latter as a strong signal (probably won't stop me from what I already did to   
   verify it though... :-) )   
      
   > Try getting a different USB-to-serial device. There's a high chance   
   > that the case would be the same.   
      
   Seeing that I cannot find any IOCTL_SERIAL_* which will do it, and the   
   CP210x  0x222??? IoControl codes can mean something quite different for   
   another device (if they than mean anything at all to begin with) I cannot   
   other than agree with your "high chance" there.   
      
   Alas, it means that I can't create an up-to-the-times serial connection   
   configuration dialog (making it easy to select fast baudrate *that will be   
   accepted* by the targetted serial device). :-\   
      
   > It roughly means: user specified. IOTW: any.   
   >   
   > But no device has no limit. It has to have a limit. At least for   
   > this specific case. Thus it means: unspecified. IOTW: unknown.   
      
   Not specifying would be easy, just don't set any bitflag (leave the field   
   0x0).   
      
   But now it *is* specified, though neither of us can figure out *what* is   
   specified.  If we assume its indicating BAUD_USER its, in the "maximum   
   accepted baudrate" context, absolutily meaningless. :-\   
      
   > There's no guarantee that a device provides the information via   
   > vendor-specific method.   
      
   The IOCTL_SERIAL_GET_PROPERTIES request isn't what I would call "vendor   
   specific" ...   
      
   The problem with the returned dwMaxBaud field is that not even the MS   
   documentation says anything about that 0x10000000 (BAUD_USER ?) value, let   
   alone usefull to it.  :-\   
      
   Regards,   
   Rudy Wieser   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca