Looks like you have mixed up versions . Here are some rules to use ML
Use original minecraft.jars only . do not put anything in them .
The window where you added mods to , is for CORE MODS only, its so you don't have to put the mods into the minecraft.jar file . You will need to experiment with the order of CORE MOD injection. move the items in the list up and down until there are no errors .
Forge mods go into the /mods/"version#" , where "version#" without the brackets is the Minecraft version ie ... / mods / 1.7.10
No mixing of mod versions .

Looking at your mods names , they do not look like the originals . did you get the mods from Curse or original author .?

From what I remember ,there where 2 versions of TMI a Core mod and a Forge version same for Optifine and other mods as well

Looks like you have mixed up versions . Here are some rules to use ML
Use original minecraft.jars only . do not put anything in them .
The window where you added mods to , is for CORE MODS only, its so you don't have to put the mods into the minecraft.jar file . You will need to experiment with the order of CORE MOD injection. move the items in the list up and down until there are no errors .
Forge mods go into the /mods/"version#" , where "version#" without the brackets is the Minecraft version ie ... / mods / 1.7.10
No mixing of mod versions .

Looking at your mods names , they do not look like the originals . did you get the mods from Curse or original author .?

From what I remember ,there where 2 versions of TMI a Core mod and a Forge version same for Optifine and other mods as well

If you have some Coding knowledge it would be easier to under stand this stuff . The 1.7 branch consists of patches to correct errors . the stable version is 1.7.10 . everything below this is demoted because its broken .

here is an analogy , they all have to be apples to make apple sauce , if you throw in a orange and a banana , you get fruit salad . lol

It wont work because during obfuscation the real *.class names are changed in each version . If a variable is called from Minecraft 1.7.3 , it can only talk to b1.7.3 , it cant talk to any other version because they were not compiled and obfuscated together .

and again why are you playing with broken builds ? the only supported version of the 1.7 branch is 1.7.10

A programmer is writing code for say minecraft , they release 1.7.0 and people find bugs and tell the programmer . They fix the error , compile and obfuscate , then release 1.7.1 . More bugs are reported and fixed , then a 1.7.2 is released . Then a 1.7.3 etc ... all the way to 1.7.10 , when the programmer says its finished or final version .

and again why are you playing with broken builds ? the only supported version of the 1.7 branch is 1.7.10

A programmer is writing code for say minecraft , they release 1.7.0 and people find bugs and tell the programmer . They fix the error , compile and obfuscate , then release 1.7.1 . More bugs are reported and fixed , then a 1.7.2 is released . Then a 1.7.3 etc ... all the way to 1.7.10 , when the programmer says its finished or final version .

I think you are confused; they are referring to BETA 1.7.3, which is an entirely different version from release 1.7.x, not really even an "apples and oranges" comparison:

It is correct though that they are attempting to use TMI for Beta 1.7.2 on Beta 1.7.3, which will not work except with rare exceptions (usually very basic Forge mods which entirely rely on Forge hooks with no references to anything in Minecraft itself).

As what I'd call a highly advanced modder (if not very well known due to the fact I make mods for myself and for a very old version) I'm well aware of that and even mentioned it as one of my very first posts on these forums.

all the links and feeds in ML are hardcoded . sp614x is fully aware that some of the links are out of date . There is also a problem with parsing minecraft version variables past 1.12.2 . He may be waiting for 1.13 final before he fixes the code . Try MultiMC launcher