[IngPereira]

Originally Posted by euss ofcourse the redistributed PSN titles are highly optimised/reduced so that they will NOT have problems in the software emulator which is why they are stricly speaking not PS2 titles anymore, but PS3/PSN hybrids.

Yeah but there is a new emu file on 3.7+ is named PS2_netemu.self referring to the PS2 Classics on SEN (Like before with ps1_netemu.self), with this new stuff PS2 Classics are being played on any OFW 3.7+...

Even if you manage to decrypt some stuff from PS2 Classics you will never play that classics on cfw (right now) because you don't have that new emu kernel self on cfw...

[svenmullet]

Originally Posted by euss ofcourse the redistributed PSN titles are highly optimised/reduced so that they will NOT have problems in the software emulator which is why they are stricly speaking not PS2 titles anymore, but PS3/PSN hybrids.

I'm under the impression that PS2 Classics sold on the PS Store contain an iso of the original game.

[euss]

which not mean they are used 1:1 just as the ps2 versus ps3, as the binairy (or ref. file) differs / they just use a simular struct for data (which says nothing about how that data is being used)
************* [ - Post Merged - ] *************

Originally Posted by IngPereira Yeah but there is a new emu file on 3.7+ is named PS2_netemu.self referring to the PS2 Classics on SEN (Like before with ps1_netemu.self), with this new stuff PS2 Classics are being played on any OFW 3.7+... Even if you manage to decrypt some stuff from PS2 Classics you will never play that classics on cfw (right now) because you don't have that new emu kernel self on cfw...

Please point to me what you name 'kernel'

If you ment lv2_kernel.self then I have to disappoint you, ps2 runs in seperate LPAR (SCE_CELLOS_SYSTEM_MGR_PS2 PS2_LPAR)

ps1_emu.self (1.02++) ps1_netemu.self (1.70++) ps1_newemu.self (2.10++) ps1_rom.bin (2.10++) CRC32: D5FF6273 / CRC16: 111D (file is same as in 4.11 and all versions in between) ps2_emu.self (1.02++) ps2_gxemu.self (1.50++) ps2_softemu.self (1.90++) 1.90-1.94 (11065), 2.00-2.10 (11830), 3.15 (12840), 3.41-3.55 (13474), 3.66-3.70 (15435), 3.72-4.11 (15529) ps2_netemu.self (3.70++) psp_emulator.self (3.15++) psp_translator.self (3.15++) \flash0 (3.15++) \release (3.15++)

Imo, the more FW intriguing revisioned part is the iso modules (e.g. sv_iso_for_ps2emu.self) that gotten split since FW 3.60 from other iso modules (e.g. sv_iso_spu_module.self) inside the CoreOS package. With Cobra already released, Sony must have had a very good reason in splitting those up while working on that _net emu module.

[IngPereira]

Not disappoint me friend , I call 'kernel' to this self's because it matches the description if not check the encryption keys of the ps2 emulator and they are the same of lv2_kernel (They are loaded by lv2ldr ) both are loaders for LPAR's they are like lv2_kernel for PS3_LPAR but ps2_emu for PS2_LPAR...

[svenmullet]

Can anyone who is on official firmware and bought one of these PS2 Classics tell me if the controller de-syncs when you boot the game?

[stayhye]

Godhand (PS2 classic PSN) on ofw 4.11:

controllers de-syncs, just like normal, but I have a 60gb NTSC, not that it would make a difference......I have an overlay when I hit home button. With PS2 disc, I get the black background menu when I hit home button(no see-through background)......different emus...

[svenmullet]

AFAIK, if the controller de-syncs that means it's (warm) rebooting into another LPAR (GameOS, PS2, OtherOS, System Update, etc) so this means to me (at least with a fully BC PS3) that the PS2 Classic titles are PS2 binaries, and you are booting a PS2 game when you run them. I'd love to hear from someone with a non-BC PS3.

[gladiator5]

would be the same, i cant say for 100% ofcourse, but the new emu.self, will get tweaked over time too play the games that are getting released on the PSN.

It would still be emulated, and that why the controller de-syncs.

if we could make that ps2_netemu.self (3.70++) compatible on 3.55, we could boot such a game.

and maby even unpack that game, and replace it with another.

bu this ps2_netemu.self (3.70++) uses other keys.

when did the ps2 support for slims started with cobra? which official firmware was out then? does the cobra use this: ps2_netemu.self (3.70++) file?

[euss]

Cobra starts with 3.40/3.41/3.42 and does not use 3.70(+) encrypted/signed files

[gladiator5]

okey, that should make clear why the compatibility on the slims is horrible.

so it uses the 2.60 one?