[Bug 19816] Multiple games and applications need 'msvbvm60.dll' (' winetricks vb6run' is a workaround)

[wine-bugs at winehq.org]

https://bugs.winehq.org/show_bug.cgi?id=19816

--- Comment #24 from Anastasius Focht <focht at gmx.net> ---
Hello folks,

for documentation the official Microsoft Support Statement for Visual Basic 6.0
on Windows:

https://docs.microsoft.com/en-us/previous-versions/visualstudio/visual-basic-6/visual-basic-6-support-policy

--- quote ---
64-Bit Windows

Visual Basic 6.0 runtime files are 32-bit. These files ship in 64-bit Windows
Operating Systems referenced in the table below. 32-bit VB6 applications and
components are supported in the WOW emulation environment only. 32-bit
components must also be hosted in 32-bit application processes.

The Visual Basic 6.0 IDE has never been offered in a native 64-bit version, nor
has the 32-bit IDE been supported on 64-bit Windows. VB6 development on 64-bit
Windows or any native architecture other than 32-bit is not and will not be
supported.
Windows 10

Since the initial release of this support statement, the Windows 10 operating
system has been released. This document has been updated to clarify Microsoft’s
support for VB6 on Windows 10.

The VB6 runtime will ship and will be supported in Windows 10 for the lifetime
of the OS. Visual Basic 6.0 runtime files continue to be 32-bit only, and all
components must be hosted in 32-bit application processes. Developers can think
of the support story for Windows 10 as being the same as it is for Windows 8.1.
Windows 8.1

Since the initial release of this support statement, the Windows 8.1 operating
system has been released. This document has been updated to clarify Microsoft’s
support for VB6 on Windows 8.1.

The VB6 runtime will ship and will be supported in Windows 8.1 for the lifetime
of the OS. Visual Basic 6.0 runtime files continue to be 32-bit only, and all
components must be hosted in 32-bit application processes. Developers can think
of the support story for Windows 8.1 as being the same as it is for Windows 7.
Windows 7

Since the initial release of this support statement, the Windows 7 operating
system has been released. This document has been updated to clarify Microsoft’s
support for VB6 on Windows 7.

The VB6 runtime will ship and will be supported in Windows 7 for the lifetime
of the OS. Visual Basic 6.0 runtime files continue to be 32-bit only, and all
components must be hosted in 32-bit application processes.
Windows Server 2016

Since the initial release of this support statement, the Windows Server 2016
operating system has been released. This document has been updated to clarify
Microsoft’s support for VB6 on Windows Server 2016.

The VB6 runtime will ship and will be supported in Windows Server 2016 for the
lifetime of the OS. Visual Basic 6.0 runtime files continue to be 32-bit only,
and all components must be hosted in 32-bit application processes. Developers
can think of the support story for Windows Server 2016 as being the same as it
is for Windows Server 2012 R2.
Windows Server 2012 R2

Since the initial release of this support statement, the Windows Server 2012 R2
operating system has been released. This document has been updated to clarify
Microsoft’s support for VB6 on Windows Server 2012 R2.

The VB6 runtime will ship and will be supported in Windows Server 2012 R2 for
the lifetime of the OS. Visual Basic 6.0 runtime files continue to be 32-bit
only, and all components must be hosted in 32-bit application processes.
Developers can think of the support story for Windows Server 2012 R2 as being
the same as it is for Windows Server 2012.
Windows Server 2012

Since the initial release of this support statement, the Windows Server 2012
operating system has been released. This document has been updated to clarify
Microsoft’s support for VB6 on Windows Server 2012.

The VB6 runtime will ship and will be supported in Windows Server 2012 for the
lifetime of the OS. Visual Basic 6.0 runtime files continue to be 32-bit only,
and all components must be hosted in 32-bit application processes. Developers
can think of the support story for Windows Server 2012 as being the same as it
is for Windows Server 2008 R2.
Windows Server 2008 R2

Since the initial release of this support statement, the Windows Server 2008 R2
operating system has been released. This document has been updated to clarify
Microsoft’s support for VB6 on Windows Server 2008 R2.

The VB6 runtime will ship and will be supported in Windows Server 2008 R2 for
the lifetime of the OS. Visual Basic 6.0 runtime files continue to be 32-bit
only, and all components must be hosted in 32-bit application processes.
Developers can think of the support story for Windows Server 2008 R2 as being
the same as it is for Windows Server 2008.
Windows Server 2008

Since the initial release of this support statement, the Windows Server 2008
operating system has been released. This document has been updated to clarify
Microsoft’s support for VB6 on Windows Server 2008.

The VB6 runtime will ship and will be supported in Windows Server 2008 for the
lifetime of the OS. Visual Basic 6.0 runtime files continue to be 32-bit only,
and all components must be hosted in 32-bit application processes.
--- quote ---

@alexchandel

--- quote ---
ComDlg32.OCX (winetricks comdlg32ocx) presumably falls under this category.
--- quote ---

No, that ActiveX control doesn't fall into same category according to the link.

--- quote ---
Supported runtime files to distribute with your application

comct232.ocx     msbind.dll     msdbrptr.dll     msstdfmt.dll
comct332.ocx     mscdrun.dll     msflxgrd.ocx     msstkprp.dll
comctl32.ocx     mschrt20.ocx     mshflxgd.ocx     mswcrun.dll
comdlg32.ocx     mscomct2.ocx     mshtmpgr.dll     mswinsck.ocx
dbadapt.dll     mscomctl.ocx     msinet.ocx     picclp32.ocx
dbgrid32.ocx     mscomm32.ocx     msmapi32.ocx     richtx32.ocx
dblist32.ocx     msdatgrd.ocx     msmask32.ocx     sysinfo.ocx
mci32.ocx     msdatlst.ocx     msrdc20.ocx     tabctl32.ocx
msadodc.ocx     msdatrep.ocx     msrdo20.dll
--- quote ---

Regards

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.