X

Halo 2 Videos and Trailers - XBX

  • Publisher: Microsoft
  • Genre:Shooter
  • Developer: Bungie
  • Release Date:Nov 8, 2004
  • # 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:The evil Covenant has overrun Earth's defenses and is digging in on the surface, and Master Chief will lead a last-ditch effort to save humanity. So begins the long-awaited second chapter of Halo as the stage for battle comes to Earth. Two years in the making and pushing the Xbox to the outer limits, Halo promises to be THE video game experience of 2004. Engage in an epic single-player story mode filled with danger, courage, and dazzling action. Lead the resistance against the Covenant. Or take on your friends in a revamped multiplayer mode. Battle online through Xbox Live. Blast them out of the solar system Master Chief!
G4TV Rating
N/A
  • Avg User Rating
    (20 Ratings)
    5 / 5
  • Rate This Game

Halo 2 Videos

Displaying 31–35 of 35 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>