DLLs and Windows registry

[DienyduToit]

We have a Delphi project (exe), supported by several PB/DLL 5 modules (DLLs).

When one copies these to a PC (and sets up the necessary data directory sub-structure, it refuses to run. Is it necessary to do something about the Windows registry as regards the DLLs?

[Lance Edmonds]

No, DLL's created with PB/DLL do not need to have any registration or special placement (unless the Delphi code expects the DLL's to be in a specific location). Usually, you would place the DLL's in the same directory as the Delphi code. Any registry entries required will be as a result of your coding, not PowerBASIC itself.

Can you be more explicit about the "refuses to run" problem? For example, what error messages do you get?

My suspicions are that the Delphi EXE requires a library/DLL that is unrelated to PowerBASIC.

What you probably need is a "dependency walker" to list all of the DLL's thet your EXE requires.

-------------
Lance
PowerBASIC Support
mailto:[email protected][email protected]</A>

[Lance Edmonds]

Try these links:
http://mspress.microsoft.com/reslink...ls/depends.htm
http://stevemiller.net/depends.html
http://www.dependencywalker.com/


-------------
Lance
PowerBASIC Support
mailto:[email protected][email protected]</A>

[Greg Turgeon]

One point to verify: Is the correct case used in declaring the DLL 
functions (in the Pascal code)?  By default, PB exports everything in 
upper case, so the Delphi code needs: 
   
procedure PBFUNCTION1(s: pchar; x: integer);
            stdcall; far; external 'THEPBDLL';
   
You can have complete control over the case of exports by using ALIAS 
in the PB function declarations.  See the PBDLL help file on this 
topic.

[This message has been edited by Greg Turgeon (edited January 18, 2000).]

[Scott Turchin]

And how true that is, and what's ESPECIALLY difficult is whhen it's a third party DLL that is expecting you to use C code...

Jim helped me isolate my problem, now to make the DLL work!

Scott

-------------
Scott Turchin