Hi friends

[Andy Master]

Someone knows, how I can register the controls ocx in syswow64 without using cmd?

[Arnoutdv]

Did you copy them manually??

[TysonLPrice]

Someone knows, how I can register the controls ocx in syswow64 without using cmd?

You could put the command in a .bat file and register it by shelling it.

[Inside]

You could put the command in a .bat file and register it by shelling it.

This is how my .bat file looks like.

I use the bat name: !!! aaa vb Add Control.bat
Then a space and then the control name, enter.

But an easier method, is this (wrote it now just for you, but we all can use it! ) :


Here's the layout:


and the code:

Private Sub Command1_Click()

   xx = Shell("regsvr32.exe" + " " + Chr$(34) + Text1.Text + Chr$(34), vbNormalFocus)

End Sub

Sometimes it took long to copy the path and the name of the file, but you can use a little program like this (Myself):
The program:


The code:

Dim PaD$
Private Sub Dir1_Change()
   File1.Path = Dir1.Path
   TeX.Text = Dir1
   
   If Right$(Dir1, 1) = "\" Then
      PaD$ = Dir1
   Else
      PaD$ = Dir1 + "\"
   End If
End Sub

Private Sub Drive1_Change()

   Dir1.Path = Drive1.Drive

End Sub

Private Sub File1_Click()

   TeX.Text = PaD$ + File1

End Sub

Private Sub TeX_Click()

   If Che.Value = 1 Then
      TeX.SetFocus
      TeX.SelStart = 0
      TeX.SelLength = Len(TeX.Text)
      SendKeys "^C"
   End If

End Sub

Hope it helps

[Arnoutdv]

Normally you don't need to register a component which is located in syswow64. :-/

[TysonLPrice]

Normally you don't need to register a component which is located in syswow64. :-/

That depends on how it got there.

[Andy Master]

Thanks friends, I really have used CMD, but it takes long time....
I have Windows 10 64 bits, in cmd, it takes a lot of time listing to give permissions, I do not know if there is any other way, other than using cmd, I takes one minute but in other pcs, could be takes more...
My recent code in vb6 with cmd for to do it is this...

Public Function RegistrarOcxDllWin64(ByVal Hwnd As Long, Optional ByRef DireccionD As Variant) As Boolean
On Error Resume Next
If Not EsMatriz(DireccionD) Then
    If DireccionD = "" Then GoSub AgregarDD
End If

Dim C As String
Dim Direccion As String, I As Long, NR As Integer

SendMessage Hwnd, BCM_SETSHIELD, 0&, 1&

'Concatenar C, "/Q", True
Concatenar C, "@echo off", True
Concatenar C, "IF ERRORLEVEL 2 GOTO ERROR", True
Concatenar C, "takeown /f " & LeerRutaEspecial(WindowsCarpetaIni, True, "SysWOW64") & " /r /d s", True
Concatenar C, "icacls " & LeerRutaEspecial(WindowsCarpetaIni, True, "SysWOW64") & " /grant Administradores:F /t", True

If EsMatriz(DireccionD) Then
    For I = LBound(DireccionD) To UBound(DireccionD)
        If DireccionD(I) = "" Then GoTo S1
    Direccion = DireccionD(I)
    GoSub AgregarC
    SumVar NR
S1:

    Next I
Else
    If Direccion = "" Then GoTo S2
Direccion = CStr(DireccionD)
GoSub AgregarC
SumVar NR
S2:
End If


If NR < 1 Then Exit Function
Concatenar C, "CD " & LeerRutaEspecial(WindowsCarpetaIni, True, "System32\"), True

If EsMatriz(DireccionD) Then
    For I = LBound(DireccionD) To UBound(DireccionD)
    Direccion = DireccionD(I)
    GoSub AgregarR
    Next I
Else
Direccion = DireccionD
GoSub AgregarR
End If

Concatenar C, "EXIT", True
Concatenar C, ":ERROR", True

EscribirArchivo C, DirAct(True) & "ACMDExt.bat"

Dim H2 As Long
H2 = ShellExecute(Hwnd, "runas", DirAct(True) & "ACMDExt.bat", "", CurDir$(), vbHide)

I = 0
Do While ExisteProceso("CMD.EXE")
Sleep 1000
SumVar I
    If I >= 120 Then Exit Do
Loop
Dim NC As Long ' Numero de Comprobaciones

If EsMatriz(DireccionD) Then
    For I = LBound(DireccionD) To UBound(DireccionD)
    Direccion = DireccionD(I)

        If ExisteAC(LeerRutaEspecial(WindowsCarpetaIni, True, "SysWOW64\") & SNA(Direccion)) Then SumVar NC

    Next I
Else
    Direccion = DireccionD
    If ExisteAC(LeerRutaEspecial(WindowsCarpetaIni, True, "SysWOW64\") & SNA(Direccion)) Then SumVar NC
    
End If

If NR = NC Then RegistrarOcxDllWin64 = True
EliminarArchivo DirAct(True) & "ACMDExt.bat", True

Exit Function
AgregarC:
Concatenar C, "CD " & SoloPath(Direccion), True
Concatenar C, "Copy " & SNA(Direccion) & " " & LeerRutaEspecial(WindowsCarpetaIni, True, "SysWOW64\ /Y"), True
Return
AgregarR:
Concatenar C, "regsvr32.exe /S " & LeerRutaEspecial(WindowsCarpetaIni, True, "SysWOW64\" & SNA(Direccion)), True
Return
AgregarDD:
Dim UDD As Long
UDD = -1
Agregar:
GoSub AgregarDDD

DireccionD(UDD) = OpenDialog(, "Ocx o Dll|*.Ocx;*.Dll", "Registrar ocx o dll")

If DireccionD(UDD) = "" And UDD < 1 Then Exit Function
If DireccionD(UDD) = "" Then
ReDim Preserve DireccionD(UDD - 1): SumVar UDD, -1
Else
    If Msg("¿Quiere agregar otra ocx o dll a registrar?", vbQuestion + vbYesNo, "Agregar otra dll u ocx") = vbYes Then GoTo Agregar
End If

Ya:
Return

AgregarDDD:
If UBound(DireccionD) < 0 Then
ReDim DireccionD(0)
Else
ReDim Preserve DireccionD(UDD + 1)
End If

UDD = UBound(DireccionD)

Return

End Function

I have made other functions like Concatenar, SumVar, Leerrutaespecial, many months ago...
But I need to know, how to register the ocx with admin permissions with vb6 only

I hope that my code helps you understand me, and if it works for you, I would like that too.
Sorry for my English
Greetings.

[Inside]

The register Control program I written yesterday, here it is in after I modified it a bit:

!Control Register JJ.zip

[Arnoutdv]

@Andy Master, why not use a normal installer instead of copying and registering OCX files yourself?
This can really mess up someones installation.

[Andy Master]

Thanks Inside, but it doesn't work in my windows 10 64 bits, but I appreciate your help.

In previous versions of windows this worked fine.

I have a PC with WinXP and this one with Win10.

I am seeing many changes now with this windows 10, since I had always used windows xp, but I will have to keep investigating until I find a faster solution.

Thanks a lot again.

[Andy Master]

Hi Arnoutdv.
I do not know how to use the msi installer with my programs, if you can explain how to do it I would greatly appreciate it.

[Inside]

Thanks Inside, but it doesn't work in my windows 10 64 bits, but I appreciate your help.

Strange... I only use windows 10 64...

You can:
[folder where VB6 is installed]\VB6.EXE RClick and set Properties:

[Arnoutdv]

I assume it's not for your own PC, so you really should use an installer or switch to Side-by-Side installations.
Otherwise you are going to ruin some windows installations

[Andy Master]

I wanted to register that ocx but I have problems with it Inside, but I tried it with your program and compatibility Win-XP-SP3, but it seems more dificult hehe.



Could any API work with it?

I need to do an installer for my program

Anyway Thanks for your help Inside.

[Arnoutdv]

Use the Package & Deployment Wizard which comes with VB6

[Andy Master]

Hi Arnoutdv, I used it, but error again , Do you have an idea of ​​why this happens?

[Arnoutdv]

Are you somehow using controls in your project which are not registered on your computer??

[Inside]

Something strange with my program:

It does not register some controls when I run it while it's compiled, but register all controls so far when I only run it from the VB design "RUN" / F5.

Why? I do not know...

[Arnoutdv]

I think your IDE is running with elevated rights and the created executable is not.

[Andy Master]

Hi Arnoutdv and Inside, I guess the control is registered by this...


But then I see that the control is not found automatically in syswow64...


I don't understand well...

[Arnoutdv]

I think you already have a messed up system.
Having the control in multiple folders is not okay.
The C:\Windows\SysWow64\mscomctl.ocx looks the like the valid location and is the registered version.

Where does the second screenshot (with the OCX located in ..\Documents\..) come from?
Is it a different project??

[Andy Master]

Yes it is different project, but I thought that was automatic detection of the only registered mscomctl.ocx

[Andy Master]

One project was from "Inside" and the other is "my project"

[Arnoutdv]

The you really should not touch the version in ..\documents\.. , you are really going to ruin your system!

[Andy Master]

Yes I understand you, that is why I copied the ocx files to SysWOW64 for to register them, like said that page...
https://support.microsoft.com/es-mx/...error-messages

[Andy Master]

also that is why, I don't understand it:

[Arnoutdv]

If you installed VB6 property then there is already a correct and registered version of MSCOMCTL.OCX in the correct location.
What are you doing with these system OCX files that you are copying them around??

[dilettante]

If MSComCtl.ocx is to be successfully installed, it must be installed into C:\Windows\System32 though if your system root is different it might be another drive letter and "Windows" could be named something else.

This is spelled out in MSComCtl.dep:

; Dependency file for setup wizards.

[Version]
Version=6.1.97.82

; Dependencies for MSComCtl.ocx

; Default Dependencies ----------------------------------------------

[MSComCtl.ocx]
Dest=$(WinSysPath)
Register=$(DLLSelfRegister)
Version=6.1.97.82
Uses1=ComCat.dll
Uses2=
CABFileName=MSComCtl.cab
CABDefaultURL=http://activex.microsoft.com/controls/vb6
CABINFFile=MSComCtl.inf

[ComCat.dll]
Dest=$(WinSysPathSysFile)
Register=$(DLLSelfRegister)
Uses1=
:
:

Any 32-bit installer, whether a PDW Setup or an Installer MSI package, will automatically deal with Win64 issues via the file redirection (Wow64FsRedirection) feature in Windows.

The installer must run elevated, and it should be responsible for registering an installed OCX. Registry redirection takes care of any x64 issues here as well.


Trying to stuff these kinds of files onto a non-system drive (much less a network share - I cringe at the thought) is a recipe for disaster even if you somehow manage to get it to work. That isn't a supported configuration even when using Activation Context manifests unless each such file has been marked to run from swap memory, and even then it is only meant for something like an installer. But if you try to register such files in a funky location you do indeed risk breaking other applications.


You are breaking too many rules and it has bit you in the rear. People got themselves into deep trouble trying tricks like always logging on as an Administrators or Power Users user so they could pretend they were still on Windows 95. This left machines very insecure, so after XP we got UAC and the elimination of Power Users to help secure PCs for people who have these bad habits.

It sounds like you have now managed to break your development PC as well.

Trying to go from 2001's Windows XP used in "pretend we still use Windows 95 mode" to 2015's Windows 10 in one jump was bound to give you fits. You are trying to program from a perspective that is now over 20 years behind the times. You have a lot of bad habits to unlearn, and some 20 years of changes to learn.

I just don't know how we can help you. You have pulled out onto a freeway in a horse-drawn carriage. VB6 is not a "beginner's language" but a tool for professionals. That is exactly why after such a very bad experience with VB5 Microsoft eliminated the "Standard Edition" previously sold to hobby users.

[Andy Master]

If I understand those bad habits for that very reason I want to correctly register the activex controls in their correct folders, but it turns out that when I wanted to run a program made in vb6 here in Windows 10, this one did not run and I did not know how to do an installer, it is So I asked for help to be told how to do a normal installer too.

[Arnoutdv]

Then why do you try to register the OCX from such a strange location?
Based on your IDE screenshot the control is already registered from within the correct location.

[Andy Master]

No!, I have never registered that control in this location, but I thinking why it takes this location....