Invalid Dynamic Link Call to a DLL????
Henry Jaremko -- henryj@epic.co.uk
Thursday, January 11, 1996
Hello everyone,
I have a program that uses a DLL (which I also wrote) and this thing
runs fine under Windows 3.1/3.11. I've just upgraded (?) my machine
to Windows 95 and now the same exe won't run anymore displaying
the massively helpful error box:
Your program is making an Invalid Dynamic Link call to a DLL file
The only option is to choose the close button which terminates the
program. There are no errors reported during the compile / link cycle of
either the DLL or the calling program.
I've searched USENET for references to this and it seems
quite a common problem with a variety of products but there were
no answers to what was actually causing it. I also searched MSDN
and the Microsoft Knowledge base with no success.
Anybody got any ideas or can shed any light on this?
Henry
---------------------------------------
henryj@epic.co.uk
also known as:
* - hsq@mistral.co.uk
* - sysop 2:441/51 (FidoNet BBS - 01273 885884 24hrs V32b V42b HST)
* - sysop@squelch.demon.co.uk
Sanjay -- SGUPTA@aegonusa.com
Tuesday, January 16, 1996
We have exactly same problem. A Win16 exe using Afxdlls works under
Win3.1 but Invalid dynamic link call under Win95. We finally overcame
that problem but without any definitive cause as to what was causing it?
It could be because of one of the following reasons:
* One of your Win95 system file is conflicting wioth what your afxdll
requires. Try reinstalling Win95. The problem went away with this in my
case.
* If your afxdll uses a vbx control, maybe Win95 has another version of
the VBX control which could be conflicting with yours.
*Check CRC of the dll and this should be same for both Win3.1 and
Win95.
You can get Invalid Dynalink call under Win3.1 also, and in this case
usually the problem is bad afxdll. Sometimes if you are developing in a
team environment, header files required by the exe and the dll could be
different on different machines. This could happen if you are maintaining
more than one set of files. Even if your exe works on one machine,
doesn't mean that it actually is bug free. This can work on one machine
and not on the other because of the memory configuration. One machine may
bring out the bug which could be invisible on the other machine.
We went through this laborious and tedious process of figuring out a way
to install our app at different machines and figuring out why tings won't
work.
You are right about one thing, Microsoft itself is no help on such HIGHLY
INFORMATIVE message!
Good Luck!
Sanjay Gupta
SGUPTA@AEGONUSA.COM
----------
From: owner-mfc-l[SMTP:owner-mfc-l@netcom.com]
Sent: Tuesday, January 16, 1996 06:10
To: mfc-l
Subject: Invalid Dynamic Link Call to a DLL????
Hello everyone,
I have a program that uses a DLL (which I also wrote) and this thing
runs fine under Windows 3.1/3.11. I've just upgraded (?) my machine
to Windows 95 and now the same exe won't run anymore displaying
the massively helpful error box:
Your program is making an Invalid Dynamic Link call to a DLL file
The only option is to choose the close button which terminates the
program. There are no errors reported during the compile / link cycle of
either the DLL or the calling program.
I've searched USENET for references to this and it seems
quite a common problem with a variety of products but there were
no answers to what was actually causing it. I also searched MSDN
and the Microsoft Knowledge base with no success.
Anybody got any ideas or can shed any light on this?
Henry
---------------------------------------
henryj@epic.co.uk
also known as:
* - hsq@mistral.co.uk
* - sysop 2:441/51 (FidoNet BBS - 01273 885884 24hrs V32b V42b HST)
* - sysop@squelch.demon.co.uk
David Elliott -- dce@netcom.com
Tuesday, January 16, 1996
Oops! Sorry about that one, folks.
Henry and I discussed this before his question got to me (see
Henry - I told you I didn't see your question!). His problem
was that he had a DLL with the same name as an existing DLL.
I thought that this message was his question on how to detect
this situation programmatically.
David Elliott - dce@netcom.com - http://www.btw.com/dce
| Вернуться в корень Архива
|