X

SOCOM II: U.S. Navy Seals Videos and Trailers - PS2

  • Publisher: Sony Computer Entertainment
  • Genre:Shooter
  • Developer: Zipper Interactive
  • Release Date:Nov 5, 2003
  • # 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:SOCOM returns with SOCOM II! Earth, land, air, sea, night and day, the U.S. Navy Seals are back again to protect freedom. Embark on 12 international missions, working the Navy Seals magic in urban, rural and wilderness settings in locations such as Algeria, Albania, Brazil and Russia. Missions take place at night and at day, in a variety of weather conditions, in rainy storms and hot desert environments. Team-up with allied Special Ops forces such as the Russian Spetznaz and the British SAS. Up to 16 players can play simultaneously in various online multiplayer modes, in interactive team-based operations and battles. Incredibly detailed graphics and award-winning gameplay will put you deep in the action.
G4TV Rating
N/A
  • Avg User Rating
    (2 Ratings)
    5 / 5
  • Rate This Game

SOCOM II: U.S. Navy Seals 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>