Berion
Developer
I have changed partition ID type from 0001h (PFS) to 8300h (Linux) in hex editor and now partition in uLE disappear from list in HDD Manager (it obviously disappear from file manager, but why disappear from HDD Manager menu?).
There is some kind of checksum (or something like that) for each APA "header" in partition index on "hdd0:/__mbr"? If yes, then where, from what range is calculating and how to rehash it?
If You are curious why:
I did that because I'm created on PS2 the Linux space to safe me headache related to recreating APA junk from scratch on PC. In file system space where is PFS, on PC, I have replace it as zeroes and pin that address range as loop device, created EXT2 and put there squashfs files from live distribution via rsync. So that's why I need now change ID from "PlayStation FileSystem" to Linux, to avoid displaying in file manager and killing EXT2 if someone try write something there, yet it must be correctly listed in "__mbr" to avoid overwriting when user create new partition. Main purpose of this complex magic is to keep everything on PS2 because normally fdisk from all Linux expecting MBR (do not mislead it with partition "__mbr" and partition index inside, instead with partition table type) and standard partitioning type. My solution bypassing such limitation so it is possible to have all PS2 related stuff and PS2 Linux on the same HDD.
There is some kind of checksum (or something like that) for each APA "header" in partition index on "hdd0:/__mbr"? If yes, then where, from what range is calculating and how to rehash it?
If You are curious why:
I did that because I'm created on PS2 the Linux space to safe me headache related to recreating APA junk from scratch on PC. In file system space where is PFS, on PC, I have replace it as zeroes and pin that address range as loop device, created EXT2 and put there squashfs files from live distribution via rsync. So that's why I need now change ID from "PlayStation FileSystem" to Linux, to avoid displaying in file manager and killing EXT2 if someone try write something there, yet it must be correctly listed in "__mbr" to avoid overwriting when user create new partition. Main purpose of this complex magic is to keep everything on PS2 because normally fdisk from all Linux expecting MBR (do not mislead it with partition "__mbr" and partition index inside, instead with partition table type) and standard partitioning type. My solution bypassing such limitation so it is possible to have all PS2 related stuff and PS2 Linux on the same HDD.
Last edited:
