I´d renamed MYPS2.ELF to BOOT.ELF and returned the same error. So that isn´t the solution. Any more suggestion?
Printable View
I´d renamed MYPS2.ELF to BOOT.ELF and returned the same error. So that isn´t the solution. Any more suggestion?
I'm getting the same error with the latest 1.1 version.Quote:
Originally Posted by RoVeR
i also use 1.1
I've since managed to sort mine. I think my old DOS version of RAR was corrupting the archive. After downloading and extracting with WINRAR it now starts up.
However, I can't connect to Shoutcast but I've just copied over my Winamp bookmarks file to the Shoutcast folder and that works fine.
Why not set LaunchELF to load it Default; default time 1 sec
how do you do that? is that a new feature? i got ver S and i cant find any settings for default loading... anyway its not that important, I decied to stay with Ulaunchelf because its way more stable than myps2, but when it get more stable i will try it again, i like the gui, but function first as the ulaunchelf programers use to say :)
i found it. thanks for the tip
I actually haven't tried loading from MC, just from HDD and MASS... I have a partition for elfs on my HDD and it gave me that same error whether I was on HDD or MASS.
I have another problem now that I can't even delete the folder from the partition on my HDD. It will delete everything except the deepest folders and when I try to delete those files my partition disappears from PFS and I have to mount it again.
I've given up on trying to fix this now, I'll just wait for a newer version, redownload and start from scratch. It's almost certainly some corrupted file or bad FTP transfer causing my grief.
no body wants to help on these errors
mines the one with the gui string not loading, I posted here just now and over at the for dummys a little while ago 1.1 worked if I leave it all on the MC but if I move it all to the hard drive... gui error
Heya there, I had the same problem just after I fixed my HDD mounting error (errno -2) anyways you're probably after my solution...
What's Causing It? It's caused by incorrectly formatted line endings within your CONFIG.DAT file, I'm guessing that most of you (about 90%) are running Windows and you're using either Notepad or Wordpad to edit your config.
Solution: Switch to a better text editor, get Notepad 2 (Link) goto File > Line Endings > Unix (LF). Be sure to add an extra blank line at the end. I've found it helps.
Still Having Problems? If your still having problems, then get in touch, send me a private message with your config file, I'll fix it for you and send it back.