X

Conflict: Desert Storm 2 - Back to Baghdad Latest News - PS2

  • Publisher: Take Two
  • Genre:Shooter
  • Developer:
  • Release Date:Oct 10, 2003
  • # of Players:1 player
  • ESRB:T - Teen (Titles rated "Teen (T)" may be suitable for ages 13 and older, and may contain violent content, mild, or strong language, and/or suggestive themes.)
  • Platforms:
Game Description:Command your Special Forces team deep into the deserts of Iraq and strike hard at the heart of the evil dictator's regime! Play as a four-man squad from the US Delta Force or the British SAS in this follow-up to last year's Conflict, which has you going straight for the capital of Iraq in a fictitious scenario set after the 1991 Gulf War. Equipped with an authentic arsenal of the military's finest weapons and vehicles, you must fight against impossible odds and utilize the special skills of each of your team members to survive. Take on ten gripping missions alone or co-operatively with up to four friends.
G4TV Rating
N/A
  • Avg User Rating
    (2 Ratings)
    5 / 5
  • Rate This Game

Conflict: Desert Storm 2 - Back to Baghdad News

Displaying 1–1 of 1 articles

  • War is Games: From the Civil War to the Iraq War and Beyond

    Memorial Day. What does that mean? Well, to the typical America, it means beer, bikinis, and a day off from work! And if you're a gamer, it also means double experience in Call of Duty: Modern Warfare 2. Or even TRIPLE experience if you're diving into the recently updated Gears of War 2 experience. What better way to honor the valiant dead than...

    Posted May 30, 2011

    War is Games: From the Civil War to the Iraq War and Beyond

 


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>