X

Serious Sam: The Second Encounter Latest News - PC

Serious Sam: The Second Encounter
Game Description:Sam is back and with a bang like never before!! Help Sam take up the fight against his arch-nemesis Mental. Sam hijacks an alien aircraft to confront Mental but somehow crash lands in the South American Mountains. Now Sam is forced to battle his way towards Mental's fortress and put a stop once and for all to his plans of world domination but this is not easy as you have to face a stronger, meaner Mental army.
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game

Serious Sam: The Second Encounter News

Displaying 1–1 of 1 articles

  • Sessler's Soapbox: Dante's Inferno - When Cloning Goes Wrong

    We've all played clones before. When a big franchise develops a great gameplay mechanic and becomes popular it's only a matter of time before other publishers and developers start pumping out very familiar feeling games. Adam Sessler was reminded of this while he was writing his review of Dante's Inferno, and some of you didn't take too kindly...

    Posted February 9, 2010

    Sessler's Soapbox: Dante's Inferno - When Cloning Goes Wrong
  • Sessler's Soapbox: Dante's Inferno - When Cloning Goes Wrong

    Posted: February 9, 2010

    34,930 Views | 07:26

 


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>