AwesomeMod "Breaks" Sims 3 upon installation- competent edition!

[Claeric]

Yeah.

I just installed WA, and it would appear AM is "breaking" the game on installation. Rather than get lost in the grammar topic the other guy made, I figured I'd just start my own.

DETAILS!

Windows 7 x64 Pro
Graphics card and all that jazz, I doubt that would matter. Radeon 4870, triple core whatever, 4GB Ram.

Game Versions: 1.7.9/2.2.8. The reason I am not using 1.8 is beause when I first installed WA, I had to completely re-install and it was implied that my issue may have been the later patch. So I left it at 1.7.9.

Other mods: Yep, but this happens whether they are there or not.
Framework properly installed: Check, all my other CC works flawlessly.
Old save file being used: Nope, completely clean install.

Now, here's what happens: Game loads. Load bar gets as far to the right as it possibly can, and nothing happens. Music keeps playing, spinny keeps spinning, that's it. Remove awesomemod and it works again. I have tried both the 1.7.9 version of AM(as it is what I was using before with 1.8 <_< and the newest one. Both do this.

Attempted combinations and results:

All CC and AwesomeMod: Failure
All CC and AwesomeMod with Aweconf: Failure
All CC w/o AwesomeMod: Success!
No CC and AwesomeMod: Failure
No CC and AweseomeMod with Aweconf: Failure
No CC and Nothing: Success!

Files are in ElectronicArts/TheSims3WorldAdventures/Mods/Packages.

Any ideas? If I find nothing, I'll attempt an update to 1.8, but for now I would rather not.

[kutto]

The current version of Awesomemod is clearly labeled as compatible with 1.8/2.3 only.

[Claeric]

Yes, I know. And my post is clearly labeled as having used the old edition, too.

[adds]

I think I have read somewhere that while installing dont keep the MODs folder in the game directory. Keep it at some other location . after the installation put the MODS folder back & play.

[Silent Dreamer]

Old versions are unsupported, so we are not very inclined to help you until you get with the times. And even then we're not really inclined to help you since this problem has been beaten to death and tossed into a BFBVBS.

[Claeric]

I had no mods when installing. None at all.

[J. M. Pescado]

The old edition cannot be supported under any circumstances. In fact, it no longer exists.

[Claeric]

So I'm screwed?

I really didn't want to risk updating to 1.8 and breaking everything in general. Though I did just discover the idiot system is having trouble with some of my CC and causing slower rendering so I'll be troubleshooting all damn night anyway. Gotta single the packages down.

[J. M. Pescado]

Nothing "in general" broke, or we would not have adopted the patch. There are issues, but there are workarounds that restore regular operation, so we move forward. If a patch "in general" broke everything, I would simply refuse to adopt it. As I have judged the issues tolerable, and the maintenance of trying to support two patches at once untenable, this is where we are.

[Claeric]

Oh, no, it wasn't a matter of thinking the patch was broken. I just didn't want to risk going beyond what I knew was a sure thing. It was just laziness and an unwillingness to reinstlal on my part. Besides that I have to change the SKU of the base game to update and replace backup files to update WA for various reasons, and it could've caused problems.

Lucky lucky me however, as I am now successfully running 1.8/2.3, along with awesomemod.

[pbox]

So what happened is that you fucked up your game with broken/incompatible CC, yes? And you chose to point fingers before trying to fix it, out of "laziness and an unwillingness to reinstall"? Why is this thread called "competent edition" then? 

[Claeric]

Because...I didnt fuck up the game with CC?

 It was a fresh install. It was working as-is. I had issue with 1.8 before, and since it was working as-is, wanted to know if I could get any help for the older awesomemod, made for 1.7. I didn't want to risk breaking it.