18
Parzi
6y

trying to do anything on the PS2 is almost fucking impossible

i imagine a board meeting where they were designing the hardware

"how can we make this insanely hard to use?"

"let's make decentralized partition definitions, allow fragmenting of entire partitions, and require all partitions to be rounded to 4MB. If you delete a partition, don't wipe the partition out, just rename it to "_empty" and the system will do it for you, except it actually won't because fuck you"

"let's require 1-bit serial registers to be used for memory card access and make sure you can't take more than 8 CPU cycles to push each bit or it'll trash the memory card"

"let's make the network module run on a 3-bit serial register and when initialized it halves the available memory but only after 8 seconds of activity"

"let's require the system to load feature modules called "IOPs" and require the software to declare which of the 256 possible slots it wants to use (max of 8 IOPs) then insert stubs into those. Any other IOP you call will hang the system and probably corrupt the HDD. You also have to overwrite the stubbed IOPs with your own but only if you can have the stubs chainload the other IOPs on top of themselves"

"let's require you to write to the controller registers to update them, but you have to write the other controller's last-polled state or the controller IOP will hang"

of course this couldn't make sense, it's

s s s s
o o o o
n n n n
y y y y

Comments
  • 9
    @dudeking this is all documented in the OFFICIAL INTERNAL-USE-ONLY SDK. And that means all of this had to be obeyed by all devs.
  • 2
    It’s design is meant to be that way
  • 3
    Everyone else seemedbto manage..?
  • 3
    There is a presentation by failoverflow on hacking a PS4 to run linux. They essentially explain the fuckfest that is the PS4 hardware.
Add Comment