X

Prince of Persia: Warrior Within Videos and Trailers - PS2

  • Publisher: Ubisoft
  • Genre:Action, Adventure
  • Developer: Ubisoft Montreal
  • Release Date:Dec 1, 2004
  • # of Players:1 player
  • ESRB:M - Mature (Titles rated "Mature (M)" may be suitable for ages 17 and older. They may include more intense violence or language than products rated "Teen" as well as mature sexual themes.)
  • Platforms:
Game Description:The Prince is back! Return to the sands of time in Prince of Persia 2, Ubisoft's thrilling follow-up to last year's universally acclaimed remake. This time the Prince is more deadly than ever. With new acrobatic moves and the ability to do extensive fighting combos without cut-scene interruptions, the Prince will take on more challenging bosses and massive armies of evil. With more angst in his belly due to a price on his head, the Prince will journey through a darker, wind-swept landscape of Persian fantasy. Tuned to perfection, epic and elegant in all the right places, Prince of Persia 2 promises to be one of the best titles of 2004.
G4TV Rating
N/A
  • Avg User Rating
    (1 Rating)
    5 / 5
  • Rate This Game

Prince of Persia: Warrior Within Videos

Displaying 1–1 of 1 videos

 


Runtime Error

Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>