ibstop() doesn't abort ibrda() under Windows 98?

[ndiamond]

Is there a known problem in which a call to ibstop() doesn't abort a call to ibrda() in a non-controller under Windows 98?

If I make the controller send another byte to the non-controller then ibrda() completes normally and then ibstop() completes normally. But if I don't add that unwanted operation to the controller, then the non-controller seems to hang in both ibrda() and ibstop().

The timeout of 10 seconds also comes and goes with no effect on the hang. In fact if I make the controller send that extra unwanted byte after more than 10 seconds of hang then ibrda() and ibstop() both complete normally instead of reporting a timeout.

[ndiamond]

I will post a corrected version of this question, so please ignore this one. The correction is to my last paragraph, in which I forgot which timeout settings I had in some experiments.

Since this web interface doesn't allow posting a correction to my own question, I am "answering" this one and posting a new question separately. Sorry for the inconvenience.

[ndiamond]

Hmm, this web interface doesn't even let me give my "answer" a 1-star rating 🙂