I have the same problem on a high end pc with windows 98, but it usually only happens when I switch between D3D and OpenGL plugs.
1 - 14 of 14 Posts
G
This problem is known about and it is caused by the internal SPU. Are you using the internal SPU? If you are, then you can only start and stop ePSXe, whether playing a game or configuring, so may times (aroun 3 or 4) before it will crash. The only solution, right now, is to use another SPU like Null's or Petes. The ePSXe team is working on this problem and hopefully it will be resolved in the next release. BTW it has happened to me too.
sincerely,
sx/amiga
sincerely,
sx/amiga
G
Actually, to my way of thinking, the internal SPU IS the best SPU to use. It plays all the sounds in Gauntlet Legends properly, whereas the other SPUs don't and Null2's doesn't work for me at all. Unfortuneately, until this problem is fixed, it makes it very hard to use and enjoy it.
sincerely,
sx/amiga
sincerely,
sx/amiga
It's weird, but I never have had this problem with ePSXe. I use the internal SPU all the time, and believe me, in my development work, I am launching ePSXe a hell of a lot without having to reboot
The only issue I have with it is this: I launch ePSXe using a batch file, so I can re-direct the DOS window output to a file (in case it says something important). If I launch ePSXe as the first application after rebooting, I get a problem ... but only on the next launch of ePSXe! What happens is DDHELP keeps a lock on the file which I redirect ePSXe output to! This is f**king weird behaviour, IMHO. It means the next time I use the shortcut, I get a "Can't create file" error.
I can get round this in two ways, each way involves invoking DDHELP before running ePSXe
1. Launch any other DirectX program before launching ePSXe
2. Launch DDHELP directly, by typing DDHELP in the RUN box in the START menu.
The alternative is to use developer tool, and kill DDHELP manually.
I recommend HandleEx, from Sys Internals, which is the tool that told me DDHELP was locking the damn loggin file. With that, you can see DDHELP running in the background, and kill it without rebooting
The only issue I have with it is this: I launch ePSXe using a batch file, so I can re-direct the DOS window output to a file (in case it says something important). If I launch ePSXe as the first application after rebooting, I get a problem ... but only on the next launch of ePSXe! What happens is DDHELP keeps a lock on the file which I redirect ePSXe output to! This is f**king weird behaviour, IMHO. It means the next time I use the shortcut, I get a "Can't create file" error.
I can get round this in two ways, each way involves invoking DDHELP before running ePSXe
1. Launch any other DirectX program before launching ePSXe
2. Launch DDHELP directly, by typing DDHELP in the RUN box in the START menu.
The alternative is to use developer tool, and kill DDHELP manually.
I recommend HandleEx, from Sys Internals, which is the tool that told me DDHELP was locking the damn loggin file. With that, you can see DDHELP running in the background, and kill it without rebooting
Finally a similar problem, if you go into the threads, you'll find my problem well explained. And I have a SBlive, but this problem didn't ocurred when I had a voodoo3. And now I have a GTS. This problem only occurs when I have Dx8, Dx8a or Dx8.1 installed. Dx7a resolves the problem. ePSXe is more important to me than Dx8, then I'm using Dx7a now!
A simple test to know if it is occuring with you: Run ePSXe with Pete's D3D, then exit it, now run VGS, hehe, it will appear a exception message and VGS will close.
A simple test to know if it is occuring with you: Run ePSXe with Pete's D3D, then exit it, now run VGS, hehe, it will appear a exception message and VGS will close.
1 - 14 of 14 Posts
