[VIRGIN KLM]

Update, comparing files between a Cobra dev_flash and mine:
\ps2emu\ps2_softemu.self - Not Matching
\ps2emu\pst_emu.self - New file
\ps2emu\pst_gxemu.self - New file
\sys\internal\libdtshdcoredec.sprx - Not matching*
\sys\internal\libdtshddec.sprx - Not Matching*
\vsh\module\nas_plugin.sprx - Not matching*
\vsh\module\xmb_plugin.sprx - Not matching*
\vsh\resource\explore\xmb\category_gam2.xml - New File*
\vsh\resource\explore_plugin_full.rco - Not matching*
\vsh\resource\xmb_ingame.rco - Not matching*

Any idea what the ones with ''*'' effectively do?

[Elyssion]

Originally Posted by VIRGIN KLM Update, comparing files between a Cobra dev_flash and mine: \ps2emu\ps2_softemu.self - Not Matching \ps2emu\pst_emu.self - New file \ps2emu\pst_gxemu.self - New file \sys\internal\libdtshdcoredec.sprx - Not matching* \sys\internal\libdtshddec.sprx - Not Matching* \vsh\module\nas_plugin.sprx - Not matching* \vsh\module\xmb_plugin.sprx - Not matching* \vsh\resource\explore\xmb\category_gam2.xml - New File* \vsh\resource\explore_plugin_full.rco - Not matching* \vsh\resource\xmb_ingame.rco - Not matching* Any idea what the ones with ''*'' effectively do?

How are you doing the comparison?
Between which firmwares?

I've comparedoriginal cobra one (not modified ones) with 3.55 OFW, and only differences are ps2_softemu, lv2_kernel and lv1 diffference, the addition of the pst* files and category_gam2.xml.

All other files you mention are equal between OFW and cobra original CFW!

[VIRGIN KLM]

Then something is obviously being patched in lv2.
I guess we found it and we can conclude to a way reverse engineering it.
The correct move to play nativelly PS2 games in a non-BC console is to put to replace the files of the Cobra CFW on the dev_flash as they are (not rename and replace anything) and make a lv2 patch. Still I'm curious to see the xRegistry.sys before and after the patch, there must be a debug value (that till now we don't know what it does) that triggers the PS3 to enable this debug operation.

[superfurry]

I added you on msn mate


Thanks, superfurry

[samson]

just a warning to you all dont try flashing over all of the dev_flash cobra files, you'll get the red error screen on reboot, lol good job i'm a pro at crashing XD installing rebug .. again.

[Dev-Dave]

Good read, is there anything I may help or add to this project? Is there any update to where you are, and whats left to do? and what is the many attractions of the Cobra for you guys, I know my reasons.

[VIRGIN KLM]

Originally Posted by samson just a warning to you all dont try flashing over all of the dev_flash cobra files, you'll get the red error screen on reboot, lol good job i'm a pro at crashing XD installing rebug .. again.

Actually I don't think that i said to people to replace those files ever but better to confirm that they should do so. (No offence but) I guess recently we got proof that not anybody in this forum meets the lowest IQ to understand some things, especially one-post-worders! Thanx samson for the backup!

Originally Posted by Dev-Dave Good read, is there anything I may help or add to this project? Is there any update to where you are, and whats left to do? and what is the many attractions of the Cobra for you guys, I know my reasons.

Yes, thank you for your interest! I spoke with PCSX2 team and actually they got intrigued so what we actually need now, that I'm pretty sure that block us from enabling that feature is a lv2 patch. Hint to the developer that will work on it that there is a suspicious string in the lv2_kernel of Cobra CFW that makes PS3 think it boots on Service Mode on this specific feature or it swaps when it should be active from Service Mode to Retail/Normal Mode.
Here ends my knowledge of understaning code, which actually makes me sad to ask a (probably busy) developer to continue the work but I have no other choise...

[Dev-Dave]

Hi,

I was thinking about this a lot lately, and I, like you have a good but small amount of knowledge of all the code thats used, but what we do have is its all been done before, with acid duel boot. so if they could do it in 3.41, then we can do it in 3.55. and duel boot to a lite version of 3.70 on the usb. the loader is out there but just needs modding to work on 3.55 and the creation of firmware to stick on the usb could be fun, and safe, to try with no fear of bricking ps3. just a thought.

[VIRGIN KLM]

Wait, did Acid CFW unlock the Full Software BC? Because I don't remember that, I think it was actually the first CFW that wasn't (mistakelly) blocking any kind of BC performs.
If yes then it should be more easy to find what has been exactly modified since it's more like ''open'' source... Also forget about the 3.70 thing, Hypervisor doesn't accent any kind of this operationw ithout the NAND/NOR get flashed completelly, what latelly have been actually fixed...

[Dev-Dave]

Originally Posted by VIRGIN KLM Wait, did Acid CFW unlock the Full Software BC? Because I don't remember that, I think it was actually the first CFW that wasn't (mistakelly) blocking any kind of BC performs. If yes then it should be more easy to find what has been exactly modified since it's more like ''open'' source... Also forget about the 3.70 thing, Hypervisor doesn't accent any kind of this operationw ithout the NAND/NOR get flashed completelly, what latelly have been actually fixed...

Its something to look into, cus at the time they didn't have the read and wright Rights as we do now, and a lot more developments have come forth.
I don't know why I said 3.70, as the thought of even downloading it makes me shudder. I am interested with booting duel firmware from a firmware and XMB testing point of view.