stopping AIM fron coming to front

[NiKeFiDO]

I was playing Freedom Fighters and when I get an IM, AIM trys to come to front but this always freezes Freedom Fighters. This usually does not happen with other programs, and I can switch out of this game manually myself, but AIM likes to mess it up.

Anyway....

is there anyway to stop AIM from coming to front when I receive a NEW instant message? I don't see it in preferences....

Also, i found this:
http://www.aol.com/aim/faq/connection.html#active
but that registry file is NOT there, and I don't think that would solve my problem anyway.

Any suggestions?

P.S. Something also keeps not allowing my AIM from going to Idle and my monitor from shutting off after the 15 minutes I have it set to...whats the deal? Adaware/Spybot/Norton (all upgraded) is finding nothing.....

 

[HermDogg]

P.S. Something also keeps not allowing my AIM from going to Idle and my monitor from shutting off after the 15 minutes I have it set to...whats the deal? Adaware/Spybot/Norton (all upgraded) is finding nothing....

It's got to be a process that you're running. Not necessarily virus/adware, just something.

As for your main problem, put your away message up when playing games and click "Hide receieved messages"

 

[NiKeFiDO]

yeah....it happened to my roomate first, now my computer does it (im talking about the lack of idling)
so it could be something on the school network. I'll see.

Anyway, I downloaded Tweak UI (check it out on the Windows site)
It allows you to stop other programs from stealing focus (which hopefully won't mess stuff up too much)

 

[fuzzynavel]

this is going to sound quite blunt....but...turn the damn thing off before u commence gaming!!!!

 

[Manzelle]

Set yourself as away and configure it to hide windows and disable sounds while you are away...it's that simple...

Or...close the damn program before you play games...

 

[imported_Fluffy]

There should be an option in Preferences stating "start messages minimized," or something of that nature. Try using that.

But, I still must agree with fuzzynavel. Turning it off solves this problem.