That was just thoughts.
I'm still in a learning process for low level programming, but I have a slight Idea of how complicated it can be, especially when there doesn't have any spare ram on the system available to build up a game-dedicated file allocation table.
But you (SWISS programmers) made wonders passing so many huge obstacles than we sometimes tend to believe nothing is impossible.
What I don't catch, is how much a file redirection would be simpler when it comes to a whole memcard image than just a file.
When you do memcard emulation, you redirect a file call to a filesystem (Memcard file allocation format), in a file (the virtual memcard image file), in another filesystem (the SD file allocation format)? On the paper, can't it be on par with redirecting a file call to a filesystem translated to another file system, if the file is already in the expected format?
Do games care of the rest of the memcard's structure once they've been given the file they seek for?
Aren't .gci files the exact file image from the memcard's filesystem?
Can't we predict what save file the game will expect?
Just questions out of curiosity, I don't want to sound rude or over-expecting.
