popsloader v3: bug on creation of pops.cfg

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Delete pops.cfg file if exist
2. Run any PS1 game with R button pressed, and select any pops version
3. Exit game and check pops.cfg in text editor

What is the expected output? What do you see instead?
Expected output: only 1 entry in the pops.cfg. Instead, there are 2 duplicated 
DISC ID entries in pops.cfg, one followed by null characters, the other 
followed by the pops version. Second time loading will rectify the issue by 
changing the first entry, but the duplicated entry persists. This also happens 
with any new games loaded for the first time.

What version of the product are you using? On what operating system?
v3, 6.20 PRO-B9 official, 3g model, hud.prx running

Please provide any additional information below.
The file attached is the result of trying to run Chrono Cross once, and 
followed by Brave Fencer Musashi once. Both are using a fixed DISC ID.

Original issue reported on code.google.com by aditi...@gmail.com on 26 Aug 2011 at 9:51

Attachments:

• pops.cfg

[GoogleCodeExporter]

correct brave fencer musashi did not wanted to boot on 3.00 pops
dont know why i build the popsloader V3 with popdeco utility
none files missing all with same Md5 as in V4D all the same the deference
is that popsloader V3 wont boot brave fencer musashi and popsloader V4D
build with popsdeco work awesome all pops work for me.

Original comment by jvhellra...@gmail.com on 26 Aug 2011 at 7:27

[GoogleCodeExporter]

so save_config isn't proper.

popsloader.prx calls load_config() then save_config().
currently if load_config() failed, fallback save_config() will be called.
Here null entry will be appended, but config_offset isn't saved.
so popsloader.prx's saving pops config for the first time will append extra 
entry.

That issue was reported by ringo (piccolo33.dip.jp) Japanese tester and fixed 
in popsloader mod v3a.

save_config()
---
    if(config_offset >= 0) {
        sceIoLseek(fd, config_offset * sizeof(CONFIG), PSP_SEEK_SET);
    }else{
        SceIoStat st;
        if(sceIoGetstat(path,&st)>=0)config_offset=st.st_size>>4;
    }
---

Original comment by popsd...@gmail.com on 27 Aug 2011 at 2:06

[GoogleCodeExporter]

Actually, as I said, if you try to load the game again (in this case, Brave 
Fencer Musashi), it will run fine (it will overwrite the NULL config). Musashi 
is one of those games that only run in certain pops, so if you run it the first 
time, it will not work as it is loaded with whatever OFW you were on (in my 
case 6.20). Try loading it again, and it will load with the correct pops.

Original comment by aditi...@gmail.com on 27 Aug 2011 at 3:08

[GoogleCodeExporter]

try to boot brave fencer with pops 302 
nothing happen  it when to the OFW with error
80000004 <= or something like that non of the pops
from 302 to 310 will boot brave fencer for me on version 3
but in popsloader V4D i build it the same way i build V3
same OFW use to build them in V3 brave fencer wont boot
and in V4D every single pops work and boots brave fencer normal
both where build with popsdeco v2.

Original comment by jvhellra...@gmail.com on 27 Aug 2011 at 5:41

[GoogleCodeExporter]

I think Musashi is a bad game to test pops for, since the game is problematic 
to begin with... Musashi will only run properly on 3.40 pops with DISC ID 
SLPS01156.

Original comment by aditi...@gmail.com on 27 Aug 2011 at 5:49

[GoogleCodeExporter]

mot with me on V4D brave fencer boots on 302
with DISC ID SLPS01156 boots to on 303 pops too
since V1 popsloader but in V3 popslaoder i get 
that error but in V4D i dont get no error at all.

Original comment by jvhellra...@gmail.com on 28 Aug 2011 at 1:27

[GoogleCodeExporter]

Replace common/conf.c to build official v3 fixed.

Original comment by popsd...@gmail.com on 7 Nov 2011 at 11:10

Attachments:

• conf.c