Upload DLL into EFS programm

[roman300178]

Hi!
I am trying to upload my dll file into my EFS script however I get an erro that the dll file couldn't be found :
"\Downloads\Esiganle_test.efs , line 10 : Can not find DLL ..."
The command I used was
var d = new DLL( "c:/testdll/myTest.DLL" );
Please help

[eSignal_JasonK]

Hello roman300178,

Try placing the dll file in the \eSignal\ folder and change the path to:

var d = new DLL( "myTest.DLL" );

Try it again. If that does not work, please post your efs and dll file.

[roman300178]

What are the requirments from dll project

Hi!
I think , the problem is with my dll file, since I took other dll (for example ACE.dll) and it has passed verification.
I am using win32 dll project in visual C++.
Please advise what exact parameters should I set for my project in order my dll pass verification.

best regards,
Roman

[eSignal_JasonK]

Hello Roman,

There was another user reporting what sounds like the same issue recently. I'm not a C++ developer so I do not have a solution for you. I've sent a message to a couple of our developers to see if they might be able to shed some light on this.

[eSignal_JasonK]

Hello Roman,

I've received some very helpful information from one of our developers. Hopefully this will help you track down a solution. To summarize:

If your dll is dependant on any other dlls that are not present on the machine, the parent dll cannot be loaded. Here's a program you can use to check it's dependency, depends.exe (http://www.dependencywalker.com/)

This turned out to be the solution for the other user. It was dependant on the C++ runtime, msvcr80d.dll. However, if you've developed the dll on the machine that is giving you the error, this may not be the source of the problem.

There may also be an incorrect or invalid manifest embedded. People have reported this problem with stuff compiled in 2005 and then run on stock XP. This might indicate the DLL was compiled for 64bit Windows, alpha architecture, or just a bug. This might be corrected by turning off Embed Manifest in the Input and Output section of the Manifest Tool.

[roman300178]

Hi Jason!
Thanks it was a lot of help, I have downloaded the 'depends' program and focused the probelm:
My dll file uses corba communications, hence I have in my dll file dependences on corba dll file called TAO.dll. The probelm is with this dependnse, since esignal can't load the TAO.dll , my dll can't be loaded as well.
Please advise if where is a workaround for this issue?

best regards,
Roman

[eSignal_JasonK]

Hello Roman,

Did you try placing a copy of the TAO.dll in the eSignal directory?

[roman300178]

Hi Jason!
Yes I've tryed .
I would like you to send the TAO.DLL so you can see it for yourself, but it's too big(400kb when zipped) . Can I emal it to you?

I've checked if eSignal may upload TAO.dll file as a stand alone dll , and I got an error message. Hence I think problem is with uploading TAO.dll .
My dll program depends on TAO.dll therefore it aslo may not be upload into the system.
Can you check what's is the problem with using TAO.dll in my program.

kind regards,
Roman

[roman300178]

Hi!
Please notify me if you have an answer for my last post, so I'd know how to proceed.
The question still remains , why can't I use TAO.dll as a dependancy in my dll program file

thanks,
Roman

[eSignal_JasonK]

Hello Roman,

I do not have an answer for you at this time. I'm checking with development on this issue.

[eSignal_JasonK]

Hello Roman,

Well the first thing that was suggested was to check TAO.dll for dependencies. If there are any, they need to be present in the eSignal directory or the \windows\systyem32\ path. You may want to check for dependencies all the way down to make sure that all dependant dlls are present on your machine.

[roman300178]

Hi Jason!
Thanks, I did as you told me. The only problem that the TAO.dll had is: with MPR.dll . I searched for this probplem at google, and found an answer at : http://www.dependencywalker.com/faq.html :

"Why am I seeing a lot of applications where MPR.DLL shows up in red under SHLWAPI.DLL because it is missing a function named WNetRestoreConnectionA? I also get a "Warning: At least one module has an unresolved import due to a missing export function in a delay-load dependent module" message.

Some versions of SHLWAPI.DLL (like the one on Windows XP) have a delay-load dependency on the function WNetRestoreConnectionA in MPR.DLL. Missing delay-load functions are not a problem as long as the calling DLL is prepared to handle the situation. Dependency Walker flags all potential problems as it cannot detect if an application intends to handle the issue. In the case of SHLWAPI.DLL, this is not an problem as it does not require WNetRestoreConnectionA to exist and handles the missing function at runtime. This warning can be ignored. See the "How to Interpret Warnings and Errors in Dependency Walker" section in help for more details
"
Hence , by their saying it shouldn't be an obsticel, other than that the TAO.dll is OK.
Please, advise what are you think about it?

Best regards,
Roman

[roman300178]

Hi!
Please notify me if you have any conclusions for my last post, so I'd know how to proceed.
Also ,please advise if you would like me to email you the below spoken TAO.dll.

thanks,
Roman

[eSignal_JasonK]

Hello Roman,

The eSignal application's ability to load custom dlls into EFS is working properly. The problem you are experiencing with your dll is related to a specific process within your dll code. Unfortunately, that is not something we can provide a solution for.