Well, I'm using litestep for over a year and so and loving it...
Using the theme "Ghost" and all was working fine, i decided to reduce my pagefile size as i have more ram now(total 2gb) so i reduced it to 300MB and rebooted.
After i rebooted litestep gave me errors that it cannot locate modules, a bunch of them.
I thought to myself ok maybe my theme has gone bad lets switch to default, but it gave errors as well so i tried to re install it yet same problem, even if i put back to the original size of my pagefile it still gives errors.

The module files are there, not write protected or anything and got access to them.
The full error is as following:
"C:\litestep\modules\taskbar3-0.306_alpha-2.dll
Error: could not locate module.
Please check your configuration."

Using Omar litestep with RC4 addon.
Any help would be great :)

The problem is likely a missing depandency of the module. (msvcr71.dll or something). Did you clean up your root litestep folder recently? Anyway, you'll also want to upgrade to NetLoadModule 2.5.0 and the final release of Litestep 0.24.7, instead of the release candidate 4 you are currently using.

If all else fails, be sure to try re-install litestep (after backing up your personal config files) upgrade to 0.24.7 final, upgrade to NLM 2.5.0 and go from there. Good luck.

I seem to have picked up the same issue. I have tried completely reinstalling Litestep with no success. I've updated to 0.24.7 final, updated to NLM 2.5.0, still having problems. The 3 main culprits are LSXCommand, Taskbar3, and SysColor. I've not really played around with the .rc files before, but changing the version of LSXCommand requested to the latest one I could find in the \modules folder stopped that complaint. The latest versions of the other two still cause problems though. I didn't have an msvcr71.dll in my \Litestep folder until I updated NLM, but I do have one in \Windows\System32. Still no luck.

It's probably one of those other ms*.dlls you need. Wasn't there a utility that watched dll dependancies? Don't know it offhand.

I found an app called Dependency Walker, but it couldn't find any problems. Is there anyway to make litestep come up with which module specifically could not be found? As it doesn't appear to be complaining about taskbar3 itself.

Seem to have fixed it now. It seems certain modules aren't happy with DEP (Data Execution Prevention) enabled. I forgot that I'd turned it on without restarting. Adding Litestep as an exception and rebooting appears to have fixed all the problems.

For anyone interested in what this was about:

http://support.microsoft.com/default.aspx?kbid=875352