More info -
Same issue with a different machine, running Win2K.
We are using an rs-232 to rs-422 converter that is powered by the DTR line. To enable the DTR, I use the call
ComSetEscape (Comport, SETDTR);
So if this call were to fail, no communications would take place, because the converter wouldn't be powered up. Everything would look fine from the rs-232 perspective.
Does anyone know what the standard Windows serial driver is doing in re buffering decisions? At one point, the CVI help said that WinNT always allocated a minimum of 4095 bytes. NI has never stated, to my knowledge, what the effective maximum size is for input or output queues.
Does anyone know what the NI serial driver does in this case? We have many NI serial cards, can I get deterministic, documented behavior if I use an NI serial card and the NI serial driver?
Thanks,
Menchar