has this issue been fixed yet?
when explorer is the shell it's always a normal priority proccess but with litestep when explorer is started to browse files its always a highy priority proccess.
has this been fixed yet?
oh my gosh, I cant beleive I havent noticed this before!
weird...
well it's not good cuz it will slow down browing files and sometimes will hicupp music playback if explorer is searching the hardrive
I guess "use a different file manager" isn't a good answer, but it's a solution. =)
I never noticed that before either. Manually adjusting the priority seems to only be a temporary fix, too. When explorer is closed and reopened, it's back to high again...very odd.
There's a program called ProcessTamer.
I'm not sure what happens when you set
LSUseSystemDDE true
—this makes explorer processes children of LiteStep when you open paths implicitly and so they are at normal priority?
LSUseSystemDDE true == high priority (for me on win2k3 anyway...)
Hmmm, if I start explorer with a hotkey or popup, it shows up in the task manager as a high priority process. If I start it from lsxcommand, it doesn't show up at all in the process list, as it's a child of LS. Curious. I guess the commands are executed differently for those modules.