Iris Manager (Official)
|Release Type: Backup Manager||Released on: OCT. 25 2013|
|Developer(s): Estwald / D_skywalk||Version: 2.56|
|Download: Iris Manager (2.56)||CFW or ODE? CFW|
|Source Code: Github||Official Link(s): Release l Wiki|
What's New in version 2.56:
- Added support for devices with NTFS (Windows, read / write)) and EXT2/3/4 (Linux, read only) from "Archive Manager"
- Added support for BD Emu PS3_GM01 activated
NOTE: Remember that writing is experimental support and assume risks when using it: check with "chkdsk" to ensure that no data is lost or corrupted.
With the partitions "ext" to be in read, no problem that can corrupt anything.
1) plug in the device and wait 5 to 10 seconds for it to mount. If not, unplug and re-plug. Multiple devices can be plugged.
2) the partitions are displayed as "ntfs0:" a "ntfsX"
3) Remember that it is important to mount the device before unplugging: from the root option "Archive Manager" or leave Iris Manager
- Added support asynchronous copy to speed up file copying in "Archive Manager"
- Added option in "Archive Manager" (press SELECT) "Get file / folder info" for information on the number and size of files required to copy.
What is Iris Manager?
IRIS Manager is a Backups Manager in continuous development, created by D_Skywalk and based on the HManager Estwald of Hermes, 100% free code using the Psl1ght, allowing that anyone can work together to improve it. Simple loader, but with lots of options and very effective. It allows to load PS3 and PSX Backups.
Supports different CFW, such as:
CFW 3.41, CFW 3.55, CFW 3.55 DEX, CFW 4.21, CFW 4.21 DEX, CFW 4.30, CFW 4.30 DEX, 4.31 CFW, CFW 4.40, CFW 4.41, 4.46 CFW, CFW 4.50
Notice: is not proven compatibility with all the CFW.
View more info about Iris Manager by clicking here
Bing Translation from Spanish to English
See Spanish version on source link below
How does it work Iris Manager?
More info in this post => post info
Iris Manager has 3 modes to be configured, which are: With Controller (you need a disc meter in some games), without Controller (specially designed for people with this problem, the less compatible games since some require inserted disk and cannot be) and finally the Way Disc-Less , not suitable for people without reader or broken with the controller, but that is the way a star since virtualizes disk in the system for the games that require it (accessible in General Options -> Tools).
Within the modes, the sets can be configured in different ways: it is possible that the Disc-Less Mode requires a different configuration in some games for the simple reason that the game itself, makes disk and game.
The different configurations might work as well:
- the games in internal HDD are different to the external. The way to make "BD Emu" changes, in the external data are in Gamez, partition in a "FAT" and if there are files equal to or larger than 4GB, will be parties (Bigfiles passed to Splitfiles) and cannot be launched directly (os data shortfall! ), some games to internal (or with data installed on internal) require LIBFS patched (and in external with the LIBFS colgarian patching) and in some cases, explore_plugin.sprx patched.
to internal, you can change (Global Options) between /dev_hdd0/GAMES, /dev_hdd0/GAMEZ and /dev_hdd0/IMANAGER4/GAMEZ (eye with this, that if borrais the application, you lose everything. It should never delete the application, if you erase something specifically, try some file manager and ask first)
in the external path is /dev_usbxxx/GAMEZ of all the life of God. "GAMES" is an invention of Multiman solely and exclusively and each time i pass that, you must be fluent to thank DeanK or yourselves, not read and assume that you have to do things like, when is the last Multiman mono and these things were already laid down long before.
In games with external splitfiles
unless they have been copied or manipulated by Iris Manager, these games will not be detected automatically. The form of mark is very simple: it puts a character "_" to the name of the folder that contains the game to indicate that cannot be run directly. You can use the option "Check Game". By the way, the first thing that you guys should do is to check the game to know which features you have and now, especially with the version 2.50 , let Iris Manager make some corrections or os notify you if you need change something
if a game is marked with the character "_" and contains splitfiles will be given the option to install that file party within the internal hard disk, in cache. This could save some space with respect to a installation in internal hard disk and the data in cache can be cleared from the same Iris Manager once do not need it, but has the disadvantage that you cannot use "BD Emu" with "Mount BDVD" at the same time. If the game is launched with the splitfiles only, such as one normal, it will crash (black screen, dagger infinite in Uncharted 2 ... by the way, in 2.50 is fixes a problem with this that makes that previous versions did not work as of the cache)
for the operation of Iris Manager is required add two modules of the system patched:
- libfs_patched.sprx -> This module require some games to be able to function in internal hard disk, using asynchronous functions of reading. In external should not be enabled, otherwise you had a bigfile which will be installed in cache and so required. It is active in the Settings (the game) "BD Emu" -> Mount BDVD (only in internal) or LIBFS. In principle, it seems that can be used for all the CFW (or at least, with compatibility down), but the logical thing to do is employ that is appropriate for your version, to ensure.
-Explore_plugin_xxx.sprx -> This module depends on the version of the CFW and binds with the option of the XMB " /app_home" and replaces the original in the disk configurations that require or do not use /app_home, if not /dev_bdvd. When activated, can be seen a disk icon with the word "Game" and helps to increase the compatibility Disc-Less in games (although not lance from there, as in the case of the payload Disc-Less )
is a versatile option related to these two words: if you require disk, requests the presence of disk when he plays, does not address /app_home because it is supposed that we are going to launch from disk ( /dev_bdvd) and uses the explore_plugin patched that uses the path /dev_bdvd. Logically, this is adjusted to the modes with "Controller", "Without controller" or " Disc-Less " and you're not going to ask you to enter a disk if it is physically impossible or you're virtualizing the mode (although at that time, had yet to be virtualized)
The jewel in the crown: we can finally launch games without need to put a disc inside that is just the purpose we are to meet our managers: order to preserve our BDVD reader drive and launch the games from the hard disk, which is a lot easier to replace by the user in case of malfunction, and that gives us greater flexibility.
The operation of the payload can be divided into three parts: the event, the simulation of functions and final assembly.
The event is a signal by software that tells the system when there has been any change in a device. In our case, we want to force the insertion of a disc and for that purpose, we can borrow the insertion of another device (what happens when a pendrive shavers) or try forcing it, using the capture or modification of a syscall that intervene in the process, sending ourselves the signal (this is what happens in the CFW when they already have "automated" the event and pressing "PS" or when you do something that suddenly and seemingly, without coming to tale, you mount the disc).
The simulation of functions covering the part in which the system, once you do case to our event inserting disc, is "to look" that disk type is and what it's supposed to do with it. Culminates with an attempt to mount the disk, which we attempt to manipulate the system that creates that all has gone well.
However, we lack the third part: in the XMB does not appear yet to disk that cannot read data from the "nothing" that we have really mounted: you need to fling a game for that in /dev_bdvd, data can be found as the PARAM.SFO or Icon0.PNG, etc
There are people putting the version 2.36P for that from there "i choppy sound in 4.30 ". Normal, that is because of the Fan Control through payload and can be both Disable (mode SYSCON) as set to Manual Mode (it is not something that advise, but beyond each one: there are people that puts 0x70 speed to be filled) if both bother small micro-breaks in the sound or moving to CFW 4.40 Miralatijera, where sm.self makes this function.
What of the temperatures is a serious matter, and therefore, I can give option to turn it off, but for that reason, is activated by default and there are people who as you can see when you connect it, you will put the fans a lot by that speed in those brief seconds that have elapsed since the ignition, already have the console in 75 or more degrees.. Unfortunately the temperature measurement requires a certain amount of time and this causes micro-breaks (and occasional crashes may) in the CFW who cannot use sm.self, but as has been mentioned, if that is a problem, or you turn (Control Fan is in General Options -> Tools) or you spend to the CFW 4.40 with all its advantages. Since the payload, you cannot make more: not
What of the temperatures is a serious matter, and therefore, I can give option to turn it off, but for that reason, is activated by default and there are people who as you can see when you connect it, you will put the fans a lot by that speed in those brief seconds that have elapsed since the ignition, already have the console in 75 or more degrees.. Unfortunately the temperature measurement requires a certain amount of time and this causes micro-breaks (and occasional crashes may) in the CFW who cannot use sm.self, but as has been mentioned, if that is a problem, or you turn (Control Fan is in General Options -> Tools) or you spend to the CFW 4.40 with all its advantages. Since the payload, no more can be done: it is not a question of bugs, if not that miracles do not exist and has come down to where it has been possible (and wise) arrive.
i appear two disks, what use?
The downstairs, which is not labeled as "Game", which is good.
What mode and which configuration is best?
For me the best way, is the Payload Disc-Less , because the goal of always was to be able to launch the games without a disc inside, obviously. The configuration that i have ever been able to launch the game more difficult is with "BD Emu - Mount BDVD" and the patched modules, with the game Tomb Raider in external disc drive, but there are games that do not require so many complications and nothing happens by test (if anything, to erase the data that you have installed the game, it should be fixed, if it was stuck at some point). What if I think it is very advisable in Disc-Less mode or with Disc, when launching from the, is to activate the function of require disk to prevent the use or the detection of /app_home
the trick of /app_home
The games launched by /app_home van by a different road to the games that are released from disk. And when I say this, I am not referring to that are released only from another site, if not that really changes everything.
/App_home is used during the development phase of the game and this brings about that, whether the system, as the game itself detected its use, cause some problems. For this reason, when a game is launched from the disk itself (or from Disc-Less , which is the same thing) it is recommended that you turn on the "Disk" to prevent any abuse of /app_home that we cause problem.
When we use the explore_plugin.sprx patched, /app_home is replaced by /dev_bdvd. Even so, the system still knowing that has been launched from another track and the game can be detected using a flag that has been launched from hdd (i.e. , app_home from his point of view) and we are in the same. For this reason, although launching from "Game" we had an increase a bit more compatibility in a principle, you will never have the capability of the Disc-Less that uses the proper track.
What could be done "is not that" with the PARAM.SFO?
If, with something of manipulation, but anything accessory that can be done from outside Iris Manager in relation to strange things, should be done from the outside, not from within, so that the people retain their original files in order not to complicate a program where some of them don't even know that the games in external van in GAMEZ.
Download: Iris Manager 3.56 (Official)