thanks all for the answers, I understand a little more about the UMD format now.
Too bad you cant use the same tactics on every iso, rip certian files, relink, dummy them. It probably depends on the game itself what kind of security it had.
btw I also see a lot of prx fixes, why are these needed? doesnt every iso run with devhook, without modifing the prx files?
I've had one or two isos that worked fine until i removed the update folder then for some reason they wouldnt work so I just opened notebook and made a 0k file and named them boot.bin etc. and put them in an update folder in the same location and then they worked fine again and the update icon didnt come up either. I don't know if any else has this issue, but hopefully it helps some1 out there.
This thread help me alots, now i don't have to worry about the update icon showing under the game in Devhook XMB... I'm so worry letting my sis bring my psp to school and accidently update it.
same with Exit ... I was said it's because LBA but I thought lastest UMDGen keeps LBA.
else it works well, I always delete UPDATE folder, it failed only twice.
I guess eboot.bin and boot.bin are needed if you use an umd emulation (devhook or system menu in daxziso/umdemu) , got an error without (contrary to "direct run").
actually with devhook 0.4x, the update icon won't excute update operation
my way to remove this: create 3 files< "PARAM.SFO" "EBOOT.BIN" "DATA.BIN" > filled with zero(HEX editor).replace orginal update files with these zero filled ones by a tool named "VCDROM Extension". BUT make sure you mark the checkbox "Keep Original File Size".then save and exit. this should be ok.compressed with Ciso can release these zero filled spaces.
what's wrong with removing update folder, it's not like as if the game will freeze. ANd is there a way to not have the upgrade icon showing when emulating firmware/games using devhook?
Reply With Quote
