Closed GoogleCodeExporter closed 8 years ago
Original comment by ekeeke31@gmail.com
on 14 Apr 2010 at 10:58
Dit it happen in previous versions ? because absolutely nothing has changed
regarding
memory card support since the last official release.
Original comment by ekeeke31@gmail.com
on 14 Apr 2010 at 11:00
Fixed in r435.
For further reference, it was due to 2 things:
(1) memory card encryption was disabled by writing to gamecube EXI base address
(Wii
hardware uses a different address)
(2) the return status of the CARD_GetSectorSize function was not checked which
could
lead to infinite loop in case of error.
Original comment by ekeeke31@gmail.com
on 14 Apr 2010 at 12:33
Issue 72 has been merged into this issue.
Original comment by ekeeke31@gmail.com
on 16 Apr 2010 at 7:36
Original comment by ekeeke31@gmail.com
on 16 Apr 2010 at 7:37
k,thanx. sorry 'bout the duplicate.
i used the latest libogc with 3rd party classic controller mod.thats probably
the
source of my issue. i have an sd card. i just use the memcard to compensate for
the
lack of saveslots.
Original comment by keh...@gmail.com
on 16 Apr 2010 at 7:49
For the record, I got issues too, even with the latest libogc from SVN.
It was when trying to load a savestate which did not exist: instead of giving
me an
error saying the file was not found, it hanged somewhere in the code, probably
trying
to read a nun-existent file.
The problem is that there is nothing in my code that can explain the infinite
loop
and as I said, there haven't been any changes since the last official release,
I only
secured some parts I reviewed in the last revisions. More over, the issue is not
constant and I successfully saved/loaded state files on the memory card.
The reason is probably that Wii memory card support in libogc is quite unstable
or
have been modified: I know they commited some fixes lastly, it might have
introduced
some issues while fixing others, I really don't know. It might also be relate
dto
memory card types (official or not, sector size, format, free space, etc).
Original comment by ekeeke31@gmail.com
on 16 Apr 2010 at 8:08
Original issue reported on code.google.com by
keh...@gmail.com
on 14 Apr 2010 at 9:02