LiteStep looks great, (I was directed here following a Q on /. badly wanting an X-flavored WM/shell on windows -- which I'm stuck using on a contract job).
I'm on win2k I think SP4, it's a fairly customized enterprise version of W2k Problem is:
I've installed v 3.0.2, read the install doc etc.
litestep segfaults on startup post-login. I don't have too many details handy, 'cept it's triggering an error in rundll32.dll, crashes and leaves no shell running.
Tried it on 2 different accounts, same results.
I'll try installing an older version of litestep unless anyone has other ideas?
tnx
Does relaunching litestep.exe (via task manager) help? If so it might be a problem in the startup code. Are you sure that it's rundll32.
dll? You may also want to upgrade to the latest LS build. Run C:\Litestep\Utilities\UpdateBuild.exe and point it at
http://leaf.terica.net/software/releases/lscore/LS-0.24.7-RC2.zip
Hmm, well not exactly 'help' it no longer segfaults, however it seems to have
pretty much locked up the desktop, nothing on the DT works and the hourglass
predominates :-)
Pardon the error was in rundll32.exe, I misquoted --- instruction at 0x1000b3f2 cannot read address 0x1000b3f2
after that effectively the same error comes up referncing litestep.exe addr 0x01b6b3f2.
Tonight when I get home I'll try updating. Although litestep's bg is saying it's 0.24.7, and the .exe claims a version of 0.2.4.7, it's dated nov '03 (latest I could find on this site)
Thanks for the tips! I'll give the newer version a go
no joy.
The more recent version *did* work for a test account I setup local on the machine in question, (it still gives a rundll32 error but litestep keeps going.
However for my real uid which is a domain account and has to log onto their network, the error ie exactly as it was before.
I'll try to dump some better diagnostics tomorrow
Hurm - my guess is that the rundll32 is a startup item that somehow depends on explorer and/or exposes a bug in Litestep. Grab
Autoruns from sysinternals.com and check if there is any "rundll32" item in the startup list. If there is such an item try to figure out which program it belongs to. Check if disabling it helps. There isn't much else (besides wild guesses) that I can say at this point, let me know how it turns out.