Over the past week, I have stumbled over Litestep. I took the plunge of installing it, and grabbed Omar's Installer (3.02) and jumped right in. By the way, I'm running Win XP SP2. The install went perfectly fine. I read that since I'm running XP SP2, that once the install was done, I should not reboot, and go the the Litestep folder, and use the SetShell utility to set the shell once again. I think I then updated the build to the latest 24.7 final, and then rebooted. Now here comes the problem. XP starts up fine, and gets to the welcome screen. I click on my username, and attempt to log in. As I start the log in process, a couple of things start up, my background appears, some desktop icons appear, and the litestep taskbar appears for the most part, and then... BOOM... nothing- everything just freezes. The mouse doesn't move, nothin. All I can do is run Task Manager, and reset the shell to explorer. I've done everything I can think of and have read. I've checked the registry, downloaded dll's, all of that.

If anyone has any insight or helpful info, it would be greatly appreciated.

I would uninstall then reinstall then update manually again.
If it worked fine the first time try again.
Maybe the setshell messed you up somehow.
Also did you download the new beta's on lsdev.org or the 0.24.7 final that is known as the last stable release?

Hey, thanks for the quick response-
My build is the 0.24.7 final, not the beta's
Should I install the beta build?

I would stick with the Final Build atm...
At least until you know whats going on with ls.

"Litestep Freeze" sounds like a tasty treat for a summer day.

Sounds like a module is causing a conflict with something else on your computer, try downloading a different theme or commenting out modules until it loads properly. I would even comment out every module except the one that runs the popup menu then turn them back on one by one until it freezes again. Just recycle Litestep each time until you find the module that is causing problems.

If it freezes even with all the modules commented out then it's obviously another problem, but at least you've narrowed it down some ;)