Uninstall the VC runtime. Remove any vcomp100.dll files which are on your computer. If you start dolphin, it should complain about the missing vcomp100.dll file. If it doesn't, there still is one lying around in any of your PATH directories or in the Dolphin path. Find the file and remove it until starting Dolphin complains about the missing vcomp100.dll file.
Then, install the CORRECT VC runtime and try again.
(09-28-2012, 05:29 AM)neobrain Wrote: [ -> ]Uninstall the VC runtime. Remove any vcomp100.dll files which are on your computer. If you start dolphin, it should complain about the missing vcomp100.dll file. If it doesn't, there still is one lying around in any of your PATH directories or in the Dolphin path. Find the file and remove it until starting Dolphin complains about the missing vcomp100.dll file.
Then, install the CORRECT VC runtime and try again.
Yes he said vcomp100.dll not found, but i have reeinstal C++ 2010 64x and error´s back... Why he reinstalls with the error?
I think now is problem, some times ago i installed a emulator control xbox 360, which replaces some DLLS, and others like x_input, possibly be that. But i dont remember exactly all archives. Its joystick archives of system 32, you know?
that would also cause this error, remove xinput1_3.dll from system32
(09-28-2012, 08:03 AM)LPFaint99 Wrote: [ -> ]that would also cause this error, remove xinput1_3.dll from system32
He said: is missing xinput1_3.dll... Someone have a xinput1_3.dll,xinput1_1.dll,xinput1_2.dll, XInput9_1_0.dll original from windows 7 x64 service pack1? Upload please from system 32.
I'm not so sure distributing dll's like that is entirely legal. They are, after all, proprietary Windows software.
Besides, Xinput is a part of DirectX (basically anything with an x in front is DirectX).
(09-28-2012, 03:15 PM)Axxer Wrote: [ -> ]I'm not so sure distributing dll's like that is entirely legal. They are, after all, proprietary Windows software.
I'm not sure MS could be bothered to care in any case, since they provide the DLLs in question free to anyone with an internet connection. At any rate, i-cold, downloading random DLLs is a recipe for trouble. Just stick to using installers.
(09-28-2012, 03:27 PM)Shonumi Wrote: [ -> ] (09-28-2012, 03:15 PM)Axxer Wrote: [ -> ]I'm not so sure distributing dll's like that is entirely legal. They are, after all, proprietary Windows software.
I'm not sure MS could be bothered to care in any case, since they provide the DLLs in question free to anyone with an internet connection. At any rate, i-cold, downloading random DLLs is a recipe for trouble. Just stick to using installers.
The only solution I see uninstall and install direct x again, just not sure how.
IIRC, that bit of snafu was due to how it made the patches available. I think originally AutoPatcher downloaded the patches on it's own, then pushed them out to users, i.e. the patches were coming from servers other than MS. They apparently don't care anymore since newer version of the app now download straight from MS' servers.
Keep in mind, AutoPatcher was a fairly popular and well known application. Between threatening legal action against a few random kids passing around a small DLL or getting real work done, I'm pretty sure the latter takes priority. Sharing DLLs (and fonts or other system files) probably gets done a lot on the net, but it's not worth their time to care. They don't even go after a lot of the people who pirate their entire OS (they mostly complain, sometimes take action against fake sellers, not so much with downloaders). I'm not condoning it since it probably isn't legal to share MS' DLLs (unless the license says it's okay), I'm just saying, where MS could care, they could be doing something else (and they usually do).
(09-29-2012, 12:36 AM)Shonumi Wrote: [ -> ]IIRC, that bit of snafu was due to how it made the patches available. I think originally AutoPatcher downloaded the patches on it's own, then pushed them out to users, i.e. the patches were coming from servers other than MS. They apparently don't care anymore since newer version of the app now download straight from MS' servers.
Keep in mind, AutoPatcher was a fairly popular and well known application. Between threatening legal action against a few random kids passing around a small DLL or getting real work done, I'm pretty sure the latter takes priority. Sharing DLLs (and fonts or other system files) probably gets done a lot on the net, but it's not worth their time to care. They don't even go after a lot of the people who pirate their entire OS (they mostly complain, sometimes take action against fake sellers, not so much with downloaders). I'm not condoning it since it probably isn't legal to share MS' DLLs (unless the license says it's okay), I'm just saying, where MS could care, they could be doing something else (and they usually do).
Ok, i going try.