Big mistake! .net

Hedroom · Post by **Hedroom** » Mon Apr 10, 2006 7:57 am

Hi

I appear to have made a big mistake.

I installed a piece of software the other day which would allow me to transfer mp3s to my SonyErricson phone (I kno, pathetic isn't it!?). Installing it required the new version of Microsoft .net (2 I think but I can't really remember). I foolishly allowed the installer to install it for me.

Now, whenever I load my Live set in 5.03 it poofs and dissapears. In any other version of Live (including 5.2), my system will work veeeeerrry slowly. Opening or closing the browser takes about 5 seconds. If I play a clip I get extreme glitching and the cpu meter goes up to about 500%!!

I have a very large set but never had any troubles before. Why did .net do that reduced my Ableton performance so drastically?

I've tried deleting Preference.cfg. The problem may be related to something else rather than .net. However, this is the only thing I've changed in my system lately.

Help please!!

I'm on XP with a P4 2.4 GHz processor, 1 Gb RAM.

Gareth

leinad · Post by **leinad** » Mon Apr 10, 2006 9:54 am

I'm also on XP with a P4 2.4 GHz processor, 1 Gb RAM, .NET 2.0 installed and everything works fine here.

Hedroom · Post by **Hedroom** » Mon Apr 10, 2006 10:37 am

Thanks for the response.

Interesting... I'm pretty sure that is te only thing in my system which has changed. I wonder what else could be the culprit.

anti-banausic · Post by **anti-banausic** » Mon Apr 10, 2006 3:53 pm

This may be a stupid question, but have you checked your buffer settings? Maybe they were changed somehow?

Hedroom · Post by **Hedroom** » Tue Apr 11, 2006 9:57 am

Solved it!!

I discovered that my computer was only addressing 512MB of RAM instead of the 1GB it should have inside of it. As such it was obviously struggling when it loaded up my monster set!

My laptop has 2 * 512MB modules in it and I recently swapped them over to try and rectify an annoying issue with a fan touching them and making a loud lawnmower(!) noise. I remembered this and tried swapping them back. Now the full compliment of memory is recognised by my machine and my set opens fine.

No idea why swapping the memory over makes any difference but it seems to have sorted it.

djastroboy · Post by **djastroboy** » Wed Apr 12, 2006 5:51 pm

You probably didn't get the memory seated in the socket "just so" when you swapped them the first time.