I tried LinuxSampler too on XP and get "the application failed to initialize properly (0xc000001d) click ok to terminate." I did a clean install without Gigedit and I get the same message.
You're given informations are a little bit sparse. You are actually talking about the LinuxSampler backend, right? And the mentioned error message appears immediately when you launch the LS backend application? If so, you said you tried to install LS without the gigedit component. Make sure the LS Windows installer did not create a directory named "plugins" in the installation directory of LS (the default installation directory of LS is "C:\Program Files\LinuxSampler", so in that case you would check for the existence of a directory named "C:\Program Files\LinuxSampler\plugins"). In case there is such a "plugins" directory, delete it and try again to launch the LS backend application. If this won't help, check if your system is missing any mandatory DLLs. You can do that i.e. with the "Dependency Walker" tool, which you can download here: http://www.dependencywalker.com (The site seems currently to be down while I'm writing this, hope it's up again soon) It's just a single .exe application which you don't have to install. Just run it, click on "Open" and select the "linuxsampler.exe" binary from your LS installation directory. Dependency Walker will then show all the DLL dependencies of LS in a tree (since most DLLs have dependencies to other DLLs as well) and will markup all the DLLs that it could not resolve. If the latter is the case on your system, tell us which DLLs exactly it could not resolve. Which sound card and which ASIO driver are you using BTW?
*** This bug has been marked as a duplicate of 67 ***
? DWMAPI.DLL it says erroe opening file, cannot find file (2) these two have a red file next to them MPR.DLL SHLWAPI.DLL Warning: At least one delay-load dependency module was not found. Warning: At least one module has an unresolved import due to a missing export function in a delay-load dependent module. I use asio4all, and my onboard and a ensoniq soundcard
Please use bug #67 for further comments. It is the exact same issue. Otherwise we end up with dozens of individual reports about the same problem. The three DLLs you mentioned should be unrelated to this problem. It's rather a normal situation on most Windows versions. *** This bug has been marked as a duplicate of 67 ***