Installing Litestep on Windows 7 x64
You need to download some required libraries in order for Litestep to run on
Windows. The libraries are called "Microsoft Visual C++ Redistributables"
otherwise known as vcredist.exe. What you will need are the 2005, 2005 SP1,
2008, 2008 SP1 to run properly (it is what the Litestep installer will be looking for)
If you currently develop with Microsoft Visual Studio (Express, Web Developer),
whichever version, your libraries should already be in place; though checking
for updates is a good idea. For good reason, I also recommend looking for
"Sec ATL" updates, they contain patches and fixes for possible security flaws within
Microsoft's code source.
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 program is by default, 32-bit architecture,
however the 64-bit update package (0.25 Alpha and greater) will be a patch after
you install Litestep. The 32-bit libraries are for the core runtime of Litestep, the
64-bit libraries are to run the threads and core instance of Litestep, and any possible
plugins or other code source which may require 64-bit libraries.
To take a look at what you may need for LOSI or Litestep, tobbe on githup can show
you here: tobbe.github.com/losi/prereq.h…
The downloads for the Microsoft Visual C++ Redistributable Packages can be found
You will need to search for the following packages, the links change sometimes.
(if you cannot find them within your country, you can try www.microsoft.com/downloads/en…
to search the English Microsoft Download Center)
Visual C++ 2005 Redistributable Package (x86)
Visual C++ 2005 SP1 Redistributable Package (x86)
Visual C++ 2008 Redistributable Package (x86)
Visual C++ 2008 SP1 Redistributable Package (x86)
Visual C++ 2008 Feature Pack Redistributable Package (x86)
Visual C++ 2005 Redistributable Package (x64)
Visual C++ 2005 SP1 Redistributable Package (x64)
Visual C++ 2008 Redistributable Package (x64)
Visual C++ 2008 SP1 Redistributable Package (x64)
Visual C++ 2008 Feature Pack Redistributable Package (x64)
After you have installed the Redistributable packages, head on over to
lsdev.org or litestep.net (lsdev.org is further updated) to get the Litestep
LiteStep 0.25.0 "Alpha" from lsdev.org - which has the 64-bit (x64) patch
For litestep installer (src and bld are available there) litestep.net/
for the 64-bit packagewww.lsdev.org/doku.php?id=lsde…
NEWER WAY: tobbe.github.com/losi/download…www.lsdev.org/doku.php?id=lsde…
After installing 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 install directory.
When running the installer, I highly reccomend setting the install directory
to C:\Program Files\Litestep or C:\Litestep to run the process. Modifying
permissions for all directories within the LiteStep install are recommended to
be Read-Only; except for $ThemeDir$, that should be read and write if you
are making and or installing themes. Some themes may need their sub-directories
to be writable in order to save file changes within the theme.
Setting LiteStep as your default shell manually:
You can use an advanced startup configuration tool such as Microsoft Autoruns, which
allows you to see registry entries (if located within the System32 folder. If not, it will
only show regular startup entries. Same with any of the TechNet tools, when not in System32)
To edit your Registry, you can launch regedit in a few different ways:
cmd /c C:\Windows\system32\regedit.exe
cmd /c regedit
HotKey (bring up the RUN console) : WIN+R : (then type in) regedit
To locate the default shell for your Windows Logon navigate through the following folders:
( %LSLocation% is a word for, where you installed Litestep; %LSLocation% by default in the LiteStep installer is C:\Program Files(x86)\LiteStep (-OR-) C:\Program Files\LiteStep (-OR-) C:\Litestep\ )
Policies held by the system shell
Logon events for the shell, in event viewer and auditing
Local Machine policy for the rule of system shell
If you wish to run LiteStep and Explorer in a "Dual Shell" mode, you should
leave the System Shell entries alone, and add LiteStep to your startup list
in order to run it when you log on. (I recommend installing it as a Service,
which you can learn more about Service.exe here: www.msfn.org/board/topic/83272…
C:\> cmd /c sc create LiteStep binPath= "C:\Program Files\Litestep\litestep.exe"
(note: C:\Program Files\Litestep\litestep.exe can be replaced with where you installed LiteStep)
after you install litestep, go ahead and open
This will tell LiteStep that it is not the default shell. If you are running a "Dual Shell" mode.
Once you get this done, you can run your themes, though what I have learned from this:
You do not need jDesk or xDesk to run your themes, however you may still need to set your workspace.
Running themes without jDesk or xDesk is still possible; it will enable you to use the Windows Active Desktop
when running LiteStep. Though depending on your version of xDesk or jDesk you may need to use it.
There are a few ways to make LiteStep plugins / addons and modules without using jDesk or xDesk,
but it is fairly complicated as far as LiteStep plugin scripting goes.