X

SOCOM: U.S. Navy SEALs Videos and Trailers - PS2

  • Publisher: Sony Computer Entertainment
  • Genre:Action, Shooter
  • Developer: Zipper Interactive
  • Release Date:Aug 27, 2002
  • # of Players:16 players
  • 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:NOTE: As a rental, this game does not include the headset. Become part of America's elite all-terrain fighting force in SOCOM: U.S. Navy SEALs, an all-out action-adventure shooter. You are a SEAL commander who will lead his men on 17 dangerous missions, 12 of them ideal for single players. You'll use more than 30 high-tech weapons along with your SEAL training and tactical prowess to rescue hostages and hunt down terrorists, operating in sea, air, and land, day and night. Intense team-based cooperative gameplay is one of SOCOM's most impressive features, allowing for 16 players to play simultaneously with a PlayStation 2 network adapter and broadband connection.
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game

SOCOM: U.S. Navy SEALs Videos

Displaying 1–2 of 2 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>