- Oct 13, 2016
- 3,626
- 7,628
that is a call to the "registry" of windows to "properly" make the .ocx registered.
now, maple.x is not using that .ocx u show in that window.
I have coded in a way that maple.x only require the minimum. try to just ignore and proceed.
surely, if this is the case for "many" .ocx it could mean it will fail later to use maple.x.
files I know are important:
msvbvm60.dll
oleaut32.dll
olepro32.dll
vb6stkit.dll
as u see, all .dll not .ocx. so keep that in mind.
this is to run the base-code. (as u already showed maple.x could start but failed after a bit so some of those .dll should be installed already)
other important things are as I told u: direct2d/directx11. those need to be installed and available.
API Im using are from DLL (those DLL are system-dll that windows should already have)
msvbvm60 (msvbvm60.dll) *from VB6
ole32 (oleaut32.dll + olepro32.dll) *from VB6
Shlwapi
kernel32
user32
gdi32
gdiplus
ntdll
comdlg32 *from VB6 (but only used in the editor-mode, should not affect u)
winmm
shell32
now, maple.x is not using that .ocx u show in that window.
I have coded in a way that maple.x only require the minimum. try to just ignore and proceed.
surely, if this is the case for "many" .ocx it could mean it will fail later to use maple.x.
files I know are important:
msvbvm60.dll
oleaut32.dll
olepro32.dll
vb6stkit.dll
as u see, all .dll not .ocx. so keep that in mind.
this is to run the base-code. (as u already showed maple.x could start but failed after a bit so some of those .dll should be installed already)
other important things are as I told u: direct2d/directx11. those need to be installed and available.
API Im using are from DLL (those DLL are system-dll that windows should already have)
msvbvm60 (msvbvm60.dll) *from VB6
ole32 (oleaut32.dll + olepro32.dll) *from VB6
Shlwapi
kernel32
user32
gdi32
gdiplus
ntdll
comdlg32 *from VB6 (but only used in the editor-mode, should not affect u)
winmm
shell32
Last edited: