kadorna2
Member
Correct me if I'm wrong but i don't think it's possible to access lv1 from ps2 lv2RSX clock can be set in real time through lv1 poke
Correct me if I'm wrong but i don't think it's possible to access lv1 from ps2 lv2RSX clock can be set in real time through lv1 poke
Correct me if I'm wrong but i don't think it's possible to access lv1 from ps2 lv2
that's exactly my point, how do you use a syscall that's not enabled in the emu while not being able to access the rest of the system? not that you can use ps3mapi or any other RTM tools, the emu should be modded first to make that system call. chicken and egg situationWhy can't? You just need to use "sc 1" instruction to access hvcall. It used in lv2 and linux. Insert it anywhere in emu and it will work. Ofc emu itself must use it to do anything at all.
that's exactly my point, how do you use a syscall that's not enabled in the emu while not being able to access the rest of the system? not that you can use ps3mapi or any other RTM tools, the emu should be modded first to make that system call. chicken and egg situation
what about enabling it with config files?
EDIT: we should also be able to revert the OC as soon as emu exits or the clocks will be the same on xmb and anything you run after unless you reboot
Hello, is it possible to implement rsx overclock inside the emu? I just found out during qCFW testing on my superslim that booting ps2 emu will reboot the whole console. This causes rsx clock to reset to default value. This mean for now only way to overclock is to use old custom pup method.
Thanks
What is the difference?https://limewire.com/d/519lr#nRzeSLJiVI
ps2_netemu patched with the earlier ps2_softemu bios, enjoy folks!
For reference ps2_softemu stores the bios at section/segment 38, ps2_netemu is 40.
What is the difference?
It doesn't boot any iso games just packages
It doesn't boot any iso games just packages
just a guess, but it could be improper hash for cobra, since the hash has changed, so I'd imagine no cobra functions work.
I decrypted the original .self using rpcs3, everything else failed complaining about missing keys or npdrm, metadata, I used makeself from break n make to resign it after I edited the file in a hexeditor to overwrite the bios section.
it won't matter. even if you decrypt, then reencrypt with no changes, the hash will be different, because of encryption and compression.
Yeah I was wondering why the filesizes of the .self kept changing vs the original, it kept throwing me off thinking I was using a older base build or smaller .elf to begin with.
I don't know what to suggest. you could try to compile cobra just to test it. I think there's a safeguard in case cobra is messed up, to disable cobra, but I could be wrong. the latest cobra is on github under @Evilnat 's account. I don't know if you'd be interested in testing that. good luck. if you have a NOR console, it's actually pretty hard to hard brick the system. afaik, you could even delete all of dev_blind and still recover. the recovery menu is the emer_init.self, and it's part of the coreOS, which you don't have access to in cfw, for safety reasons. I've heard NAND consoles are more sensitive though, that you can hard brick, because most of the firmware is not located on the hard drive.
Is this official scetool or opensource? how do I get the template file?