Driver hanging and eventually failing with empty read buffer

Hi Mike,

The reason I suggested trying 4.0 is because there was a low level reworking of the code that reads from the network stream for 4.1.1. Using 4.0 would help to identify/eliminate that as the culprit, and potentially get you up and running with a newer version of the driver without the need for your console app.

I've added this to my to do list and will investigate more thoroughly, once a couple of high priority items are out of the way.

Thanks
Andy