Crash when NI hardware in use is disconnected.

[N3Roaster]

No description provided.

[N3Roaster]

In the long term the way this gets fixed is to move communications with this hardware out of process and while trying to avoid the communications process crashing cope with the situation if it does. This approach may be required as NI DAQmx Base cannot be linked at runtime with a 64 bit binary on Mac OS X and it's only going to get harder to keep making 32 bit builds of Typica and its dependencies. There is a branch that attempts to solve this in process, but it is not yet clear how successful that work will be.

[N3Roaster]

I had a branch where I was working on this problem without resorting to separating the code out of Typica's process, but I haven't been able to get to the bottom of some segmentation faults that are happening on the NI side of things. I may need to resign myself to the prospect of whatever process handles communication with this hardware crashing, in which case the most sensible thing to do is get that code out of Typica and into an external process that Typica can restart when needed. Unfortunately, I do not believe that I will be able to get that done before the release of Typica 1.7.