Browsing the Internet with Wipeout Pure
Materials
-PSP
-Wipeout Pure
Steps
Setting up the PSP Network Connection
1. Go to PSP Home Menu and scroll down to bottom and click on Network Settings.
2. Select Infrastructure Mode (though this could be done via an Ad Hoc connection directly to and through the PC).
3. Select New Connection (we recommend this so you don't mess with other working connections).
4. Name the connection (figure 3)
5. Enter or select your SSID value (wireless router name).
6. Select Custom for Address Settings.
7. Select Automatic for your IP Address Setting.
8. Select Automatic for DNS Setting.
9. Select Use for Proxy Server.
10. Enter the IP address of your local computer (figure 4).
11. Enter the port number for Charles (default 8888).
12. Arrow through the Setting List screen (figure 5).
13. Save settings, launch Charles, and test your connection. If all went well, you should be rewarded with a screen containing your network information.
Using the Wipeout Browser
At this point your settings should be ready. Your next step is to start up Wipeout Pure. Once the game loads, select 'DOWNLOAD' from the Main Menu. This will prompt you with a warning that your 'Game experience may change during wireless play', which is interesting because there is nothing to be found at the default Wipeout site. Regardless of this, select the OK option.
Getting around in the Wipeout browser is fairly simple. The following breaks down the buttons and what they can do:
L trigger: Back
R trigger: Forward
Left side controls: Controls the selected item on the screen
Square: Refresh
X: Enter
Start: Browser menu (Continue, Go to Home Page, Quit)
It is important to note that surfing on the PSP is not fast or as feature rich as it is on a PC browser. In fact, you will notice extreme lag times and problems when attempting to download large files. Disconnects and PSP freezes are not uncommon, and will require a reboot of the PSP to recover. I have even had to remove my PSP battery to get back up and running.
I also noted that the browser could only download a 349999 byte file. If it attempted to download a 350k file, it would reset the download process and try again. Without really delving into the problem, I would guess that there is a memory issue. Seeing how the device is limited in memory, and there is no cache to fill up, I suspect there is a limit as to how much this browser can handle.
