|
Post by deacon on Jul 23, 2007 16:40:30 GMT -5
If you're using that should AFAIK work perfectly well in Linux, but it may increase the possibility that one of your drives may be faulty - if pSX is using a faulty drive, this may be the cause of your problem. You need to test your RAM with Memtest86, linked above if your OS doesn't include it (Ubuntu, for instance, gives you the option to run Memtest at boot). Sorry, what ? What have RAM with HDD to do....? First: The emulator wont start at all... 2nd: Linux has no access on these drives... 3rd: i have Mandriva... What i wanted to know, i know now... "You will need libgtkglext1" This is not offered to me, nor its on the system... this lasts two suggestions: 1. The emulator gets another code, to work on Mandriva... 2. i run an other emulator (which also not working)
|
|
|
Post by Sune on Jul 23, 2007 16:50:45 GMT -5
What i wanted to know, i know now... "You will need libgtkglext1" This is not offered to me, nor its on the system... pSX won't work without it. You will have to find a way to get it.
|
|
|
Post by patrickp on Jul 23, 2007 17:39:08 GMT -5
Well, the error deacon gets is Sune. deacon: I didn't say that your RAM has anything to do with your drives. But problems with either your RAM or with your hard drives, I think, would be the most likely cause of this error. And I don't see how- how are you running Linux, then?
|
|
|
Post by Sune on Jul 23, 2007 19:26:13 GMT -5
Well, the error deacon gets is Well yes, but after you've helped him fix that, he'll still need libgtkglext1!
|
|
|
Post by patrickp on Jul 24, 2007 1:55:06 GMT -5
Yes, unless what he's installed from the Mandriva repositories as libgtkglext is the same library, Sune.
|
|
|
Post by deacon on Jul 24, 2007 6:03:28 GMT -5
how are you running Linux, then? on a separate drive.... libgtk.... is installed, but still wont work... maybe in future there is an update.... Thanks to you ! i'm showing up time to time
|
|
|
Post by patrickp on Jul 24, 2007 12:17:53 GMT -5
Deacon, your memory access error is much more likely to be a system problem than a pSX one. That's why we want you to test your RAM; it might be an idea to run some sort of diagnostic on your drive, as well. Where is your swap partition and how big is it?
|
|
|
Post by deacon on Jul 29, 2007 16:22:47 GMT -5
nevermind dont think so.
I think, i'll be patient
|
|
|
Post by Gamesoul Master on Jul 30, 2007 8:20:22 GMT -5
deacon: Dude... a memory access error could be quite serious, especially if it keeps happening consistantly like it apparently is. You should really take the advice to check things out. It'd be more than worth it if you find something wrong. Problems like that usually tend to start out small, and if that ends up being the case here... you'll eventually end up with a problem you won't be able to fix anymore, possibly at a cost.
|
|
|
Post by deacon on Jul 31, 2007 21:30:07 GMT -5
yeah, ok... what if i tell you that "only" pSX suffer this error
every other app can run for hours and days, also games with high requirements in memory and graphics run for hours with any problem.
this one what i have causes in wrong memorymapping from pSX, i guess, but i really dont know... what i know is, any another program run like hell. as long power comes from the cord.
|
|
|
Post by Ultima on Aug 5, 2007 20:53:42 GMT -5
Could simply be a case of canary in a coal mine. Just because the problem occurs while running pSX doesn't mean pSX is the cause; it could mean pSX detected problems with the system and exhibited odd symptoms from the problems. What have RAM with HDD to do....? Not much, but I seriously doubt you've got 1TB of memory too. Memory != hard drive space. You never really took patrickp's advice to try running MemTest86+ (preferably, overnight) to see if there are any problems. If pSX is complaining about a memory access error, a pretty obvious move for you to make would be to check the integrity of your RAM, and that's exactly what patrickp told you to do by running MemTest86+.
|
|
|
Post by deacon on Aug 11, 2007 6:31:27 GMT -5
Could simply be a case of canary in a coal mine. Just because the problem occurs while running pSX doesn't mean pSX is the cause; it could mean pSX detected problems with the system and exhibited odd symptoms from the problems. . Yeah, right.... btw Memtest shows no errors....
|
|
|
Post by patrickp on Aug 11, 2007 7:54:59 GMT -5
How many passes did you run it for, deacon?
|
|