To retrieve the timestamp of a file you need to use "cellFsStat" from "libfs.sprx" (mysis suggested it in a irc talk)
And i think the most important file in dev_flash is dev_flash\vsh\module\vsh.self
I was thinking in not to erase backuped files (not to erase the old backup when a new one is done), and let the user keep several ones, and decide if making a copy to PC (for testing, paranoid, or whatever)... but this needs a menu to select the folder to restore
After this selection the EBOOT can trigger the verification process and inform the user if the files matches, his timestamps, (or trigger the warning screens combo, that can be useful if he wants to restore files from a friend that fails all verifications)
Something like this looks a bit more advanced and needs a menu, is just an idea and not prioritary
By now the restoration can be "locked" and automatized like you said, only keeping 1 backup folder... if it works fine is "user error free" and good enought for a first version
About the .txt file (with timestamps or other settings) in the "backups" folder... it must be a specific file for this backup, not shared between backups (so put it inside the backup folder, or the option i said.... rename the folder with this timestamp and you dont need the .txt)
The reason is to prepare the code for later storing more backups folders that are not dependant of an "index.txt" with his timestamps
The restoration is not locked in RC4, actually the way it works since RC4 is this:
Everytime a user installs XMB Manager plus or Rebug Package Manager a backup with the operation timestamp is created.
The restore option is only activated if there are backups in the XMBMANPLS/USRDIR/backups folder (each backup is a folder)
When restore option is activated and you click it you will have a menu listing all you're backups and you can restore whatever you want
That's why with the time stamp on a file in the backups folder it should be enough to resolve this possible firmware change conflict
When i say delete the backups folder is ONLY after the app detects it's a new firmware (different timestamp).
I don't see the point off keeping backups of previous installed firmware since the files are not there anymore.
New version of 1.00RC5:
- more flexible (all readed from directorys, so if you change the directoryes names you will change in the homebrew automaticlly)
You can really add other types of dev_flash changes in new directories if you want.
XMBM+ installer is now more like a flexible dev_flash file changer.
- new auto-detect firmware changes (user installed other firmware deletes old backups)
- new option to delete all backups
Hiyas everyone, nice stuff! (first time posting here xD)
I take this opportunity to share a little thing I found out while using XMBM+
Basically, I been investigating how "Original PS2 Discs" are detected when inserted (using the XMBM+ 'All Active Devices" utility), and these are the results:
It didn't work, but maybe someone can find this useful. Maybe if we are able to force the PS3 to mount the DVD-R disc as "CELL_FS_ISO9660" it could be detected as a PS2 Disc, idk LOL.
Since a long time I been wondering how CobraUSB patches the PS3 to accept DVD-Rs as Original PS2 / PSX discs.
Anyway, sorry if all this is just garbage xD, my original programming strength is for windows platform, lately I been trying to learn about PS3 the most I can.
EDIT: LOL, forget about all this, I just verified with a CD-R backup disc of a PSX game and even when it mounted it as 'CELL_FS_ISO9660' it wont do any difference, still displayed as Data Disc.
SeeYa!
Last edited by CaptainCPS-X; 07-10-2012 at 03:34 PM.
CaptainCPS-X, thanks for your comment and your comment on ps3hax.
We didn't want to release XMBM+ at this RC stage because this RC's was not tested in all firmwares, but the development thread is public and now is in the ps3 news sites...
For what you say in ps3hax, the install seems very slow on ps3 Phat. I'm putting some warnin gmessages in the installer and will in the future try to put a more informative "installign process" to avoid users from disconnecting the ps3 while the setup is beeing made with can corrupt rco and originate a soft brick (need to reinstall firmware from service menu.
1- The new installer looks great: it would be nice if the app could detect the current CFW. The default option is for Cobra CFW, but I believe that most users use Rebug or Kmeaw.
Yes, it would . I don't know how we can get the version of the firmware in c++. I can get the version number but not the description. Do you know?
Originally Posted by aldostools
2- Once the rco's and category_game.xml are flashed, it would be nice to give the option to remove the files to save up to 32MB from internal HDD.
Yes, it's true. I think after 1.00 it's time to install XMBM+ xml files directly in dev_flash. Why? Because it would resolve 3 problems:
1. You could remove the installer with no problems
2. When you remove the installer and XMBM+ is installed you have to reinstall the firmware this will resolve this problem
3. Better compability with gameData tool
Originally Posted by aldostools
3- It would be nice if you could add the mmCM/multiMAN to the XMB like in my XMBM+ mod.
mmCM/multiMAN is in the Homebrew category, backup managers part
Originally Posted by aldostools
4- In Download_Manager-PSN.xml, it didn't show the download icons. Maybe something was broken when you removed the tracking params from the URL.
Yeah. I think we can't have so much items. We will have to see that in the future
Originally Posted by aldostools
5- It would be nice if you could re-add the "★ Install Package Files" to the some place in category_game.xml (even when it is redundant)
The last time I installed XMBM+ and deleted its app icon from the XMB, I had a hard time trying to reinstall XMBM+ and any other PKG.
To fix it I had to re-flash the original category_game.xml manually via FTP.
what i described in point 2 would resolve this problem
Originally Posted by aldostools
6- The spanish translation needs some improvement (it looks like translated via Google). Where do I change the text?
XMBM+ Installer:
- More information when copying versions (andreus)
- Try to reorder automaticly directory Firmware reading to put normal CFW in first and rebug in second and also XMBM+ first instead of rebug and also the backups from latest to first (andreus)
XMBM+ XMB App:
- Correct PSN part (aldostools, can you do it?)
- Complete homebrew (waiting for XiorgON to finish this)
Test in more firmware (all)
For 1.10:
XMBM+ Installer:
- Install XMBM+ XMB app in dev_flash instead of dev_hdd0 (andreus)
- Changes in sprx at least for changing unlink text to delete (ps3hen?)
- Check if is possible to detect different 3.55 firmware versions (andreus)
- Check why it doesn't appear "Install all packages" in package manager
XMBM+ XMB App:
- Sandungas category suggestions
- Put mmCM likealdos tools suggested? (this is pratical is true, but does not make much structural sense, so give your opinion)
Originally Posted by sandungas
Reply With Quote
