brazil...a shell replacement should NOT be something that you DL with a browser and auto-install.
This is the problem.
People think it is just another proggy, and have no idea how to reverse the changes made, and assume that LiteSTEP [or some other shall] has trashed their system when it is their own ineptitude which has caused it.
In my ReadMeFirst.txt in my themes, I comment 'LiteSTEP doesn't kill computers, people do.'
And it's true, but a few simple 'rules' to abide by and it is a painless experience [usually].
The sad thing is that in '97-'98 when I first started playing with shells, no-one much was around to hold my hand and walk me through it, but I survived...without pickling any OS. Sure, I got into lots of fun over the years attempting stupid things, but you expect that when you are messing with something still in beta, sometimes oddly buggy, and continuously evolving, but that is all about what skinning/themeing is all about.
It's a 'young' industry in constant development...
At one stage, I toyed with various propietary 'installer' creating proggies and made my own self-extracting, self installing Litestep shell, but I continually got lost 'making' it install new system fonts at the same time and got a bit peeved. Also, there can be more 'issues' with a non 9x Windows, eg. registry settings, which I was loathe to include in an installer just in case it fragged someone's OS. Now it's gathering dust somewhere. [It DID work, though]...
In the next few weeks, I'll put together a 'basic' OTS-compliant theme and shell along with a blow-by-blow description of how and what to do to make it work.
I'll upload it here as a complete functional shell, not just a theme, and I'll include the most important part.....an 'RTFM'.....'TFM' that everyone 'needs' to 'R'...