Instead of swapping pods in and out of a single pod.ini
file, I decided to write a batch file that would easily
replace the pod.ini with one of several, full, 31 pod
pod.ini's. I have two pod.ini files so far, named pod1.ini
and pod2.ini. My batch file will automatically replace
the pod.ini in the MTM2 directory, with one of several
pod*.ini's. I just placed my pod*.ini files in a separate
directory on my hard drive (name doesn't matter), and
put my custom .bat file in the same directory as the
pod*.inis. I then created a shortcut to my custom .bat
file, and in the pif properties, selected the "close on exit"
box. This closes the MSDos box after you quit the pod
selector. To create your own pod selector, just paste
the contents of my script into a blank text file that you
rename *.bat (the prefix doesn't matter). Put this .bat
file, along with your pod*.ini's, into a directory of your
choice. Here are the contents of my .bat file.

@echo off
:menu
cls
echo.
echo YourNameHere MTM2 POD SELECTION MENU
echo ====================================
echo.
echo 1 - Pod 1
echo.
echo 2 - Pod 2
echo.
echo Q - Quit
choice /c:12Q>nul
if errorlevel 3 goto done
if errorlevel 2 goto pod2
if errorlevel 1 goto pod1
echo CHOICE missing
goto done

:pod1
copy pod1.ini c:\progra~1\micros~4\monste~1\pod.ini
goto menu

:pod2
copy pod2.ini c:\progra~1\micros~4\monste~1\pod.ini
goto menu

:done
exit

The lines in the batch file with the path to your MTM2
directory may have to be modified, depending on how
many directories you have on your hard drive with a
"Microsoft" prefix. For example, my path is properly
named c:\progra~1\micros~4\monste~1\. The problem
section that many would have is micros~4. Because I
have several "Microsoft *******" directories on my hard
drive, Windows assigns several numbers to the short
Dos names of those directories, in order to distinguish
them. For example, I have a micros~1, micros~2, etc.
My "Microsoft Games" directory is shortened to
micros~4. This won't be the case for many of you. Most
will probably have their "Microsoft Games" directory
shortened to micros~1. To find out the short name for
your "Microsoft Games" directory, just open a Dos
window, and look at the short name for your "Microsoft
Games" directory. Just replace the micros~4 sections of
the batch file, with the correct number Windows has
assigned for you. For example, if your "Microsoft
Games" directory is micros~1, just change the sections
in your batch file paths from micros~4 to micros~1. Now
the batch file will be able to find your MTM2 directory,
and change your pod.ini file. I don't have MTM1, but if
you do, and it uses the same directory naming structure
as MTM2, then you should verify the monste~1 short
name as well.

Notice that the pod*.ini files will be copied into the default
MTM2 directory. If your game is in a different directory,
you will have to change the path in the pod*.ini lines.
Now, I installed MTM2 using the typical install, then
moved all the pod files into a separate directory, except
for some of the "system" pods. I am doing this so that
when I have collected 650 megs worth of pods, I can
then record a CD with all of the add on pods I have
collected. Please don't ask me if I will distribute such a
CD, as I will not. With the fact that I moved most of my
pods into a separate directory in mind, here is a sample
of my pod1.ini and pod2.ini files. I haven't added any new
pods to the pod2.ini file, so it just contains the basic MTM2
system pods. Do not try doing any of this unless you are
comfortable with it, and back up your pod.ini file first please.
I don't plan on replying further to this message, so if I have
made any errors in describing the process, someone can
correct me here. Remember, at the moment, there is a 31
pod limit, so once you have 31 pods in an ini file, it is time
to create a new one. Here are my pod1.ini contents;

31
startup.pod
d:\mtm2trks\music.pod
sound.pod
d:\mtm2trks\truck2.pod
d:\mtm2trks\cockpit.pod
d:\mtm2trks\ui.pod
d:\mtm2trks\tpark.pod
d:\mtm2trks\alaska.pod
d:\mtm2trks\junk.pod
d:\mtm2trks\crazy98.pod
d:\mtm2trks\snake.pod
d:\mtm2trks\main.pod
d:\mtm2trks\aztec.pod
d:\mtm2trks\outback.pod
d:\mtm2trks\rockqry.pod
d:\mtm2trks\baja.pod
d:\mtm2trks\summit1.pod
d:\mtm2trks\summit2.pod
d:\mtm2trks\summit3.pod
d:\mtm2trks\btest.pod
d:\mtm2trks\canyoncliffs.pod
d:\mtm2trks\domin.pod
d:\mtm2trks\sum_exc.pod
d:\mtm2trks\koth.pod
d:\mtm2trks\sum_lil.pod
d:\mtm2trks\myst.pod
d:\mtm2trks\carpe.pod
d:\mtm2trks\quarry.pod
d:\mtm2trks\mars.pod
d:\mtm2trks\trumble.pod
d:\mtm2trks\twistmxm2.pod

Here are my pod2.ini contents;

6
startup.pod
d:\mtm2trks\music.pod
sound.pod
d:\mtm2trks\truck2.pod
d:\mtm2trks\cockpit.pod
d:\mtm2trks\ui.pod

Remember, if you put your pods that are outside your MTM2
directory, into a different directory than I have, you must
change the paths in your pod*.ini files to reflect this. If you
leave all of your pods in your default MTM2 directory, then
you don't need any path, just like the startup, and sound pods,
which are in my default MTM2 directory. Hopefully, Terminal
Reality will increase the pod limit in a future patch. Finally, I
decided to print out a list of all the tracks that are in each of my
pod*.ini files, so I know which pod*.ini file I want to use at any
moment. I hope this info helps anyone with another, not
necessarily better, way of using their extra pods.

Now, an additional hint for those who are not familiar with .bat
files, and want to add more than the 2 pod*.inis in my example.
First, here is my original .bat with the pod1 and pod2 inis;

@echo off
:menu
cls
echo.
echo    YourNameHere MTM2 POD SELECTION MENU
echo    ====================================
echo.
echo    1 - Pod 1
echo.
echo    2 - Pod 2
echo.
echo    Q - Quit
choice /c:12Q>nul
if errorlevel 3 goto done
if errorlevel 2 goto pod2
if errorlevel 1 goto pod1
echo CHOICE missing
goto done

:pod1
copy pod1.ini c:\progra~1\micros~4\monste~1\pod.ini
goto menu

:pod2
copy pod2.ini c:\progra~1\micros~4\monste~1\pod.ini
goto menu

:done
exit

Now, lets say you have collected more tracks than 2 pod*.inis
can hold. Now you have a pod3.ini, and a pod4.ini. Here is
the difference with these two additional pods;

@echo off
:menu
cls
echo.
echo    YourNameHere MTM2 POD SELECTION MENU
echo    ====================================
echo.
echo    1 - Pod 1
echo.
echo    2 - Pod 2
echo.
echo    3 - Pod 3
echo.
echo    4 - Pod 4
echo.
echo    Q - Quit
choice /c:1234Q>nul
if errorlevel 5 goto done
if errorlevel 4 goto pod4
if errorlevel 3 goto pod3
if errorlevel 2 goto pod2
if errorlevel 1 goto pod1
echo CHOICE missing
goto done

:pod1
copy pod1.ini c:\progra~1\micros~4\monste~1\pod.ini
goto menu

:pod2
copy pod2.ini c:\progra~1\micros~4\monste~1\pod.ini
goto menu

:pod3
copy pod3.ini c:\progra~1\micros~4\monste~1\pod.ini
goto menu

:pod4
copy pod4.ini c:\progra~1\micros~4\monste~1\pod.ini
goto menu

:done
exit

As you can see, the changes that are made to accommodate
the two additional pod*.ini files are pretty straightforward and
logical. A neat thing about managing your pods in this way, is
you can easily synchronize the tracks that you are running
with your friends, as long as you all have the same tracks
listed in each of the pod*.inis. You could say, "Hey, let's run
pod4.ini this week," and you would all have 25+ new tracks
to enjoy (more if you combine pods), with no need to wonder
about who has what track. Remember to create a shortcut to
your .bat file, then right click on the shortcut, select properties,
then select the "program" tab, and select the "close on exit"
box. This will gracefully exit the Dos window when you hit the
"Q" for exit key. Again, if you attempt this, please back up
that pod.ini in your MTM2 directory first. That way, if you type
something amiss in your pod*.ini files, you will be able to get
back to playing the game by simply restoring the original
pod.ini. I hope you like this way of managing pods.