The above video goes away if you are a member and logged in, so log in now!
ripper 3.1 - cant launch any apps from mc
ripper 3.1 - cant launch any apps from mc –
i have a pstwo-slimline modded with ripper 3.1. the only app i can launch from memory-card is ripper3-navigator. if i try to launch anything iÂ´ve installed with the r3navi, i just get to the normal ps2-browser. iÂ´ve also tried to install the mediaplayer 1.50 from the cd, using mcloader. first created the save file with mediaplayer, then installed it. now i have that mp1.50 icon on my mc, but when iÂ´m trying to launch it, using the dev.olution mode (pressing triangel wile booting the ps2) i just get to the normal ps2-browser. i cant even use the ripper2navi from mc, i can just boot it from cd and install, but when trying to launch with dev.-mode, iÂ´m just getting back to the normal browser.
could anyone explain, what the problem is? iÂ´ve already burned so many cds and itÂ´s not working at all, iÂ´m really getting mad!
Could this be because the exploit is disabled in V12 PSTwo's??
First, disregard the mention of exploit problems in the reply by Angelus3X.
As you're using the Dev.olution mode 1 of the Ripper 3, no exploit is involved at all.
I have no Ripper 3 myself, nor even a PSTwo, but I have long used a Ripper 2 Gold with my PS2, though I recently had that chip replaced with a Matrix Infinity. Anyway, I'm fairly sure I know the cause of your problem.
From your description I take it that you can use NO other ELFs other than the R3Navi, which itself is quite useless if it can't launch other ELFs... But since you could install that, at least, you can launch ELFs from CD-R. Your next step should therefore be to try booting some other launchers/browsers (eg: PS2OS, PS2Menu-K, Altimit, etc) from CD-R, and use them to inspect what really has been installed on your memory card.
I suspect that the reason for your problems may be that the installer scripts you've used are incompatible with R3Navi. There is good reason to think so, since the history of these script methods is rather messy...
Originally (ie: DMS3 and later Ripper2), the main Dev1 program was always installed as "mc0:\BOOT\BOOT.ELF". Normally that would be the DMS Explorer (even with other chips) or the Ripper 2 Navigator (a rip-off of DMS Explorer). The applications installed for them would normally be stored as something like "mc0:\BOOT\APPNAME\APPNAME.ELF". The backslashes used in all these paths are NOT the valid folder separator for PS2 MCs, so each and every file installed that way would show up as a 'corrupt data' block in the PS2 browser...
That was found unacceptable by most people, so they patched DMS explorer to use valid separators instead, resulting in paths like "mc0:/BOOT/BOOT.ELF" and "mc0:/BOOT/APPNAME/APPNAME.ELF". That does result in proper subfolders, but unfortunately adds a new worry, as the PS2 browser does not support subfolders on MC properly. It works only as long as you do NOT attempt to copy or erase the /BOOT/ folder using the PS2 browser.
Another solution has been to place each installed application in separate folders, and editing the menu files to hold the correct paths. That works fine as far as being compatible with the PS2 browser, but you can forget the installer support built-in to the DMS Explorer, as it can't handle such paths.
Installer scripts would have to be different for each of the cases above, and also for the final case described below. Using the wrong script will result in just the symptom you got (no launching at all) even in those cases where the ELF is displayed correctly in launch menus.
Finally, new mod-chips have modified the original methods slightly, in ways I'm not certain of myself, except for the chip I currently use, the Matrix Infinity. It allows two different ELFs to be launched directly by Dev mode 1, rather than just one as the older chips allowed. Those two are "mc0:/MATRIXTEAM/MANAGER.ELF" (when pressing triangle at reset) and "mc0:/BOOT/BOOT.ELF" (when pressing R1 at reset). However, since I find the supplied manager worthless (still no HDD support) I'm using LaunchELF v3.4b2 for both those ELFs instead (renamed as needed). One of those I use as my main launcher/browser menu, while the other serves to quicklaunch HDLoader.
I suspect your R3Navi also is quite limited and that you'd be better served by using LaunchELF instead, but even if you want to use R3Navi, you still have to make sure to use compatible installer scripts.
----- snip ----- Some web browsing later...:
I just downloaded R3Navi from the Ripper 3 site, and I can confirm that it is just a rip-off of the Matrix Infinity manager that I use with my chip. This means that most installer scripts on PS2 sites are NOT compatible with it, since those were made for compatibility with DMS Explorer and its close relatives. On the bright side, however, it does mean that the methods I use should work fine for you too.
Although they have modified the MANAGER.ELF a bit, I still see the same folder names in it as in the version I got from the Matrix site, so possibly the R3Navi does use the same folder for its installation (mc0:/MATRIXTEAM/). But you should still check the contents of your MC by some browser, as described above, to make sure of which folders are used.
Best regards: dlanor
You're right dlanor, the problem with Dev.olution mode (Dev1) of ripper2gold -and as it seems for ripper* chips, is the need of backslashes to find the BOOT.elf. Nevertheless your post help me to find the solution to my needs, aka put the elf I want as boot while I press the square ( /\ )button. This post is for other guys who wants to do the same and who don't care about MC exploit stuff:
1) Get the image of Ripper2Navi
2) Mount it with Daemon tools and copy all files in a folder of your choice (ex: MyPS2Boot)
3) Put in ihis folder an elf of your choice and rename it BOOT.elf
4) Edit INSTALL.CNF and replace EXPLORER.ELF with BOOT.ELF in the last line. You should have now the following line:
COPY cdrom0:\BOOT.ELF;1 mc0:\BOOT\BOOT.ELF
5) Launch CDGenPS2 and dragndrop all the files you have in your directory (start with SYSTEM.CNF, then INSTALL.CNF, EXPLORER.ELF, BOOT.ELF, and finally 0.BIN)
6) Save image as bin, then burn it in 2x mode with Fireburner (or Nero, or any other tool you think it will proper burn your image)
7) Put your freshly burned CD into your PS2, wait until the text "Browser" is ligthening
8) Reboot your PS2 with square button pressed
Hope this will help
PS: If someone knows how to create dir/files with backslashes directly -and not with the need to burn a CD for doing that...
Last edited by pagurus; 05-08-2005 at 05:48 PM.
Reason: Just a liitle precision
All I Get Now Is A Blue Screen With The Only Otption Being Browser, What Is This Navi Supposed To Do?
As dlanor said, the navi CD you have is a copy of software for DMS chips. Unfortunately ripper* seems to miss a piece of writeable memory, and the only thing this CD is doing is to put on your MC a BOOT.elf with backslashes as separator. This BOOT.elf do nothing, as it tries to access ROM. Nevertheless, it has the correct path for dev mode =). If you have followed the steps I have mentionned before (for example by using LaunchELF as BOOT.elf), you only need to reboot after the blue screen (always and again while keeping pressed the square button) to enjoy your elf..
Last edited by pagurus; 05-09-2005 at 06:36 PM.
Reason: my english is rich =)