PS3 Apollo save tool (development thread)

Algol said:
I repeat my demand.

Could you give me the procedure (the method) to install 16 and 32 MB PS2 SAVEs on my PS3 Slim compatible with CFW CECH-2504B (REBUG-4.84.2 REX) and the one under HEN-3.0 .3 (UltraSlim CECH-4204C in HFW-4.88 / HEN-3.0.3).

I thank you in advance and wish you a happy new year 2022, full of good things.

Merci @bucanero
Click to expand...

I don't really know, I never tried using any memory card over 8 Mb on the PS3. For regular memory card images I'd try replacing the VM2 files on the hard disk, but don't know if the console will actually read the new file or not.

for hen, the only option is to encrypt the image to the classic format, but Apollo can only encrypt 8 Mb cards. I did some changes to encrypt bigger cards but I never tested or released it.

if you want to test I might be able to build a version with that change. But again I don't know if the emulator will read the bigger encrypted files
 
Oui, j'accepte de tester cette nouvelle build qui me permettra de créer des VMCs de 16 ou 32 Mo.
Il est dommage que vous-même ou l'un des nombreux utilisateurs de "Apollo" pour PS3 n'ai pas demandé cette fonctionnalité car il est intéressant d'avoir une VMC standard de 8Mo qui reçoive les SAVEs des jeux auxquels on joue (la VMC_0 par ex.) et une plus grosse VMC de 16 ou 32Mo qui reçoive uniquement les copies anciennes (la VMC_1 par ex.).

Merci par avance pour votre contribution @bucanero .


In English via G-Trad :

Yes, I agree to test this new build which will allow me to create 16 or 32 MB VMCs.
It is a pity that you or one of the many users of "Apollo" for PS3 did not request this feature because it is interesting to have a standard 8MB VMC which receives the SAVEs of the games you are playing (the VMC_0 for example) and a larger VMC of 16 or 32MB which receives only the old copies (the VMC_1 for example).

Thank you in advance for your contribution @bucanero.

Algol "le papy".
 
Algol said:
Yes, I agree to test this new build which will allow me to create 16 or 32 MB VMCs.
It is a pity that you or one of the many users of "Apollo" for PS3 did not request this feature because it is interesting to have a standard 8MB VMC which receives the SAVEs of the games you are playing (the VMC_0 for example) and a larger VMC of 16 or 32MB which receives only the old copies (the VMC_1 for example).

Thank you in advance for your contribution @bucanero.

Algol "le papy".
Click to expand...

here's the EBOOT.BIN with the change to encrypt 8, 16, and 32 Mb ps2 virtual memory cards. So in theory you'll get a .VME from that virtual card that you could later use with a ps2 classic game.

Just download the file and replace the eboot on your current Apollo PS3 installation (/dev_hdd0/game/NP0APOLLO/USRDIR/)
https://www.mediafire.com/file/b8kj9ir38iz21z7/EBOOT.BIN/file

Please let me know if it works or not. If the encrypted .VMEs work then I'll include this change in the next release, if it doesn't work then I'll just remove it (no need to keep stuff that doesn't work)

cheers
 
Oui, oui, je démarre aujourd'hui même (cette après-midi) les tests. Je viens de créer une VMC par OPL de 16Mo et aussi une de 32Mo que je rempli de SAVEs pour une quantité d'au moins 16Mo. Les tests vont être réalisés en premier sur une PS3 Slim (CECH-2004B) ayant le REBUG-4.84.2/Cobra-8.3 puis une PS3 de modèle CECH2504B (REBUG-4.84.2/Cobra-8.1), Enfin ce sera le tour avec une PS3 de modèle CECH-3004B (Slim) ayant le Système HFW-4.88/HEN-3.0.3. Après cela, je t'informerai de mes résultats.

Question : Faut-il donner l'extension ".VMC" à toutes les VMC en provenance de OPL (lui c'est du ".bin") et les mettre sur une clef USB pour les convertir dans le dossier "PS2/VMC" ???

Merci de me répondre au plus tôt pour que je démarre mes tests ...


In English via G-Trad :

Yes, yes, I'm starting the tests today (this afternoon). I just created a VMC by OPL of 16MB and also one of 32MB that I filled with SAVEs for an amount of at least 16MB. The tests will be carried out first on a PS3 Slim (CECH-2004B) with REBUG-4.84.2/Cobra-8.3 then a PS3 model CECH2504B (REBUG-4.84.2/Cobra-8.1), Finally it will be the turn with a PS3 model CECH-3004B (Slim) with System HFW-4.88/HEN-3.0.3. After that, I will inform you of my results.

Question: Should we give the ".VMC" extension to all VMCs from OPL (it's ".bin") and put them on a USB key to convert them into the "PS2/VMC" folder ???

Thank you for answering me as soon as possible so that I can start my tests...
 
Probably VM2, not VMC.

"VMC" is a shortcut from "Virtual Memory Card", which means real device image like i.e disc image but for mc.

*.vm2 is extension name used for VMC from PS2, with ECC codes (BTW: Apollo recognize if VMC is with or without them, so don't bother with this).
 
Algol said:
Yes, yes, I'm starting the tests today (this afternoon). I just created a VMC by OPL of 16MB and also one of 32MB that I filled with SAVEs for an amount of at least 16MB. The tests will be carried out first on a PS3 Slim (CECH-2004B) with REBUG-4.84.2/Cobra-8.3 then a PS3 model CECH2504B (REBUG-4.84.2/Cobra-8.1), Finally it will be the turn with a PS3 model CECH-3004B (Slim) with System HFW-4.88/HEN-3.0.3. After that, I will inform you of my results.

Question: Should we give the ".VMC" extension to all VMCs from OPL (it's ".bin") and put them on a USB key to convert them into the "PS2/VMC" folder ???

Thank you for answering me as soon as possible so that I can start my tests...
Click to expand...

Yes you should use the VMC extension and try Apollo to import/convert them as VM2 . (on usb, write the files to /dev_usb00x/PS2/VMC/ , then check the "user backup" menu on Apollo)

for ps2classics, once you have the VM2 on your hard disk, you should be able to import/convert to VME
 
Réponse à @Berion : Non, car il faut que je transforme une "generic_1.bin" en "generic_1.VMC" ou autre pour qu'enfin "Apollo" transforme cette VMC de 16 ou 32Mo en VM2 (ou autre) et ainsi être utilisée dans les PS3.

No, because I have to transform a "generic_1.bin" into "generic_1.VMC" or other so that "Apollo" finally transforms this 16 or 32MB VMC into VM2 (or other) and thus be used in the PS3.
 
Last edited:
Note: I haven't used Apollo's ps2 stuff in a long time, but I know that apollo should detect if the .vmc has ECC or not, and add it as needed when converting to VM2. So hopefully you just need to rename the file and let apollo do the import to vm2
 
La transformation des VMCs de 16 et 32Mo en fichiers ".VM2" a fonctionné, à priori correctement, MAIS ...

=> le système "REBUG-4.84.2/Cobra-8.3" ne gère pas correctement de VMCs dont la taille est supérieure à 8Mo; les copies de VMC à VMC par exemple se font mais dès que le contenu de la VMC dépasse les 8Mo, il y a génération de "fichiers endommagés", rien ne peut y remédier même la fonction système "Reconstruire la base de données" ne peut remédier à ces erreurs.
Je pense que les autres systèmes ne feront pas mieux mis à part si Apollo n'a pas su créer correctement une VM2 via une VMC provenant de OPL (Code ECC ou pas, à voir avec @Berion, lui seul peut m'en dire plus).
Je souhaite que la création de la VM2 soit correcte si elle provient d'une VMC ayant des corrections ECC ou pas, à toi de vérifier @bucanero. Je souhaite continuer ces tests mais il faut être sûr que la transformation est bonne.

Je reste en attente de vos réponses @Berion, @bucanero.


In English :

The transformation of the 16 and 32MB VMCs into ".VM2" files worked, a priori correctly, BUT...

=> the "REBUG-4.84.2/Cobra-8.3" system does not correctly manage VMCs whose size is greater than 8MB; copies of VMC to VMC for example are made but as soon as the content of the VMC exceeds 8MB, there is generation of "damaged files", nothing can remedy this even the system function "Rebuild the database" cannot correct these errors.

I think the other systems will not do better except if Apollo did not know how to correctly create a VM2 via a VMC coming from OPL (ECC code or not, to do with @Berion, only he can tell me more ).

I want the VM2 creation to be correct if it is from a VMC that has ECC fixes or not, up to you to check @bucanero. I want to continue these tests but you have to be sure that the transformation is good.

I am still waiting for your answers @Berion, @bucanero.

Algol "le papy" ...
 
XMB will not display contents from larger VM2 than 8MiB. That's normal.

The question is, does game on emulator recognize save from VM2 and VME larger than 8MiB? Especially if save lie on LBA exceeded 8MiB barrier (You can check it by reading VM2 in IsoBuster).
 
Last edited:
Apollo creates correct VM2 files with ECC from memory card images, that's not the issue. The thing is that the PS3 firmware doesn't support memory cards over 8 Mb as Berion just said. My guess is that most memory card handling code in XMB is hardcoded to 8 Mb.

You should try the VME encryption from Apollo, maybe the ps2classic emulator is not hard-coded to 8Mb memory cards and might be able to handle bigger cards. (but my guess is that it will be hardcoded too)

you can test: import a 16mb vmc to APOLLO0.VM2. Then open a ps2classic save, and import/encrypt the vm2 to VME
 
Quelle version de IsoBuster (sur PC) car moi je ne possède qu'une vieille machine "MacMini 2,53Ghz-C2D - 8Go Ram" "démarrant" directement sous un vieux Windows-Seven-SP1" ???

What version of IsoBuster (on PC) because I only have an old machine "MacMini 2.53Ghz-C2D - 8Go Ram" "starting" directly under an old Windows-Seven-SP1" ???
 
v4.7 and newer (current is 4.9 if I'm correct). It works on even XP. ;)

Remember to keep proper file extension because recognition of ECC/none-ECC card based not by data analysis like in other media/fs but file extension. So i.e *.bin will be thread as none ECC and *.vm2 as with ECC. Messing with it results garbage displaying instead of proper data.
 
bucanero said:
you can test: import a 16mb vmc to APOLLO0.VM2. Then open a ps2classic save, and import/encrypt the vm2 to VME
Click to expand...
Je ne vois pas comment faire cela.
@bucanero - Pouvez-vous me décrire la procédure exacte SVP ???
Je viens de faire une importation directe via APOLLO v1.6.4, il me dit "Encrypting VM2 CARD" et il reste sur cette page avec le trait noir qui tourne autour de l'icône d'APOLLO, ce n'est sûrement pas normal !!!

I don't see how to do this. @bucanero - Can you describe the exact procedure please ???
I just made a direct import via APOLLO v1.6.4, it says "Encrypting VM2 CARD" and it stays on this page with the black line that revolves around the APOLLO icon, this is surely not normal! !!
 
Last edited:
@bucanero :

Apollo v1.6.5 : la page "View Save Detail" est vide (pas de texte) sur ma PS3 UltraSlim CECH-4204C sous le HEN-3.0.3. Peux-tu corriger cette erreur SVP ???

Apollo V1.6.5: The "View Save Detail" page is empty (no text) on my Ultraslim CECH-4204C under HEN-3.0.3. Can you correct this error please ???
 
bucanero said:
please can you explain, step by step, where it fails? HDD saves? usb saves? opening a ps3 save or a PSV file, etc

there are many menus and screens so having the steps to reproduce the issue will help to solve it
Click to expand...

It is showing fine the text on Evilnat 4.88.2.

That issue could happen when system fonts were replaced by custom fonts or when a system language that uses non-ANSI character set is selected. I suggest that @Algol check the current character set in Settings and restore the system fonts if they were replaced.
 
aldostools said:
It is showing fine the text on Evilnat 4.88.2.
Click to expand...

I tested my build on Rebug 4.84 REX, and everything seems to work just fine.

btw, the changes between 1.6.4 and 1.6.5 are minimal , so I'd be surprised if a bug slipped somehow. So please Algol share all the details step-by-step to reproduce the problem, it might be a very specific case (like "opening a codebreaker PS2 save on USB and converting to PSV") that can't be noticed easily.
 
Salut @bucanero.

Bizarrement le souci a disparu ce matin. C'était toutes les pages de APOLLO v1.6.5 où l'on pouvait obtenir des "détails" par la touche "Triangle" qui généraient des pages sans info (un fond mais pas de texte). Ceci est arrivé après l'installation de APOLLO v1.6.5 mais aujourd'hui toutes ces pages fonctionnent correctement. C'est a n'y rien comprendre !!!

Par ailleurs, pourrais-tu répondre à la question que je t'ai posé concernant la procédure exacte pour installer des VMC de taille supérieure à 8Mo (de 16 et 32Mo) juste un peu plus haut dans le fil de discussion ???


Strangely the problem disappeared this morning. It was all the pages of APOLLO v1.6.5 where one could obtain "details" by the "Triangle" key which generated pages without info (a background but no text). This happened after installing APOLLO v1.6.5 but today all these pages work fine. It makes no sense !!!

By the way, could you answer the question I asked you about the exact procedure to install VMCs larger than 8MB (16 and 32MB) just a little higher in the thread ???

Algol "le papy".
 
You must log in or register to reply here.

Similar threads

Back
Top