Not too bad, BoXXi....but...
Since the OS actually knows where the system.ini file actually is, and by finding it to read it and determine what shell to load, it is already in the root directory of the OS, namely c:\windows, and doesn't need to be told where explorer.exe is, cos it's in the same folder....
There's typically no leading spaces in the path statement, either....

So ignoring case-sensitivity as an issue, [which it isn't]...this would be the typical entries....

shell=Explorer.exe

This needs to be changed to:

shell=C:\Litestep\litestep.exe


The Windows kernel and registry is totally oblivious to the litestep.exe proggy, so the full path MUST be included....if not, no shell, no GUI, no fun...

One other thing Paul, I put shell=Explorer.exe in my system .ini, and the system wouldn't start.
When I went back in and put shell=C:\WINDOWS\Explorer.exe It started up!
Why is that? Any ideas?

Bryan...you must have chosen a 'custom install' for Windows...either that, or your registry is a bit wacky....every system.ini I have seen in 'normal' use, has never had the path...

I gotta admit, though, I once was told in no uncertain terms that a failed install of a litestep shell was NOT down to typing errors in the system.ini, but that some unknown gremlin or whatever had caused the message to pop up that he must re-install windows.
He couldn't be convinced that it was pure cause and effect....if he got the error message it MEANT he had typed the paths incorrectly.

Sad thing about WindBlows is that it is too stupid to give out more accurate advice.
It should have said....
"Twit, you tried to edit the shell= line in the system.ini and now you will die a horrible death for doing it wrong".....

Wow that is very cool. I'm not a Litesteper but I know I've seen the info at LS2K.

Keep in mind the "system.ini" information applies for Win9x systems only.
For WinNt, Win2k, or WinXP it requires a registry entry.