DLL needs to be in the same folder as LabView85.exe

[DavidU]

Hi,

As I suspected, this hasn't worked

I added the path to both the PATH environment variable in autoexec and the VI Search Path.

Thanks
David



Message Edited by DavidU on 07-01-2008 09:09 AM

[JamesC]

Hi David,

Please can you try opening the Run menu Start >> Run and typing:

regsvr32 <path to DLL>

To make sure the DLL is registered, hopefully at this point LabVIEW will not require continual re-linking manually

Regards
JamesC
NIUK and Ireland

It only takes a second to rate an answer 🙂

[DavidU]

OK, when I try that I get:

dll was loaded but DLLRegisterServer entry point was not found.

which is not good. I've tried reinstalling the dll witht the setup that came with the spectrometer, but it hasn't helped.

Also, I've noticed that the program works fine if I am logged under a particular username, but not if I'm logged in under any other name. All user profiles on the computer have Administrator privileges. I get the DLLRegisterServer error under all user logons.

David

[JamesC]

---

@DavidU wrote:

Also, I've noticed that the program works fine if I am logged under a particular username, but not if I'm logged in under any other name. All user profiles on the computer have Administrator privileges. I get the DLLRegisterServer error under all user logons.

David

---

Hi David,

In that case there must be something registered in the Windows Registry under HKEY_CurrentUser, which will need to be transferred to HKEY_LocalMachine.

You will probably have to talk to the instrument manufacture to see what they put in the registry.

Regards
JamesC
NIUK and Ireland

It only takes a second to rate an answer 🙂

[F._Schubert]

 I come over from the other post you've made. I guess the file dialog is just somehow on the Win side memorizing the folder (MRU list). It also could be that the user where it is working has the folder in the MRU list. From my experience, I have a driver that only works under LV if I copy manually some of it's dll's into the system32 path (WinXP), because this is the default search path. Also consider, that the dll might in turn call other dll's, which need to be found. I don't know why, but this seemed to be a LV specific issue.

Felix 

[DavidU]

Hi Felix,

thanks for the reply. I've tried various combinations of dll locations (inlcuding dls that it might call) etc and so far none have worked.

Dave