I've recently installed winXP 64bit edition as part of an upgrade. Using Omars Litestep Installed 3.0.2 I was able to sucessfully install litestep but whenever I try to use explorer.exe for file browsing the explorer shell is launched instead on top of litestep.
Needless to say this is somewhat annoying. I had no problems using explorer.exe for file management in XP 32bit edition.
A registry entry to stop that probably moved. Id say manually walk through the install instructions at http://lsdocs.shellfront.org
and make sure everything was set properly. Then report back so that this can be corrected in the future.
This sounds similar to my problem. (found here: http://www.litestep.net/index.php?section=4&action=view&catId=1&id=4552
I think perhaps a new windows update (post-SP2) may have caused explorer to look in a different place in the registry.
I am post XP SP 2 and I have not started having any issues.
Im win2k3 and not having any issues :-k
I'm completely up-to-date on all XP patches, and problem free. however, you can try using setshell.exe to revert back to explorer as the shell, then use it (setshell.exe) again to go back to litestep. something odd may have happened.
I'm having the same issues with Windows 64bit edition. Everytime i click explorer to search through my files the windows taskbar pops back up. This is very annoying. anyone have a clue how to fix it?
emomoe :: completely different issue. your issue is caused by a bad setup. compare your registry to the description in the install instructions.
I've followed every step set out by the instructions. I've re-installed Litestep 6 times. I've done everything i could possible think of. However... I'm still getting the explorer taskbar everytime i try to run file manager in ls is 64 bit windows.
They sound like exactly the same issue to me...
The reg entry must have moved or been renamed, do us a favour and do some detective work ;)
It hasen't moved, it's a completely different app that's being launched! It's the 64-bit explorer instead of the 32-bit version...
right... How to solve it then?
I think RabidCow is doing a 64-Litestep compile.
I've tried moving the registry keys out of the wow6432node, adding that into the string, etc. I still don't know how to stop explorer from wanting to be the shell. Haven't had a lot of time to devote to the messier investigations though, so it's possible that it's not terribly impossible.
LiteStep does run ok on top of 64-bit Explorer tho. :)
Well, *noob giving advice when he prolly has NO CLUE what hes talking about* Until they fix this issue, maybe you could used a different explorer program. Just a thought.
Has anyone figured this one out yet?
hey... I've been doing a little tinkering with the registry and i need some help reading some of these files. I've been working with Regmonamd64 and making a log when i try to open file manager. so... if someone would like.. I'll send them the log so we can figure this out
Ill be happy to take a look :) (I dont have a 64 OS though, so...)
Anyone else want to take a crack at this one?
It was taking too long so I tried again, and then a third time with only half of the log. :D
Eat it up sucka's
ps: DeViLbOi is gonna kill me!!! :D
look below for link ;)
Only half of what emomoe sent me. And something tells me "I buggered something."
So not only did you post the WORLD'S LONGEST POST, but you posted it twice.
Good job fractal :P
And something tells me it doesn't end with the line "5735.88805485explor" :P
I'll have a link to it tomorrow morning.. I'll upload the entire log to my website for all of you to look at.
I hope it's alright to put a link in this forum. but here it is. The Regmon log file from when i tried opening file manager in 64 bit windows. good luck.
Ok...you know...when you are the same person that made the two previous posts that you have issues with patience. This problem is a little bigger than you seem to think. There is also a thread over in the Builds category on it and a couple different forums dedicated to it at other sites.
With all of the reverse engineering involved with a project like this it is likely to be a while. Heck...is XP64 even officially for sale yet?
157 5.79129648 explorer.exe:1524 QueryValue HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\shell SUCCESS "Explorer.exe"
Please use the XP 64 thread under LS Builds from here on out.