Litestep freezes when explorer is called Thread last updated on 2006-02-22 05:05:47

Posted by member 252500 on 2006-02-18 13:20:39

I just manually installed litestep .24.7 on XP SP2. After each log in, the first time I access explorer (via lsxcommand, popup, whatever), litestep freezes. Then if I end task rundll32.exe the explorer window pops up and everything is fine. If I end task rundll32.exe before calling explorer then this doesn't happen.

One other thing, I changed the registry keys myself, and I forgot to run SetShell before rebooting after install. I don't know what effect if any this would have.

Any suggestions?
questionmuppet

Posted by member 1 on 2006-02-18 14:18:01 link

Did you change the BrowseInNewProcess registry entry?

Posted by member 252500 on 2006-02-18 15:34:48 link

No. I added a DWORD called DesktopProcess = 1 to both
HKCU\software\microsoft\currentversion\explorer\ & HKCU\software\microsoft\currentversion\explorer\advanced\. There's a DWORD named SeparateProcess in the "...\advanced" key. Do I need to do something with this, or add another entry?

Posted by member 1 on 2006-02-18 16:29:05 link

Straight from the docs...

HKey_Current_User\Software\Microsoft\Windows\CurrentVersion\Explorer\BrowseNewProcess > - Change this value to "yes", it seems to correct a few problems with explorer spawning itself as the shell.

Posted by member 252500 on 2006-02-18 22:00:06 link

I didn't have a registry entry by that name. I created a DWORD of value 1 with that name but no dice. I also tried it with other variable types (string, extended string) with a value of "yes". Still nothing.

Posted by member 5575 on 2006-02-18 23:18:30 link

Try running lscheckreg.exe and see what it says.

Posted by member 252500 on 2006-02-19 11:52:48 link

I ran lscheckreg.exe and each of the keys comes up as "OK" or "Seems to be OK" (except the syscolor and wallpaper keys under Litestep Installer, which I didn't use for the install.) This is strange because it lists a value of "yes" for BrowseNewProcess but I can't find this entry in the registry.

Posted by member 5575 on 2006-02-19 13:48:39 link

Hmmm, I see it just fine. Try saving this as a .reg file and importing it:

REGEDIT4

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\BrowseNewProcess]
"BrowseNewProcess"="yes"

Posted by member 252500 on 2006-02-19 15:15:54 link

Whoops, I was looking in HKCU instead of HKLM so that's why I didn't see the entry. In any case, the BrowseNewProcess key is set to "yes" now and the same thing happens when I log in :(.

Posted by member 1 on 2006-02-19 19:03:01 link

is there a reason why you refuse to let LS set itself as the shell?

Posted by member 212670 on 2006-02-19 19:29:47 link

Heh that's what I've been thinking. Why not just use the installer?

Posted by member 31 on 2006-02-22 05:05:47 link

The BrowseNewProcess value is 'supposed' to be for internet explorer to launch each ie window in a separate process. The DesktopProcess value is for the shell, which separates the shell from the file manager. The SeparateProcess value is for the file manager to launch each window in a separate process.

Of course, as Dev said, sometimes it seems to help to change them all to be 'yes' or '1' (depending on which) as there seems to be some cross dependancies now and then. Fun stuff.