LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

analyze dll with dependency walker

Solved!
Go to solution

hallo guys,

i can not figure out why a LV dll (probably made with LV2012) is not recognized as a valid windows dll by depends.exe (dependency walker).

I want to know version information or more..

 

koen.

0 Kudos
Message 1 of 16
(3,796 Views)

he's probably encrypted?

0 Kudos
Message 2 of 16
(3,793 Views)

Hello Koen,

 

I just retried (quickly) the creation of a new password protected NI LabVIEW DLL and I do not get an error concerning it being a valid windows dll.

 

A few questions from my side:

Can you share the DLL you are looking at? (and necessary files)

Did you create the DLL?

If not, then where did you get it from?

Have you tried to look at your own self-created DLLs to notice differences?

Is there a specific reason why you need the Version Information of the DLL?

 

Thanks in advance for your cooperation!

Kind Regards,
Thierry C - CLA, CTA - Senior R&D Engineer (Former Support Engineer) - National Instruments
If someone helped you, let them know. Mark as solved and/or give a kudo. 😉
0 Kudos
Message 3 of 16
(3,761 Views)

Hey Thierry,

how do You decide "valid windows dll"? I use depends.exe on Windows7.

 

The labView dll is generated by someone else (external party).

This dll is used by a labView exe.

So, I think the answer to Your question if the dll can be shared is yes. (to a labview exe)

If I have time and the necessary resources (which I have not sufficient at this moment; missing vi packages from our external partner), I can try to see the differences. But I expect the same issue.

I need the version of the dll to be able to manage/administer worldwide testsystems.

 

regards,

Koen.

0 Kudos
Message 4 of 16
(3,752 Views)

@kdCMC wrote:

The labView dll is generated by someone else (external party).

This dll is used by a labView exe.

So, I think the answer to Your question if the dll can be shared is yes. (to a labview exe)



By "share" he means post your DLL so the rest of us can see it.

0 Kudos
Message 5 of 16
(3,746 Views)

I'm very sorry, but I will not post the dll....

0 Kudos
Message 6 of 16
(3,744 Views)

@kdCMC wrote:

I'm very sorry, but I will not post the dll....


Then you've pretty much will have to figure this out yourself.

 

0 Kudos
Message 7 of 16
(3,738 Views)

I do not completely understand password protected dll.

Could this mean that when You want to open this dll with depends.exe, You first have to enter a password??

0 Kudos
Message 8 of 16
(3,732 Views)

Hello Koen,

 

I am also using Dependency Walker and I can use it to walk through its dependencies.

Forget my note about Password protected DLLs, since this seems to have caused confusion.

 

Since you cannot share the DLL, I have the following questions:

- Are you in contact with the 3rd party that made the DLL?
- Have you asked them the same questions?

  They would be better suited to provide you with the necessary information.

- Can you share a screenshot of the error message you are getting?

Kind Regards,
Thierry C - CLA, CTA - Senior R&D Engineer (Former Support Engineer) - National Instruments
If someone helped you, let them know. Mark as solved and/or give a kudo. 😉
0 Kudos
Message 9 of 16
(3,722 Views)

Hallo Thierry,

the error I get is:

see attachement msWord doc

Our partner will get this question in the long term if it's not solved in the mean time (lower priority)

0 Kudos
Message 10 of 16
(3,711 Views)