I've used Litestep for some time, previous versions didn't give me this problem.
This is a fresh install of Litestep 0.24.7 on a Win4k box, with an AMD chip, 1.3g of ram and a Firegl graphics card.
I leave the computer on all the time.
If left over night the screen graphics lock up and keyboard functions don't work. I must reboot manually.
On reboot and I call up windows task manager I can see that Litestep is occupying all cpu activity and, while the screen graphics come up fine, nothing works. From the task manager I kill litestep and restart it and it will work fine for quite a while until it locks up again.
Ram useage is minimal, even when litestep locks and has taken over the cpu, ram is hardly touched.

I really like Litestep and would like to continue using it, but not without some guidance on how to fix this.

thanks,

It might be your llama output, a bad theme, or ls just may not work on 2k4, i dunno. What theme are you using? Try switching to the default if your not using it and see if that cures your problems.

I'm using the default theme Austerity.
Previous versions of litestep worked on this computer with Win2k.
llama?

The only guidance is that you need to track down the module that causes this. Since LS almost completely consists of modules there is no other way.

First you could try to load litestep with no modules at all. If you see the same behavior even with such a configuration it's a core bug. If not, add all your modules back in one by one.

I've had that happen on my box a couple of times (the CPU issue, not the lockup) and I'm running virtually identical hardware: AMD Athlon XP 2400+, 1 GB RAM, FireGL X1 video card. I also keep my system on 24/7.

However, I only noticed this with older LS 0.24.7 builds. It was intermittent, usually occurring on the initial startup of the shell and didn't seem to be related to any particular theme IIRC. You may want to try running the "update build" utility if you haven't already, or you may want to try one of the unofficial builds available from the LiteStep page at ldex.terica.net.

HTH.

Edit: I'm on XP SP1a, tho, with a Gigabyte motherboard (VIA chipset).

Never had this problem on Win2k/SP4