

The contents of bblock1 are then copied to the block given in bblock2. Recovery caused by removal of the memory card is implemented whenever a memory card is inserted into the PS2 by checking bblock2, if it's not erased, then programming is assumed to have not been completed. The block being programmed is then erased and writed. Then a copy of the new data that is going to be written is stored in bblock1, and the number of the block that is going to be written is stored in bblock2. Writing data to card requires erasing and reprogramming an entire blockīefore writing a block, both bblock1 and bblock2 are erased. Two complete blocks are reserved to deal with the possibility of the memory card being removed by the user when data is being saved. This gives an available space to store data of: Total-ECC = 8650752-262144 = 8388608 bytes = 8mb Used to store a copy of the data that is going to be programmed to a blockĪ standard Ps2 Memory Card is composed by 1024 blocks, each block contains 16 pages of 528 bytes, for a total of 528*16*1024=8.650.752 bytes (0x840000) Used to store the number of the block that is going to be programmed The last 16 bytes of all the pages are reserved for this code. Memory Card features (0x01 = ECC support, 0x08 = Bad Block support, 0x10 = Erased state zeroed)Įrror Correction Code. Not used.Ĭluster offset of the first cluster of the root directory. Cluster values in the FAT and directory entries are relative to thisĬluster offset number after the highest allocatable cluster.
#Edit ps2 game saves full
(1.2.0.0 = full support for bad_block_table map)įirst allocatable cluster number. While some things like the do end up in fixed locations on standard 8M memory cards, you shouldn't rely on this. Located in the first page of the memory, this is the only part of the file system with a fixed location. The key to the PS2 memory card file system is the superblock. On standard PS2 memory cards, the cluster size 1024 bytes, or 2 pages long.

Like the FAT file system, which groups disk sectors into clusters, the PS2 memory card file system groups flash memory pages in to clusters. 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 its directory entry. It's overall structure is similar to the well known MS-DOS FAT file system. The PS2 memory card file system has a fairly simple design, with some allowances made for the limitations of flash memory. Memory Card Formats PS2 Memory card PS2 (original) See: Content Information Files - Saved Data Utility (PS3)
#Edit ps2 game saves ps3
Any_Other_Files Represents all the other files in the folder generated by the game with any filename and filextensions that are dependant of each game and can vary, e.g: "PROFILE.BIN"(in PS3 Game Saves) or "SECURE.BIN" (in Minis Game Saves) etc.The name assigned to the card when it was created from the "Memory Card Utility (PS/PS2)" in XMB.Name of the folder where the game was installed (different than the TITLE_ID in their PARAM.SFO that refers to the original ID when the game was released years ago as a disc).Name of the folder where the savedata files are stored, composed by TITLE_ID + some variable characters added by the game, e.g: BLES00001-nick01save01.The number assigned by the system to this user when their account was created (is a counter).
