It seems I have this sorted:
start cmd /k "C:\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Terrain SDK\resample.exe" klam_1m_WGS84_03140308.inf
start cmd /k "C:\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Terrain SDK\resample.exe" klam_1m_WGS84_03140309.inf
...spins off two new cmd windows each resampling different parts of the imagery.
More details if anyone's curious:
The entire project currently uses 92 sources (.tifs) at roughly 1.1 Gb apiece. The simulator has a limitation where a .bgl can't exceed 2 Gb or it won't show. Resample has an option for "SplitFileLOD" where it will split large projects like this up into smaller .bgls to avoid exceeding the 2 Gb limitation, I'm using SplitFileLOD=9 where it splits the .bgls at LOD9 boundaries which are approximately 13 miles across in both the X and Y directions. The 92 sources are split into 31 separate .bgls using SplitFileLOD=9. Resample also has an option for "BoundingCell" where you can constrain the output to a particular cell, BoundingCell=11,314,308 for example causes resample.exe to resample just one of the 31 .bgls that make up the project (klam_photo_1m_03140308.bgl). If I leave BoundingCell out of the .inf resample will start at the top left corner and resample each of the 31 .bgls in turn until it finishes the project. That means it's bedtime because last I checked it takes a little over 4 hrs to do that, lol.
Being able to spin this off into multiple instances, maybe six instances at a time to get the CPU load up somewhere near 100%, I can cut that resampling time down significantly. Also if I make edits to just one or two .tifs I can resample only the .bgl affected by those .tifs I've edited rather than having to resample the whole lot at once.
Thanks for checking this thread out folks. I think I'm good to go now.
Jim