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

comctl32.dll

0 views
Skip to first unread message

Tom Sielicki

unread,
Apr 1, 1997, 3:00:00 AM4/1/97
to

Has anyone experienced runtime problems with VC5.0 and using an old
version of this DLL. My VC4.2 ran fine with the old or new version of
Comctl32.dll.
So, does microsoft now expect me to upgrade an OS dll so my VC5.0 builds
will run?


Andy Yee

unread,
Apr 1, 1997, 3:00:00 AM4/1/97
to

You must install IE 3.01 to get that DLL.

--------------------------------------------------------------------------------
Andy Yee Corporate E-mail: an...@xiotech.com
Principal Software Engineer Personal E-mail: n...@visi.com
XIOtech Corporation Personal Home Page: http://www.visi.com/~nde
Eden Prairie, MN

"Question authority...and the authorities will end up questioning YOU!"
--------------------------------------------------------------------------------

Tom Sielicki

unread,
Apr 1, 1997, 3:00:00 AM4/1/97
to

I know that. So I now have to ship Internet Explorer 3.01 to my customers
so that they can
run my VC5.0 build of my product.

Andy Yee <an...@xiotech.comDELETE_ALL_CAPS_TO_RESPOND> wrote in article
<evrfwRs...@uppssnewspub04.moswest.msn.net>...

Andy Yee

unread,
Apr 1, 1997, 3:00:00 AM4/1/97
to

In article <01bc3ec8$6a9210b0$6dae9782@tsielick>, "Tom Sielicki" <tom.si...@software.rockwell.com> wrote:
>I know that. So I now have to ship Internet Explorer 3.01 to my customers
>so that they can
>run my VC5.0 build of my product.
>
>Andy Yee <an...@xiotech.comDELETE_ALL_CAPS_TO_RESPOND> wrote in article
><evrfwRs...@uppssnewspub04.moswest.msn.net>...
>> In article <01bc3ec1$510c44a0$6dae9782@tsielick>, "Tom Sielicki"
><tom.si...@software.rockwell.com> wrote:
>>
>> You must install IE 3.01 to get that DLL.
>>
>>
>>

Ain't that stupid?? :(

--------------------------------------------------------------------------------

Brian

unread,
Apr 1, 1997, 3:00:00 AM4/1/97
to

Andy Yee wrote:
<tom.si...@software.rockwell.com> wrote:
>
> You must install IE 3.01 to get that DLL.

Not really.....Why not install IE 3.01 yourself, get your hands on the dll,
and ship THAT to your customers. If you use Wise install, you can also
change a system dll as part of your install. Write a batch file for your
customers to get it swapped during a restart, and you're there.
Don't send IE with your product for just one file.

Brian

Keith Wipprecht

unread,
Apr 1, 1997, 3:00:00 AM4/1/97
to

You bring up an excellent question that I think a lot of people in this
forum can benefit from the answer. Would you please send the question to
ms...@microsoft.com and possibly the support guys and ask the question?

Let us know what you find out.

Keith Wipprecht
Cincinnati Componentware, Inc.
http://home.sprynet.com/sprynet/cinncomp

Tom Sielicki <tom.si...@software.rockwell.com> wrote in article
<01bc3ec1$510c44a0$6dae9782@tsielick>...

Andy Yee

unread,
Apr 2, 1997, 3:00:00 AM4/2/97
to

Uh...that would be nice, except that MS does NOT allowcomctl32.dll to be
distributed :((

Andy Yee

unread,
Apr 2, 1997, 3:00:00 AM4/2/97
to

In article <eb#8LK7P8...@uppssnewspub05.moswest.msn.net>, "Walter Sullivan" <wal...@microsoft.com> wrote:
>OK, I couldn't believe this when I first read it and so I spent this
>morning reformatting a machine and building a stock, default MFC app that
>used a Tree View, ToolBar and Tab control. All from comctl32.dll. My
>comctl32.dll is 4.00.950, it's the only one on this system and is the
>version that originally shipped with Windows 95.
>
>I did have to install axdist.exe, which comes with VC and installs the new
>oleaut32.dll which we depend on now. But I definitely was not dependant on
>the new comctl32.dll which only IE and NT4 ship, which currently isn't
>redistributable.
>
>So if someone could post a little more info that would be very helpful.
>What controls is your app using? How have you determined that you need the
>new comctl32.dll?
>
>If you're actually using one of the new controls, like the Rebar or
>something, then you are dependant on the new comctl32.dll and the Internet
>Client SDK (which is the only place that has documentation on the Rebar, or
>any of the other new controls) clearly says in ccinfo.doc that you can't
>redistribute comctl32.dll so hopefully it isn't a surprise.
>

I'm using VC++ V4.2, and it would be convenient (not having to re-invent
the wheel)...if I could use:

1. "Tooltip"-like windows for tree view items that go beyond the right
edge of the control

2. The ability to select an entire row in a CListCtrl using the multi-
column report format.

Walter Sullivan

unread,
Apr 2, 1997, 3:00:00 AM4/2/97
to

The main reason that IE is required for VC5 install is because the new help
system is HTML based and IE is the technology we have right now for viewing
HTML. It's not being installed for the new comctl32.dll.

How does your app just not run? Is there an error message that is
displayed? Does it just hang? Does it start to run then silently exit?
Does it generate an application violation?

If I don't replace the old oleaut32.dll with the new one I get a message
saying that I'm linking to a missing export in oleaut32.dll I'm pretty
sure. I'll try it out. I don't see how the two are related in this case
however (meaning, I can't see how just updating comctl32.dll and not
oleaut32.dll would make my app start working).

What is your sample app? One of the MFC samples? You own app? An App
Wizard app? If it's an App Wizard app, what modifications have you made to
it?

Thanks!
Walter
Tom Sielicki wrote in article <01bc3fb6$8ef4b1d0$6dae9782@tsielick>...
>Are you saying that the program would not run and oleaut32.dll fixed this
>problem.
>The problem I was seeing in using the treecontrol that is in the common
>controls
>is that my VC5.0 build would not run on some windows 95 machines. In
>looking
>at the DLLS that were loaded on two machines( 1 that runs and 1 that
>freezes up),
>3 were older revs. They were Advapi32.dll, comctl32.dll, and
>oleaut32.dll. Comctl32.dll allowed the app to run normally when it was
>updated. VC4.2
>builds would run on either machine with no updates. So I have concluded
>that this
>DLL is needed since installing it alone allowed my application to run.
Now
>since this
>is not my DLL I dont know the exact dependencies of what other possible
>combinations
>work. If you did not update oleaut32.dll would your app run with the
new
>comctl32.dll??
>
>Also, why would internet explorer be required to install VC5.0. I
thought
>more people would
>be seeing this problem.
>
>
>Walter Sullivan <wal...@microsoft.com> wrote in article
><eb#8LK7P8...@uppssnewspub05.moswest.msn.net>...

>> At this point, I can't get a VC5 built app to force a dependency on
this
>> new DLL unless I explicitly introduce that dependency. Any help in
>> repro'ing this problem would be greatly appreciated!
>>
>> Thanks,
>>
>> Walter Sullivan
>> MFC/ATL Program Manager
>> Andy Yee wrote in article ...


>> >In article <01bc3ec8$6a9210b0$6dae9782@tsielick>, "Tom Sielicki"
>> <tom.si...@software.rockwell.com> wrote:
>> >>I know that. So I now have to ship Internet Explorer 3.01 to my
>> customers
>> >>so that they can
>> >>run my VC5.0 build of my product.
>> >>
>> >>Andy Yee <an...@xiotech.comDELETE_ALL_CAPS_TO_RESPOND> wrote in
article
>> >><evrfwRs...@uppssnewspub04.moswest.msn.net>...
>> >>> In article <01bc3ec1$510c44a0$6dae9782@tsielick>, "Tom Sielicki"

>> >><tom.si...@software.rockwell.com> wrote:
>> >>>
>> >>> You must install IE 3.01 to get that DLL.
>> >>>
>> >>>
>> >>>
>> >

>> >Ain't that stupid?? :(
>> >
>>
>>--------------------------------------------------------------------------
-
>
>> -----

Thomas Olsson

unread,
Apr 2, 1997, 3:00:00 AM4/2/97
to

And if you run NT 3.51?

Tom Sielicki <tom.si...@software.rockwell.com> wrote in article

<01bc3ec8$6a9210b0$6dae9782@tsielick>...

Thomas Olsson

unread,
Apr 3, 1997, 3:00:00 AM4/3/97
to

Three problems:

1) Since COMCTL32.DLL is not among the 'redistributable' DLLs I am not sure
you are allowed to do this.

2) The is not clear info of what version of COMCTL32.DLL to install in
Win95, Win NT 3.51 and WIN NT 4.0. I have found three (3!) different
COMCTL32.DLL with version 4.70. It seems like the ones that work on Win NT
3.51 does not work on Win 95.

3) We have not been able to install COMCTL32.DLL using Wise on Win95. It
works fine on NT, but on Win95 it simple is not installed. We have reported
this problem to Wise. (Yes, we are running the latest version (as of 2
April 97).)

Brian <bb...@accessone.com> wrote in article
<3341A4...@accessone.com>...


> Andy Yee wrote:
> <tom.si...@software.rockwell.com> wrote:
> >
> > You must install IE 3.01 to get that DLL.
>

> Not really.....Why not install IE 3.01 yourself, get your hands on the
dll,
> and ship THAT to your customers. If you use Wise install, you can also
> change a system dll as part of your install. Write a batch file for your
> customers to get it swapped during a restart, and you're there.
> Don't send IE with your product for just one file.
>

> Brian
>

Walter Sullivan

unread,
Apr 3, 1997, 3:00:00 AM4/3/97
to

Thomas Olsson wrote in article <01bc4001$03baccd0$1c66f482@thomaspro>...

>1) Since COMCTL32.DLL is not among the 'redistributable' DLLs I am not
sure
>you are allowed to do this.

It is not redistributable yet. So in any case you shouldn't try probably.

>2) The is not clear info of what version of COMCTL32.DLL to install in
>Win95, Win NT 3.51 and WIN NT 4.0. I have found three (3!) different
>COMCTL32.DLL with version 4.70. It seems like the ones that work on Win
NT
>3.51 does not work on Win 95.

I'm not sure, but perhaps there is a unicode and ansi version of
comctl32.dll. So the NT version wouldn't work on Win95 because it's
Unicode.

>3) We have not been able to install COMCTL32.DLL using Wise on Win95. It
>works fine on NT, but on Win95 it simple is not installed. We have
reported
>this problem to Wise. (Yes, we are running the latest version (as of 2
>April 97).)

Perhaps is is for the same ANSI vs. Unicode issue.

Walter


Thomas Olsson

unread,
Apr 4, 1997, 3:00:00 AM4/4/97
to

Walter Sullivan <wal...@microsoft.com> wrote in article
<eb#8LK7P8...@uppssnewspub05.moswest.msn.net>...
> OK, I couldn't believe this when I first read it and so I spent this
> morning reformatting a machine and building a stock, default MFC app that
> used a Tree View, ToolBar and Tab control. All from comctl32.dll. My
> comctl32.dll is 4.00.950, it's the only one on this system and is the
> version that originally shipped with Windows 95.
>
> I did have to install axdist.exe, which comes with VC and installs the
new
> oleaut32.dll which we depend on now. But I definitely was not dependant
on
> the new comctl32.dll which only IE and NT4 ship, which currently isn't
> redistributable.
>
> So if someone could post a little more info that would be very helpful.
> What controls is your app using? How have you determined that you need
the
> new comctl32.dll?

I have found that ToolTips does not work with COMCTL32.DLL v4.00.950 for
programs compiled with VC++ 5. (I guess this is actually due to the new MFC
version.)


Griffo Brothers, Inc

unread,
Apr 4, 1997, 3:00:00 AM4/4/97
to

>No, you do what you need to do for the customers. You either stay at
>Visual C++ 4.2b or yeah, have your customers distribute IE 3.02...
>
>What is important in 5.0 that you need it?


Question wasn't for me, but...

5.0 has more JAVA, OLE support as well as some bug fixes. One would normally
assume that in a 'mature' product, a major release would be more stable and
have more features than a previous release. You would think by the time they
got to 5.0, it would be mature and stable. And, if you've paid the big bucks
for it, you should expect it to work, and work correctly.

>And why, for gods sake, would you program to a control in the web browser that
>is not redis...?????
>
>Chris


If you use the MFC wizard to generate some controls or dialogues, you don't
really have control over what DLL that control or dialogue may use. You just
have to assume that it will be available either from the operating system or
developer studio. The last thing a programmer should have to worry about is if
any of the controls supplied with Developer Studio is redistributable. By
definition, they must be. Otherwise, wouldn't you have to get permission from
MicroSoft depending upon which control the Wizard picks for you? Doesn't make
much sense, or am I missing something here.

And you shouldn't have to redistribute IE 3.02, just the COMCTRL32.DLL.


Of course, that starts my rant on all wrong things with DLL design---but I'll
save that for later. Much later.


Ducking now while flames are incoming.

dick
jarv...@griffobros.com

Chris Dickerson

unread,
Apr 4, 1997, 3:00:00 AM4/4/97
to Tom Sielicki

Tom Sielicki wrote:
>
> I know that. So I now have to ship Internet Explorer 3.01 to my customers
> so that they can
> run my VC5.0 build of my product.

No, you do what you need to do for the customers. You either stay at


Visual C++ 4.2b or yeah, have your customers distribute IE 3.02...

What is important in 5.0 that you need it? And why, for gods sake, would

0 new messages