TOKOBOT WORKING WITH SAVES

[gthirst]

Well after reading this thread from start to finish and using every combination listed in 8c settings I have come to the conclusion this is b.s. I am using a version 1.5 U.S. psp with lumines in the umd slot. Settings in 8c have been tried with each option listed in every position but I still get the Lumines umd screen upon return to selection screen. I can get the game to run fine through fast loader (without saves) but it won't start at all through umd8c. The downloaded version has the f0 and f1 folders and the iso is listed as "sushi-tokobot" and also includes the nfo file. This does not work!?!?!?!?!?!?!?!?

lol its not bs.

just use copy load with no special settings and boot the game

[mmmmmm]

I'm so glad of PSP-hacks. I was just on maxconsoles. I said "I hope the sushi trick will be applied to more games", meaning the ones that play on 1.5 but wont save. Next thing I get a PM from a mod [I didnt pay attention to its name] saying "dont mention release groups, you wont be warned again". Like their trying to keep it all respectable. More like they are keeping their cocks up their own arses!

[Aenea]

What I meant was, where do I find this EBOOT?
And how does it work?

If you have the working version of Tokobot there's an EBOOT.BIN in SYSDIR which contains an intro and also the loader which makes Tokobot work. It has some form of firmware emu (plus lots more actually, it isn't that simple) which makes the games work...

[Aenea]

i have same problem...the hanging sushi screen....press the x key and it locks up?

You are using umd emu with a game umd in the drive, with the correct settings and with the F0 and F1 folders in the root of the mem.stick?

[Aenea]

so do you plan on doing coding each eboot.bin in EVERY 2.0 game and releasing them individually like tokobot? or will there be some kind of Kxploit-type "patcher" in the future?

Every game will be re-released when they start working (almost there) and they will be locked to that particular game. When all games are working I'm planning on creating a general loader for ORIGINAL 2.x umd's...

[Aenea]

y does this game need v2.00 F0 and F1 folders if the Flash0, Flash1 emulation is off? as then nothing will b used?

Because the loader on the iso image contains it's own firmware emulation code ('cos someday it has to be useable without umd emu and 'cos this way I know exactly what is being emulated so no conflicts happen)...

[Gary13579]

If you have the working version of Tokobot there's an EBOOT.BIN in SYSDIR which contains an intro and also the loader which makes Tokobot work. It has some form of firmware emu (plus lots more actually, it isn't that simple) which makes the games work...

Aha, so the EBOOT.BIN contains all the firmware emulation code, and the ISO is all you need to have to run it...
Makes sense now :D

And your plan to make a loader for the original UMD only, good luck with that. I would buy SOCOM if it worked on a 1.5, definetly. However, most people do not agree with me. Look at what happened to McZonk with his ISO check, many people got pissed at him.
Also, wouldn't you just be able to load the ISO with UMD Emu on system menu, then run your program? You're going to have to add some check to see if UMD Emu is running and the ISO is mounted before you load the UMD...
Maybe just dump memory before and after you start UMD Emu, and compare?
I'm sure you know more then me, just trying to help :P

[Mookdog]

Why when someone cannot get something to work right away its b.s. ?
It just cracks me up how people are taking the time to get games to work
and people got to doubt them or their work cause Mr Joe Blow can't get it running. Do me a huge favor before you post on any psp forum. Read the success stories before you post.

Just my 2 cents
Mookdog

[fidzer]

Hi aenea , if your reading this. I am fairly new to the files system etc of the psp. Im trying to understand how eboot and boot bin files work.
From what i gather , boot.bin files are basically unencrypted eboot files and thats how umdemulator etc work. I have also used your 2.x eboot/prx decrypter to look at enecrypted eboots.
Now, from what i can see from looking around various places , eboots are compiled elf/mips files?
These call all the fuctions required to boot games etc.
Ive had a look through a few boot files etc using various programs, from plain text editors to a reverse compiler and managed to see various procedure calls etc.
What i'd like to know is what is the best way to view/edit + recompile them. im fairly sure that my reasons for this are obvious and I dont expect to be handed this info on a plate but a few pointers would be cool.
Righty , im gonna delve back into this eboots and see if i can find the procedure that calls wrong game when the checksums dont match!

[nef]

Every game will be re-released when they start working (almost there) and they will be locked to that particular game. When all games are working I'm planning on creating a general loader for ORIGINAL 2.x umd's...

AMEN.