Missing Export

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Ruthsdad - 27 Sep 2004 13:52 GMT

Hi there
Can anyone tell me what the following error message means,
also can it be fixed and how do I fix it.

"The MSIMG32.DLL file is linked to missing export
GDI32.DLL:Gdi Gradient Fill"

Regards
Ruthsdad

Reply to this Message

Mike M - 27 Sep 2004 14:34 GMT

Ruthsdad,

Such a message tells you that the version of gdi.dll is not that expected
by msimg32.dll. This can happen when one or other of the two files is
intended for use on another operating system. Have you perhaps recently
replaced gdi32.dll with an updated version as a result of running the gdi+
tool from the Windows Update site? If so did you perhaps install a
version for use with say XP rather than Win Me?

Using Windows Explorer, locate all copies of the file gdi.dll, right click
on each file and select Properties and then click the version tab. Make a
note of the version for each copy that you have. Likewise for
msimg32.dll. Post back details.

Signature

Mike Maltby MS-MVP [2001-2004]
mcmaltby@hotmail.com

> Hi there
> Can anyone tell me what the following error message means,
> also can it be fixed and how do I fix it.
>
> "The MSIMG32.DLL file is linked to missing export
> GDI32.DLL:Gdi Gradient Fill"

Reply to this Message

Ruthsdad - 27 Sep 2004 21:14 GMT

>-----Original Message-----
>Hi there
[quoted text clipped - 6 lines]
>Regards
>Ruthsdad

>.Hi Mike

Thanks for the prompt response. With regards to
installing a version for
use with XP..........Not knowingly. Here is the info you
requested:-
msimg32.dll
Location - C:\Windows\System
File Version - 5.1.2600.1106
Description - GDIEXT Client DLL
Created - 28 August 2002
Modified - 28 August 2002

GDI32.DLL
Location - C:\Windows\System
File Version - 4.90.0.3000
Description - Win32GDI core component
Created - no date shown
Modified - 08 June 2000

gdi32.dll
Location - C:\Windows\System32
File Version4.0.0.950
Description - Win32GDI core component
Created - 05 April 1998
Modified 05 April 1998

I have a 50% chance of posting this reply where it should
be. Please
forgive me if I get it wrong (1st timer)

Regards
Ronnie Middleton
(Ruthsdad)
beechwalker@hotmail.com

Reply to this Message

Mike M - 27 Sep 2004 22:13 GMT

Ronnie (who I'm guessing could be Ruth's "Dad" <g>),

I'm a bit concerned about the copy of gdi32.dll in the windows\system32
folder as this a copy of the version supplied with Win 95. I suspect this
could well be the cause of your problem. Try renaming this copy to
gdi32.old and then copying the version in the windows\system folder to the
windows\system32 folder (don't move but rather leave the original in the
windows\system folder) just in case you have an application that is
looking in the system32 folder rather than the windows\system folder.

Signature

Mike Maltby MS-MVP [2001-2004]
mcmaltby@hotmail.com

> Thanks for the prompt response. With regards to
> installing a version for
[quoted text clipped - 24 lines]
> be. Please
> forgive me if I get it wrong (1st timer)

Reply to this Message

Ruthsdad - 28 Sep 2004 12:37 GMT

Hi Mike,
Yes, that's me. I have done what you suggested but it
has not solved my problem. I may be able to assist you
further if I gave you the full story:-
All this stated just over a week ago when I tried to use
Movie Maker1 to burn some home movies. Up popped an
error message saying "A device attached to the system is
not functioning MSIMG32.DLL " No problem I thought,
I'll use NeroVision Express2........... that's when I got
the error message in my original post. I contacted the
Nero people who suggested that I totally remove Nero from
my PC (using their cleaner tool) and re-installing.
Nero6 re-installed fine but NeroVision Express failed due
to the following files failing to self register -
GCCore.dll
GCFilter.ax
GCFX.DLL
GCHW.Dll
GCLib.DLL
Nerovision.exe
Nerovision API.dll

I did post the problem on the Windows ME Moviemaker
Discussion on 21.09.04 but have had no responses. I hope
this makes some sense to you. I am sorry for being a
nuisance.
Regards
Ronnie
(Ruthsdad)

>-----Original Message-----
>Ronnie (who I'm guessing could be Ruth's "Dad" <g>),
[quoted text clipped - 6 lines]
>windows\system folder) just in case you have an application that is
>looking in the system32 folder rather than the windows\system folder.

Reply to this Message

Mike M - 28 Sep 2004 13:06 GMT

Ronnie,

Replace MSIMG32.DLL with the copy that came with Win Me (v5.00.2218.1
dated 8 June 2000). The version you have (v5.1.2600.1106) is that from
Windows XP SP1 hence the error you are seeing when it attempts to call a
function not included in the Win Me copy of gdi32.dll. I've no idea as to
how you might have installed the wrong version as to do so would have
required you to overcome Win Me's System File Protection mechanism.

MSIMG32.DLL is contained in WIN_12.CAB of the Win Me cab set and can be
replaced by booting to Safe Mode and using MSConfig | General | Extract
File and following the prompts. The "cab" files are in the Win9x folder
on the Win Me CD and also in either the C:\Windows\Options\Cabs or
C:\Windows\Options\Install, which depends on the media from which Win Me
was installed. See MS KB 265371 - "How to Extract and Replace a
Protected File in Windows Me" (http://support.microsoft.com?kbid=265371)
for details of how to extract files from the cab set.

MSIMG32.DLL belongs in the windows\system folder.

Hopefully this should fix the problem.

Signature

Mike Maltby MS-MVP [2001-2004]
mcmaltby@hotmail.com

> Hi Mike,
> Yes, that's me. I have done what you suggested but it
[quoted text clipped - 22 lines]
> this makes some sense to you. I am sorry for being a
> nuisance.

Reply to this Message

Ruthsdad - 29 Sep 2004 20:23 GMT

Mike.........1000 thanks mate, problem solved, programs
seem to be working A.O.K. For people like me who are on
the lower end of the learning curve, people like you are a
godsend. Again I express my gratitude, thankyou.

Take care
Regards
Ronnie
(Ruthsdad)

>-----Original Message-----
>Ronnie,
[quoted text clipped - 18 lines]
>
>Hopefully this should fix the problem.

Reply to this Message

Mike M - 29 Sep 2004 21:11 GMT

That is so good to read Ronnie.

My apologies for starting off down the wrong road in getting you to
remove/rename the old version of gdi32.dll when from your post it should
have been clear to me that the problem was with MSIMG32.DLL. It's not as
if you hadn't given me all the information I needed. <vbg>

Cheers and thanks for the feedback.

Signature

Mike Maltby MS-MVP [2001-2004]
mcmaltby@hotmail.com

> Mike.........1000 thanks mate, problem solved, programs
> seem to be working A.O.K. For people like me who are on
> the lower end of the learning curve, people like you are a
> godsend. Again I express my gratitude, thankyou.

Reply to this Message

dave tolladay - 27 Sep 2005 14:42 GMT

At last! I've been trying to sus this problem out for ages. My PC (nt4
workstation) started displaying "The procedure entry point GdiGradient Fill
could not be located in the dynamic link library GDI32.dll" just after
installing remote desktop connection. I've trawled the web trying to find the
reason. By renaming MSIMG32.dll (5.1.2600.1106 (xpsp1 020828-1920) it went
away.
Thanks very much for the tip.
I still don't know where it came from though, unless its part of RDC.

>That is so good to read Ronnie.
>
[quoted text clipped - 8 lines]
>> the lower end of the learning curve, people like you are a
>> godsend. Again I express my gratitude, thankyou.

Reply to this Message