http://bugs.winehq.org/show_bug.cgi?id=19816
Summary: Enhancement request: MSVBVM60 Product: Wine Version: unspecified Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: bammzilla@astronomy.com.ph
I would like to request that Wine have its own built-in version of MSVBVM60. I don't know how difficult it would be, but since WinXP has it by default I would love Wine to have it as well.
http://bugs.winehq.org/show_bug.cgi?id=19816
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |WONTFIX
--- Comment #1 from Dmitry Timoshkov dmitry@codeweavers.com 2009-08-23 01:52:19 --- This is outside of Wine development, same as MFC and others.
http://bugs.winehq.org/show_bug.cgi?id=19816
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #2 from Dmitry Timoshkov dmitry@codeweavers.com 2009-08-23 01:52:47 --- Closing.
http://bugs.winehq.org/show_bug.cgi?id=19816
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |UNCONFIRMED Resolution|WONTFIX |
--- Comment #3 from Alexandre Julliard julliard@winehq.org 2009-08-23 02:48:04 --- If it's shipped with Windows then it's within Wine's scope. Of course it probably won't happen any time soon, but it's still a valid request.
http://bugs.winehq.org/show_bug.cgi?id=19816
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Version|unspecified |1.1.28 Ever Confirmed|0 |1 Severity|normal |enhancement
--- Comment #4 from Austin English austinenglish@gmail.com 2009-08-23 03:12:45 --- Confirming
http://bugs.winehq.org/show_bug.cgi?id=19816
--- Comment #5 from Dmitry Timoshkov dmitry@codeweavers.com 2009-08-23 09:47:15 --- Windows also ships msvbvm50, mfc40, mfc42, mfc71, msvcp50, msvcp60, msvcp70, msvcp71, msvcr70, mdac.
Is it ok to start accepting requests for those as well?
http://bugs.winehq.org/show_bug.cgi?id=19816
--- Comment #6 from Alexandre Julliard julliard@winehq.org 2009-08-23 12:16:19 --- (In reply to comment #5)
Windows also ships msvbvm50, mfc40, mfc42, mfc71, msvcp50, msvcp60, msvcp70, msvcp71, msvcr70, mdac.
Is it ok to start accepting requests for those as well?
Yes, certainly.
http://bugs.winehq.org/show_bug.cgi?id=19816
--- Comment #7 from Bamm Gabriana bammzilla@astronomy.com.ph 2009-08-23 14:41:43 --- As the requestor of this enhancement, please let me explain. So many installers nowadays no longer include these DLLs because they assume they are on the system. As a user, I believe that ideally, running the installer in Wine should allow the user the immediately run the program. I think requiring the user to know that they need to use winetricks after installing their app adds to the reputation of Wine being only for advance users.
I believe that winetricks should always and only remain a hack for things that do not work at the moment. It shouldn't be considered a solution for end users. We shouldn't even require end users to know which runtime is needed by their apps, especially since it works out of the box in XP (which by default is what Wine tells the installers it is, btw).
Lastly (and this may be just me), I don't like having the real msvbvm50/60 on my system. I just want my apps. If I can have free alternatives then better.
If I had the programming skills for this I would probably scratch my itch. But having none, I do the next best thing and file a request in the remote hope that someone has a similar itch with necessary skills. I am by no means requiring those who are already working on other parts (and doing a good job too!) to work on my request instead of what they believe to be important to them.
I know that Wine has many more important bugs that need to be worked on, but that shouldn't be reason to prevent what I perceive to be a valid request. After all, it took me 3 years to finally decide to file this bug, because I respect the more important things that needed to be done.
http://bugs.winehq.org/show_bug.cgi?id=19816
--- Comment #8 from Vitaliy Margolen vitaliy@kievinfo.com 2009-08-23 15:07:14 --- Just make a bunch of dummy dlls that when loaded pop-up a message - "Use 'winetricks X' to install missing dependency". Not much else you can do short of rewriting 90% of MS' software.
OP, if you expect someone to implement all these garbage you are NUTZ!!!
http://bugs.winehq.org/show_bug.cgi?id=19816
--- Comment #9 from Bamm Gabriana bammzilla@astronomy.com.ph 2009-08-23 15:46:38 ---
OP, if you expect someone to implement all these garbage you are NUTZ!!!
I have no illusions that this will be fixed soon. That's reality. My request is not for all these garbage but specifically about MSVBVM60.
The other reality is that non-geek users just want their app to run. Alexander understands this, why can't you?
http://bugs.winehq.org/show_bug.cgi?id=19816
--- Comment #10 from Vitaliy Margolen vitaliy@kievinfo.com 2009-08-23 17:35:39 --- You talking about implementing something that's not a part of an OS. What's worse, you talking about something that MS holds lots of patents and copyrights on. Ask any lawyer how feasible it is to re-implement MSVB.
And I think this is question for for some one else not Alexandre to answer. These are really shaky grounds.
http://bugs.winehq.org/show_bug.cgi?id=19816
--- Comment #11 from Austin English austinenglish@gmail.com 2009-08-23 18:28:56 --- (In reply to comment #10)
You talking about implementing something that's not a part of an OS. What's worse, you talking about something that MS holds lots of patents and copyrights on. Ask any lawyer how feasible it is to re-implement MSVB.
They also hold patents on a lot of windows builtin functionality.
http://bugs.winehq.org/show_bug.cgi?id=19816
--- Comment #12 from Bamm Gabriana bammzilla@astronomy.com.ph 2009-08-23 22:50:17 ---
You talking about implementing something that's not a part of an OS.
Is Notepad a part of the OS?
Runtimes allow software to be run, which is what Windows does: provide the means for user's applications to run.
Vitaliy, if you don't want to work on it you don't have to. But neither do you have to prevent other people from doing it if they so desire.
To illustrate people's differences in interests, I know you like games, but I think games are silly and a waste of time. If Wine is working on DirectX then I don't see reason why Wine shouldn't work on runtimes of more productive apps.
If I had the skills, I'd work on this. If someone picks it up, it's his choice. It's not for you to say that he should be working on something more important.
http://bugs.winehq.org/show_bug.cgi?id=19816
--- Comment #13 from Detlef Riekenberg wine.dev@web.de 2010-04-22 07:47:40 --- (In reply to comment #5)
Windows also ships msvbvm50, mfc40, mfc42, mfc71, msvcp50, msvcp60, msvcp70, msvcp71, msvcr70, mdac.
Is it ok to start accepting requests for those as well?
Wine has now builtins for more C/C++ runtime libraries: - msvcr70.dll (VS2002) - msvcr71.dll (VS2003) - msvcr80.dll (VS2005) - msvcr90.dll (VS2008) - msvcr100.dll (VS2010)
They are far from complete, but enough for many apps.
http://bugs.winehq.org/show_bug.cgi?id=19816
A Wine user RandomAccountName@mail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |RandomAccountName@mail.com
http://bugs.winehq.org/show_bug.cgi?id=19816
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Enhancement request: |Add implementation of |MSVBVM60 |MSVBVM60
http://bugs.winehq.org/show_bug.cgi?id=19816
Andrew Millington andrew.millington@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |andrew.millington@gmail.com
--- Comment #14 from Andrew Millington andrew.millington@gmail.com 2011-04-29 21:48:52 CDT --- HardOCP UT2k3 Benchmark requires MSVBVM60
err:module:import_dll Library MSVBVM60.DLL (which is needed by L"C:\UT2K3 Benchmark v2.1\HardOCP UT2k3 Benchmark.exe") not found err:module:LdrInitializeThunk Main exe initialization for L"C:\UT2K3 Benchmark v2.1\HardOCP UT2k3 Benchmark.exe" failed, status c0000135
http://bugs.winehq.org/show_bug.cgi?id=19816
fracting fracting@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fracting@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=19816
Diego paloseco@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |paloseco@gmail.com
--- Comment #15 from Diego paloseco@gmail.com 2011-05-05 17:05:34 CDT --- so I guess windows 7 comes with A LOT of these bundles, and like net framework and such....
http://bugs.winehq.org/show_bug.cgi?id=19816
Rex Tsai chihchun@kalug.linux.org.tw changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |chihchun@kalug.linux.org.tw
http://bugs.winehq.org/show_bug.cgi?id=19816
Diego paloseco@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC|paloseco@gmail.com |
http://bugs.winehq.org/show_bug.cgi?id=19816
Ken Sharp kennybobs@o2.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |kennybobs@o2.co.uk
http://bugs.winehq.org/show_bug.cgi?id=19816
Dan Kegel dank@kegel.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sydbarrett74@gmail.com
--- Comment #16 from Dan Kegel dank@kegel.com 2012-03-09 15:03:59 CST --- *** Bug 30124 has been marked as a duplicate of this bug. ***
http://bugs.winehq.org/show_bug.cgi?id=19816
Felix Yan felixonmars@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |felixonmars@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=19816
--- Comment #17 from Austin English austinenglish@gmail.com --- Still present in 1.7.21.
https://bugs.winehq.org/show_bug.cgi?id=19816
--- Comment #18 from Austin English austinenglish@gmail.com --- Still in 1.7.51.
https://bugs.winehq.org/show_bug.cgi?id=19816
--- Comment #19 from Rosanne DiMesio dimesio@earthlink.net --- Still not implemented in 1.9.24; also affects Brother's Keeper 7.x.
https://bugs.winehq.org/show_bug.cgi?id=19816
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |joe.frey@radioles.com
--- Comment #20 from Austin English austinenglish@gmail.com --- *** Bug 42448 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=19816
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Add implementation of |Multiple games and |MSVBVM60 |applications need | |'msvbvm60.dll' ('winetricks | |vb6run' is a workaround) CC| |focht@gmx.net
--- Comment #21 from Anastasius Focht focht@gmx.net --- Hello folks,
refining the summary to provide the workaround similar to MFC related tickets:
https://bugs.winehq.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NE...
The implementation part ... to quote myself from various MFC tickets:
--- quote --- Implementing MFC requires lots of effort which would drain the already limited developer resources available to the Wine project - with little to no benefit. MFC will be long dead when this effort reaches a usable state (if ever). --- quote ---
Same applies for Microsoft Visual Basic 6.0 Runtime.
Regards
https://bugs.winehq.org/show_bug.cgi?id=19816
alexchandel@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |alexchandel@gmail.com
--- Comment #22 from alexchandel@gmail.com --- ComDlg32.OCX (winetricks comdlg32ocx) presumably falls under this category.
Not saying it should be a priority at all, but fwiw LOTS of industry software still uses this crap (MSVBVM60.dll, ComDlg32.OCX, etc). Microsoft has a solid foothold there, kept by these old APIs, & they're not going to surrender it for a while.
https://bugs.winehq.org/show_bug.cgi?id=19816
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |luca.finizio.mgbx@hotmail.i | |t
--- Comment #23 from Zebediah Figura z.figura12@gmail.com --- *** Bug 46034 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=19816
--- Comment #24 from Anastasius Focht focht@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...
--- 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
https://bugs.winehq.org/show_bug.cgi?id=19816
Louis Lenders xerox.xerox2000x@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |slawomir.obuchowicz@gmail.c | |om
--- Comment #25 from Louis Lenders xerox.xerox2000x@gmail.com --- *** Bug 48752 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=19816
Anya maniikarabera@protonmail.ch changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |maniikarabera@protonmail.ch
https://bugs.winehq.org/show_bug.cgi?id=19816
--- Comment #26 from Bamm Gabriana bammzilla@astronomy.com.ph --- Would this project be useful to lead to a possible implementtion someday?
https://github.com/cocus/openmsvbvm
https://bugs.winehq.org/show_bug.cgi?id=19816
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #27 from Zebediah Figura z.figura12@gmail.com --- (In reply to Bamm Gabriana from comment #26)
Would this project be useful to lead to a possible implementtion someday?
Probably not. They appear to have used methods that aren't considered safe for Wine development:
"API Monitor from ROHITAB was also used to check some runtime values and function calls from the original MSVBVM60.dll. Some reverse-engineering sites such as the ones listed in http://sandsprite.com/vb-reversing/"
There's also the problem that there's no actual license attached (although that could probably be resolved by contacting the author and asking for an explicit license).
https://bugs.winehq.org/show_bug.cgi?id=19816
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4@web.de
https://bugs.winehq.org/show_bug.cgi?id=19816
Bartosz gang65@poczta.onet.pl changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |gang65@poczta.onet.pl
https://bugs.winehq.org/show_bug.cgi?id=19816
Zeb Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ry1tg3+RY1TN1@rokejulianloc | |khart.anonaddy.com
--- Comment #28 from Zeb Figura z.figura12@gmail.com --- *** Bug 55280 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=19816
soredake broaden_acid002@simplelogin.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC|broaden_acid002@simplelogin | |.com |