Okay, I'm on an 800mhz Celeron system with 384 megs of SDRam. I don't know if that could be part of the problem but, yeah that's what I have. I'm running XP and I'm using the omar 3.0.2 build.

Whenever I leave Litestep on for a long time, I was watching a movie in DivX the first time. Litestep starts using 95-98% of my processor and like 120megs of Ram. Programs in themselves work fine but litestep takes a really, really long time to load up anything. It took somewhere around a minute to load the menu when I right clicked on the desktop. After it loaded up the menu it wasn't horribly slow to load the subgroups. This doesn't happen whe the computer is not on for a very long time but it may just have been running the applications that I was. Any help would be appreciated.

You can edit your posts. No need for the DP.

A 800MHz (100MHz FSB I take it? Celeron III?) Celeron w/ 256+MB on XP should be a fine desktop setup.

1. Kill any non-necessary background apps (AV anf firewall apps need to stay).
2. What theme is it? All themes? If not, try different themes and see what happens. Sounds like a module is going crazy with a memory problem--even super-bloated themes rarely reach 20MB RAM.
Litestep has grown into largely being a plugin manager, as far as how we use it goes. There are many modules and many versions of most modules out there, it could be any one.

Also, since this isn't really a builds question, don't be suprised if it is moved into Modules or General.

Disable popupicons

The theme I have is called Grayscale (I think it did the same thing with one called litescape) I got them both at this site. Sorry but I don't know how to do those things, is there anywhere I can go to read about that stuff or could you tell me? Sorry and thank you.

Sometimes this happens when LiteStep hangs up. If you give LiteStep focus, by clicking on something LS controls, it normally fixes it right up.

Just now I was in the default theme, austerity I think, and the same thing happend except this time explorer started sucking up all of the processor but only about 30megs of RAM. This time everything ran really, really slow and it took about 15 minutes to just get the system to restart.

if you would have left clicked on your desktop like I had suggested it would have probably gone back to 0 CPU.