I'm not sure exactly how your console game is set up, but here's an easy approach I use in graphical games.

Declare an int called "iAppState" somewhere where you'll be able to access it easily (as a global variable, or in your App/Game class if you wrote one). If you're not familiar with Hungarian notation, the "i" simply indicates it's an int-- if you don't use Hungarian notation, name it however you like. This variable will keep track of the state of the application, as the name indicates.

Then, in some header that you have your often-used defines (#define), define these and whichever else come to mind:

#define MODE_TITLE 1#define MODE_GAME 2#define MODE_HIGHSCORE 3 // (optional, but it's an idea)

Whenever you change from the title screen to the game, or from the game to the title screen, or from the game to the high score list, etc., set iAppState to whatever the new state is.

Then, in your game loop, you'll want to have a switch statement to handle all possible iAppMode states.

switch (iAppMode){  case MODE_GAME:     // do your game logic here     break;  case MODE_TITLE:     // do your title screen logic here     break;}

You should have similar in the drawing part of your game loop as well.

That's all there is to it, but this technique is suited best for simple games. For large-scale games, you may want to go so far as to write a GameState class full of variables regarding the state of the game (are we on the title screen? is the game paused? how many players are currently playing?).