dll file not found revisited

[irsillymonkey]

Hello all,

I've seen this question here elsewhere and I tried the suggestions, but to no avail. I built a dll in fortran and am using it in vb 6.0. It works fine on my computer, but when I install it on another, it says "error 53, file not found". I know it has something to do with fortran or the dll.

I have:

1. compiled the dll in both release and debug mode. Neither worked on the target machine.

2. compiled in both modes with the library settings on non-debug single threaded and debug single threaded .

3. Put the 3 dlls (I read I may need these: dforrt.dll , dformd.dll, mscvrt.dll) and the fortran dll I made in the Program's .exe path, winntsystem32, and I even tried to make a folder - c:Program filesmatlab6p5..well, you get the point. All to no avail.

If someone knows what I'm doing incorrectly, advice would be greatly appreciated.

I'm new to this site, so if anyone responds,would you pease e-me @ irsillymonkey@yahoo.com and tell me how to check the responses.

Thanx in advance, Brad

[Jugoslav_Dujic]

You can use "Dependency walker" (...CommonToolsDepends.exe) tool from CVF program group -- it will show you the dependency tree for the opened dll or exe, i.e. which dll's are required (and some other handy stuff, like exported & imported routines).

For example, opening depends.exe itself in depends.exe shows that it uses only standard Windows dll's, so you should be able just to copy it to the target machine :-). (I guess no one will reproach if you violate the copyright a bit :) )

I'm new to this site, so if anyone responds,would you pease e-me @ irsillymonkey@yahoo.com and tell me how to check the responses.

If you left a valid e-mail address in your user profile (you can click on your name to access it), you're supposed to be automatically notified via e-mail. (provided that "Watch this topic" check-box in message editor is checked, which is the default).

Jugoslav

[Intel_C_Intel]

Brad, let me guess that you have specified a path to your DLL in VB side, say Declare Sub MyDLL Lib "C:MyPathMyDLL.dll" (ByVal ...), and let me guess that this path does exist in your computer but not in the target computer or your DLL is not copied to the correct path in the target computer.

Sabalan.