Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

msimg32.dll

24 views
Skip to first unread message

Micus

unread,
Mar 23, 2006, 8:18:53 PM3/23/06
to
[VS 2003 c++, WinXP Pro; msi target Win9x, ME, 2000, and XP]

Hello, I have an app which requires msimg32.dll for an Alphablend() call
. I've searched through all the merge modules and it is not included in any
of them. Also, I've looked through the Redist components in VS and it is not
listed. Though this dll is included in Win98se and later OS's, it is not a
part of Win95 and maybe 98. In MSDN, Alphablend() is list as supported by
Win95, however the msimg32.dll for XP, when installed on Win95, gives the
error that it is looking for a different OS. Does anyone have any
suggestions how to rectify this or links to help.

Thanks,
M


Richard [Microsoft Windows Installer MVP]

unread,
Mar 23, 2006, 8:41:34 PM3/23/06
to
[Please do not mail me a copy of your followup]

This sounds like either a doc bug (perhaps its only supported on
Win98SE or later) about the platform support for the function, or
there is some undocumented way of getting the DLL for Win95.

You don't get it on Win95 when you run Windows Update and install all
the updates?
--
"The Direct3D Graphics Pipeline"-- code samples, sample chapter, FAQ:
<http://www.xmission.com/~legalize/book/>
Pilgrimage: Utah's annual demoparty
<http://pilgrimage.scene.org>

Kalle Olavi Niemitalo

unread,
Mar 24, 2006, 12:29:00 AM3/24/06
to
"Micus" <no@way> writes:

> In MSDN, Alphablend() is list as supported by Win95

Where do you see that?
<http://msdn.microsoft.com/library/en-us/gdi/bitmaps_6ig4.asp>
lists the requirements for AlphaBlend:

Windows NT/2000/XP/Vista: Included in Windows 2000 and later.
Windows 95/98/Me: Included in Windows 98 and later.

which does not include Windows 95.

Micus

unread,
Mar 24, 2006, 1:04:41 AM3/24/06
to

"Richard [Microsoft Windows Installer MVP]"
<legaliz...@mail.xmission.com> wrote in message
news:%23mspWQu...@TK2MSFTNGP09.phx.gbl...

> [Please do not mail me a copy of your followup]
>
> This sounds like either a doc bug (perhaps its only supported on
> Win98SE or later) about the platform support for the function, or
> there is some undocumented way of getting the DLL for Win95.
>
> You don't get it on Win95 when you run Windows Update and install all
> the updates?
> --

For now, my Win95 system is not capable of handling my DSL service. However,
I'm going to get the msimg32.dll from a Win98se system and see if it will
fly. It might be a case of ansi v. unicode. Msimg32 is a resource dll so I
didn't think there would be issues. I've went through the MS downloads site
to see if there were any files there concerning my problem (no). Perhaps
update is the only avenue. I'll post how the Win98se file works when I get
my hands on it.

Thanks for your help Richard,
M


Micus

unread,
Mar 24, 2006, 1:19:51 AM3/24/06
to

"Kalle Olavi Niemitalo" <k...@iki.fi> wrote in message
news:87fyl85...@Astalo.kon.iki.fi...

It's been my experience that anything that I've programmed using the
Windows API/GDI, and can run on 98 or ME, will run on 95. I believe the
'included' refers to the shipping OS having the dll and does not mean 'not
supported' on 95. I should have my answer tomorrow as I am going to obtain
the 98se dll.

Thank you Kalle,
M


Micus

unread,
Mar 24, 2006, 3:13:46 PM3/24/06
to
The msimg32.dll ver 5.0.xxxxx from Win98se works like a peach on Win95.
The ver 5.1.xxxxx from XP might be the unicode version. Now I need to know
if it is legal for me to distribute/install this dll with my application
(?). Any help will be appreciated.

Best Regards,
M

"Micus" <no@way> wrote in message
news:eWIhhDuT...@TK2MSFTNGP12.phx.gbl...

Richard [Microsoft Windows Installer MVP]

unread,
Mar 24, 2006, 3:56:31 PM3/24/06
to
[Please do not mail me a copy of your followup]

"Micus" <no@way> spake the secret code
<#n0ns93T...@TK2MSFTNGP14.phx.gbl> thusly:

>[...] Now I need to know


>if it is legal for me to distribute/install this dll with my application
>(?). Any help will be appreciated.

No, its not legal. If it were, it would be available as a
redistributable from Microsoft.

Richard [Microsoft Windows Installer MVP]

unread,
Mar 24, 2006, 3:57:33 PM3/24/06
to
[Please do not mail me a copy of your followup]

"Micus" <no@way> spake the secret code

<eJqJtrw...@TK2MSFTNGP12.phx.gbl> thusly:

> It's been my experience that anything that I've programmed using the
>Windows API/GDI, and can run on 98 or ME, will run on 95. I believe the
>'included' refers to the shipping OS having the dll and does not mean 'not
>supported' on 95.

Not true. It means its supported in 98 or later, not 95. Just
because you flop the DLL down there and it doesn't blow up in your
face doesn't mean its supported. Basically you're creating something
that works by accident, not by design.

Micus

unread,
Mar 24, 2006, 8:51:03 PM3/24/06
to
Thanks for your help. I guess I'm going to have to eliminate my Alphablend()
call.
-M

"Richard [Microsoft Windows Installer MVP]"
<legaliz...@mail.xmission.com> wrote in message

news:%23a5ouV4...@TK2MSFTNGP14.phx.gbl...

Richard [Microsoft Windows Installer MVP]

unread,
Mar 24, 2006, 10:06:58 PM3/24/06
to
[Please do not mail me a copy of your followup]

"Micus" <no@way> spake the secret code

<eaaIM66T...@TK2MSFTNGP12.phx.gbl> thusly:

>Thanks for your help. I guess I'm going to have to eliminate my Alphablend()
>call.

What people usually do is see if they can dynamically load the DLL
that's only available on some platforms they target and then use the
call if its available and do something else when its not available.

That way you get the benefit of AlphaBlend when its available.

Micus

unread,
Mar 25, 2006, 10:33:34 AM3/25/06
to

"Richard [Microsoft Windows Installer MVP]"
<legaliz...@mail.xmission.com> wrote in message
news:u2fwuk7T...@TK2MSFTNGP14.phx.gbl...

> [Please do not mail me a copy of your followup]
>
> "Micus" <no@way> spake the secret code
> <eaaIM66T...@TK2MSFTNGP12.phx.gbl> thusly:
>
> >Thanks for your help. I guess I'm going to have to eliminate my
Alphablend()
> >call.
>
> What people usually do is see if they can dynamically load the DLL
> that's only available on some platforms they target and then use the
> call if its available and do something else when its not available.
>
> That way you get the benefit of AlphaBlend when its available.
> --

I've never done that before, but it sounds like a worth while
programming adventure. I've posted in win32.programmer.gdi to see if anyone
there has run into Win95 and Alphablend() in the past. While I'm waiting for
a response, I'll look into dynamically loading the DLL.

Very Appreciated,
M


Richard [Microsoft Windows Installer MVP]

unread,
Mar 25, 2006, 7:15:33 PM3/25/06
to
[Please do not mail me a copy of your followup]

"Micus" <no@way> spake the secret code

<OivDxFCU...@TK2MSFTNGP14.phx.gbl> thusly:

> I've never done that before, but it sounds like a worth while
>programming adventure. I've posted in win32.programmer.gdi to see if anyone
>there has run into Win95 and Alphablend() in the past. While I'm waiting for
>a response, I'll look into dynamically loading the DLL.

Your code will basically look like:

1. call LoadLibrary to see if you can get msimg32.dll

2. if LoabLibrary worked, use GetProcAddress to get the pointer to
the AlphaBlend function

Micus

unread,
Mar 25, 2006, 8:42:55 PM3/25/06
to

"Richard [Microsoft Windows Installer MVP]"
<legaliz...@mail.xmission.com> wrote in message
news:uZF2mpGU...@TK2MSFTNGP14.phx.gbl...

Richard,

I am going to write some test code tonight trying out the dynamic
library loading you've outlined above as well as a suggestion from the GDI
newsgroup to use GetDeviceCaps().

Thank You!
M


0 new messages