Talking in terms of the LabVIEW distribution, I would recommend zipping the .llb, .mnu files, and .dll in a .zip file with a folder path of "driver prefix". The LabVIEW user can then extract this zip file to thier <LabVIEW>\instr.lib\"driver prefix" folder. This should minimize any issues with working on different OS's or different machines.
Also, it is important that your LabVIEW wrapper VIs have only a relative path to the dll stored in the Call Library Node. Basically, this will have LabVIEW look in all predefined paths on the computer for the dll. One of these paths is the current directory. Therefore, the VIs should have no problem linking to the dll if the dll is in the same directory as the VI (or if the dll is in any other defined system path like the VXIpnp directory). The CVI run time engine should be installed with LabVIEW. It is also installed with VISA, so if you wrote your driver with VISA this should not be an issue. Let me know if you have any other questions regarding this approach. I would also like to include your drivers on IDNet when you are finished so don't forget to submit them. Hobbs
