Home > Archive > Visual Basic Syntax > April 2005 > Re: Downloadable VB6 MS Common Control Hotfix
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: Downloadable VB6 MS Common Control Hotfix
|
|
| Ken Halter 2005-04-29, 4:03 am |
| "Randy Birch" <rgb_removethis@mvps.org> wrote in message
news:%23Wl%23dR5SFHA.2556@TK2MSFTNGP12.phx.gbl...
> http://support.microsoft.com/?id=896559
>
> FIX: The Windows Common Controls Mscomctl.ocx or Comctl32.ocx may cause
> your
> application or the Visual Basic 6 IDE to unexpectedly quit, or you may
> receive a "Divide By Zero" error message.
> APPLIES TO
> • Microsoft Visual Basic 6.0 Professional Edition
> • Microsoft Visual Basic 6.0 Enterprise Edition
> • Microsoft Visual Studio 6.0 Service Pack 5
>
From that page....
"RESOLUTION
Important note: If the application that you are running was provided to you
by a third party, you may want to contact the third party that provided the
application to you before you install the fix. For example, you did not
develop the application yourself. If you install this fix without sufficient
testing, the applications may stop functioning."
....any reports of breakage yet? I wonder what broke on their PCs that would
prompt them to add that note... hmmm...
--
Ken Halter - MS-MVP-VB - http://www.vbsight.com
Sign up now to help keep VB support alive - http://classicvb.org/petition
Please keep all discussions in the groups..
| |
| Rick Rothstein 2005-04-29, 4:03 am |
| > > http://support.microsoft.com/?id=896559
cause[color=darkred]
may[color=darkred]
>
> From that page....
>
> "RESOLUTION
> Important note: If the application that you are running was provided
to you
> by a third party, you may want to contact the third party that
provided the
> application to you before you install the fix. For example, you did
not
> develop the application yourself. If you install this fix without
sufficient
> testing, the applications may stop functioning."
>
> ...any reports of breakage yet? I wonder what broke on their PCs that
would
> prompt them to add that note... hmmm...
[Rick, wildly waving his hands, trying to get everyone's attention]
Excuse me! Uh, there was also this note in the cited Fix page:
"Note: The enclosed fix cannot be uninstalled or removed after it is
installed."
Now, this might seem like a stupid question but... what the hell are we
supposed to do with this fix??!!!? Think about it. If we are using a 3rd
party application, we shouldn't apply the fix because it might break.
Uh, isn't almost everything we run on our system provided by a 3rd
party? Is Microsoft saying these programs might stop working if we fix
our system so that we can continue developing VB6 programs (that use
ListView I guess)? Now that is a hell of a trade-off for Microsoft to
impose on us! Yep, it sure looks more and more like Microsoft will do
whatever it can to make people stop using VB.Classic, doesn't it? Do
they really think this is the way to convince us developer that
Microsoft languages are the ones we should continue investing our
efforts on in the future? Give me a f***ing break here. Also, what if
that 3rd party vendor is no longer in business (say his/her application
works flawlessly, but he/she has "moved on")? What should we do then?
WHAT THE HELL KIND OF A FIX IS THIS ANYWAY??!!!!??!!!!
Hopefully I have read this situation all wrong and someone will post
back correcting my thoughts on this.
Rick
| |
| Randy Birch 2005-04-29, 4:03 am |
| I suspect that warning is for the benefit of end users who install the fix
with the expectation there would be an entry in add/remove programs if
issues arose. I'm sure any competent developer could unregister/delete
mscomctl.ocx and comcl32.ocx and re-register earlier versions.
--
Randy Birch
MS MVP Visual Basic
http://vbnet.mvps.org/
----------------------------------------------------------------------------
Read. Decide. Sign the petition to Microsoft.
http://classicvb.org/petition/
----------------------------------------------------------------------------
"Rick Rothstein" <rickNOSPAMnews@NOSPAMcomcast.net> wrote in message
news:uSgwHoGTFHA.2336@TK2MSFTNGP12.phx.gbl...
:> > http://support.microsoft.com/?id=896559
: > >
: > > FIX: The Windows Common Controls Mscomctl.ocx or Comctl32.ocx may
: cause
: > > your
: > > application or the Visual Basic 6 IDE to unexpectedly quit, or you
: may
: > > receive a "Divide By Zero" error message.
: > > APPLIES TO
: > > Microsoft Visual Basic 6.0 Professional Edition
: > > Microsoft Visual Basic 6.0 Enterprise Edition
: > > Microsoft Visual Studio 6.0 Service Pack 5
: > >
: >
: > From that page....
: >
: > "RESOLUTION
: > Important note: If the application that you are running was provided
: to you
: > by a third party, you may want to contact the third party that
: provided the
: > application to you before you install the fix. For example, you did
: not
: > develop the application yourself. If you install this fix without
: sufficient
: > testing, the applications may stop functioning."
: >
: > ...any reports of breakage yet? I wonder what broke on their PCs that
: would
: > prompt them to add that note... hmmm...
:
: [Rick, wildly waving his hands, trying to get everyone's attention]
:
: Excuse me! Uh, there was also this note in the cited Fix page:
:
: "Note: The enclosed fix cannot be uninstalled or removed after it is
: installed."
:
: Now, this might seem like a stupid question but... what the hell are we
: supposed to do with this fix??!!!? Think about it. If we are using a 3rd
: party application, we shouldn't apply the fix because it might break.
: Uh, isn't almost everything we run on our system provided by a 3rd
: party? Is Microsoft saying these programs might stop working if we fix
: our system so that we can continue developing VB6 programs (that use
: ListView I guess)? Now that is a hell of a trade-off for Microsoft to
: impose on us! Yep, it sure looks more and more like Microsoft will do
: whatever it can to make people stop using VB.Classic, doesn't it? Do
: they really think this is the way to convince us developer that
: Microsoft languages are the ones we should continue investing our
: efforts on in the future? Give me a f***ing break here. Also, what if
: that 3rd party vendor is no longer in business (say his/her application
: works flawlessly, but he/she has "moved on")? What should we do then?
:
: WHAT THE HELL KIND OF A FIX IS THIS ANYWAY??!!!!??!!!!
:
: Hopefully I have read this situation all wrong and someone will post
: back correcting my thoughts on this.
:
: Rick
:
| |
| Rick Rothstein 2005-04-29, 4:03 am |
| You may be right; but I'm skeptical. First off, how do you know the two
mentioned DLL's were the only things changed in this Fix? Simply
unregistering/deleting and re-registering them may not be
well-coordinated way to uninstall the Fix. Also, if that is all it would
take, and since the Fix is directed at VB6 developers, you would think
the Note about the Fix not being uninstallable could have been left off.
I still think a Fix that might work here but not over there is a
terrible thing to foist on us. And, of course, if this proves to be a
major problem, then we are at Microsoft's mercy to perform an
out-of-support fix for the fix. Haven't we been waiting for something
like that for the SP6 release?
Rick
"Randy Birch" <rgb_removethis@mvps.org> wrote in message
news:OANl73GTFHA.2096@TK2MSFTNGP14.phx.gbl...
> I suspect that warning is for the benefit of end users who install the
fix
> with the expectation there would be an entry in add/remove programs if
> issues arose. I'm sure any competent developer could
unregister/delete
> mscomctl.ocx and comcl32.ocx and re-register earlier versions.
>
> --
>
> Randy Birch
> MS MVP Visual Basic
> http://vbnet.mvps.org/
> ----------------------------------------------------------------------
------
> Read. Decide. Sign the petition to Microsoft.
> http://classicvb.org/petition/
> ----------------------------------------------------------------------
------
>
>
>
> "Rick Rothstein" <rickNOSPAMnews@NOSPAMcomcast.net> wrote in message
> news:uSgwHoGTFHA.2336@TK2MSFTNGP12.phx.gbl...
> :> > http://support.microsoft.com/?id=896559
> : > >
> : > > FIX: The Windows Common Controls Mscomctl.ocx or Comctl32.ocx
may
> : cause
> : > > your
> : > > application or the Visual Basic 6 IDE to unexpectedly quit, or
you
> : may
> : > > receive a "Divide By Zero" error message.
> : > > APPLIES TO
> : > > Microsoft Visual Basic 6.0 Professional Edition
> : > > Microsoft Visual Basic 6.0 Enterprise Edition
> : > > Microsoft Visual Studio 6.0 Service Pack 5
> : > >
> : >
> : > From that page....
> : >
> : > "RESOLUTION
> : > Important note: If the application that you are running was
provided
> : to you
> : > by a third party, you may want to contact the third party that
> : provided the
> : > application to you before you install the fix. For example, you
did
> : not
> : > develop the application yourself. If you install this fix without
> : sufficient
> : > testing, the applications may stop functioning."
> : >
> : > ...any reports of breakage yet? I wonder what broke on their PCs
that
> : would
> : > prompt them to add that note... hmmm...
> :
> : [Rick, wildly waving his hands, trying to get everyone's attention]
> :
> : Excuse me! Uh, there was also this note in the cited Fix page:
> :
> : "Note: The enclosed fix cannot be uninstalled or removed after it is
> : installed."
> :
> : Now, this might seem like a stupid question but... what the hell are
we
> : supposed to do with this fix??!!!? Think about it. If we are using a
3rd
> : party application, we shouldn't apply the fix because it might
break.
> : Uh, isn't almost everything we run on our system provided by a 3rd
> : party? Is Microsoft saying these programs might stop working if we
fix
> : our system so that we can continue developing VB6 programs (that use
> : ListView I guess)? Now that is a hell of a trade-off for Microsoft
to
> : impose on us! Yep, it sure looks more and more like Microsoft will
do
> : whatever it can to make people stop using VB.Classic, doesn't it? Do
> : they really think this is the way to convince us developer that
> : Microsoft languages are the ones we should continue investing our
> : efforts on in the future? Give me a f***ing break here. Also, what
if
> : that 3rd party vendor is no longer in business (say his/her
application
> : works flawlessly, but he/she has "moved on")? What should we do
then?
> :
> : WHAT THE HELL KIND OF A FIX IS THIS ANYWAY??!!!!??!!!!
> :
> : Hopefully I have read this situation all wrong and someone will post
> : back correcting my thoughts on this.
> :
> : Rick
> :
>
| |
| Randy Birch 2005-04-29, 4:03 am |
| The file contains seven files:
ADVPACK.DLL
comctl32.ocx
KB896559.TXT
mscmupd.inf
mscomctl.ocx
W95INF16.DLL
W95INF32.DLL
The ADVPACK.DLL file is from 2002, as are the last two DLLs.
mscomctl.ocx is version 6.1.97.86, dated November 1, 2004 which puts it
around the time we initially raised the issue with the listview with MS.
A bug in comctl32.ocx show an incorrect date of August 18, 19103. The
version on my machine (which has VB6 SP5)is dated October 11, 1999 installed
with a version number of 6.0.81.5. The version of the fix comctl32 file is
6.0.81.6.
The INF file simply installs the two OCX files:
; INF file for Visual Basic 6.0 Run-time Redist Pack
[DefaultInstall]
CheckAdminRights=1
CopyFiles=install.files,install.file
[DestinationDirs]
install.files=11
install.file=11
[install.files]
MSCOMCTL.OCX,,MSCOMCTL.OCX,1064;
COMCTL32.OCX,,COMCTL32.OCX,1064;
[install.file]
KB896559.TXT,,KB896559.TXT,4;
[KB896559.TXT]
file-win32-x86=thiscab
[MSCOMCTL.OCX]
file-win32-x86=thiscab
FileVersion=6,1,97,86
[COMCTL32.OCX]
file-win32-x86=thiscab
FileVersion=6,0,81,6
[version]
signature="$CHICAGO$"
AdvancedINF=2.5,%BadAdvpackVer%
[SourceDisksNames]
1="default",,1
[Strings]
BadAdvpackVer="This setup requires a newer version of the Setup API"
--
Randy Birch
MS MVP Visual Basic
http://vbnet.mvps.org/
----------------------------------------------------------------------------
Read. Decide. Sign the petition to Microsoft.
http://classicvb.org/petition/
----------------------------------------------------------------------------
"Rick Rothstein" <rickNOSPAMnews@NOSPAMcomcast.net> wrote in message
news:OebIJEHTFHA.2912@TK2MSFTNGP10.phx.gbl...
: You may be right; but I'm skeptical. First off, how do you know the two
: mentioned DLL's were the only things changed in this Fix? Simply
: unregistering/deleting and re-registering them may not be
: well-coordinated way to uninstall the Fix. Also, if that is all it would
: take, and since the Fix is directed at VB6 developers, you would think
: the Note about the Fix not being uninstallable could have been left off.
: I still think a Fix that might work here but not over there is a
: terrible thing to foist on us. And, of course, if this proves to be a
: major problem, then we are at Microsoft's mercy to perform an
: out-of-support fix for the fix. Haven't we been waiting for something
: like that for the SP6 release?
:
: Rick
:
:
: "Randy Birch" <rgb_removethis@mvps.org> wrote in message
: news:OANl73GTFHA.2096@TK2MSFTNGP14.phx.gbl...
: > I suspect that warning is for the benefit of end users who install the
: fix
: > with the expectation there would be an entry in add/remove programs if
: > issues arose. I'm sure any competent developer could
: unregister/delete
: > mscomctl.ocx and comcl32.ocx and re-register earlier versions.
: >
: > --
: >
: > Randy Birch
: > MS MVP Visual Basic
: > http://vbnet.mvps.org/
: > ----------------------------------------------------------------------
: ------
: > Read. Decide. Sign the petition to Microsoft.
: > http://classicvb.org/petition/
: > ----------------------------------------------------------------------
: ------
: >
: >
: >
: > "Rick Rothstein" <rickNOSPAMnews@NOSPAMcomcast.net> wrote in message
: > news:uSgwHoGTFHA.2336@TK2MSFTNGP12.phx.gbl...
: > :> > http://support.microsoft.com/?id=896559
: > : > >
: > : > > FIX: The Windows Common Controls Mscomctl.ocx or Comctl32.ocx
: may
: > : cause
: > : > > your
: > : > > application or the Visual Basic 6 IDE to unexpectedly quit, or
: you
: > : may
: > : > > receive a "Divide By Zero" error message.
: > : > > APPLIES TO
: > : > > Microsoft Visual Basic 6.0 Professional Edition
: > : > > Microsoft Visual Basic 6.0 Enterprise Edition
: > : > > Microsoft Visual Studio 6.0 Service Pack 5
: > : > >
: > : >
: > : > From that page....
: > : >
: > : > "RESOLUTION
: > : > Important note: If the application that you are running was
: provided
: > : to you
: > : > by a third party, you may want to contact the third party that
: > : provided the
: > : > application to you before you install the fix. For example, you
: did
: > : not
: > : > develop the application yourself. If you install this fix without
: > : sufficient
: > : > testing, the applications may stop functioning."
: > : >
: > : > ...any reports of breakage yet? I wonder what broke on their PCs
: that
: > : would
: > : > prompt them to add that note... hmmm...
: > :
: > : [Rick, wildly waving his hands, trying to get everyone's attention]
: > :
: > : Excuse me! Uh, there was also this note in the cited Fix page:
: > :
: > : "Note: The enclosed fix cannot be uninstalled or removed after it is
: > : installed."
: > :
: > : Now, this might seem like a stupid question but... what the hell are
: we
: > : supposed to do with this fix??!!!? Think about it. If we are using a
: 3rd
: > : party application, we shouldn't apply the fix because it might
: break.
: > : Uh, isn't almost everything we run on our system provided by a 3rd
: > : party? Is Microsoft saying these programs might stop working if we
: fix
: > : our system so that we can continue developing VB6 programs (that use
: > : ListView I guess)? Now that is a hell of a trade-off for Microsoft
: to
: > : impose on us! Yep, it sure looks more and more like Microsoft will
: do
: > : whatever it can to make people stop using VB.Classic, doesn't it? Do
: > : they really think this is the way to convince us developer that
: > : Microsoft languages are the ones we should continue investing our
: > : efforts on in the future? Give me a f***ing break here. Also, what
: if
: > : that 3rd party vendor is no longer in business (say his/her
: application
: > : works flawlessly, but he/she has "moved on")? What should we do
: then?
: > :
: > : WHAT THE HELL KIND OF A FIX IS THIS ANYWAY??!!!!??!!!!
: > :
: > : Hopefully I have read this situation all wrong and someone will post
: > : back correcting my thoughts on this.
: > :
: > : Rick
: > :
: >
:
| |
| Jim Carlock 2005-04-29, 4:03 am |
| There are the problems with DLLCache and other storage locations of the
file as well. SFC/WFP will likely attempt to correct and then complain and
ask you to reinsert your Original CD.
You can download the update from the link. PowerArchiver or WinZip
will be able to uncompress the executable.
http://support.microsoft.com/?id=896559
Microsoft doesn't want to come out and say that WFP/SFC is the worst
idea they've ever put into effect, and it doesn't look like they want to tell
you how to get around it and make it public knowledge to everyone for
some reason.
comctl32.dll is found inside sfcfiles.dll as a protected file, but mscomctl.ocx
is not. So you'd only have to worry about comctl32.dll I think (to get around
the WFP/SFC problems).
--
Jim Carlock
Please post replies to newsgroup.
"Rick Rothstein" <rickNOSPAMnews@NOSPAMcomcast.net> wrote:
You may be right; but I'm skeptical. First off, how do you know the two
mentioned DLL's were the only things changed in this Fix? Simply
unregistering/deleting and re-registering them may not be
well-coordinated way to uninstall the Fix. Also, if that is all it would
take, and since the Fix is directed at VB6 developers, you would think
the Note about the Fix not being uninstallable could have been left off.
I still think a Fix that might work here but not over there is a
terrible thing to foist on us. And, of course, if this proves to be a
major problem, then we are at Microsoft's mercy to perform an
out-of-support fix for the fix. Haven't we been waiting for something
like that for the SP6 release?
Rick
"Randy Birch" <rgb_removethis@mvps.org> wrote:
> I suspect that warning is for the benefit of end users who install the fix
> with the expectation there would be an entry in add/remove programs if
> issues arose. I'm sure any competent developer could unregister/delete
> mscomctl.ocx and comcl32.ocx and re-register earlier versions.
>
> --
>
> Randy Birch
> MS MVP Visual Basic
> http://vbnet.mvps.org/
> ----------------------------------------------------------------------------
> Read. Decide. Sign the petition to Microsoft.
> http://classicvb.org/petition/
> ----------------------------------------------------------------------------
| |
| Randy Birch 2005-04-29, 4:03 am |
| .... one other point. The EULA file contains two sections. For developers
it's a simple:
The Microsoft COMCTL32.OCX AND MSCOMCTL.OCX Controls accompanying this
End-User License Agreement are provided by Microsoft to update validly
licensed copies of Microsoft Visual Basic 6.0 and Microsoft Visual Studio
6.0. These controls are also being provided as a standalone software web
download. If you have a validly licensed copy of Microsoft Visual Basic 6.0
or Microsoft Visual Studio 6.0 (each a "Microsoft Product"), these controls
are provided to you by Microsoft Corporation to update the Redist.txt
portion of such Microsoft Products and are subject to the terms and
conditions of the applicable end-user license agreement under which you
validly licensed the Microsoft Product.
If you don't own VB, you're an end user and a standard end-user EULA
applies, which is too big and typically legal to include here.
--
Randy Birch
MS MVP Visual Basic
http://vbnet.mvps.org/
----------------------------------------------------------------------------
Read. Decide. Sign the petition to Microsoft.
http://classicvb.org/petition/
----------------------------------------------------------------------------
"Rick Rothstein" <rickNOSPAMnews@NOSPAMcomcast.net> wrote in message
news:OebIJEHTFHA.2912@TK2MSFTNGP10.phx.gbl...
: You may be right; but I'm skeptical. First off, how do you know the two
: mentioned DLL's were the only things changed in this Fix? Simply
: unregistering/deleting and re-registering them may not be
: well-coordinated way to uninstall the Fix. Also, if that is all it would
: take, and since the Fix is directed at VB6 developers, you would think
: the Note about the Fix not being uninstallable could have been left off.
: I still think a Fix that might work here but not over there is a
: terrible thing to foist on us. And, of course, if this proves to be a
: major problem, then we are at Microsoft's mercy to perform an
: out-of-support fix for the fix. Haven't we been waiting for something
: like that for the SP6 release?
:
: Rick
:
:
: "Randy Birch" <rgb_removethis@mvps.org> wrote in message
: news:OANl73GTFHA.2096@TK2MSFTNGP14.phx.gbl...
: > I suspect that warning is for the benefit of end users who install the
: fix
: > with the expectation there would be an entry in add/remove programs if
: > issues arose. I'm sure any competent developer could
: unregister/delete
: > mscomctl.ocx and comcl32.ocx and re-register earlier versions.
: >
: > --
: >
: > Randy Birch
: > MS MVP Visual Basic
: > http://vbnet.mvps.org/
: > ----------------------------------------------------------------------
: ------
: > Read. Decide. Sign the petition to Microsoft.
: > http://classicvb.org/petition/
: > ----------------------------------------------------------------------
: ------
: >
: >
: >
: > "Rick Rothstein" <rickNOSPAMnews@NOSPAMcomcast.net> wrote in message
: > news:uSgwHoGTFHA.2336@TK2MSFTNGP12.phx.gbl...
: > :> > http://support.microsoft.com/?id=896559
: > : > >
: > : > > FIX: The Windows Common Controls Mscomctl.ocx or Comctl32.ocx
: may
: > : cause
: > : > > your
: > : > > application or the Visual Basic 6 IDE to unexpectedly quit, or
: you
: > : may
: > : > > receive a "Divide By Zero" error message.
: > : > > APPLIES TO
: > : > > Microsoft Visual Basic 6.0 Professional Edition
: > : > > Microsoft Visual Basic 6.0 Enterprise Edition
: > : > > Microsoft Visual Studio 6.0 Service Pack 5
: > : > >
: > : >
: > : > From that page....
: > : >
: > : > "RESOLUTION
: > : > Important note: If the application that you are running was
: provided
: > : to you
: > : > by a third party, you may want to contact the third party that
: > : provided the
: > : > application to you before you install the fix. For example, you
: did
: > : not
: > : > develop the application yourself. If you install this fix without
: > : sufficient
: > : > testing, the applications may stop functioning."
: > : >
: > : > ...any reports of breakage yet? I wonder what broke on their PCs
: that
: > : would
: > : > prompt them to add that note... hmmm...
: > :
: > : [Rick, wildly waving his hands, trying to get everyone's attention]
: > :
: > : Excuse me! Uh, there was also this note in the cited Fix page:
: > :
: > : "Note: The enclosed fix cannot be uninstalled or removed after it is
: > : installed."
: > :
: > : Now, this might seem like a stupid question but... what the hell are
: we
: > : supposed to do with this fix??!!!? Think about it. If we are using a
: 3rd
: > : party application, we shouldn't apply the fix because it might
: break.
: > : Uh, isn't almost everything we run on our system provided by a 3rd
: > : party? Is Microsoft saying these programs might stop working if we
: fix
: > : our system so that we can continue developing VB6 programs (that use
: > : ListView I guess)? Now that is a hell of a trade-off for Microsoft
: to
: > : impose on us! Yep, it sure looks more and more like Microsoft will
: do
: > : whatever it can to make people stop using VB.Classic, doesn't it? Do
: > : they really think this is the way to convince us developer that
: > : Microsoft languages are the ones we should continue investing our
: > : efforts on in the future? Give me a f***ing break here. Also, what
: if
: > : that 3rd party vendor is no longer in business (say his/her
: application
: > : works flawlessly, but he/she has "moved on")? What should we do
: then?
: > :
: > : WHAT THE HELL KIND OF A FIX IS THIS ANYWAY??!!!!??!!!!
: > :
: > : Hopefully I have read this situation all wrong and someone will post
: > : back correcting my thoughts on this.
: > :
: > : Rick
: > :
: >
:
| |
| Randy Birch 2005-04-29, 4:03 am |
| The fix does not include comctl32.dll ... just comctl32.ocx.
--
Randy Birch
MS MVP Visual Basic
http://vbnet.mvps.org/
----------------------------------------------------------------------------
Read. Decide. Sign the petition to Microsoft.
http://classicvb.org/petition/
----------------------------------------------------------------------------
"Jim Carlock" <anonymous@localhost> wrote in message
news:u$U%23NQHTFHA.2756@tk2msftngp13.phx.gbl...
: There are the problems with DLLCache and other storage locations of the
: file as well. SFC/WFP will likely attempt to correct and then complain and
: ask you to reinsert your Original CD.
:
: You can download the update from the link. PowerArchiver or WinZip
: will be able to uncompress the executable.
: http://support.microsoft.com/?id=896559
:
: Microsoft doesn't want to come out and say that WFP/SFC is the worst
: idea they've ever put into effect, and it doesn't look like they want to
tell
: you how to get around it and make it public knowledge to everyone for
: some reason.
:
: comctl32.dll is found inside sfcfiles.dll as a protected file, but
mscomctl.ocx
: is not. So you'd only have to worry about comctl32.dll I think (to get
around
: the WFP/SFC problems).
:
: --
: Jim Carlock
: Please post replies to newsgroup.
| |
| Jim Carlock 2005-04-29, 4:03 am |
| Oops. It's comctl32.ocx that is the new file. So neither one of the files are
listed as protected files inside sfcfiles.dll. Sorry about the confusion. Both
of the files in the update are ocx files. They both wrappers to comctl32.dll?
Disregard my previous post. I just deleted both of the files to see if they're
protected. And neither one of the files are protected on an XP system.
When I did the search through sfcfiles.dll I was searching for comctl32 and
for mscomctl. Comctl32 turned up but I wasn't paying too much attention,
it's a .dll and the files that are updated are both .ocx.
--
Jim Carlock
Please post replies to newsgroup.
"Jim Carlock" <anonymous@localhost> wrote:
There are the problems with DLLCache and other storage locations of the
file as well. SFC/WFP will likely attempt to correct and then complain and
ask you to reinsert your Original CD.
You can download the update from the link. PowerArchiver or WinZip
will be able to uncompress the executable.
http://support.microsoft.com/?id=896559
Microsoft doesn't want to come out and say that WFP/SFC is the worst
idea they've ever put into effect, and it doesn't look like they want to tell
you how to get around it and make it public knowledge to everyone for
some reason.
comctl32.dll is found inside sfcfiles.dll as a protected file, but mscomctl.ocx
is not. So you'd only have to worry about comctl32.dll I think (to get around
the WFP/SFC problems).
--
Jim Carlock
Please post replies to newsgroup.
"Rick Rothstein" <rickNOSPAMnews@NOSPAMcomcast.net> wrote:
You may be right; but I'm skeptical. First off, how do you know the two
mentioned DLL's were the only things changed in this Fix? Simply
unregistering/deleting and re-registering them may not be
well-coordinated way to uninstall the Fix. Also, if that is all it would
take, and since the Fix is directed at VB6 developers, you would think
the Note about the Fix not being uninstallable could have been left off.
I still think a Fix that might work here but not over there is a
terrible thing to foist on us. And, of course, if this proves to be a
major problem, then we are at Microsoft's mercy to perform an
out-of-support fix for the fix. Haven't we been waiting for something
like that for the SP6 release?
Rick
"Randy Birch" <rgb_removethis@mvps.org> wrote:
> I suspect that warning is for the benefit of end users who install the fix
> with the expectation there would be an entry in add/remove programs if
> issues arose. I'm sure any competent developer could unregister/delete
> mscomctl.ocx and comcl32.ocx and re-register earlier versions.
>
> --
>
> Randy Birch
> MS MVP Visual Basic
> http://vbnet.mvps.org/
> ----------------------------------------------------------------------------
> Read. Decide. Sign the petition to Microsoft.
> http://classicvb.org/petition/
> ----------------------------------------------------------------------------
| |
| Randy Birch 2005-04-29, 4:03 am |
| Only comctl32.ocx is a wrapper to the DLL. For VB6, MS decided to re-write
the functionality of the DLL into the OCX rather than make it dependent on
the DLL, which is why a VB5 common control under XP with a manifest will
display using Windows themed appearance naturally, while the VB6 controls
remain, well, VB6-ish.
--
Randy Birch
MS MVP Visual Basic
http://vbnet.mvps.org/
----------------------------------------------------------------------------
Read. Decide. Sign the petition to Microsoft.
http://classicvb.org/petition/
----------------------------------------------------------------------------
"Jim Carlock" <anonymous@localhost> wrote in message
news:OHjclcHTFHA.3464@tk2msftngp13.phx.gbl...
: Oops. It's comctl32.ocx that is the new file. So neither one of the files
are
: listed as protected files inside sfcfiles.dll. Sorry about the confusion.
Both
: of the files in the update are ocx files. They both wrappers to
comctl32.dll?
:
: Disregard my previous post. I just deleted both of the files to see if
they're
: protected. And neither one of the files are protected on an XP system.
:
: When I did the search through sfcfiles.dll I was searching for comctl32
and
: for mscomctl. Comctl32 turned up but I wasn't paying too much attention,
: it's a .dll and the files that are updated are both .ocx.
:
: --
: Jim Carlock
: Please post replies to newsgroup.
:
: "Jim Carlock" <anonymous@localhost> wrote:
: There are the problems with DLLCache and other storage locations of the
: file as well. SFC/WFP will likely attempt to correct and then complain and
: ask you to reinsert your Original CD.
:
: You can download the update from the link. PowerArchiver or WinZip
: will be able to uncompress the executable.
: http://support.microsoft.com/?id=896559
:
: Microsoft doesn't want to come out and say that WFP/SFC is the worst
: idea they've ever put into effect, and it doesn't look like they want to
tell
: you how to get around it and make it public knowledge to everyone for
: some reason.
:
: comctl32.dll is found inside sfcfiles.dll as a protected file, but
mscomctl.ocx
: is not. So you'd only have to worry about comctl32.dll I think (to get
around
: the WFP/SFC problems).
:
: --
: Jim Carlock
: Please post replies to newsgroup.
:
: "Rick Rothstein" <rickNOSPAMnews@NOSPAMcomcast.net> wrote:
: You may be right; but I'm skeptical. First off, how do you know the two
: mentioned DLL's were the only things changed in this Fix? Simply
: unregistering/deleting and re-registering them may not be
: well-coordinated way to uninstall the Fix. Also, if that is all it would
: take, and since the Fix is directed at VB6 developers, you would think
: the Note about the Fix not being uninstallable could have been left off.
: I still think a Fix that might work here but not over there is a
: terrible thing to foist on us. And, of course, if this proves to be a
: major problem, then we are at Microsoft's mercy to perform an
: out-of-support fix for the fix. Haven't we been waiting for something
: like that for the SP6 release?
:
: Rick
:
:
: "Randy Birch" <rgb_removethis@mvps.org> wrote:
: > I suspect that warning is for the benefit of end users who install the
fix
: > with the expectation there would be an entry in add/remove programs if
: > issues arose. I'm sure any competent developer could unregister/delete
: > mscomctl.ocx and comcl32.ocx and re-register earlier versions.
: >
: > --
: >
: > Randy Birch
: > MS MVP Visual Basic
: > http://vbnet.mvps.org/
:
> ----------------------------------------------------------------------------
: > Read. Decide. Sign the petition to Microsoft.
: > http://classicvb.org/petition/
:
> ----------------------------------------------------------------------------
:
:
:
| |
| Jim Carlock 2005-04-29, 4:03 am |
| The actual Modified Date on both of the files is: Friday, April 15, 2005
It's when you view the Comments in the file properties that you see the
strange date: August 18, 19103. Does anything ever use that (the
Comments)?
--
Jim Carlock
Please post replies to newsgroup.
"Randy Birch" <rgb_removethis@mvps.org> wrote:
The file contains seven files:
ADVPACK.DLL
comctl32.ocx
KB896559.TXT
mscmupd.inf
mscomctl.ocx
W95INF16.DLL
W95INF32.DLL
The ADVPACK.DLL file is from 2002, as are the last two DLLs.
mscomctl.ocx is version 6.1.97.86, dated November 1, 2004 which puts it
around the time we initially raised the issue with the listview with MS.
A bug in comctl32.ocx show an incorrect date of August 18, 19103. The
version on my machine (which has VB6 SP5)is dated October 11, 1999 installed
with a version number of 6.0.81.5. The version of the fix comctl32 file is
6.0.81.6.
The INF file simply installs the two OCX files:
; INF file for Visual Basic 6.0 Run-time Redist Pack
[DefaultInstall]
CheckAdminRights=1
CopyFiles=install.files,install.file
[DestinationDirs]
install.files=11
install.file=11
[install.files]
MSCOMCTL.OCX,,MSCOMCTL.OCX,1064;
COMCTL32.OCX,,COMCTL32.OCX,1064;
[install.file]
KB896559.TXT,,KB896559.TXT,4;
[KB896559.TXT]
file-win32-x86=thiscab
[MSCOMCTL.OCX]
file-win32-x86=thiscab
FileVersion=6,1,97,86
[COMCTL32.OCX]
file-win32-x86=thiscab
FileVersion=6,0,81,6
[version]
signature="$CHICAGO$"
AdvancedINF=2.5,%BadAdvpackVer%
[SourceDisksNames]
1="default",,1
[Strings]
BadAdvpackVer="This setup requires a newer version of the Setup API"
--
Randy Birch
MS MVP Visual Basic
http://vbnet.mvps.org/
----------------------------------------------------------------------------
Read. Decide. Sign the petition to Microsoft.
http://classicvb.org/petition/
----------------------------------------------------------------------------
"Rick Rothstein" <rickNOSPAMnews@NOSPAMcomcast.net> wrote in message
news:OebIJEHTFHA.2912@TK2MSFTNGP10.phx.gbl...
: You may be right; but I'm skeptical. First off, how do you know the two
: mentioned DLL's were the only things changed in this Fix? Simply
: unregistering/deleting and re-registering them may not be
: well-coordinated way to uninstall the Fix. Also, if that is all it would
: take, and since the Fix is directed at VB6 developers, you would think
: the Note about the Fix not being uninstallable could have been left off.
: I still think a Fix that might work here but not over there is a
: terrible thing to foist on us. And, of course, if this proves to be a
: major problem, then we are at Microsoft's mercy to perform an
: out-of-support fix for the fix. Haven't we been waiting for something
: like that for the SP6 release?
:
: Rick
:
:
: "Randy Birch" <rgb_removethis@mvps.org> wrote in message
: news:OANl73GTFHA.2096@TK2MSFTNGP14.phx.gbl...
: > I suspect that warning is for the benefit of end users who install the
: fix
: > with the expectation there would be an entry in add/remove programs if
: > issues arose. I'm sure any competent developer could
: unregister/delete
: > mscomctl.ocx and comcl32.ocx and re-register earlier versions.
: >
: > --
: >
: > Randy Birch
: > MS MVP Visual Basic
: > http://vbnet.mvps.org/
: > ----------------------------------------------------------------------
: ------
: > Read. Decide. Sign the petition to Microsoft.
: > http://classicvb.org/petition/
: > ----------------------------------------------------------------------
: ------
: >
: >
: >
: > "Rick Rothstein" <rickNOSPAMnews@NOSPAMcomcast.net> wrote in message
: > news:uSgwHoGTFHA.2336@TK2MSFTNGP12.phx.gbl...
: > :> > http://support.microsoft.com/?id=896559
: > : > >
: > : > > FIX: The Windows Common Controls Mscomctl.ocx or Comctl32.ocx
: may
: > : cause
: > : > > your
: > : > > application or the Visual Basic 6 IDE to unexpectedly quit, or
: you
: > : may
: > : > > receive a "Divide By Zero" error message.
: > : > > APPLIES TO
: > : > > Microsoft Visual Basic 6.0 Professional Edition
: > : > > Microsoft Visual Basic 6.0 Enterprise Edition
: > : > > Microsoft Visual Studio 6.0 Service Pack 5
: > : > >
: > : >
: > : > From that page....
: > : >
: > : > "RESOLUTION
: > : > Important note: If the application that you are running was
: provided
: > : to you
: > : > by a third party, you may want to contact the third party that
: > : provided the
: > : > application to you before you install the fix. For example, you
: did
: > : not
: > : > develop the application yourself. If you install this fix without
: > : sufficient
: > : > testing, the applications may stop functioning."
: > : >
: > : > ...any reports of breakage yet? I wonder what broke on their PCs
: that
: > : would
: > : > prompt them to add that note... hmmm...
: > :
: > : [Rick, wildly waving his hands, trying to get everyone's attention]
: > :
: > : Excuse me! Uh, there was also this note in the cited Fix page:
: > :
: > : "Note: The enclosed fix cannot be uninstalled or removed after it is
: > : installed."
: > :
: > : Now, this might seem like a stupid question but... what the hell are
: we
: > : supposed to do with this fix??!!!? Think about it. If we are using a
: 3rd
: > : party application, we shouldn't apply the fix because it might
: break.
: > : Uh, isn't almost everything we run on our system provided by a 3rd
: > : party? Is Microsoft saying these programs might stop working if we
: fix
: > : our system so that we can continue developing VB6 programs (that use
: > : ListView I guess)? Now that is a hell of a trade-off for Microsoft
: to
: > : impose on us! Yep, it sure looks more and more like Microsoft will
: do
: > : whatever it can to make people stop using VB.Classic, doesn't it? Do
: > : they really think this is the way to convince us developer that
: > : Microsoft languages are the ones we should continue investing our
: > : efforts on in the future? Give me a f***ing break here. Also, what
: if
: > : that 3rd party vendor is no longer in business (say his/her
: application
: > : works flawlessly, but he/she has "moved on")? What should we do
: then?
: > :
: > : WHAT THE HELL KIND OF A FIX IS THIS ANYWAY??!!!!??!!!!
: > :
: > : Hopefully I have read this situation all wrong and someone will post
: > : back correcting my thoughts on this.
: > :
: > : Rick
: > :
: >
:
| |
| Rick Rothstein 2005-04-29, 9:03 am |
| Thanks Randy (and you too Jim)... I'm not skeptical anymore.<g>
Rick
"Randy Birch" <rgb_removethis@mvps.org> wrote in message
news:OeFrhQHTFHA.2432@TK2MSFTNGP12.phx.gbl...
> The file contains seven files:
>
> ADVPACK.DLL
> comctl32.ocx
> KB896559.TXT
> mscmupd.inf
> mscomctl.ocx
> W95INF16.DLL
> W95INF32.DLL
>
> The ADVPACK.DLL file is from 2002, as are the last two DLLs.
>
> mscomctl.ocx is version 6.1.97.86, dated November 1, 2004 which puts
it
> around the time we initially raised the issue with the listview with
MS.
>
> A bug in comctl32.ocx show an incorrect date of August 18, 19103. The
> version on my machine (which has VB6 SP5)is dated October 11, 1999
installed
> with a version number of 6.0.81.5. The version of the fix comctl32
file is
> 6.0.81.6.
>
>
> The INF file simply installs the two OCX files:
>
> ; INF file for Visual Basic 6.0 Run-time Redist Pack
>
> [DefaultInstall]
> CheckAdminRights=1
> CopyFiles=install.files,install.file
>
> [DestinationDirs]
> install.files=11
> install.file=11
>
> [install.files]
> MSCOMCTL.OCX,,MSCOMCTL.OCX,1064;
> COMCTL32.OCX,,COMCTL32.OCX,1064;
>
> [install.file]
> KB896559.TXT,,KB896559.TXT,4;
>
> [KB896559.TXT]
> file-win32-x86=thiscab
>
> [MSCOMCTL.OCX]
> file-win32-x86=thiscab
> FileVersion=6,1,97,86
>
> [COMCTL32.OCX]
> file-win32-x86=thiscab
> FileVersion=6,0,81,6
>
> [version]
> signature="$CHICAGO$"
> AdvancedINF=2.5,%BadAdvpackVer%
>
> [SourceDisksNames]
> 1="default",,1
>
> [Strings]
> BadAdvpackVer="This setup requires a newer version of the Setup API"
>
>
> --
>
> Randy Birch
> MS MVP Visual Basic
> http://vbnet.mvps.org/
> ----------------------------------------------------------------------
------
> Read. Decide. Sign the petition to Microsoft.
> http://classicvb.org/petition/
> ----------------------------------------------------------------------
------
>
>
>
> "Rick Rothstein" <rickNOSPAMnews@NOSPAMcomcast.net> wrote in message
> news:OebIJEHTFHA.2912@TK2MSFTNGP10.phx.gbl...
> : You may be right; but I'm skeptical. First off, how do you know the
two
> : mentioned DLL's were the only things changed in this Fix? Simply
> : unregistering/deleting and re-registering them may not be
> : well-coordinated way to uninstall the Fix. Also, if that is all it
would
> : take, and since the Fix is directed at VB6 developers, you would
think
> : the Note about the Fix not being uninstallable could have been left
off.
> : I still think a Fix that might work here but not over there is a
> : terrible thing to foist on us. And, of course, if this proves to be
a
> : major problem, then we are at Microsoft's mercy to perform an
> : out-of-support fix for the fix. Haven't we been waiting for
something
> : like that for the SP6 release?
> :
> : Rick
> :
> :
> : "Randy Birch" <rgb_removethis@mvps.org> wrote in message
> : news:OANl73GTFHA.2096@TK2MSFTNGP14.phx.gbl...
> : > I suspect that warning is for the benefit of end users who install
the
> : fix
> : > with the expectation there would be an entry in add/remove
programs if
> : > issues arose. I'm sure any competent developer could
> : unregister/delete
> : > mscomctl.ocx and comcl32.ocx and re-register earlier versions.
> : >
> : > --
> : >
> : > Randy Birch
> : > MS MVP Visual Basic
> : > http://vbnet.mvps.org/
> :
> ----------------------------------------------------------------------
> : ------
> : > Read. Decide. Sign the petition to Microsoft.
> : > http://classicvb.org/petition/
> :
> ----------------------------------------------------------------------
> : ------
> : >
> : >
> : >
> : > "Rick Rothstein" <rickNOSPAMnews@NOSPAMcomcast.net> wrote in
message
> : > news:uSgwHoGTFHA.2336@TK2MSFTNGP12.phx.gbl...
> : > :> > http://support.microsoft.com/?id=896559
> : > : > >
> : > : > > FIX: The Windows Common Controls Mscomctl.ocx or
Comctl32.ocx
> : may
> : > : cause
> : > : > > your
> : > : > > application or the Visual Basic 6 IDE to unexpectedly quit,
or
> : you
> : > : may
> : > : > > receive a "Divide By Zero" error message.
> : > : > > APPLIES TO
> : > : > > Microsoft Visual Basic 6.0 Professional Edition
> : > : > > Microsoft Visual Basic 6.0 Enterprise Edition
> : > : > > Microsoft Visual Studio 6.0 Service Pack 5
> : > : > >
> : > : >
> : > : > From that page....
> : > : >
> : > : > "RESOLUTION
> : > : > Important note: If the application that you are running was
> : provided
> : > : to you
> : > : > by a third party, you may want to contact the third party that
> : > : provided the
> : > : > application to you before you install the fix. For example,
you
> : did
> : > : not
> : > : > develop the application yourself. If you install this fix
without
> : > : sufficient
> : > : > testing, the applications may stop functioning."
> : > : >
> : > : > ...any reports of breakage yet? I wonder what broke on their
PCs
> : that
> : > : would
> : > : > prompt them to add that note... hmmm...
> : > :
> : > : [Rick, wildly waving his hands, trying to get everyone's
attention]
> : > :
> : > : Excuse me! Uh, there was also this note in the cited Fix page:
> : > :
> : > : "Note: The enclosed fix cannot be uninstalled or removed after
it is
> : > : installed."
> : > :
> : > : Now, this might seem like a stupid question but... what the hell
are
> : we
> : > : supposed to do with this fix??!!!? Think about it. If we are
using a
> : 3rd
> : > : party application, we shouldn't apply the fix because it might
> : break.
> : > : Uh, isn't almost everything we run on our system provided by a
3rd
> : > : party? Is Microsoft saying these programs might stop working if
we
> : fix
> : > : our system so that we can continue developing VB6 programs (that
use
> : > : ListView I guess)? Now that is a hell of a trade-off for
Microsoft
> : to
> : > : impose on us! Yep, it sure looks more and more like Microsoft
will
> : do
> : > : whatever it can to make people stop using VB.Classic, doesn't
it? Do
> : > : they really think this is the way to convince us developer that
> : > : Microsoft languages are the ones we should continue investing
our
> : > : efforts on in the future? Give me a f***ing break here. Also,
what
> : if
> : > : that 3rd party vendor is no longer in business (say his/her
> : application
> : > : works flawlessly, but he/she has "moved on")? What should we do
> : then?
> : > :
> : > : WHAT THE HELL KIND OF A FIX IS THIS ANYWAY??!!!!??!!!!
> : > :
> : > : Hopefully I have read this situation all wrong and someone will
post
> : > : back correcting my thoughts on this.
> : > :
> : > : Rick
> : > :
> : >
> :
>
| |
| Jim Carlock 2005-04-29, 4:03 pm |
| Testing the new mscomctl.ocx running on XP SP2, and the column reordering
bug with the listview control seems to be fixed.
The following was tested:
Under Project, Components,
Microsoft Windows Common Controls 6.0 (SP6)
Filename: C:\WINDOWS\system32\mscomctl.ocx
File Version: 6.01.97.86
Mod Date: Friday, April 15, 2005, 7:58:16 PM
The code used on a form with a listview control named lvMain:
Option Explicit
Private Const MIN_WIDTH As Long = 4800&
Private Const MIN_HEIGHT As Long = 3600&
Private Sub Form_Load()
Dim itmX As ListItem
With lvMain
.Visible = False
.Appearance = ccFlat
.AllowColumnReorder = True
.FlatScrollBar = True
.View = lvwReport
.Sorted = False
.ColumnHeaders.Add , , "Test3"
.ColumnHeaders.Add , , "Test4"
.Appearance = ccFlat
.View = lvwReport
'no rows yet
Dim ir As Long, ic As Long, sR As String, sC As String
Dim sRow As String, sItem As String
sRow = "Row": sItem = "Item"
For ir = 1 To 138000
'ten rows
sR = Format$(CStr(ir), "0000000")
Set itmX = .ListItems.Add(, , (sRow & sR & " " & sItem & CStr(1)))
For ic = 2 To 4
sC = CStr(ic)
'four columns already built
If ic = 1 Then
Else
'itmX.SubItems(1) = "Row1Item2"
'itmX.SubItems(2) = "Row1Item3"
'itmX.SubItems(3) = "Row1Item4"
itmX.SubItems(ic - 1) = (sRow & sR & " " & sItem & sC)
End If
Next ic
Next ir
'.ListItems.Item(0).Text = "Item1"
'.ListItems.Item(1).Text = "Item2"
.Visible = True
End With
End Sub
Private Sub Form_Resize()
Dim h As Long, w As Long
'4800 4605
w = Me.Width
'3600 2535
h = Me.Height
If w <= MIN_WIDTH Then
Me.Enabled = False
w = MIN_WIDTH
End If
If h <= MIN_HEIGHT Then
Me.Enabled = False
h = MIN_HEIGHT
End If
With lvMain
Call .Move(.Left, .Top, (w - 195), (h - 1065))
End With
With Me
Call .Move(.Left, .Top, w, h)
.Enabled = True
End With
End Sub
The only thing I currently have a problem with (that I'm noticing), is that
I'm missing a scrollbar. I was thinking it should automatically appear. It
automatically appears if .FlatScrollBar is set to False, but it does NOT
appear when it's set to true.
--
Jim Carlock
Please post replies to newsgroup.
"Randy Birch" <rgb_removethis@mvps.org> wrote:
Only comctl32.ocx is a wrapper to the DLL. For VB6, MS decided to re-write
the functionality of the DLL into the OCX rather than make it dependent on
the DLL, which is why a VB5 common control under XP with a manifest will
display using Windows themed appearance naturally, while the VB6 controls
remain, well, VB6-ish.
--
Randy Birch
MS MVP Visual Basic
http://vbnet.mvps.org/
----------------------------------------------------------------------------
Read. Decide. Sign the petition to Microsoft.
http://classicvb.org/petition/
----------------------------------------------------------------------------
| |
| Ken Halter 2005-04-29, 4:03 pm |
| "Jim Carlock" <anonymous@localhost> wrote in message
news:uu5sa%23NTFHA.2908@TK2MSFTNGP10.phx.gbl...
> Testing the new mscomctl.ocx running on XP SP2, and the column reordering
> bug with the listview control seems to be fixed.
>
>
> The only thing I currently have a problem with (that I'm noticing), is
> that
> I'm missing a scrollbar. I was thinking it should automatically appear. It
> automatically appears if .FlatScrollBar is set to False, but it does NOT
> appear when it's set to true.
>
> --
> Jim Carlock
> Please post replies to newsgroup.
FlatScrollbar support has always had problems <g> To me, the real question
is.... what apps did it break?...and, if we package this thing up and deploy
it, who's PC's gonna get trashed? <g>
Text below's a repost from yesterday if you missed it....
From that page....
"RESOLUTION
Important note: If the application that you are running was provided to you
by a third party, you may want to contact the third party that provided the
application to you before you install the fix. For example, you did not
develop the application yourself. If you install this fix without sufficient
testing, the applications may stop functioning."
....any reports of breakage yet? I wonder what broke on their PCs that would
prompt them to add that note... hmmm...
--
Ken Halter - MS-MVP-VB - http://www.vbsight.com
Sign up now to help keep VB support alive - http://classicvb.org/petition
Please keep all discussions in the groups..
|
|
|
|
|