• All PS1 BIOS Errors!
    8 replies, posted
https://youtu.be/e2HkTzxXH94 I know this was uploaded two months ago but I found it interesting
The startup music messing up is the strangest part of it for me, it almost sounds intentional.
It's hard to tell with the audio quality but it just sounds like it's the samples used in the midi looping forever. I'm surprised all it takes to corrupt it is an unrecognized disc https://files.facepunch.com/forum/upload/109665/6b5170b7-b962-4345-a480-0857e0ae2d34/SCPH1001_00002.wav https://files.facepunch.com/forum/upload/109665/0a51f0f0-60e0-45f1-81f9-65e95514ea53/SCPH1001_00000.wav https://files.facepunch.com/forum/upload/109665/f36ff301-7dd7-4567-ae7d-d8c586ae5ec1/SCPH1001_00001.wav
The startup music is hardcoded into the BIOS and uses the PS1's integrated sound chip. When something goes horribly wrong with the BIOS, code execution is immediately halted, which typically results in held notes because the sound chip doesn't move forward without explicit instruction from the CPU. Personified Harmony is a fucked up edge case where the CPU sorta grinds its gears, iterating through RAM, but since there's no data for the sound chip to play, it stays quiet until an overflow occurs in the memory pointer, which will then reset to 0 and play whatever values are in the registers after that, which causes the seemingly random cacophany of sounds, because that's what's left in RAM after the CPU called it quits. Mind that I read about this a solid year ago and I don't remember specifics so I could be wrong.
Pretty sure most of these bugs will only occur on a modchipped PS1, the PS1 shouldn't be reaching that second black screen with some random disc on an unmodded console, it'll just throw the "Insert Playstation Media" error instead. A lot of modchips just try to trick the PS1 into thinking any disc is a valid PS1 disc by telling the system that the "SCEA/SCEE/SCEI" string, which is embedded in the disc in a particular way, is there. So for some reason, some BIOS revisions lacking certain sanity checks are, I guess, trying to load random data as if it were valid and reaching into that scary undefined territory as a result.
I feel like if you sped up that fearful symphony error in this video, you'd just get the audio from the second logo. which fits with what @Gorou said.
In case you guys want to see how much you can fuck up PS1 with memory corruption (via emulator) https://www.youtube.com/watch?v=NKK7EosIwIA https://www.youtube.com/watch?v=smqaGLBxtKk
Ah yes, the Sony SCEE, my greatest childhood time-sink https://files.facepunch.com/forum/upload/255063/9932f294-41e7-46f1-afb0-eef7e6e0e2da/image.png
Sorry, you need to Log In to post a reply to this thread.