PlayStation Portable

Based on README.PSP and jak66's forum post.

Installation

First, look up the version/firmware or your PSP. You can do this by going to system settings and then system information.

You will get 3 lines:

MAC Address: (Your PSP's specific MAC address)
System software version: (Your PSP's firmware version)
Nickname: (The nickname you put onto PSP)

Firmware Versions

There are 20 different firmware versions:

Official Versions

• 1.00
• 1.50
• 1.51
• 1.52
• 2.00
• 2.01
• 2.50
• 2.60
• 2.70
• 2.71
• 2.80
• 2.81
• 3.00
• 3.01
• 3.02
• 3.03

Unofficial Versions

• 1.50 CF (Custom Firmware, Shows as 1.50)
• 2.71 SE (Special Edition) (5 different versions; A, B, B', B" and C)
• 3.02 OE (Open Edition) (2 different versions; A and B)
• 3.03 OE (Open Edition) (1 version; A)

Installing onto Memorystick

Now that you know your firmware version we can begin with the installation instructions which are different for the firmwares, depending on the exploit they are using.

Firmware 1.00/1.50 CF - No Exploit

Firmware 1.00 needed no exploit to run homebrew as there was no security against the system from running unsigned eboot.pbp's. Firmware 1.50 CF patched a PSP running a regular firmware 1.50 so that it could run unsigned eboot.pbp's like firmware 1.00 (among other features).

To install ScummVM on one of these firmwares, copy the folder inside the single-eboot folder from the ScummVM PSP zip to X:/PSP/GAME/. Then run from the XMB.

Firmware 1.50/1.50 CF - kxploit

Patching the vunerability that firmware 1.00 had, firmware 1.50 was released. Shortly after, an exploit was found, 'swaploit', which involved swaping between two memory sticks which enabled the homebrew to load. Later, kxploit was released which could load homebrew from one memory stick using 2 folders (i.e. example and example%)

To install ScummVM on one of these firmwares, copy the folders inside the 1.50-eboot folder from the ScummVM PSP zip to X:/PSP/GAME/. Then run from the XMB.

Firmware 2.00/2.01/2.50/2.60/2.70/2.71/2.80 - Eloader

It was firmware 1.51 that blocked kxploit, but many PSP users refused to update. This caused Sony to release a major update that would tempt people to update. Thus, firmware 2.00 was released which came with a built-in web browser, and caused many PSP users to update. However, one of the new features brought two new exploits (both are TIFF exploits). The first was exclusive to 2.00 and was patched with 2.01. The second wasn't discovered until after firmware 2.80 was released, a vunerability with libtiff. Team Noobz have built on these exploits to bring the homebrew community Eboot Loaders (called Eloader)

To install ScummVM on one of these firmwares, copy the folder inside the single-eboot folder from the ScummVM PSP zip to X:/PSP/GAME/. You now, also need to install Eloader, the newest version can be found at www.noobz.eu. Download the exe and follow the instructions to make sure you install successfully. Once you have Eloader installed, turn your PSP on and go to the XMB photo viewer. There should be a new folder called eloader0995. Trying to open this folder will do one of two things:

1. Crash your PSP. If this should happen, restart your PSP and try again.
2. Start Eloader. Run from Eloader menu.

Firmware 2.71 SE/3.02 OE/3.03 OE

All of these custom firmwares were made by Dark_AleX. They combine firmware 1.50 with another firmware (as stated in their names) so PSP users can play homebrew and use higher firmware features (most recently POPS the official PS1 emulator), without needing devhook, two PSPs or a modchip.

To install ScummVM on one of these firmwares, copy the folders inside the 1.50-eboot folder from the ScummVM PSP zip to X:/PSP/GAME150/. Then run from the XMB. Alternatively, copy the folder inside the single-eboot folder from the ScummVM PSP zip to X:/PSP/GAME150/. Then run from the XMB.

Firmware 1.51/1.52/2.81/3.00/3.01/3.02/3.03

Currently there is no exploit that allows you to run unsigned eboots on these firmwares. 1.51 and 1.52 can upgrade to a higher firmware that runs homebrew. X:/ is the drive given to your PSP by windows (i.e. G:/). XMB stands for Cross Media Bar, which is the menu you get on your PSP (also on PS3).

Notes

• You can degrade your PSP's firmware to 1.50, but doing so can completely break your PSP (a process called "bricking", as afterward your PSP is essentially nothing but a fancy brick). The reason some brick is mainly due to a hardware problem. Some PSP's have a motherboard referred to as TA-082, and any PSP with this motherboard will not allow 1.50 to be run on the PSP, therefore downgrading will irrevocably break such a PSP.

Controls

Left Trigger	ESC
Right Trigger	Enter
Analog	Mouse Movement
D-Pad	Mouse Movement
Analog + Triangle	Fine Control Mouse
X	Mouse Button 1
Circle	Mouse Button 2
Square	. (Skip dialogue in some games)
Select	Show/Hide Virtual Keyboard
Start	F5

Notes

• While it is possible to compress certain game resources to reduce their size, this can (and usually will) cause games (especially animations) to be choppy sometimes, as it requires extra CPU power to decode these files. As such, it is recommended to play games in their original, uncompressed, form whenever possible.

• Sleep/Suspend mode currently isn't supported, so don't use it when running ScummVM.

Frequently Asked Questions

Q: What do I need to run the games?
A: A 1.00 or 1.50 firmware PSP (or an EBOOT loader on firmware 2.00 or higher), and the necessary datafiles for the game you want to play and obviously ScummVM.

Q: Can I run <Game XXX> with this?
A: See the list of supported games.

Q: My Monkey Island 1 doesn't have any music, what gives?
A: If your version of Monkey Island came on a CD then it has the music as CD Audio tracks. You need to rip those to MP3/Ogg and copy them to the same directory as the game data files for music to work.

Q: <Game XXX> crashes, or <Feature YYY> doesn't work. Can you fix this?
A: Possibly.
Because of the large amount of games ScummVM supports we obviously haven't played them all start-to-finish on the PSP, so it is possible there are bugs or issues that we are not aware of.
When you encounter such a bug, please use the ScummVM bug tracker, and mention all relevant info (i.e. that you're using the PSP version, which ScummVM version it is, if the problem exists in a recent PC SVN version, a detailed description of the problem, and if possible a nearby savegame). This will make it much easier for us to understand, reproduce and hopefully fix the problem.

External links

• ScummVM PSP forum