X

Test Drive Latest News - PS2

  • Publisher: Infogrames
  • Genre:Racing
  • Developer: Pitbull Syndicate
  • Release Date:May 28, 2002
  • # of Players:2 players
  • 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:Play for pink slips on the mean streets of underground racing. Choose from more than 20 classic muscle cars and exotic racing machines and take them out in four detailed real-world cities: London, San Francisco, Tokyo, and Monte Carlo. The cities are alive with traffic and pedestrians, so watch out! You'll have to dodge the cops and search out the best route to the finish line. Plug in an extra controller for adrenaline-soaked multiplayer action.
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game

Test Drive News

Displaying 1–1 of 1 articles

  • Atari To Revive '90s Franchises in 2010: 'Baldur's Gate', 'Test Drive', And More

    Hey, remember the '90s? Sure, we all do! It was the decade when BioWare got to show how awesome it was with the its Baldur's Gate role-playing games for PC and Test Drive was still a top-tier racing-game franchise. Atari is planning to bring those series back...but not until 2010. Eurogamer reports: "Atari plans to revisit the likes of...

    Posted December 2, 2008| 16 Comments

    Atari To Revive '90s Franchises in 2010: 'Baldur's Gate', 'Test Drive', And More

 


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>