|
|
Post by Carl Gundel on Feb 23, 2019 11:09:21 GMT -5
Unfortunately for those of us who use software developed in Microsoft C++ (and LB5's VM is) we are forced to somehow include the vcruntime140.dll Visual C++ runtime DLL. I don't understand why this isn't included in the Windows updates, and I don't like it. I guess they have their reasons. In older versions of my development platform this wasn't needed, but alas...  I thought it was important to explain why it's there. Hopefully we will be able to make this work alright. There is a version of this for 32-bit and for 64-bit. |
|
|
|
Post by tsh73 on Feb 23, 2019 15:56:26 GMT -5
On Win 10 home 32 bit Russian starting LB5 produced error in Russian saying vcruntime140.dll is not designed for Windows or contains an error Error code 0xc000035a Renaming it to vcruntime140_.dll allows to start lb5alpha.exe, so it works now for me. Search for vcruntime140.dll found one in Windows\system32 time modified 10 10 2017 version 14.12.25810.0 of Microsoft Visual Studio 2017 (English) (version shipped with LB5 is 14.00.23026.0, Visual Studio 2015) Googling for error code says docs.microsoft.com/en-us/openspecs/windows_protocols/ms-erref/596a1078-e883-4972-9bbc-49e60bebca55May that DLL shipped with LB really be 64 bit instead of 32? |
|
|
|
Post by Carl Gundel on Feb 23, 2019 16:08:47 GMT -5
What happens if you delete the DLL. Does Liberty BASIC start?
|
|
|
|
Post by tsh73 on Feb 23, 2019 16:14:19 GMT -5
After I renamed supplied dll, LB5 starts and works.
|
|
bart
New Member
Posts: 7
|
Post by bart on Apr 14, 2020 23:34:42 GMT -5
I'm just trying version 5 for the first time. Have downloaded and extracted lb5-350.zip but when running lb5alpha.exe I get the error message "The code execution cannot proceed because VCRUNTIME140.dll was not found. Reinstalling the program may fix this problem."
I've tried deleting the included vcruntime140.dll but still the same error.
I'm running Win 10 pro 64 bit. What am I doing wrong?
|
|
|
|
Post by Chris Iverson on Apr 14, 2020 23:49:03 GMT -5
|
|
bart
New Member
Posts: 7
|
Post by bart on Apr 15, 2020 7:30:19 GMT -5
Thanks for the suggestion Chris. That did the trick.
|
|
cundo
Full Member
Muchas Gracias!!
Posts: 146
|
Post by cundo on Jun 9, 2020 17:57:47 GMT -5
I'm having this issue with a 32 bits Windows 10. I can fix it placing my own copy of the dll, which is somewhere under the windows winsxs folder, I think it's a backup, and I rename that to vcruntime140.dll. Has a weird sufix name attached, that is why I rename it.
I don't know why but it works.
|
|
|
|
Post by Chris Iverson on Jun 9, 2020 19:00:15 GMT -5
If you're able to tell, what's the exact name and path you got the file from, and where did you copy it to?
The WinSxS folder is part of the OS's component servicing and versioning model. Copies of multiple versions of DLLs can be placed in there, side-by-side, without overwriting each other, and the system's loader can automatically load the correct one in for programs that request it(usually by the program having a matching manifest).
SxS actually stands for side-by-side. Feel free to copy OUT of there, if needed, but do not move or change anything in the folder. You SHOULD be prevented from making changes, anyway, but if you do manage to, you could wind up accidentally hosing your system in some way.
I'd try downloading the runtime I linked to above, and also downloading the 64-bit version from the Microsoft support page linked to above, to make sure it covers the 64-bit version of LB5.
|
|
cundo
Full Member
Muchas Gracias!!
Posts: 146
|
Post by cundo on Jun 9, 2020 20:08:14 GMT -5
Hi Chris, I have many copies of the runtime dll, the one I copied to the LB5 folder was vcruntime140_dr400.dll
There is one also with that name under system32/.
I just noted audacity also comes with a copy, I'm using that one right now.
|
|
