Posts: 4.504
Threads: 14
Joined: Jul 2009
Reputation:
89
The best thing you can do is uninstalling the emulator from the C:\Program Files (x86) and install it on a user created folder, something like C:\Emulators is fine. From now on avoid installing any game on that C:\Program Files... PC games or otherwise. That is imperative to any game that rely on plugins and/or mods.
Imagination is where we are truly real
Posts: 7
Threads: 1
Joined: Aug 2011
Reputation:
0
Nope, still no luck.
Have reinstalled to C:\PCSX2 and reloaded the BIOS/Plugins folder to this location but I am still getting the same errors. All games are running incredibly slowly and I can't change the graphics settings to compensate for this.
I think it may just be that the programme is incompatible with my PC: this won't be anything to do with the plugins not being compatible with Windows 7 x64 will it?
Posts: 3.018
Threads: 88
Joined: Jul 2010
Location: FREE SYRIA
(09-02-2011, 07:30 PM)WelshPaul Wrote: Nope, still no luck.
Have reinstalled to C:\PCSX2 and reloaded the BIOS/Plugins folder to this location but I am still getting the same errors. All games are running incredibly slowly and I can't change the graphics settings to compensate for this.
I think it may just be that the programme is incompatible with my PC: this won't be anything to do with the plugins not being compatible with Windows 7 x64 will it?
i have 7 x64 no such problem here
did you run PCSX2 as an administrator
Posts: 7
Threads: 1
Joined: Aug 2011
Reputation:
0
09-04-2011, 10:30 AM
(This post was last modified: 09-04-2011, 10:30 AM by WelshPaul.)
Yes I did. I also gave my usual (non-admin) user account "Full Control" NTFS permissions of the PCSX2 folder, which is now on the root of C:\.
I'm going to try it on XP to see if that makes a difference but dual-booting between 7 and XP is a nightmare.
Posts: 15.303
Threads: 431
Joined: Aug 2005
Reputation:
352
Location: Athens,Greece
Hmm so you used the binary, extracted it in C:/PCSX2 (after uninstalling the previous installation) and you're still getting that error? If you did so, you would not be needing run as admin or any other kind of permissions tweeks