Mapping in GMax isn't actually all that hard, but there's a process involved. I totally empathize with you, as I went from FSDS to GMax sometime in FS2002, and learning to map textures was the worst part for me. That's irrelevant to us, though, because you're only in the mood to modify, and we've got a tool for that - unwrap UVW.
Max (and its derivatives, like GMax) are very hierarchical. What I mean is that all the controls have classifications and classifications within classifications. It's very orderly, but the directions don't start with telling you how the order works! So, if you came in from FSDS, you're bound to be lost. The main control panel, on the right of the screen, has lots of little buttons on it that determine what set of controls you're going to use. There's a tab to create things, a tab to modify things that you've already created at the subobject level, a tab to play with pivots and whatnot, a tab to assign different kinds of motion controllers, a tab to tell the program how to display things, and a tab for tools that can be used to fix problems (or make your problems worse!). We're concerned, at the moment, with modifying objects at the subobject level. Click the "modify" button to open up the real meat and potatoes of how we edit objects - the modifier stack:
The object in our case is the quick and dirty imagineered DC-9-ish windows I threw together for another mini-tutorial. I've gone ahead and mapped an old photo of a warehouse dock to it and collapsed the modifier stack (I'll get to that later) so it appears as it'd probably appear if it were part of a finished model.
Remember what I said about Max being obsessed with hierarchy? The modifier stack is a literal stack of changes that apply cumulatively, with the most recent changes being at the top. Let's say I want to change the mapping on just the front part of the window frame. I'm going to first want to select the polygons I want to modify. We could simply click the little plus sign where it says "editable poly" and select the polygons there, but I want to add a modifier to perform this function, so you can get an idea how modifiers work. Since this is an editable poly object (which is a minor detail that isn't important to you, but has certain consequences if you start building models), I'm going to use a "poly select" modifier. Click the list, and select "poly select."
The only thing this modifier does is allow you to select the things you want to select, so that the next modifier only affects what you selected. If I click "polygon" and select a few polygons, then the next modifier will only modify those polygons. If a decide, instead, to click "vertex" and select some vertices, then the next modifier will only apply to those vertices. If I click "polygon" and select some polygons, then change my mind and click "vertex" and select some vertices, then the next modifier will only affect the vertices. If I add a modifier on top, and play with it, then decide to click on the poly select modifier, the changes will "undo" (because they haven't happened yet) until I select the next modifier again. Here's where things can go south if you don't know what you're doing: if I decide to click on the poly select modifier, then just click "polygon" - without doing anything else - then the polygons I originally selected will still be selected, and if I then click on the next modifier (whatever it may be), then the next modifier will instead modify those polygons!
It sounds confusing, but it's not. The last thing you did in the poly select modifier is going to be the thing the next modifier in the stack modifies. Deleting a modifier will cause the object to act as if the changes never happened, and this is really handy if you want to try something without doing permanent damage. Right clicking in the stack and selecting "collapse all," however, will make all of your changes permanent, so collapse a stack with extreme caution. Now that we have a basic understanding of how we stack modifiers on top of each other, let's do something with the polygons we selected. Click on the list of modifiers again, and select "unwrap UVW."
Now click "edit." Things will start to look a little more familiar to you now...
...because this reminds me a whole lot of the mapping editor in FSDS, except that instead of having fields to enter text, which changes the size of a box, which tells you how big the object is on the texture, you've got the object projected on the image, and you can modify the UV coordinates (the little vertices) to your heart's content (I think you could do this with individual faces in FSDS, but my memory fails me). The controls at the bottom right allow you to pan and zoom around the little 2D world, and you can work fairly precisely if you zoom in far enough. Let's click the "move" button and move these UVW points to another part of the image:
Now the middle frames are mapped to another part of the image. We can do more, though. Click and hold where it says "UV" and select "VW."
This demonstrates something very useful - textures are mapped in 3D space, and by selecting different "views" in which to edit them, you can treat them as though you were modifying 3D objects to create some strange mapping. This is a side view of the mapping coordinates. Notice how they look "squashed." I used a simple planar map, and Gmax doesn't allow us to modify the "depth" of the mapping coordinates when we do this. That's fine; it doesn't matter - but if you decided to rotate the UVW coordinates, things might get a bit out of proportion.
For your purposes, though, you needn't bother. Just stay in UV view and move things as you see fit. I only told you about the ability to view things from other directions so you can get an idea of the real power behind some of these seemingly simple functions.
Note that many materials (the material is what you "make the object out of" - i.e. the skin you put on it, and includes the texture maps) have more than one map (image) specified for different effects. In the upper right corner, where it says "map #0" you can change the backdrop of the unwrap UVW window to whatever map you want to view - just in case the one you want to see projected isn't the one that shows up right away.