IRISMAN VS uefi-ntfs

Irisman download

When you jailbreak the must have apps are WebmanMod (general CFW/HEN console management) and Irisman (mostly for BluRay discs backup). Basically that's all you'd ever need.

"downgrade" (old method for exploit some game consoles) or new marketed web "term" (thanks youtubers, other forums etc) is not required anymore (almost couple years now) and for multiregion all ps3 are multiregion for ps3,ps2,ps1,psp after CFW or HEN exploits (with little exeption in running ps1 pal video modes easy bypasssed with irishman or managunz homebrew) , for ps3 fats - BC is recomended a CFW (recomended exploit / hack / enable homebrew) use official page for lastest development maintained for developers and collaborators http://ps3xploit.com/ , till now all ps3 machines in 4.89 can be exploited with HFW (Hen) exploit/hack/homebrew enabler, but in your friend case ps3 fat is recomended a CFW like CFW evilnat, like you comment he is in HEN 4.89, till time comes, check next weeks ps3xploit when "buguerville" update bgtoolset tools for install CFW in 4.89 (now in internal testing) incompactible machines (like all ps3 FATS) meanwhille for PS2 iso load try irishman 4.88 https://github.com/aldostools/IRISMAN or managunz https://github.com/Zarh/ManaGunZ (unknow if work in ps BC machines with HEN), not use ps2clasics converts pkg or psn ps2 classics because it will use ps2 "software emulator = low compactibility bugs black screen and higth risk overheat that models etc" keep in mind hardware ps2 chips are only available in ps3 fat models looking back serial CECH"A/B/C/E" (20gb/60gb USA-JAPAN only) if have another "letter " or is EUR model it means not have ps2 hardware chips anymore so in this case ps3 will only use ps2 "software" emulation for this use webmamod plugin from autor here https://github.com/aldostools/webMAN-MOD ps2CONFIGXXX, ps2classics placeholder then use recomended tools for encryt your .iso to .BIN.ENC (read wiki for more instrucctions).

Because we use UEFI:NTFS to ensure that:

Indeed, that 1 MB volume is the UEFI:NTFS partition that is described here.

Please see here or here.

I am the developer of Rufus, and I have spent an inordinate amount of time making sure that, YES, EVEN UEFI COMPUTERS THAT ARE "ALLEGEDLY" ONLY MEANT TO SUPPORT FAT32 FOR BOOT CAN ACTUALLY BOOT FROM THE NTFS PARTITION CREATED BY RUFUS (through the magic of a little solution called UEFI:NTFS). See also this entry from our FAQ.

For more details about the second UEFI:NTFS partition, see https://github.com/pbatard/uefi-ntfs.

Rufus dev here. That's the UEFI:NTFS partition, needed to boot computers that don't have a native NTFS driver and it is completely harmless (and uses a negligible amount of space since it's just 1 MB). So, yes, this is meant to happen.

So if you want to copy the contents of the ISO as is, you need to extract them to exFAT or NTFS (which are file systems that the Windows installer can also read outside of FAT), but this means that you may have to install an exFAT or NTFS UEFI driver to chain load the Windows installer, which is why utilities like Rufus and WoeUSB add a 1 MB UEFI:NTFS partition at the end of the drive, that takes care of that.

Rufus uses UEFI:NTFS, and therefore WILL allow your firmware to boot from NTFS. So, no, you don't have to use FAT32, and you should let Rufus create the drive with NTFS, as, even when using NTFS, it will create a drive that can be booted from UEFI.

If it's because Rufus creates 2 partitions, then you should read about this (UEFI:NTFS is what Rufus uses to boot drives that are NOT compatible with UEFI, such as ones where you cannot use FAT32 because they contain a file that is larger than 4 GB), and understand that the data on the NTFS partition is exactly the same as the one you'd have found on a FAT32 drive, if your data was suitable for FAT32.