| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | RXASYNC - Serial I/O |
Ian Timms wrote in a message to Jerry McBride: IT> G'day Jerry, Salutations! IT> Got your messages okay but we've been having the odd hiccup IT> down here so I don't know how long the turnaround is, I even IT> tried netmailing back to you but have no idea whether it got IT> through. Thanks for the atempt, it never made it, however... IT> Please accept my appologies for any intervening outbursts. IT> ;-) Why? I enjoy an occasional rub... IT> As to readwrite_denynone, if the calling program doesn't open IT> the port in such a way that 'called' programs can use the IT> handle then there is little point in providing the handle in IT> the first place. OS/2 just spits the dummy and causes the IT> child program to error if it attempts to write or read from the IT> port when it is not allowed to do so. Perhaps this is what my bbs does, MAXIMUS. I have tried to use the passed handle with rxasync (with out calling rxasyncopen) and it failed to work. However, I can call rxasyncopen and tell it what portname that the bbs is on and it'll all work just fine. The only thing is, I have to pass portname (com1, etc...) with the call. Ian, would it be possible to add in another function? One that would take a hot porthandle passed from the bbs and just start using it? Jerry McBride --- timEd/2 1.01+* Origin: MoDem_Corner_609-877-0836_EdgeWater_Park_NJ_USA_V.34 (1:266/28) SEEN-BY: 105/42 620/243 624/50 711/401 409 410 413 430 807 808 809 934 955 SEEN-BY: 712/407 515 628 704 713/888 800/1 7877/2809 @PATH: 266/28 400 100 505 3615/50 396/1 270/101 105/103 42 712/515 711/808 @PATH: 711/809 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™.