Installing Litestep on Windows 7 x64
By Sean Lum (me! atde)

; if there is anything I have missed, or anything you would like to add
; please let me know
First off:

you need to download some requirements in order for litestep to run on
Windows. What you need is called "Microsoft Visual C++ Redistributables"
otherwise known as vcredist.exe. and the versions are 2005, 2005 SP1
(and reccomended feature pack), also 2008, and 2008 SP1
(feature pack also reccomended), getting the security updates is also
reccomended for this, just because. I know it sounds funny, but you
need to get the x86 (32-bit) and the x64 (64-bit) installers for this
reason. The Litestep installer is an application by default with an
32-bit architecture to it and so, you need to get the 32-bit vcredists
first. They are included in the package, along with the 64-bit. Suprisingly
the 32-bit and the 64-bit redists can actually be left on your computer,
the 32 and 64 bit libraries are helpful to the native 32 and 64 bit compiled
programs that have visual c++ in them.  BTW, having Microsoft Visual Studio,
or Microsoft Visual Studio Express (newer version if possible, if not, check your
service pack installs)

you can go here:
[link]

MICROSOFT VISUAL C++ REDISTRIBUTABLES 64-BIT

Visual C++ 2005 Redistributable Package (x64)
[link]

Visual C++ 2005 SP1 Redistributable Package (x64)
[link]

Visual C++ 2008 Redistributable Package (x64)
[link]

Visual C++ 2008 SP1 Redistributable Package (x64)
[link]

Visual C++ 2008 Feature Pack Redistributable Package (x64)
[link]

MICROSOFT VISUAL C++ REDISTRIBUTABLES 32-BIT

Visual C++ 2005 Redistributable Package (x86)
[link]

Visual C++ 2005 SP1 Redistributable Package (x86)
[link]

Visual C++ 2008 Redistributable Package (x86)
[link]

Visual C++ 2008 SP1 Redistributable Package (x86)
[link]

Visual C++ 2008 Feature Pack Redistributable Package (x86)
[link]

After you have the requirements you can go and get the litestep.exe installer
from litestep.net (or you can use the one in this package). Then after that,
you will need to get the 64-bit litestep process and sub-requirements ( it is
needed in order for the process to run correctly) and I am using:
LiteStep 0.25.0 "Alpha" from lsdev.org

Old way (works!)
For litestep installer (src and bld are available there)
[link]

for the 64-bit package
[link]

New Way:
[link]
[link]

So, after you install litestep on your computer, go ahead and open the
0.25.0 Alpha package (the new litestep installer should technically
have $Win64$ support on it already). Once you open the archive, go ahead
and find your litestep install directory. Then from the archive, extract the
files into your litestep directory.


When running the installer, I highly reccomend setting the install directory
to Crogram Fileslitestep or C:litestep to run the process (auditing can
also be a good security boost for this application, along with making it read-only
for all files except for your $ThemeDir$, that should be read and write if you
are making and or installing themes)


Setting Litestep as your default shell manually (not hard):

You can use an advanced startup configuration tool such as Microsoft Autoruns
(or a tool that allows you to see, and edit registry values for on and off).
Then you look for the startup entry for your shell (should be the following)


HKLMSOFTWEAREMicrosoftWindows NTCurrentVersionWinlogonShell

open regedit (WIN+R, input = regedit) and then run it (the process is required
to run at an administrative level so you don't really need to worry about
using run as administrator option) and then do a search for the above key.
Once the key is found,

change explorer.exe
to C:%LSLocation%litestep.exe

%LSLocation% by default in the litestep installer is Crogram Files(x86)Litestep

These other registry keys are good to take a look at, for security and also
for auditing / logging of shell events, though I think LOSI also has an event
tool in it (like a debugger) that can be used for the same purposes, I'm researching
on how I can log all the events at the moment, if you have any reccomendations,
please let me know!

Policies held by the system shell
HKCUSoftwareMicrosoftWindowsCurrentVersionPoliciesSystemShell

Logon events for the shell, in event viewer and auditing
HKCUSOFTWAREMicrosoftWindows NTCurrentVersionWinlogonShell

Local Machine policy for the rule of system shell
HKLMSoftwareMicrosoftWindowsCurrentVersionPoliciesSystemShell

RUNNING THEM TOGETHER:

DO NOT CHANGE DEFAULT SHELL VALUES IN REGISTRY IF YOU DO THIS, you will
not be able to get explorer running in shell mode if you disable the entry,
you would have to launch explorer.exe in a weird way to get only the shell running.


after you install litestep, go ahead and open %LSLocation%personalpersonal.rc
then add this to the personal.rc somewhere in order to tell litestep that it is not
the default system shell.

LSNoShellWarning

Once you get this done, you can run your themes, though what I have learned from this:

it is harder to set up jDesk (if you are running multiple monitors, then you can use
windows desktop on one monitor, and jDesk on the other. It solves a jDesk bug, and
enables you to use windows active desktop and jDesk at the same time). If not then you
have to make multiple desktops, and establish them on both monitors.

As far as desktop goes and whatnot. You have to use jDesk to help your litestep when running
both shells at once, and then making your theme be a default bottom layer. (Always on top won't
work right with jDesk ((you can use other modules like xdesk)) on multi-monitors so easily, but
works great on one.

When designing litestep themes, here is a hint, keep in consideration your windows taskbar so that
way your active desktop notices litestep and explorer running, so you can use them.