➛ Scope

This guide will walk you through the processes of:

• Installing OPL with (preferably best settings & configurations for your unique setup and) no prior experience or knowledge of PS2 Modding.
• Upgrading / Downgrading an existing OPL installation in the event you encounter a bug or wish to try out a new or deprecated feature.
• Troubleshoot an error with a bad OPL install due to environment changes or improper config.

➛ What is Open PS2 Loader?

Before beginning, it is important to understand what OPL is and why are we using it in the first place. OPL is a game and application loader compatible with all PS2 & backwards compatible PS3 units with support for various devices (on PS2 units) namely:

• BDM (USB/MMCE/MX4SIO/exFAT format HDDs)
• APA format HDDs
• SMBv1 share devices
• UPDBD
• iLink (SBP2 compliant storage devices via IEE1394)

It supports loading files in the:

• *.iso
• *.zso
• .elf (for APPS)
  formats.

Along with this, OPL is also capable of advanced features like resolution switching (upto 1080i) via GSM, emulating other gamepads like DS3/DS4 and passing them as PS2 compatible DualShock 2 controllers via **PADEMU ** and also injecting cheats into games at runtime.

➛ Determining the best configuration for our OPL install

Now that we have a good idea of what OPL is, we will now proceed to understand the various configurations it can be adapted to so you can determine which one works best with your particular setup.

- For Phat PS2s

If you have a Phat model PS2 or a SCPH-70XXX model slim with the IDE HDD mod, you can use these setups below (sorted: best to worst):

1. APA Jail setup (APA Partitions + exFAT partitions on same disk)
2. Pure exFAT format HDD
3. APA HDD Method
4. MMCE
5. MX4SIO
6. UDPBD
7. SMBv1 share
8. exFAT format USB Storage
9. iLink (only on models <SCPH-50XXX)

- For Slim PS2s

If you have a Slimline model PS2, you can use these setups below (sorted: best to worst):

1. MMCE
2. MX4SIO
3. UDPBD
4. SMBv1 share
5. exFAT format USB Storage

➛ APA Jail

➛ exFAT format HDD

➛ APA format HDD

➛ MMCE

➛ MX4SIO

➛ UDPBD

➛ SMBv1 share

➛ exFAT format USB Storage

➛ iLink

This guide will walk you through the very very basics of installing an App via it’s SAS Compliant APP PSU* in your MemoryCard.

➛ What is an App PSU?

Before beginning, you might ask yourself what is an APP PSU and why do we need it? For starters a PSU file is like a .zip file for the PS2, we can use it to pack stuff on the console. Much like zip files, if you package some files in a PSU they remain exactly in the same position after extraction. The reason this is useful is that we can package PS2 executables (or ELFs) along with other interesting stuff like icons and configuration into 1 easy to share and install file. PSUs also preserve the timestamp data of the package, allowing for pinned applications within the PS2 Browser or knowing when an app was last updated.

➛ What makes a PSU ‘SAS Compliant’?

SAS is a new upcoming standard on the PS2 which aims to unify how apps work and interact with each other on the PS2. When we talk about a SAS Compliant PSU we mean a PSU which has the following:

• A 'prefix' to denote what 'type' of Application is in the package. Example: SYS for System-Apps, GME for Games, APP for Standard executables.
• A 3D icon with it's type indicators which shows up in the OSDSYS (PS2's Browser) with separate Copy and Delete icons for the respective action.
• A title.cfg file which contains basic information about the app and makes it readable and executable from other apps such as Open PS2 Loader (OPL) and RetroLauncher.

…and more.

Now that we know what we are working with let us move on to the…

➛ Prerequisites

You’ll need:

1. A MemoryCard with atleast 1MB free space
2. A way to launch LaunchELF/uLaunchELF/wLaunchELF
3. A USB drive formatted as FAT32 with atleast 2MB free space
4. A way to copy over the APP PSU downloaded from SAS Apps Archive
5. Patience to follow the guide (Most important)

➛ Steps

Step 1: Open LaunchELF

Once you are in LaunchELF, check the version to make sure the one you are using can extract PSUs.

Step 2: Find the PSU

Press ‘Circle’ to enter the FileBrowser, then navigate to your FAT32 formatted USB

Press circle to enter it and look for the PSU you want to install.

Once you have highlighted the PSU you want to install, Press ‘R1’ to bring up the Menu and navigate to ‘Copy’ and select it by pressing ‘Circle’.

Step 3: Installing

Once you have successfully ‘Copied’ the file (check the box on the right), we will now paste it.

Navigate to your MemoryCard where you wish to install the App and press ‘Circle’ to Enter it.

Now press ‘R1’ to open the Menu again and navigate to the psuPaste option and press circle.

Now relax for a while and let the PS2 copy stuff over. Don’t press any buttons on the controller or unplug/remove your MC, USB drive, controller or any other accessory.

Once the dialogue box disappears, the app should be installed on your MemoryCard.

Step 4: Verification

You can verify if everything is installed as expected.

Now reboot your PS2 and naviagte to the ‘Browser’ and ‘MemoryCard 1 or 2’ (depending on where you installed the app)

Step 5: Rinse and Repeat!

Congratulations! Now that you have learned how to install SAS Compliant APP PSUs you are ready to install whatever apps you may desire.

If you come across something which is not on the SAS Apps Archive, let us know and we will add it at the earliest!

See ya!  

1. Understanding BlueRetro and Button Remapping

• BlueRetro allows you to connect modern Bluetooth controllers (e.g., DualShock 3/4) to your PS2 and offers customizable button mappings, which is perfect if you want to swap the R2 and X buttons to take advantage of R2’s pressure sensitivity.
• BlueRetro runs on the ESP32 and hosts a web interface that can be accessed via Bluetooth for configuration.

2. Accessing the BlueRetro Web Interface via Bluetooth:

• Ensure that your ESP32 running BlueRetro is connected to the PS2 and powered on.
• On your Bluetooth-enabled device (laptop, phone, etc.), connect to the BlueRetro ESP32 via Bluetooth.
• After connecting, open a web browser and type:
  http://blueretro.io
• This will bring up the BlueRetro web interface where you can configure controller settings.

3. Navigating to Controller Configuration:

• Once in the BlueRetro web interface, go to the section called Controller Mapping or Player Configuration. Here, you will see a mapping table showing which buttons are assigned to which inputs on your PS2.
• For more information on this, refer to the BlueRetro Wiki at:
  https://blueretro.io/wiki

4. Swapping R2 and X for Pressure Sensitivity:

• Locate the X Button (Cross):
  • Find the X button (cross) in the mapping interface. By default, this will be mapped to the X button on your controller. You need to change this mapping to R2.
• Change R2 Mapping:
  • Next, find R2 in the mapping interface and change it to X.
  • This will make R2 function as the X button, allowing you to use its pressure-sensitive feature for tasks normally assigned to X (like acceleration or certain in-game actions).

5. Saving the Changes:

• After you’ve swapped R2 and X, click the Save Configuration button in the web interface to apply these changes.
• BlueRetro will store this configuration, so you won’t need to redo the mapping each time you use the PS2.

6. Testing the Configuration:

• Now that you’ve saved the button mappings, boot up a game that uses pressure sensitivity (e.g., a racing game where X is used for acceleration). Pressing R2 should now function like X but with the benefit of pressure sensitivity.

7. Further Button Remapping or Adjustments:

• If you want to remap more buttons or fine-tune your setup, you can do so easily through the same web interface. BlueRetro supports remapping most buttons on modern controllers to match the PS2’s layout.

Resources for BlueRetro and Button Remapping:

• BlueRetro GitHub (Project repository and latest firmware updates):
  https://github.com/darthcloud/BlueRetro

• BlueRetro Wiki (Comprehensive guide on setup, remapping, and troubleshooting):
  https://blueretro.io/wiki

• BlueRetro FAQ (Frequently asked questions, including button mapping details):
  https://blueretro.io/wiki/#/faq

By following these steps, you’ll have successfully swapped R2 and X to ensure that you can take full advantage of R2’s pressure sensitivity for games that benefit from it. Let me know if you encounter any issues or need further clarification!

To clarify, when I mentioned “if compatible” regarding multiple profiles and game-specific remapping, I was referring to features that might depend on the version of the BlueRetro firmware you’re using. Let’s break down what is compatible and what isn’t based on the current state of BlueRetro functionality:

BlueRetro Compatibility for Button Remapping and Profiles:

1. Global Button Remapping (Always Compatible):
   • Every version of BlueRetro supports global button remapping. Once you remap buttons like R2 and X, this remap will apply to all connected controllers and all games by default.
   • This means if you swap R2 and X, it will stay swapped for every game and controller until you change the mapping again.
2. Game-Specific Profiles (Limited Support):
   • Profile-based remapping—where you can save different button layouts for different games or situations—depends on the firmware version you are using.
   • As of the latest updates (September 2023), BlueRetro supports multiple profiles, but not all configurations may allow this feature in full detail yet.

Current BlueRetro Firmware Features:

• Global Remap: Always supported.
• Multiple Profiles: Supported in newer firmware, but still evolving. You can save and switch profiles for different controller setups or specific games. However, profile management may be limited depending on the setup of your ESP32 and the specific build you’re using.
• Controller-Specific Remapping: BlueRetro does not yet offer a fully automated system for switching remaps based on individual games, but you can manually change profiles through the web interface.

Compatibility Check:

• If you’re using an updated firmware version (recent 2023 builds), you likely have access to multiple profiles and can configure button mappings for different setups manually.
• Older or custom builds of BlueRetro may not yet support profile management, and in these cases, only global remapping is available.

For more specific compatibility, you can check your firmware version and compare it to the latest BlueRetro releases on their GitHub page:
https://github.com/darthcloud/BlueRetro/releases

You can also refer to the detailed Wiki for updated profile-related features:
https://blueretro.io/wiki

What Is Compatible:

• Global button remapping works on all versions.
• Multiple profiles or game-specific remapping may be available in recent versions, but it is not an automatic feature based on the game you’re playing.

1. Check Current Firmware Version:
   • Access the BlueRetro web interface by connecting via Bluetooth and visiting:
     http://blueretro.io
   • The current firmware version is often displayed in the interface or accessible via a settings/about page.
2. Download the Latest Firmware:
   • Visit the BlueRetro GitHub releases page to find the latest firmware version:
     https://github.com/darthcloud/BlueRetro/releases
   • Download the latest release compatible with your ESP32 board.
3. Update the Firmware:
   • Follow the instructions in the BlueRetro Wiki for updating the firmware. This typically involves:
     • Connecting the ESP32 to your computer via USB.
     • Using tools like esptool to flash the new firmware onto the ESP32.
   • Detailed instructions for updating can be found here:
     https://blueretro.io/wiki/#/updating
4. Verify Profile Management Features:
   • After updating, recheck the BlueRetro web interface to confirm if game-specific profiles or advanced remapping features are available.
   • The latest firmware versions should include the ability to create and manage multiple profiles, allowing you to configure specific button mappings for different games.

What to Expect with Upgraded Firmware

• Game-Specific Profiles: With newer firmware, you should be able to save and switch between different button remapping profiles. This means you can have specific configurations for different games.
• Profile Management: Look for options in the web interface that allow you to create, save, and switch profiles. This feature enables you to customize your setup based on the needs of each game.
• Improved Functionality: Upgrades often come with bug fixes and new features, improving overall performance and usability.

Resources

• BlueRetro GitHub Releases:
  https://github.com/darthcloud/BlueRetro/releases

• BlueRetro Wiki (Updating Firmware):
  https://blueretro.io/wiki/#/updating

By upgrading to the latest firmware, you can access advanced features like game-specific profiles, enhancing your gaming experience with customizable button mappings.

To verify the MD5 hash of your PS2 ISOs against the Redump database, you’ll want to follow a series of straightforward steps. Redump is a project dedicated to preserving the integrity of disc-based media, and by checking your ISOs against their database, you can ensure your backups are accurate. Here’s a simplified guide:

1. Obtain an MD5 Checksum Utility

• First, you need a tool to calculate the MD5 checksum of your ISO file. For Windows, an easy-to-use option is “WinMD5” or “MD5Summer”. Mac users can use the built-in “Terminal” app, and Linux users can also use their terminal.

For Windows:

• Download and install WinMD5 or any other preferred MD5 checksum tool.
• For Mac/Linux:
• Use the terminal. No additional software is usually needed.

2. Calculate the MD5 Hash of Your PS2 ISO

Windows:

• Open WinMD5.
• Click on the ‘Browse’ button and select your PS2 ISO file.
• The program will automatically calculate the hash once the file is selected.

Mac/Linux:

• Open the Terminal.
• Use the cd command to navigate to the folder containing your ISO. For example, cd Downloads if your ISO is in the Downloads folder.
• Type md5 [filename.iso] for Mac or md5sum [filename.iso] for Linux and press Enter. Replace [filename.iso] with the name of your ISO file.

3. Compare Your MD5 Hash with Redump Database

• Visit the Redump website or any page that lists the MD5 hashes for PS2 games.
• Use the search function to find your game.
• Find the MD5 hash listed for your game on Redump and compare it with the hash you calculated.

How to Compare:

• The MD5 hash is a long string of numbers and letters. You need to ensure every character matches perfectly with the one provided by Redump for your specific game.

If They Match: If every character in your MD5 hash matches the one on Redump, your ISO is a perfect copy of the original disc.

If They Do Not Match: If there’s any discrepancy, the ISO may not be an accurate copy. This could be due to data corruption, differences in the disc version, or modifications.

By following these steps, you’ll be able to verify the integrity of your PS2 ISOs against the Redump database, ensuring they’re accurate backups of the original media. This process is crucial for preservation purposes and for ensuring compatibility with emulators and homebrew software.

Prerequisites:

• a way to launch Homebrew
• “wLaunchELF”

Procedure:

1. Start “wLaunchELF”
2. Enter “Filebrowser” (usually via CIRCLE)
3. Enter “MISC” (scroll to it and use the “confirmation button”, which is either CIRCLE or CROSS depending on your configuration)
4. Launch “HDDManager”
5. Tap R1
6. Select “format” (scroll to it and mark it, then confirm)
7. Confirm formatting and it should be done in a few seconds.

If you intend to use OPL, please stay in the HDDManager and create an appropriately sized +OPL-Partition!

1. Tap R1
2. Select “create”
3. Name it “+OPL”
4. Choose a size! This depends on the size of the HDD as well on what you want to use (i.e. 768MB for a 500GB storage, 1.2GB for a 1TB storage, 1.5GB for a 2TB storage.). VMCs require a bit more space, so keep that in mind!

If you intend to use POPStarter, POPSLoader, or wLaunchELF_kHn, please stay in the HDDManager and create one or more of the following partitions at up to 128GB each to meet your .VCD storage needs the same way you created the +OPL partition above.

• __.POPS
• __.POPS0
• __.POPS1
• __.POPS2
• __.POPS3
• __.POPS4
• __.POPS5
• __.POPS6
• __.POPS7
• __.POPS8
• __.POPS9

Format via Windows PC

Prerequisites:

• PFS-BatchKit-Manager: A utility for Windows that allows for the management and formatting of hard drives for PS2 use.
• https://github.com/GDX-X/PFS-BatchKit-Manager

Procedure:

1. Prepare Your PC Environment Locate the PFS-BatchKit-Manager: Find the folder on your PC where you’ve stored the PFS-BatchKit-Manager. Right-click the .bat file (likely named !pfs-batchkit-manager.bat or similar) and select “Run as Administrator” to ensure it has the necessary permissions.

2. Access PFS-BatchKit Manager Navigate to Advanced Menu: Within the PFS-BatchKit Manager interface, find and enter the Advanced menu. Select “HDD Management” from the list of options.

3. Hack Your HDD for PS2 Format Choose the Option for PS2 Format: Look for and select option “8 - Hack your HDD to PS2 Format”. This prepares your hard drive to be recognized and used by the PS2 system.

4. Format Hard Drive with wLaunchELF After completing the preparation steps on your PC, safely disconnect the hard drive. Connect the hard drive to your PlayStation 2 system, using the appropriate adapter if necessary.

5. Use wLaunchELF on Your PS2 to format again properly as instructed above.

Completing the Setup

After formatting and partitioning the HDD as required, you can proceed to install your Homebrew applications, games, or other content onto the newly prepared storage.