
On this screen, you need to highlight the controllers you want to include
in the map by clicking them with the mouse. If you don't include a controller
here, than it will not be active when the map is running. This means that
you have to add all controllers even if you don't plan on assigning a
function to them. If you're using a FighterStick, ProThrottle, and
ProPedals, for example, but only want to program a character to a button
on the FighterStick, you still need to select all three devices. Any
device not selected will be "turned off" when the map is active.
Once all the Controllers that you want to include have been highlighted,
click "Okay". The next screen you see will look like this:

This screen is where you need to indicate whether you want the Wizard to
generate a "Direct Map" or a "Combined Map".
A Direct Map is one in which, initially, each controller you add will
result in a device being created for Windows which looks essentially
identical to the controller it represents except that it will have a
name like "Control Manager Device 1". The difference between doing this
and simply running the Control Manager in Direct Mode is that you will
be able to program the button and axes to send characters or control the
mouse. In Direct Mode, this isn't possible.
A Combined Map is one in which the controls from several controllers
are combined to form a single Control Manager Device that Windows will
see. This is useful for games which only recognize a single controller,
it allows you to combine a FighterStick, ProThrottle, and ProPedals
into a single 4-Axis controller for example.
Click the "Yes" or "No" button depending on what you want to do. If you
click the "Yes" button, you'll be presented with a screen that looks like
this:

This lists the various configurations that the Map Wizard can shoot for in
a Combined Map. The selection refer to the maximum number of axis and
buttons that the combined controller will have. The Map Wizard may or may
not create as many axes and buttons as are indicated, but it will not
create more axes or buttons than the selection shows. If you only have a
yoke and a set of pedals, for example, there is no way that the Map Wizard
can actually create a 32-button controller, but setting it to 32-buttons
will allow it to assign all the available buttons to the Control Manager
Device. It does no harm to specify more than are available, normally the
selection is for a 6-Axis/32-Button configuration.
The other selections are primarily for older games and simulations
that may not respond correctly when presented with a lot of axes and
buttons. If you run into problems with a particular game using the
6-Axis/32-Button configuration, going to a lower axis and button count
will often clear the problems up. MechWarrior is probably the most
common example of this. It will crash if presented with a 32-button
joystick. Use 16-button instead.
Once you've made the selection and click "Okay" (or if you chose not to
have the Map Wizard combine your controllers at the previous step) you'll
get a screen that looks like this:

The CMS Scripting facility is a text-based system that allows advanced
users to create complex functions that cannot be implemented using the
normal GUI functions. Most of the normally-needed functions can be set up
using just the GUI without the use of CMS scripting. If you're new to
the Control Manager, it's probably best to "just say no" at this point.
You can add CMS capability to the map later should the need arise. See
the CMS Programming Guide for more information on the CMS
and how it is used.
Either choice will bring you to this screen:

You can click "Okay" and the Map Wizard will create the basic map based on
your previous responses. If you click "Cancel", the Map Wizard will exit
without creating the map at all.
It's worth noting that the maps created by the Map Wizard are nothing
special. It's just an aid in making the basic assignments for you
automatically. You can change any of the assignments manually once the Map
Wizard has run its course, assigning buttons, moving axes around, etc. The
assignments made are the most common assignments for the basic axes and
buttons, but nothing is cast it stone as a result of running the Map Wizard.