PAL equivalent of SCPH-50000

Just bumping with: The latest OPL BETA (0.9 r590, labeled as 0.8) has a fix for all the v0 jap machines. And, in case you were meaning FMCB instead of OPL, 1.8c (only installable through a PS3 memory card adapter and a PC) supports v0s as well.

 

I can install FCMB 1.8c from my PS2.

 

That was very useful, thank you.

The discussion about the SCPH-18000 was to do with Free McBoot, since that is the only "v0" model to give you the OSD with FMCB. OPL has been working since version 0.8 public release, and Free McBoot 1.8b from late 2008 was already working on all v0 machines (just with no OSD on SCPH-10000 and SCPH-15000. But that's "unfixable" apparently).

So, there is nothing new in regards to compatibility has happened (in the case of OPL, there's nothing more in that regard to add, and in FMCB's case, it's impossible to add; the OSD).

 

SCPH-18000 isn't really a "V0".

It has the EXACT SAME ROMSET as the second batch of SCPH-30001 released in the US, what the pirates call "V2". :shrug:

It would be better call it the PCMCIA version of V2 because the GH-008 uses even the same EE/GS/IOP chips as the US V1/V2... :nod:

And then that explains why the FMCB software can use OSD patches on the 18000 but not on 10000 and 15000.

Finally, if we have the CEHCZM1 support on PC, we owe all of that to a fellow ASSEMbler forum member.

You know who you are. ray:

 

There is no installer for 1.8c for the PS2. The only way you can install it is with the PS3 MC adapter. If you use the 1.8b installer to install 1.8c you will still be getting 1.8b in the memory card since it uses the KELFs from 1.8b, regardless it says 1.8c in HOSDSYS, that's just the 1.8c CNF.

 

The public beta of Kermit/ODEM also supports the SCPH-10000 (and the DTL-T10000 :nod. IIRC, it was the first CDVD emulator for the 10k hardware, predating this support in OPL by quite some amount of time.

What about SP193's unofficial installer?

 

Have a look here man. This is SP193's installer.

 

An interesting thing to mention regarding Silverbull's ODEM is that it can play a few games OPL can't play right because it uses asynchronous CDVDMAN while OPL uses synchronous. That kind of screw up a lot of late Konami games based on SDK 3.xx ...

Most notably the late DDR games when they use video streaming for music videos.

 

Invalid or Deleted File.

The key you provided for file download was invalid. This is usually caused because the file is no longer stored on Mediafire. This occurs when the file is removed by the originating user or Mediafire.

If you believe you have reached this page in error, please contact support.
Click here to view our help resources






thanks, i didn't knew there was an unofficial installer

 

Far out funny, I just downloaded that 2 days ago. Try this one

 

well thanks, any advice on WHY i might be using it instead of 1.8b? i mean, 1.8b is reliable, haven't had any data loss, performance issues, etc... although i really wanted to know this earlier, the story is i have a v7 usa console with a dead drive (or dead BA/LA, but that's another story...) and HAD a 90004 slim PAL console (which was conveniently sold to a neighbor :dance... Thing is, i learned the hard way cross-region installs were not compatible with 1.8b... tried renaming the BEXEC and BEDATA folders to BAEXEC and BADATA and it didn't work, so i asked around psx-scene, and TnA came up with a multiregion DVDELF, which was to be placed in the INJECT folder of the noobie package... and for unknown reasons it didn't work either (yes, I renamed the folders once installed), all i got was a black screen... so i HAD TO bought an used, working ntsc console (just for clarification, i live in Argentina, the standard for consoles and dvds here is NTSC, while the TV broadcast is PAL-N and the current voltage is 220v, hence the mystery of why i had a pal slim console, these have an internal voltage regulator and work at 220v, all of them are sold premodded here with MI clones, so they can easily output NTSC video ;-)) just to install FMCB... now for the strange part. The "new" console (the one i bought to install FMCB, also a v7 console) booted FMCB 1 out of 5 tries, while the one with the non working drive worked every time... so i've decided to use that one to play games from the hard drive, and additionally transplanted the working drive to this last one... which didn't worked. I've tried using lenschanger to overwrite the EEPROM with the correct lens data, and guess what... didn't work. Now the console with the working drive doesn't even power up anymore... a more extensive, explained journal can be found here http://psx-scene.com/forums/f110/2x-usa-v7-consoles-i-cant-make-fully-working-console-98528/

 

The new one is regionless, so it will work on ANY PS2. You can even make a single file then cross link all regions/filenames to it. That's why the MCA tool has a function to crosslink files.

Only requirement is that the file is sitting on the memory card it's bound to (installed in).

Also FMCB 1.8c contains jimmikaelkael's version of Silverbull's EXECPS2() kernel fix built in for SCPH-10000.

The multi region DVDELF.bin is actually, my doing... :lol:

If you search the PSX-Scene board you will see that there's PPF patches to make some of the encrypted utility discs region free so you can boot them on any PS2... :thumbsup: (really the same voodoo as the DVDELF.bin file)

If you're curious, take the file and do a binary compare with the DVDELF.bin file from DVDPLJ folder at the mini kelfs zip that is floating on the internet. :nod:

Same voodoo was applied on FMCB 1.8c by jimmikaelkael himself...

 

Not on 9000x datecode 8c+ :dance:

 

There's no glitch in the software that allows it to be hacked. Sony took it out which is so stupid, because they new about it way before that.

 

If you think is stupid for an unused, obsolete feature to be taken out preventing exploits to work...

 

From what I've read it was the 10000 series and the 1.0 utility disc that gave people the ability to create the hack in the first place. So I think that it's pretty stupid that Sony waited 9 odd years to get rid of it. It's too late now, the damage (or fun) has been done already.

 

Interesting enough, there's nothing being glitched with FMCB.

It's in fact an trojaning attack where an trusted piece of signed code has compressed portions of it (not signed chunks BTW, Holy security hole, Badman) being used to inject an launcher stub.

If you want to know, the update feature was removed not because of FMCB but because of ESR. :shrug:

 

I knew that you would be able to clarify this for me.

I realize that nothing is being glitched, but there was a glitch in the EEPROM??

And was it the first console that had it??

 

The only glitch I am aware of is the buffer overflow exploit on the parser of the PS1 driver settings file (title.db) which is saved on the "Your system configuration" save file. :nod:

FMCB is a bit more advanced as it's a trojan horse ... :thumbsup:

But well... 1.8c isn't an trojaned SONY file. That's all I'll say about it. :lol:

 

That was what I was meaning. I don't retain information that well.

Yeah I see the community used We all know who's files/method and created their own kelf. I'm much impressed by that.

I just need to learn how to fully utilize Kermit now and I'll be set.