Editing PS2 Savedata
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 1: | Line 1: | ||
=Common terms used in this page= | =Common terms used in this page= | ||
{{Savedata common terms}} | {{Savedata common terms}} | ||
| Line 39: | Line 37: | ||
===Memory card PS2 (original)=== | ===Memory card PS2 (original)=== | ||
The PS2 memory card file system has a fairly simple design, with some allowances made for the limitations of flash memory. It's overall structure is similar to the well known MS-DOS FAT file system. It uses a file allocation table (FAT) to keep track of allocated space and a hierarchical directory system where all of a file's metadata is stored in | The PS2 memory card file system has a fairly simple design, with some allowances made for the limitations of flash memory. It's overall structure is similar to the well known MS-DOS FAT file system. It uses a file allocation table (FAT) to keep track of allocated space and a hierarchical directory system where all of a file's metadata is stored in it's directory entry. Like the FAT file system, which groups disk sectors into clusters, the PS2 memory card file system groups flash memory pages in to clusters. On standard PS2 memory cards, the cluster size 1024 bytes, or 2 pages long. | ||
*The Superblock | *The Superblock | ||
| Line 170: | Line 168: | ||
===Virtual Memory Card PS2 (.VM2)=== | ===Virtual Memory Card PS2 (.VM2)=== | ||
File structure is the same than a "original PS2 memory card", there are not apparent differences. | File structure is the same than a "original PS2 memory card", there are not apparent differences. | ||
Maximum VM2 Memory Card size that PS3 can handle is 32MB | Maximum VM2 Memory Card size that PS3 can handle is 32MB. 64MB card cause bootloop because indexer can't handle nothing bigger than uint_16 range for memory card free space entry, 65535KB (63.99 MB) = 0xFFFF, while 64 MB memory card is 65536KB (0x10000) so it exceed uint_16 limit, causing unrecoverable database corruption until memory card is deleted somehow from hdd. Probably 63MB VM2 card will work fine, but is just speculation. | ||
*Speculation | *Speculation | ||
Last place to store a PS3 identifyer is inside the FAT filesystem ?... maybe there is none | Last place to store a PS3 identifyer is inside the FAT filesystem ?... maybe there is none | ||
===PS2 Single Save (.PSV)=== | ===PS2 Single Save ? (.PSV)=== | ||
===Virtual Memory Card Encrypted (.VME)=== | ===Virtual Memory Card Encrypted (.VME)=== | ||
When exporting Game Saves for "PS2 classics" (CATEGORY 2P) to a external USB drive there is a "rare" PARAM.SFO exported. This PARAM.SFO seems to be a copy of the main PARAM.SFO from the installed game folder with an added "signature" "injected" at the end of the file (out of his structure) with a | When exporting Game Saves for "PS2 classics" (CATEGORY 2P) to a external USB drive there is a "rare" PARAM.SFO exported. This PARAM.SFO seems to be a copy of the main PARAM.SFO from the installed game folder with an added "signature" "injected" at the end of the file (out of his structure) with a lenght of 20 bytes. Is supposed to be a security feature when exporting the gamesave, is not confirmed if this PARAM.SFO (with the injected "signature" out of his structure) exists in the internal HDD (when importing, or present at some time with the "PS2 virtual memory cards"). | ||
Wrote by ps3hen in ps3hax forums | Wrote by ps3hen in ps3hax forums | ||