Well, then here goes: I have included notes (many) so you have any idea what I've played and that: basically control power off by temperature (90 seconds above 79 degrees) and idle time (60 minutes without touching the pad and provided they are not doing file transfers that we can touch morality) is in routine pad.c reading pad
I think it basically means operation: for not being overloaded reading, I do that every 16 tics read the timer and temperature using syscall, do the necessary checks and if the old timer is not zero and go overtime, catapum Chimpun (without a word)
I've grouped all that well is not lost [+ laughs]. And now the explanation for users:
- Now to have an hour of downtime in Iris console off
- As I said, in Iris temperature alarm: 90 seconds without the temperature drops below 80C in either CPU or RSX and the console is turned off.
- The addition of the callback Disc allows're not constantly checking whether there is a disc in and it allows the reader to rest.
- Added support for redirection libfs.sprx: copy by ftp or via usb (usb :/ gets into iris) libfs_patched.sprx, which is generated by patch_libfs.bat (do not forget to put keys in the data folder!) And games like COD4: MW to operate from internal BD-Emu mount In Tools (press START) the "Copy from / dev_usb / Iris to Iris folder" will make life easier to move things to the installation directory of Iris Manager. For example, if you put "covers" of Multiman within the USB folder, you copy your own content or libfs_parched.sprx we talked about. The option uses asynchronous copying to gain speed.
IMPORTANT: This new option may damage the Iris Manager installation if not used with head, for logical reasons.
NOTE: Obviously, there is no option to delete anything that is copied, except by FTP or pulling or uninstalling other programs (which will render the games settings, etc.) Enjoy it!