Can't find my DLL when running in NT

I've written an application that, in addition to the main EXE, also calls routines in a DLL that I wrote.  During execution, I store the DLL in the same folder as the EXE.  BTW, I also include the delphimm.dll to handle memory issues (the routines are functions that return values).

When I run the program under Win 95, there's no problem.  However, I've just installed the same application with the same folder structure on two different Win NT (4.0: one workstation, one server) systems and each complained that it couldn't find my home-grown DLL, even tho it was right there to be found.  I even moved copies of the DLL into the WINNT, WINNT\SYSTEM, and WINNT\SYSTEM32 folders, and still no go.

When I removed the delphimm.dll file, it complained about that before my own routine, and when I restored it, it went back to complain about not finding my DLL.

So, what do I need to do to make my program work under NT and find the DLL?

Thanx for any help.
nrosenblattAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

jorgen.hojdmoCommented:
How do you access the dll? Do you load it with the winAPI or do you use something like this?
procedure DoSomething; stdcall; external 'TheDLL.dll';

the latter works fine for me!


0
jturpinCommented:
I had a similar problem in WinNT. I fixed it by ensuring
the extension "DLL" was in my code like:
      procedure SomeRoutine; external 'MyDll.dll';

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
nrosenblattAuthor Commented:
Yes, adding the ".DLL" to the name of the routine in the code did the trick.  While I'm tempted to wonder why this is, I'm more tempted to leave well enough alone and get on with life.

Thanx again.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Delphi

From novice to tech pro — start learning today.