X

Mega Man Battle Network Latest News - GBA

  • Publisher: Capcom
  • Genre:Action, Adventure
  • Developer:
  • Release Date:Nov 1, 2001
  • # of Players:1 player
  • ESRB:E - Everyone (Everyone)
  • Platforms:
Game Description:In this colorful, real-time role-playing adventure, you'll play as Lan and Mega Man.exe. Lan is a young hacker who must prevent an evil group from contaminating the pervasive "Net." Lan teams up with Mega Man.exe, his good friend and all-around virus buster to save the day. With the robust battle chip system you'll collect 170+ chips that you can use to get weapons, valuable data, and upgrade Mega Man.exe.
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game

Mega Man Battle Network News

Displaying 1–1 of 1 articles

  • Capcom Trademarks Mega Man Universe

    In “Oh, what ever could it mean?!” news, Capcom has filed a trademark for a new Mega Man game called Mega Man Universe. The patent covers everything from “computer games in the form of cartridges, cassettes, discs or tapes” to downloadable mobile games to screen savers and ring tones. No mention of online games, which...

    Posted April 27, 2010

    Capcom Trademarks Mega Man Universe

 


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>