Thanks for the info Shaun and asbo. I'll try to track it down later when I have more time or get tired of dealing with it.
Can you still browse to the variables when you select the SV nodes?
Yep, I can still browse to the correct variables.
I presume it is the whole project that you are taking over as is.
Erm... sort of. The customer wanted a quick-and-dirty app to test and characterize a system they're building. I don't have much experience (or infrastructure code) with cRIO so I copied an existing project and heavily modified it. But yes, the entire project was copied to another pc using a usb stick.
It would be interesting to know whether the two errors could be linked.
Given the info from Shaun and asbo, I don't think it is. I have seen broken scan engine variables when the "no disk" error didn't appear.
Another question regarding shared variables: Are shared variables dynamically namespaced? I ask because something else occurred a while back I did not expect.
The shared variable library is located under the RT target. While working on the host app I noticed the shared variable library was showing up in dependencies, like how a vi used in the host app and RT app will show up under both targets. I moved the shared variable library from the dependencies and grouped it with the rest of my host app source code for convenience. That didn't work so well. Later on I discovered the variable YC-301 dragged from the pc target is not the same as YC-301 dragged from the cRIO target.
(As an aside, even though I am using the shared variables in the host app the shared variable library no longer shows up in the pc target dependencies. I have no idea why it was there in the first place or why it isn't there anymore.)