Missing Sound Output VIs

[eek]

Hi guys,

I hope you don't mind if I jump in this conversation for a bit. I'm curious as to how this is panning out. If I understand correctly, Slowpoke is attempting to build a .dll that calls another .dll. Do either of you know if this has been attempted before by any other users?

At this point, the suspicion is that the Noise Tool library is not being linked properly. Am I correct in this assessment? I'd like to see if I can be of any help.

Regards,

Emilie Kopp | Applications Engineer | National Instruments

[Slowpoke]

Hi Emilie,

The more the merrier!  Actually, what I'm trying to do is call a DLL from an executable, but you are correct in that the problem seems to lie with file linking.  I can call the DLL fine from a LabVIEW VI in development mode, but when I make an executable from the DLL and the calling VI, the call fails.  The problem seems to lie with at least one of the Sound Output VIs in the lvsound2.dll.  In addition, I have discovered a similar linking problem with the Write to Measurement File Express VI.  I determined this by rebuilding the DLL VIs block by block and recreating the DLL and executable, repeating this process until I got a failure.   

Oddly enough, when I rebuild the DLLs themselves as executables, they work fine. 

Emilie, I will gratefully accept any assistance you can offer.  Michael, if I scared you away or drove you insane or both, I'm sorry.  Looks like I owe you a beer or two!

I don't know if anyone else has tried calling a DLL from another DLL, but I've considered giving it a shot, just for fun.

Thanks,

Slowpoke 

[eek]

Hi Slowpoke,

So here's a thought:

If the sound.dll is linked incorrecly, there might have been some change in the default settings of your LV installation. Exactly what this change is or why it was caused, I am at a loss. But, a very simple (and admittedly "dumb") solution would be to repair your installation of LV. It's not the most pleasant of actions to take (as it takes some time) but at least we would start with a clean slate, verifying that LV is in the default state, including any links to dll's.

I figure it's worth a shot. Your call.

Cheers,

Emilie Kopp | Applications Engineer | National Instruments

[Slowpoke]

Hi Emilie,

I did as you suggested and did a repair/reinstall of LabVIEW, with no change.  However, I did resolve the issue of calling the DLL from a LabVIEW executable by creating the DLL and executable in separate projects.  I cannot say exactly what the difference is; I may only have assembled both projects correctly this time. 

Unfortunately, the issue with calling the DLL from LabWindows still exists; the links to the lvsound2.dll files still end up severed somehow.  Can I not just copy the DLL into the same directory as the LabWindows dbg.exe file, or am I missing something obvious?

Thanks,

Slowpoke

[Riconquistiamola]

Hi Slowpoke,

I've been out of the office for a while, so thanks to Emilie for taking over this issue while I was out. I'm sorry the issue is taking so long to resolve. It seems like such a simple linking problem.

I've spoken with other Applications Engineers in the department about this issue and we're still baffled as to why LabWindows/CVI can't find lvsound2.dll. We're not giving up hope, however. Here is my next questions/suggestions:

1. Copy your LabVIEW dll and lvsound2.dll into the system32 directory. Attempt to run the CVI code.
2. Copy your LabVIEW dll and lvsound2.dll to any file location you believe LabVIEW would search. Check the LabVIEW options to determine your default search paths.

If neither of those work, please email me anything and everything related to your project. My biggest issue has been an inability to reproduce this issue ...

Once again, I'm confident we can solve your problem. We seem to have reached an extremely special case. Cheers.

[Riconquistiamola]

Hi Slowpoke,

Can I not just copy the DLL into the same directory as the LabWindows dbg.exe file, or am I missing something obvious?

This sounds like your problem. Are you copying the DLL and the Data folder into the same directory as the CVI dbg.exe file? If not, that's why the linking is being severed.

Cheers.