Need help with PCSX Reloaded

[CLehn]

I am unable to find an answer no matter how much I Google for answers or mess with the settings.

I am trying to get PCSX Reloaded, version 1.9.92, to work on three computers. My laptop (a netbook), my brother's laptop, and my desktop. I can give the specs to each one upon request, but I'd rather not post the specifications to multiple computers all at once.

The emulator will play a game the first time it is opened, and recently worked multiple times on my brother's laptop when I tried it there the first time. It also didn't work with my netbook at first, but then just today I tried it after it worked on my brother's laptop and after an update to the video driver it worked on the netbook too.

Then I tried to get it working on my Desktop. No dice. I try my netbook again in frustration, and surprise surprise it doesn't work. I have yet to attempt my brother's laptop, but I bet it won't work there anymore either.

Other people have apparently had the exact same problems as me, but in every case the topics and bug reports they posted to get help were never even acknowledged!

I am desperate here. This is supposed to be the best PlayStation emulator, and it doesn't even work. I can't use ePSXe because it's too demanding for my netbook and won't work with my x64 PC. And frankly I'm going to have to use cheats to complete the games I want to play, so I can't use pSX.

Here are the problems for the two computers I can't get to work currently. If the other laptop gets a problem, I'll post it here too.

Netbook: When I try to start a game or the bios, it says "pcsx.exe has encountered a problem and needs to close. We are sorry for the inconvenience."

Desktop: When I try to start a game or the bios, it says "Playstation Emulator based on PCSX-df has stopped working"

These may or may not be the same problem, as the netbook managed to run a game one more time ater a series of driver updates, while trying the same trick on the desktop did nothing.

I know I have no right to force anything on a free program with no warranty, but I am going to have to insist that I at least get a response reasonably soon as the forum topics I saw in my lengthy and patient search don't even have a reply to them, and due to that my patience is running thin. If nobody here can help, then say so please.

[KrossX]

You can use pSX and have cheats, using the CheatEngine software. ePSXe works without problem on x64 Windows, so possibly the same reason for what it doesn't work is the same for both emulator.

The error messages don't say much at all, see if the message contains at least a reference to a culprit file (like a plugin). It might also help to remove any plugin you're not going to use from the plugin folder. And, for testing BIOS at first better use software gpu plugins.

Other than that, look for similar threads and go through the basics of what you're doing and check the FAQs too. This can be some of the reasons of why some threads are left unanswered.

__________________

[CLehn]

Thanks for the response. I sincerely appreciate it.

I'll take your word for it on ePSXe likely having the same problem, as I assumed that because they weren't the same program it couldn't be for the same reason. Unfortunately the error messages aren't very helpful. Word for word, it says...

---

Playstation Emulator based on PCSX-df has stopped working

A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.

[Debug] [Close program]

---

Nothing else to possibly hint at what the cause is. And I did click the "Debug" button, but it brought me to "Visual Studio Just-In-Time Debugger" with a "Possible Debuggers" selection menu that only has one option that leads me to a program that I believe is meant for programmers, not a general user like me. (I'm not certain why I have it, actually...) I'll check my netbook tomorrow, but for now my desktop refuses to give any clues.

I also have installed literally no plugins to PCSX Reloaded. It came with everything and worked the first time at least without anything extra, so I didn't see why I would want to mess with the plugins unless it was recommended to fix the situation, which I'm guessing from your suggestion was a good idea. I do have experience with the plugins as I have set up ePSXe in the past and it worked as required.

As for the "similar threads", I did in fact look for such, and nothing turned up unfortunately. There was also no FAQ for PCSX Reloaded, and no forums either. They did have a bugtracker, but the one person who had the same problem as I did got no response whatsoever.

There was a couple of other topics on some emulation forums. They were each the only such topic on their respective forums, as far as I can tell. I used the forum search engine and Google to dig deeper, but nothing turned up and I wasn't about to trudge through 700 or so pages of help request topics. Once again, the topics that led me to try and find a similar topic on the forum received absolutely no response.

For now, I seem to have gotten lucky and PCSXR is working on my brother's laptop, which he's allowing me to use when he's not busy with it. I'd use CheatEngine, but it seems cleaner and relatively easier to just use pre-made and tested GameShark cheats in ePSXe or PCSXR than to try and blunder my way to finding out the codes myself. I'd still like to keep trying to get this working on my desktop PC, though.

[Uuuuhm....]

You should try and download the newest SVN Version http://www.emucr.com/2012/04/pcsx-re...vn-r77477.html .Works like a charm. You might also need to switch to a real BIOS ,But I would try out the new Version first its much much better than the released Version.

[CLehn]

I tried the latest SVN, and once I installed the Microsoft Visual C++ 2010 that I needed to fix a missing .dll...

...nothing changed. Here's what my netbook has been saying in both the main release and SVN 77477 of the emulator.

---

pcsxr.exe has encountered a problem and needs to close. We are sorry for the inconvenience.

If you were in the middle of something, the information you were working on might be lost.

Please tell Microsoft about this problem.
We have created an error report that you can send to us. We will treat this report as confidential and anonymous.

To see what data this error report contains, click here.

[Send Error Report] [Don't Send]

---

That blue text isn't actually a link in these forums. Here's what clicking it on my laptop said...

---



---

The first blue link in THAT window gave me a long list of stuff I don't understand, and wouldn't let me copy it. Due to the length, a screenshot would not suffice.

Clicking the second link brought me here. HERE. Just as it said, it was nothing more than a privacy policy.

---

So now I'm really stumped. Where can I go from here?

[KrossX]

And that's just from startup? Did you ever even got the chance to setup something?

Try moving the emulator to something short and outside of troublesome directories, like C:\PCSXR for example. Also try clearing the settings and at first try with the directory containing nothing but the pcsxr.exe file. It should at least load and complain.

To clear the settings, try deleting the HKCU\Software\Pcsxr and maybe Pcsx too from the registry.

Just... things to try. Cuz yer case is weird.

__________________

[SimoneT]

Originally Posted by CLehn

I tried the latest SVN, and once I installed the Microsoft Visual C++ 2010 that I needed to fix a missing .dll...

...nothing changed. Here's what my netbook has been saying in both the main release and SVN 77477 of the emulator.

---

pcsxr.exe has encountered a problem and needs to close. We are sorry for the inconvenience.

If you were in the middle of something, the information you were working on might be lost.

Please tell Microsoft about this problem.
We have created an error report that you can send to us. We will treat this report as confidential and anonymous.

To see what data this error report contains, click here.

[Send Error Report] [Don't Send]

---

That blue text isn't actually a link in these forums. Here's what clicking it on my laptop said...

---



---

The first blue link in THAT window gave me a long list of stuff I don't understand, and wouldn't let me copy it. Due to the length, a screenshot would not suffice.

Clicking the second link brought me here. HERE. Just as it said, it was nothing more than a privacy policy.

---

So now I'm really stumped. Where can I go from here?

Sometime this error can be caused by a bad or unsupported plugin into the plugin directory. Try to delete the unused plugins,or rename its extension from .dll to .bak.
Ciao.

__________________
CPU: Intel CORE i5 M 560 @ 2.67 GHz
GPU: NVIDIA NVS 3100M

[CLehn]

@CrossX: Oh, sorry. I should have clarified. In the error on my Desktop and in the error on my Netbook, the respective problems (the same problem?) is when I try to open an ISO. I am able to do setup.

Also, I fortunately have a bit of experience with regedit. Unfortunately, your suggestion once again changed nothing. I'm really starting to think my computer just hates me.

@SimoneT: There aren't any unused plugins. I managed to get the thing working the first time with the included plugins, only for it to never work again from the second time forward. Nothing was changed between the first and second use. Thanks for the suggestion though.

---

Last edited by CLehn; May 11th, 2012 at 23:16..

[KrossX]

Well then, you're gonna have to change plugins and/or plugin settings.

__________________

[CLehn]

Alright, if you think it'll solve the problem. What plugins would you recommend?

[KrossX]

With ePSXe, try with only internal plugins and PEOPS Soft for video. Remove all other plugins from the plugins directory.

__________________

[CLehn]

Nope, still nothing. ePSXe is giving the same error as PCSX Reloaded was upon loading the ISO.

[KrossX]

Load no ISO, just run the BIOS with ePSXe v1.7.0. And since the only non-internal plugin will be PEOPS Soft, that's the only file that should remain in the plugins folder (keep the gpu.dat file, which is also PEOPS Soft).

__________________

[CLehn]

Sorry I haven't replied in this topic for so long. I tried KrossX's suggestion, and once again, nothing different happened unfortunately.

Is this topic still valid to ask for help, or did I unwittingly do some thread necromancy? I'll open a new topic if required.