X

Full Spectrum Warrior: Ten Hammers Latest News - PS2

  • Publisher: THQ
  • Genre:Shooter, Strategy
  • Developer: Pandemic Studios
  • Release Date:Mar 28, 2006
  • # of Players:4 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:A coalition of Western forces has accomplished its mission: ending the rule of dictator Al-Afad. But the victory is bittersweet. The country of Zekistan - cut by the Tien-Hamer (or "Ten Hammers") mountain range - is now in turmoil, with various forces waging a battle for power. One force, the coalition, is poised to restore order. Lead your four-man light infantry team, consisting of a team leader, rifleman, automatic rifleman, and grenadier, into Khardiman to secure the major city. Use squad-based tactics to seek strong positions, gather recon, and find cover. When things heat up, bring out mechanized units or call in airstrikes. Complete seven multiplayer missions on or offline.
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game

Full Spectrum Warrior: Ten Hammers News

Displaying 1–1 of 1 articles

  • Full Spectrum Warrior Helps P.T.S.D.

    Full Spectrum Warrior, after failing in its initial design, seems to be finding a new purpose, by aiding US veterans overcome Post Traumatic Stress Disorder in a new experimental treatment program, named Virtual Iraq. Read More?

    Posted May 12, 2008| 6 Comments

    Full Spectrum Warrior Helps P.T.S.D.

 


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>