| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | DosRead blocking |
-=> Quoting Phil Crown to James R. Cook <=-
PC> I think you need to reset it, p.exe does not seem to reset the com
PC> port to its previous state.
Okie. I'll make it a point to save the state of the port before I fiddle
with it. Say, in your opinion, is it more efficient to buffer the comm
port with a thread in the program, or not to worry with it. I've been
turning that one around in my head for a couple of days and I can't see
where the overhead would be worth it ...
PC> This is how I found what I believe is a bug in SIO's SU.EXE program.
PC> Running "su mode" will not report values
higher than 255 for
PC> the usWrite/usReadTimeout values, though they are defined as USHORT in
PC> the DCBINFO structure, and I can set/query them as values higher than
PC> 255 in my own app.
Interesting. You let Ray Gwinn know?
={) James (}=
... A jury -- twelve persons chosen to decide who has the better lawyer.
--- Blue Wave/DOS v2.30
* Origin: COMM Port OS/2 juge.com 204.89.247.1 (281) 980-9671 (1:106/2000)SEEN-BY: 50/99 54/99 270/101 620/243 625/0 160 640/201 711/409 410 413 430 SEEN-BY: 711/808 809 934 955 712/311 407 505 506 517 623 624 704 841 713/317 SEEN-BY: 800/1 @PATH: 106/2000 396/1 270/101 712/624 711/808 934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.