|
|
Post by Leif Bloomquist on Aug 6, 2004 10:27:31 GMT -5
No, 110 does not work. It gives garbage. Must be 150. OK, thanks for checking. Maybe we should focus on Modem Wars for now. Anyway, Tomorrow's out for testing as it's the Toronto Beer Festival ;D, followed by a friend's birthday party. How does Sunday afternoon/evening work? |
|
|
|
Post by Jim Brain on Aug 6, 2004 12:56:35 GMT -5
Sunday afternoon/evening looks fine.
Jim
|
|
|
|
Post by Leif Bloomquist on Aug 9, 2004 7:19:29 GMT -5
No, 110 does not work. It gives garbage. Must be 150. OK, I was looking into this a bit more. In the Control Panel, under Hardware/Device Manager (that's for Win2K) you can change the default COM Port settings. There is an option for 150 baud. Does changing this help? I've also been able to type between two Windows 2000 computers connected by a Null modem cable @ 150 baud, using Comtest ( www.bb-elec.com/comtest.asp ) So 150 baud does fundamentally work, it's just not supported by HyperTerminal. |
|
|
|
Post by Jeff Ledger on Aug 9, 2004 8:27:31 GMT -5
OK, I was looking into this a bit more. In the Control Panel, under Hardware/Device Manager (that's for Win2K) you can change the default COM Port settings. There is an option for 150 baud. Does changing this help? Windows XP also lists 150 as well as: 134 110 75 I've never heard of anyone using 134 or 75! Jeff |
|
|
|
Post by Leif Bloomquist on Aug 12, 2004 3:20:46 GMT -5
Windows XP also lists 150 as well as: OK, I now have a VB program that sends/receives at 150 baud. It's soooooo slow!  Jim, the key is the SetCommState() Win32 API call, located in kernel32.dll. Once everything else is set up, read the existing state with GetCommState() , change ComDcb.BaudRate to your desired baud, and then call SetCommState(). This would mean a divergence from the Linux code, maybe an #IFDEF would allow a compromise. |
|
