> For the complete documentation index, see [llms.txt](https://corrupt.wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://corrupt.wiki/systems/playstation-2/corrupting-the-ps2.md). # Corrupting the PS2 ### Introduction The PlayStation 2 (officially branded as PS2) is a home video game console developed and marketed by Sony Computer Entertainment. The console builds on its home entertainment value by doubling as a DVD player and accommodating most of the original PlayStation's vast library of games. At the moment, the best way to corrupt PS2 is with RTC, through PCSX2-Vanguard. {% hint style="info" %} Recommended setup: Vector Engine \ \ Startup vector suggestions:\ **Limiter**: One, **Value**: Two\ **Limiter**: Extended, **Value**: Extended\ **Limiter**: PCSX2\_BALL, **Value**: PCSX2\_NOP {% endhint %} ## Recommended Settings The PS2 corrupts very similarly to the Gamecube and Wii. PCSX2 is less stable than Dolphin but it is still sort of comparable. EERAM being the only exposed domain, there's no other domain to corrupt. You can get more results using MIPS Instruction Lists. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://corrupt.wiki/systems/playstation-2/corrupting-the-ps2.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.