i wasn't actually talking about the original games, just OXC version
People do like to keep things separate, or rather that is my personal preference. and why woudl you want 4 different versions in any case,
the method i was trying to describe,
is basically the root directory c:\Games\ with the OXC\ and the main folder and then from there split into whatever version you want. as such it would look something like this.
C:\Games\OXC\Ufo Defense\*.*
C:\Games\OXC\TFTD\*.*
C:\Games\OXC\Ufo Defense2\ *.*
C:\Games\OXC\TFTD2\*.*
C:\Games\OXC\mypersonalmods\ *.*
.
.
.
This keeps all games with in that parent folder as a cohesive group under OXC. Then again i do not know why you want to be running multiple copies of a game unless you are doing revisions or trial code.
and don't worry you don't have to speak gently, i think we are all adults here as long as you don't insult me, you can say that is "moronic idea" or "the stupidest idea" is ok, i won't run to tell my mommy
the idea of everything under OXC is simply to understand that all code in that folder belongs to the OXC branch if you wanted it will be
C:\Games\OXC\awesomly-HD-with-ubber-sptries-version-of-UFO-Defense-done-by-me\*.*
in any case as a non-programmer maybe i just don't' understand filesystem hierarchy enough.
the original games need not be touched so they can stay in their original folder
C:\Games\Ufo Defense\*.*
C:\Games\TFTD\*.*
or wherever that may be.
I think mixing with the original folders will cause confusion, furhteremore i think this will be easier to pass onto multiple OS sicne file structures do differ in that case it will simply be
...\OXC\Ufo Defense\*.*
...\OXC\TFTD\*.*
...\OXC\Ufo Defense2\ *.*
...\OXC\TFTD2\*.*
...\OXC\mypersonalmods\ *.*
That way programmers can readily tell people, no you idiot you are looking in the wrong folder
EDIT:
I just reread the whole thread, what you don't want is to have to copy the data from the original multiple times, personally i wouldn't care
but as Supsuper mentioned i think it could be done in different way with the common data paths.