Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.basic.visual.misc > #2101 > unrolled thread
| Started by | HarryC |
|---|---|
| First post | 2014-05-13 20:10 -0400 |
| Last post | 2014-05-20 06:46 -0400 |
| Articles | 5 — 3 participants |
Back to article view | Back to comp.lang.basic.visual.misc
comctl32.ocx HarryC - 2014-05-13 20:10 -0400
Re: comctl32.ocx GS <gs@somewhere.net> - 2014-05-13 21:12 -0400
Re: comctl32.ocx ralph <nt_consulting@yahoo.com> - 2014-05-13 20:46 -0500
Re: comctl32.ocx HarryC - 2014-05-14 06:01 -0400
Re: comctl32.ocx HarryC - 2014-05-20 06:46 -0400
| From | HarryC |
|---|---|
| Date | 2014-05-13 20:10 -0400 |
| Subject | comctl32.ocx |
| Message-ID | <dmc5n9hbcv47iv9ifq1gqac2ii20fgdfd6@4ax.com> |
I have a VB6 SP6 app that up until now has been installing and running just fine on Windows 8 64. Now I have a HP Windows 8 64 that returns an error when trying to register the comctl32.ocx. There are other .ocx's that get registered when installed just not comctl32.ocx. the client tells me that they can't even register or unregister it manually. Any idea's thanks Harry
[toc] | [next] | [standalone]
| From | GS <gs@somewhere.net> |
|---|---|
| Date | 2014-05-13 21:12 -0400 |
| Message-ID | <lkuftc$8gq$1@dont-email.me> |
| In reply to | #2101 |
> I have a VB6 SP6 app that up until now has been installing and > running just fine on Windows 8 64. Now I have a HP Windows 8 64 that > returns an error when trying to register the comctl32.ocx. There are > other .ocx's that get registered when installed just not > comctl32.ocx. the client tells me that they can't even register or > unregister it manually. Any idea's > > thanks > Harry If it's a corporate net it's probably Group Policy related issue. Using a manifest obviates this problem completely! -- Garry Free usenet access at http://www.eternal-september.org Classic VB Users Regroup! comp.lang.basic.visual.misc microsoft.public.vb.general.discussion
[toc] | [prev] | [next] | [standalone]
| From | ralph <nt_consulting@yahoo.com> |
|---|---|
| Date | 2014-05-13 20:46 -0500 |
| Message-ID | <lpg5n9dhu55gj0f8944ad8i1228elgj4uf@4ax.com> |
| In reply to | #2101 |
On Tue, 13 May 2014 20:10:14 -0400, HarryC wrote:
>I have a VB6 SP6 app that up until now has been installing and running
>just fine on Windows 8 64. Now I have a HP Windows 8 64 that returns
>an error when trying to register the comctl32.ocx. There are other
>.ocx's that get registered when installed just not comctl32.ocx.
>the client tells me that they can't even register or unregister it
>manually. Any idea's
>
Not enough information:
What is the actual error?
When does the error happen? When your application is installed? When
your application is loaded? Etc?
What version of Windows IExplorer are you using?
Does your application in fact use comctl32.ocx or msconctrl.ocx.
Also it is a tad confusing because you say "I have a HP Windows 8 64",
then you suggest it is "the client" that says they can't register or
unregister the component manually. Who is this you? Or them?
With limited information a best guess is that your "client" doesn't
know how to register 32-bit components on a 64-bit platform.
1) 32-bit components on a 64-bit platform are installed in the
c:\windows\sysWOW64\ folder
2) Make sure this is where comctl32.ocx is located.
2b) If not found then have them download and install ...
"Microsoft Visual Basic 6.0 Common Controls"
http://www.microsoft.com/en-us/download/details.aspx?id=10019
2c) This should install and register the component, but if not
then proceed to manually registering it ...
3) Open a CMD prompt *as Administrator*
You must have administrator priviledge.
4) In the Window change directory to the sysWOW64 folder
5) Register the component by using
regsvr32 comctl32.ocx
Notes:
a) There is a "regsvr32" located in both the sysWOW64 and the System32
folder. One needs to use the appropriate one to register either 32-bit
or 64-bit components.
b) Both are suppose to be identical and suppose to automatically
detect the bit-ness of the target and adjust accordingly. Sometimes
this seems to fail. Migrating to the correct folder and registering in
place insures bit-ness will be detected.
c) There are other obscure problems that may be occurring. They are
rare. If the above doesn't work, report back with more information.
-ralph
[toc] | [prev] | [next] | [standalone]
| From | HarryC |
|---|---|
| Date | 2014-05-14 06:01 -0400 |
| Message-ID | <0ff6n9lisfo03on6ar2p4ptl91j40u90k8@4ax.com> |
| In reply to | #2103 |
On Tue, 13 May 2014 20:46:20 -0500, ralph <nt_consulting@yahoo.com> wrote: >On Tue, 13 May 2014 20:10:14 -0400, HarryC wrote: > >>I have a VB6 SP6 app that up until now has been installing and running >>just fine on Windows 8 64. Now I have a HP Windows 8 64 that returns >>an error when trying to register the comctl32.ocx. There are other >>.ocx's that get registered when installed just not comctl32.ocx. >>the client tells me that they can't even register or unregister it >>manually. Any idea's >> > >Not enough information: >What is the actual error? >When does the error happen? When your application is installed? When >your application is loaded? Etc? >What version of Windows IExplorer are you using? >Does your application in fact use comctl32.ocx or msconctrl.ocx. > >Also it is a tad confusing because you say "I have a HP Windows 8 64", >then you suggest it is "the client" that says they can't register or >unregister the component manually. Who is this you? Or them? > >With limited information a best guess is that your "client" doesn't >know how to register 32-bit components on a 64-bit platform. > >1) 32-bit components on a 64-bit platform are installed in the > c:\windows\sysWOW64\ folder >2) Make sure this is where comctl32.ocx is located. >2b) If not found then have them download and install ... > "Microsoft Visual Basic 6.0 Common Controls" > http://www.microsoft.com/en-us/download/details.aspx?id=10019 >2c) This should install and register the component, but if not > then proceed to manually registering it ... >3) Open a CMD prompt *as Administrator* > You must have administrator priviledge. >4) In the Window change directory to the sysWOW64 folder >5) Register the component by using > regsvr32 comctl32.ocx > >Notes: >a) There is a "regsvr32" located in both the sysWOW64 and the System32 >folder. One needs to use the appropriate one to register either 32-bit >or 64-bit components. >b) Both are suppose to be identical and suppose to automatically >detect the bit-ness of the target and adjust accordingly. Sometimes >this seems to fail. Migrating to the correct folder and registering in >place insures bit-ness will be detected. >c) There are other obscure problems that may be occurring. They are >rare. If the above doesn't work, report back with more information. > >-ralph > > > Ok guys thanks In a couple of days I'll be looking at the client's computer and be able to get a better handle of the problem. I just wanted to have enough information before i got there. Thanks again Harry
[toc] | [prev] | [next] | [standalone]
| From | HarryC |
|---|---|
| Date | 2014-05-20 06:46 -0400 |
| Message-ID | <1hcmn9hvhjsini11n6qnmjdcvdmgrsptg9@4ax.com> |
| In reply to | #2105 |
On Wed, 14 May 2014 06:01:41 -0400, HarryC wrote: >On Tue, 13 May 2014 20:46:20 -0500, ralph <nt_consulting@yahoo.com> >wrote: > >>On Tue, 13 May 2014 20:10:14 -0400, HarryC wrote: >> >>>I have a VB6 SP6 app that up until now has been installing and running >>>just fine on Windows 8 64. Now I have a HP Windows 8 64 that returns >>>an error when trying to register the comctl32.ocx. There are other >>>.ocx's that get registered when installed just not comctl32.ocx. >>>the client tells me that they can't even register or unregister it >>>manually. Any idea's >>> >> >>Not enough information: >>What is the actual error? >>When does the error happen? When your application is installed? When >>your application is loaded? Etc? >>What version of Windows IExplorer are you using? >>Does your application in fact use comctl32.ocx or msconctrl.ocx. >> >>Also it is a tad confusing because you say "I have a HP Windows 8 64", >>then you suggest it is "the client" that says they can't register or >>unregister the component manually. Who is this you? Or them? >> >>With limited information a best guess is that your "client" doesn't >>know how to register 32-bit components on a 64-bit platform. >> >>1) 32-bit components on a 64-bit platform are installed in the >> c:\windows\sysWOW64\ folder >>2) Make sure this is where comctl32.ocx is located. >>2b) If not found then have them download and install ... >> "Microsoft Visual Basic 6.0 Common Controls" >> http://www.microsoft.com/en-us/download/details.aspx?id=10019 >>2c) This should install and register the component, but if not >> then proceed to manually registering it ... >>3) Open a CMD prompt *as Administrator* >> You must have administrator priviledge. >>4) In the Window change directory to the sysWOW64 folder >>5) Register the component by using >> regsvr32 comctl32.ocx >> >>Notes: >>a) There is a "regsvr32" located in both the sysWOW64 and the System32 >>folder. One needs to use the appropriate one to register either 32-bit >>or 64-bit components. >>b) Both are suppose to be identical and suppose to automatically >>detect the bit-ness of the target and adjust accordingly. Sometimes >>this seems to fail. Migrating to the correct folder and registering in >>place insures bit-ness will be detected. >>c) There are other obscure problems that may be occurring. They are >>rare. If the above doesn't work, report back with more information. >> >>-ralph >> >> >> > >Ok guys thanks >In a couple of days I'll be looking at the client's computer and be >able to get a better handle of the problem. I just wanted to have >enough information before i got there. > >Thanks again >Harry > I Finally got to look at the machine. They thought they were logged in as an administrator. Thanks again guys
[toc] | [prev] | [standalone]
Back to top | Article view | comp.lang.basic.visual.misc
csiph-web