had ls for 2+ years now, uninstalled it. reinstalled latest installer, then updated build. now whenever i load a theme i get the error message
"
Error: could not locate module
please check your configuration
"
with, i dont think it matters, but
taskbar
syscolor
lsxcommand
speedy replies would be great.
What theme? What build of litestep did you update to?
Sounds like you're probably missing a dll that the modules depend on. Make sure you have
these.
speedy replies would be great to our questions as well.
c = 3 x 10^8 m/s
No reply is faster than that.
well i had 8:30 class, i sorry i wasnt up at 2 am to answer your speedy replies. regardless, i installed the lsinstaller, then i updated my build to the latest build, so thats not it. and the theme was austerity, default settings. and i know the dll files are there, i manually zipped them and reloaded the module to get fresh copies, they might have been corrupted. but same deal. ill check those dll's later today (at school)
Those are not the DLL's that xcal was referring to - the link refers to MS runtime DLL's (on which some LS modules depend) that may not be present by default on your system. Did you look at what xcal posted?
yes, and i said i would check them out later. the dlls that he was referring to. but i was diagnosing my problem further. and no, i already had those dll files in my sys32 folder. so thats not the problem
edit: did you look at what i posted?
It wasn't clear whether you were referring to LS modules or the MS runtime DLL's in your post, so I really couldn't tell for sure.
the problematic dll files are the ones i was referring to, the ones that give error messages.
ok, i solved the problem. took me a while, heres my final diagnosis/solution:
im using an amd athlon 64 bit processor, thats the problem
solution: go into control panel -> system -> advanced -> performance options -> data excecution prevention
add litestep.exe to the exceptions list, problem solved for me.
I have a 64 bit processor and don't need ot do this. Try again.
It seems like DEP would cause problems for LS on 32-bit systems too, in that case, but it doesn't AFAIK. Perhaps something else weird is going on?
Well, DEP causes the exact same problem here on an Athlon 64 with 32 bit Win XP if it's turned on. There was a discussion about this on ls-u some months ago and it was confirmed by several Athlon users.
Ya, I remember that thread, too...think it was acidfire that started it.
DEP is off by default, so not really something that comes up much.