Msvbvm60 Dll Visual Basic 6 Runtime
Vickiana Sconyers
The Visual Basic 6.0 runtime is defined as the compiled binary files originally included in the redistribution list for Visual Basic 6.0. These files were marked as distributable in the original Visual Basic 6.0 license. Examples of these files include the Visual Basic 6.0 runtime library (msvbvm60.dll), controls (i.e., msflxgrd.ocx) along with runtime support files for other major functional areas (i.e. MDAC).
For Visual Basic 6 the debug symbols were only provided in the ISO service pack releases, the Service Pack 6 is still available via Visual Studio subscriber downloads as mu_visual_basic_6.0_service_pack_6_x86_a783d802.iso (as of Jan 2023)
I'm trying to run a windows exe via wine and it when I double click the program a message box pops up that says "The Procedure * could not be located in the DLL MSVBVM60.dll" IIRC this DLL is one of the ms visual basic runtimes and I've tried a few things to remedy this problem but none of them seem to work. I don't really use wine that much so I'm no expert with it, I tried adding the DLL to the preferred list but that didn't fix anything. The DLL's are in the same folder as the application and the app itself is portable so it doesn't need to be installed. I installed the VB6 runtime files with winetricks but I still have the same error. Any help would be appriciated.
When you say 'the procedure * could not ...' do you mean a literal '*' is there? because you can't have a procedure named '*' (unless this is some weird visual basic thing). so it's probably a problem with the exe file rather than the dll
dva...@onyxes.com
RE: MSVBVM60.DLL Not Found JohnYingling (Programmer)18 Jan 02 16:57That is the main VB6 runtime. If you are distributing a compiled VB6 program you must "package" it with at least the Package and Deployment" Wizard to include all required OCXs and DLLs into a Setup Package. The PC's on which the DLL is not found must have never had a VB6 application installed on them. www.VBCompare.com Compare Code (Text)
www.VBSortGen.com Generate Sort in VB or VBScript RE: MSVBVM60.DLL Not Found MrEGuest (Programmer)18 Jan 02 17:10There is nothing to be "fixed"
You are recieving this error because the configuration(software & os) of the PCs are different.
This file MSVBVM60.dll - Microsoft Visual Basic Virtual Machine needs to be on every machine that runs a VB app.
You're not receiving this error on some machine because either they're running a later OS or service pack in which the dll was included by default or because the machines that don't give the error have had some software installed that has already installed this file.
In any case you'll need to install this, and probably a few other files depending on your app, on any machine that will use your app.
you can copy it manually to the target machine and register it with this run from the run menu:
regsvr32 path&filename
this will allow the machine to use msvbvm60 but will by no means replace the need to deploy your app with installation software like Package & Deployment Wizard.
Josh
googletag.cmd.push(function() googletag.display('div-gpt-ad-1406030581151-2'); ); Red Flag This PostPlease let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.
CancelRed Flag SubmittedThank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.
Per comments, the poster found a copy of msvbvm60.dll (a component of the Microsoft Visual Basic 6 runtime that should be a core part of the operating system) somewhere on the Internet when they had issues with the installer asking for it.
The msvbvm60.dll file is defined as the "Visual basic virtual machine v. 6.0" that enables "Microsoft Windows" to run applications written in "Visual Basic" programming language. "Visual Basic" as a programming language lets the programming engineer visually see where he/she puts components, for example buttons and such. Even windows is using the drag and drop technique provided by msvbvm60.dll.
Downloading and InstallingIn addition to the program you may need to put msvbvm60.dll in your Windows system32 directory (which is probably c:\windows\system32\).Source code is also avalible, just remember where it came from. :-)
- BinClock v2.2 - for Win32 systems
- msvbvm60 - Visual Basic v6.0 runtime DLL
- Source Code - in a Visual Basic 6.0 project
All Visual Basic programs require and reference an associated run-timelibrary. For Visual Basic 6 this file is namedmsvbvm60.dll1. Usually it is locatedin the windows system folder. This file contains the compiled code and typelibrary declarations for the built-in standard objects belonging to theVBA and VBRUN namespaces, as the Object Browser descriptionclearly states on the status label when selecting them from the combobox. Apartfrom the regular VB objects, the runtime library also exports quite a lot ofstdcall functions that are apparently necessary for executing VBcode, as one can see by examining it's export table using the dependencyviewer.Because any VB application per definition requires this dll, any extrafunctionality we may get out of this library we get for free, i.e.without adding an extra external dependency to the project. Consequently, a scanthrough the list of exported functions might just reveal a couple of hidden gemswaiting for us to get our dirty fingers on. It turns out that most of theexported functions are of little use to us, either because their names suggeststhat they implement a trivial VB command or because it is unclear whatoperations they perform and what arguments they expect. However there are acouple of members that clearly stand out because of their descriptive andprovocative function names. They are exported as:
And there you have it: unrestricted memory access and type casting in pureVisual Basic. The VBVM6Lib type library offers the advanced VB programmera complete range of assorted low-level functions in a reasonably readable syntax,considering the technical character of these operations. It relies completely ona couple of very basic functions that are built into the VB runtime library, sousing these aliases does not introduce any external dependencies into theproject whatsoever.
In view of the technical and unprotected character of these functions itmust be said that this type library is not for the faint of heart. Anyprotection that Visual Basic traditionally offers is out of the way so it's upto the caller to ensure that these functions are called with valid arguments.Therefore when experimenting with these functions it is strongly advised to usean OS that has strong interprocess protection, otherwise the system probably hasto be rebooted on each and every invalid call6.Mind you, this risk is not related to the Visual Basic programming language butinherent to direct and unprotected memory access. In any case caution isadvised.
However assuming that you know what you are doing, this type library will allowyou to pull the same low-level tricks in Visual Basic as in any givenprogramming language. So no more excuses saying that you can't do that in VBanymore. Open the references dialog, select the Visual Basic 6 Virtual MachineType Library and just do it.
In the same way that the Windows loader reads the PE file to set up proper memory layout, the VB runtime (msvbvm60.dll) reads in the VB6 file structures to ready it for execution within its environment.