Whenever I am running LiteStep and open an Explorer window from within LiteStep, it opens fine, lets me navigate thru my folders with no problem. But, if I have been using Explorer for more than a few seconds, and right-click anywhere in the Explorer window, LiteStep crashes, and with it, the Explorer window! It doesn't happen every single time; it seems that it usually happens with a certain theme (Ghost), but occasionally happens with austerity as well.

I was watching my processes in Task Manager, and was especially watching the memory and CPU usage of LiteStep. When the Explorer window is opened, CPU usage goes up briefly (as you would expect it would) and memory usage goes up a bit. When a crash happens, explorer.exe disappears from the task manager, and litestep.exe's memory usage increases to about 22MB (higher than usual, but not outrageously high.) The window stays put, but does not respond, and Litestep refuses to respond as well. Any ideas?

Here are my system specs:
Athlon XP 3000+ 400 FSB (stock speed)
Abit AN7 w/ nForce2 Ultra400 chipset
512 MB (2x256MB) Corsair PC3200 RAM
Western Digital 80GB w/ 8MB cache
Windows XP Pro SP2

Does it change depending on if you're using LSUseSystemDDE ?
I ask because LSUseSystemDDE seems to not create an explorer.exe process when launched indirectly (e.g. run a directory) from LiteStep

I don't have LSUseSystemDDE.

in the personal.rc file the last setting...