[VIRGIN KLM]

Originally Posted by samson have you done any poking at replacing the game of a psn mini/psOne Classic? i think they all use the psp emu on ps3, even ps1... i tried a mini replacing the eboot.pbp with a psp homebrew eboot.pbp and with a bit of hex'in (first few lines and game id/name) got it to black screen w/o errors but crashed my ps3 on exit.. i'd love to know if anyone else has tried, i was thinking of a ps1 memory card management/cheating system to start off with. but a psp usb homebrew loader maybe even possible on ps3. the two games i was gonna use (installed to usb): one (psOne classic) a space shooter for two bucks (mini) psp i'm sure if we all smack our heads hard enough something will happen. tools: PBP Unpacker - http://psp.dashhacks.com/downloads/pbp-unpacker PSX2PSP - http://pspslimhacks.com/download/78/ Signed psp homebrew - http://wololo.net/talk/viewtopic.php?f=2&t=1879 ps. sorry for thread jacking >.<

Did that like 2 months ago I doesn't work that way, let me explain.
The responsible EDAT file contains a full MD5 checksum of the EBOOT.PBP so whatever you'll do with it will result into a stalled execution. It's more of an error than an authentication check. I think @snowydew and @EXE.trim.ALL must have defeated/reverse engineered that check.

BTW you can edit the savegames of PSOne games, they are exactly the same format as the ones ePSXe uses.

[samson]

ok, thanks anyway round it? copying-replacing the md5 or creating edat from dat or eboot? another thing that bugs me is the lack of analog sticks on ps1classics.

[snowydew]

I've taken a break since i last posted about it / contacted a few people with the information though (ps3 related stuff at least). iso.bin.edat is actually a table of contents not md5 checksums. for the most part at least, from what i've checked the psx games are full ToC, kinda like how the ps2 games are loaded (what i'm guessing at least). Regular iso's of playstation one games won't work, unless you have a .bin + .cue. so even then it's annoying >.> Still a bit more to work on though.

[VIRGIN KLM]

Originally Posted by snowydew I've taken a break since i last posted about it / contacted a few people with the information though (ps3 related stuff at least). iso.bin.edat is actually a table of contents not md5 checksums. for the most part at least, from what i've checked the psx games are full ToC, kinda like how the ps2 games are loaded (what i'm guessing at least). Regular iso's of playstation one games won't work, unless you have a .bin + .cue. so even then it's annoying >.> Still a bit more to work on though.

Nice, I couldn't understand exactly what were these constents but I was sure that they were the reason restricting you not replacing the PBP file. Also what about the PSP ones, these ones deffer from the PSOne classics EDATs, these ones I think contain MD5 checksums of the EBOOT.BIN, PARAM.SFO and the DATA.PSARC inside the EBOOT.PBP if I'm not wrong. Also I am unable to undestand exactly how PS2 classics work. For sure 3.55 SDK does not contain the important functions (I think they could be injected to vsh.self if somebody finds a way to work around that) but the ISO file consists from what I understood of a self executable file (I guess the optimized emulator) and a PSARC file containing the contents of the disc compressed. What do you think? Any help I could give maybe? Also I checked your tweets, I hope I could help with the NAND flasher but I doubt I can, if I can tell me...

[snowydew]

From what i've seen, at the top of extracted iso.bin.edat's is 16 bytes, i'm guessing that's what is either used to decrypt the eboot.pbp. Somewhat stumped on that since i can't really do much from where I am (not a reverse engineer heh). The psp ones should also be the same, locations on where the files are or how to unencrypt / decompress files if need be. Once the eboot.pbp's are extracted there should be several things in there, including a small file which will have flags for the emulators of choice, probably to make sure the memory cards are there and such, or to even start the emulator after loading it initially. Chances are crashserious will be finished before i am so :P

[VIRGIN KLM]

Originally Posted by snowydew From what i've seen, at the top of extracted iso.bin.edat's is 16 bytes, i'm guessing that's what is either used to decrypt the eboot.pbp. Somewhat stumped on that since i can't really do much from where I am (not a reverse engineer heh). The psp ones should also be the same, locations on where the files are or how to unencrypt / decompress files if need be. Once the eboot.pbp's are extracted there should be several things in there, including a small file which will have flags for the emulators of choice, probably to make sure the memory cards are there and such, or to even start the emulator after loading it initially. Chances are crashserious will be finished before i am so :P

Very nice, well done you both!
If I can be proven helpful please, feel free to "irritate" me!

[samson]

Originally Posted by zecoxao title says it all. i'd like to know if there has been progress with this emu, more specifically sound

well i best get back on the op's topic..

i sifted through the thread and pulled out all the rev's and language files and updated my post on this thread.
http://www.ps3hax.net/showpost.php?p...7&postcount=15

@snowydew & @CrashSerious best of luck to you both let me know if i can be of any help.