PCSX2 and Windows 8 Consumer Preview
#1
Hello,I've tried PCSX2 with both Windows 8 Developer and Consumer preview.
With the first one all it was ok and it worked perfectly,but with the Consumer preview only the official releases work.
The daily builds (http://www.google.it/url?sa=t&rct=j&q=pc...kg&cad=rja) don't work and when I try to launch them I receive this error message:
pcsx2-r5128.exe - Entry Point Not Found

The procedure entry point_invalid_parameter_noinfo_noreturn
could not be located in the dynamic link library
C:\Windows\SYSTEM32\MSVCP100.dll.

How can I solve this problem?
p.s sorry for my bad english Tongue
Reply

Sponsored links

#2
It's a Microsoft Visual C++ DLL.

Maybe try the C++ redist necessary for SVN builds...
http://www.microsoft.com/download/en/det...px?id=5555
Reply
#3
I would say so, I also tried out Windows 8 Consumer Preview myself and it was quite stable imo, but PCSX2 did worked like it should. I would almost say it worked better then on windows 7 Smile
Reply
#4
I ran the PCSX2 CPU benchmark with it, and it seemed a tad slower.
I chalked that up to the additional Start interface constantly running in the background.
Reply
#5
Make sure you own all permissions needed for your PCSX2 folder. It's best you create a new folder.
Reply
#6
(03-29-2012, 07:56 PM)Rezard Wrote: It's a Microsoft Visual C++ DLL.

Maybe try the C++ redist necessary for SVN builds...
http://www.microsoft.com/download/en/det...px?id=5555

I've already installed Microsoft Visual C++,but nothing changes =(
I'll try with the others advice ;-)
Reply
#7
I've solved the problem:I've copied the file from the older version of windows 8 to the system32 directory of the new os.Now all it works! ;-)
Reply
#8
Quote:I would say so, I also tried out Windows 8 Consumer Preview myself and it was quite stable imo, but PCSX2 did worked like it should. I would almost say it worked better then on windows 7

funny how mind trickery works.
Reply
#9
It wasn't Squall it did worked better then under Windows 7 Smile
Reply
#10
not windows 7 with kb2645594 in any case.
Reply




Users browsing this thread: 1 Guest(s)