The above video goes away if you are a member and logged in, so log in now!
I think i reported that before, the test with uLE was made too, ESR boot uLE fine, you can work with it any way you like, but soon as you launch the game from uLE the color change scheme start to flash on screen and stop at violet color, it doesn't even start the game at all.
Same problem with the PS2 multiloader, the app start fine, you can select the game you want to boot and soon as you select it, the color change start and stop at violet. ESR boot the disc with the chip off but looks like some parts of ESR are resident in some part of the memory.
The debug version is not meant to be used as the standard version, the debug version is to be used only to find out errors so we can give you precise information about the errors, so you release the standard version and this debug one for debug proposes only not just for multi games, but for any in general.
It's not the results I'm getting here. For me I can launch every game with uLE and it still does work fine (no compatibility loss comparing to launching the game directly).
Originally Posted by katananja
It's because we use different models ffgriever, i don't have any 3x/5x/7x model to test ESR with, maybe it work fine with this models, I don't know, but with 9x is how ESR works. That's why i talk about the debug version, I want to help you out.
Just like i did with Coolaan and Oliveira, i really don't care about ps2 games, i don't play games any more, what excites me about all this is the challenge. I have a chip that runs this kind of stuff, there is no need for me to run ESR or FMCB. I do what I do coming here, talking with the guys, reporting bugs is because i want to help out make this apps compatible and working with many models as possible, simple as that dude.
Do you have sio cable installed in that console? That would help a lot, since it's the least invasive method (software level, not hardware , plus at the point where it freezes we don't really have IOP available from EE, while using on-screen display would cause huge size increase, making it not reliable). Unfortunately at this point, the problem can be caused by both hardware and software (kernel differences).
And yes, the newst model I have available is v15... and up to this one, ESR didn't have any version specific problems.
ratchet and clank 3 still not working 4 me but love your work and kept it up thanks ffgriever 4 all u have done not just from me but all of us
Was it pal or ntsc version? I know someone that has the pal one, but there might be problems getting ntsc one for testing.
Originally Posted by asidtab
I've made the adapter to use with 10K, it's possible to use it with other mothels??
Originally Posted by ffgriever
The new schematic and board design are ready to use, it has the http://psx-scene.com address on it also:
But Oliveira did not send me the points that i have to connect the circuit on, the schematic was his idea and the schematic/board design i did my self, don't have a oscilloscope to find the points or the service manual for 10k model.
It doesn't need to be EE, it could be from ESR it self, you know what part or blocks have problems by showing colors, but doesn't know what exactly happens inside of it. I think the size will not be important for a debug version since no one will use this version to play games, the interest is just to locate bugs or erros.
Originally Posted by ffgriever
The problem to be in my situation is that I'm the only one in this forum (so far) that has a 90k model.
Good news ffgriever!
I've found a fix so ESR can boot multi game discs with PS2 multiloader.
The process works with mcard and dvdv direct only, it doesn't work with dvdv direct off.
All you have to do is at the multiloader screen press circle to change the MODE to 1.33. Remember that i've told you that using uLE did not work before? Now it works if you edit "VER" in the SYSTEM.CNF file, change VER = 1.0 (or what ever you have) to VER = 1.33.
Rebuild the ISO with imgburn, patch it and burn. I've tested this with 2 other multi discs that i have build and they are all working 100%.
Maybe non working games can boot with this change, i don't have any incompatible game so i can't do any further test.
Here is the video to prove it, you can watch online or download the video (h264+AAC):
What the VER string in the SYSTEM.CNF file stand for?
There is any place that we can read more about it?
kevstah2004 asked the same question loooong time ago in another forum, but no one has any clue about it.
I asked it on ngemu forums I believe, I think it's to do with the code version / re-version of the released game / disc rather than anything related to a ps2 function.
Hmmm... It shouldn't change anything. But once again... that's not the behavior I'm getting here (still, launching through uLE works as usual, through PS2Multiloader hangs due to overwriting one of the modules). This time you're the one that's privileged.
Maybe it's just a coincidence? Remember, that you reburned the DVD...?
PS. What version of PS2 Multiloader do you use? Maybe this is the point where we're getting different results .