I've been doing some testing on a project that has involved thrashing the ports a bit, starting and stopping apps with debuggers etc, and managed to get the system into a strange state. Thought I should report this in case it points to bug, although I guess (from an app dev's view) it could well just be windows…
What my app does is run 2 handles for overlapped read/write on a com0com port. That normally works fine, and the overlapped reads hang and timeout as you'd expect. But what I was seeing was the reads would immediately return with 0 bytes and not wait for data to be present. I ran through this with the debugger and verified that was happening. I shut the ports and restarted the apps and the behaviour was persistent. Rebooting Windows XP sorted it and everything behaved properly again.
Otherwise, it's a going great.
Cheers
Terry
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've been doing some testing on a project that has involved thrashing the ports a bit, starting and stopping apps with debuggers etc, and managed to get the system into a strange state. Thought I should report this in case it points to bug, although I guess (from an app dev's view) it could well just be windows…
What my app does is run 2 handles for overlapped read/write on a com0com port. That normally works fine, and the overlapped reads hang and timeout as you'd expect. But what I was seeing was the reads would immediately return with 0 bytes and not wait for data to be present. I ran through this with the debugger and verified that was happening. I shut the ports and restarted the apps and the behaviour was persistent. Rebooting Windows XP sorted it and everything behaved properly again.
Otherwise, it's a going great.
Cheers
Terry