Loss of System.EnterpriseServices.Wrapper.dll - c++

I am currently running the system on Windows XP - yes I know it is outdated. We had a program installed years ago that was designed to work on Windows XP and this week I had to take my hard drives out the computer and transfer to another mother board and most of the things are working except when I now try and log into my application it tells me that System.EnterpriseServices.Wrapper.dll or another path is missing - but they are still there.
I have copied the file from system to the winsxs folder as well but nothing is coming up.

Related

Qt app starts on device where it was compiled, but not on others

I built a Qt 5.12 app on Ubuntu then moved it to another computer (the very same Ubuntu system) - and it gave me a "__cxa_throw_bad_array_new_length, version Qt_5" at start (and quit)...
When I try with a default Qt windowed starting project (one window, nothing else) and copy the executable to the other computer (where my app is failing), it works. So I think the problem is not in the project setup and the kit.
Very strange is that several weeks ago everything was fine. I don't have any idea what has changed since. I presume that there is a version conflict with a library, but I am not a linux pro and dont't know how to figure that out.
It would be great if any of you could help. :)

Substitutes for OSR Driver Loader (windows kernel driver )

I build a kernel driver sample on VisualStudio and I attempt to deploy and debug it.
PC's environment : windows10 64bit pro ,visualstudio2017, wdk 1803
I don't have 2 PCs, so I want to deploy and debug on virtual machines
for example VirtualBox.
I'm still learning windows kernel device driver following to a windows kernel driver programing tutorial's youtube video
I attempt to download OSR Driver Loader , but error messages appears:
"The Lists are moving! Logins to this site are disabled.
For details see this post in the OSR Devs Blog."
I searching driver loader the site of the link destination,but I can't find it.
Does substitutes for Driver Loader exist ?
Please give a answer to the questions.
Peter_Viscarola's comment from OSR community:
Right now, you can't. We're in the process of trying to determine what to do with these hideously old, legacy, utilities. We haven't touched them in years and, to be frank, I'm not even sure we have the sources for some of these anymore. If we can find the sources, we'll probably move the sources for the innocuous and useless utilities to GitHub so people can do whatever they want with them, which hopefully will not including mocking our command of writing applications, 20 years ago, using MFC and C++. Some utilities which are complex and disruptive (I'm thinking of my favorites DeviceTree and IrpTracker) we may just stop distributing entirely.
Like most of the utilities on OSRONLINE, OSR Driver Loader was nice when it was written, which was like 20 years ago. Now, it provides very close to zero value. IIRC, there is nothing you can do with Driver Loader that you can't do today using the "SC" command.
You can though find some mirrors on the internet by googling the loader's full filename in quotes "osrloaderv30.zip". I found one here (or direct link) but I woudln't recommend downloading it from unknown locations actually, up to you.

My program doesn't run on some PCs

I'm working in a project building an application with Computer Vision using C++, OpenCV and Visual Studio. I'm no expert in deploying programs to use them on other PCs.
I've made a program which I need to distribute to a certain amount of people and I can't make it work on all the computers I'd like to. The program was written using Visual Studio 2015, it's an MFC Project and the code is written in C++ since I'm using OpenCV.
When it was finished, I tried to run it on another computer and I realized that it won't open. I looked on the Internet and found out that I needed to statically link the libraries, so I did it. Also, when I was looking for information, I found that Visual Studio 2015 builds its projects so you can run the programs on machines with Win7 to Win10. When I learnt that, I tried to open it on PCs running Windows 7, 8, 8.1 and 10. I tested my program in like 20 computers, give or take.
The results? I couldn't make it work for Windows 7, the error ucrtbase.terminate api-ms-win-crt-runtime-l1-1-0.dll showed every time I tried to open it. It also didn't open in one machine with Windows 8 without showing any error message, but it DID open on most of the machines with Win 8.1 and Win 10. The thing is that "most"; there were some PCs (with Win 8.1 and 10) that I couldn't open my program on. I found that sometimes it would show up in the Task Manager for less than a second and then disappear. The most stressful thing is that it doesn't tell me what the problem is, it doesn't show any error message. It just won't open.
I tried using Dependency Walker (both on my PC and one of those that I couldn't run my program on) to see if there's something missing and I got a reeaaally long list of files that the system couldn't find, here's an example:
List 1/11. Something curious is that my program executes just well on my computer and on those I could open it, even though Dependency Walker (DW) tells me that there might be a problem with it. This indicates me that DW is not finding the exact error I'm having.
Another thing I've tried is to compare the things I have installed on my computer and install them on the one I want to execute my program on. I tried installing .NET Framework 4.6.1 just because VS 2015 says that my project was built using it (and I have it installed in my PC and that other one doesn't. Also I tried with .NET 4.6.1 SDK). Nothing changed.
Just look here:
https://msdn.microsoft.com/de-de/library/ms235299.aspx
The quick-and-dirty way would be to copy the DLLs from your redist directory. For my MS VS 2013 it is hidden under the VS installation directory in:
VC\redist\x86
or
VC\redist\x64
...
which depends on your application.

Why can't I run an exe with a specific filename?

I have recently encountered a problem on my Windows 7 machine where I can't run an application with a specific name. Let's call it a.exe.
It is a C++ Qt based app and has been working OK for months but when I tried to run it today I got "The application was unable to start correctly (0x80000003). Click OK to close the application.". This happens for both 32-bit and 64-bit builds for Debug or Release.
I spent hours going round in circles checking dependencies and rolling back to previous versions without getting anywhere. I tried the software on a different machine and it worked, so it must be something on my machine...
I finally discovered that if I rename it to something else (e.g. a1.exe) then it will work :-S
I've checked the VirtualStore folder but couldn't see anything. Any other ideas?
Maybe your "known file extensions" are hided, and you are trying to access a.exe when actually the file name is a.exe.exe?

Crash on Windows 7 but running on XP

i've written a small application using c++, Qt and Visual Studio 2010. It's working on Windows XP (32bit) but it crashes on Windows 7 (64 bit) right after start-up. I see a "The program has stopped working..." error. Do I have to recompile the application for Windows 7? And is it possible to get more information why it crashes?
Thanks
In general you wouldn't have to recompile for windows 7, but it depends on your application which you haven't provided details of.
The easiest way to find out is either debug it in windows 7 or put more error handling in, so that it lets you know what has gone wrong, or where it has gone wrong
I agree with what martiert said, also, if you are using some external elements, images. sound files, video files, etc ... be sure of the file location asd this was a problem for me when I was presenting my graduation project, I moved the whole solution from a directory to another and it crashed because it was reading a not found directory ... so be sure of the links of the images, videos, sounds etc ...
You might have to recompile for Windows 7/64bit. It might not even work after a recompile, since Windows 7 is not XP, and a program written for 32 bit might not work for 64. Often one don't have to recompile, but sometimes one have to, and some times a program which works on XP won't work on Windows 7.