Windows fails to load after theme change Thread last updated on 2006-10-30 04:26:05

Posted by member 349596 on 2006-10-27 15:32:56

Okay I admidt I am a bit new to litestep but I'm not an idiot.
I tried searching the forums, read many threads and can't figure out my problem.

First I installed litstep and everything was going well. I installed a theme and that is where my problem lies. The theme loaded allright, downloaded the needed modules etc. Well now when it boots, all I get are errors. They are as follows:

gcasDTServ.exe failed to load
AOLsoftware.exe - unable to load component (AIM I believe)
msmsgs.exe - Unable to load component
gcasserv.exe - unable to load component

and they cycle through when I press "OK" on the error box. I think it is because they cannot load on the system tray.

when it first boots up I can get to the menu etc, but the second I tell it to do anything It instantly freezes. I was hoping to change back to the default theme but when I go to change the theme on the menu everything freezes except the error windows.

I also tried the windows recovery console. I thought perhaps delete the folder that the theme was in, litestep would revert back to the default and then I would be fine. However, when I try and access the litestep folder via the windows recovery console, it simply says "Access is Denied".

While the computer is frozen, other computers can still access it on the network.

Ultimately, I can't figure it out. I appreciate any opinions you guys may have. If any further information is needed I will do my best to provide it

Posted by member 248213 on 2006-10-27 18:45:05 link

Access denied from the recovery console!? Something is screwy here.

The recovery console logs in as admin (you input the password), so theoretically nothing should be denied...

Can you delete/create other things in the console?


Anyway, you should be able to login as another user (administrator for example) and reset litestep (look in litestep\profiles\[username]\themes\themeselect.rc, set the theme there)

But I have to say it sounds like there is something seriously wrong with your system (which LS has nothing to do with).

I know msmsgs.exe is MS messenger, and that loads fine under LS.

Posted by member 1 on 2006-10-27 19:11:07 link

Access the Folder or Delete the Folder? That is the question. Even Windows doesn't keep you out of the Windows folder in Recovery mode.

Posted by member 349596 on 2006-10-28 16:05:41 link

in recovery mode you log in as admin and can only access the windows directory.

Posted by member 248213 on 2006-10-28 20:53:55 link

"only" ??? I dont think so.

The old command
cd\
doesnt work, yes, but
cd \
does ;)

I know this for sure because I somehow deleted everything in C:\ the other day (not subfolders thank god!) so I had to copy stuff to C:\.

The recovery console wouldn't be very effective if you were only allowed into \windows\

So try again using "cd[space][backslash]" to get back.
or at any rate "cd .." works.

Posted by member 1 on 2006-10-29 04:23:31 link

*sigh* who knew that some day we would have to teach DOS to people.

Posted by member 248213 on 2006-10-29 09:04:45 link

well, its not DOS, is munted DOS. I only just found all this stuff out myself, so I am fine with imparting the knowledge of the recovery console ;)

Posted by member 1 on 2006-10-29 14:10:31 link

cd...mkdir...dir...del...move...those are DOS Commands...whether or not it is actually DOS or not doesn't matter.

Posted by member 248213 on 2006-10-29 19:33:41 link

Yes. I know they are DOS commands, but in the rec console they are slightly different:

cd\
will not work in the rec console.
cd \
however does (notice the space!)

Posted by member 212670 on 2006-10-29 20:20:21 link

WOOooooooOOOOOooooOOOOoooosshhhhh

Posted by member 1 on 2006-10-30 04:26:05 link

yes yes...but that is because cd\ never was a valid command name. It was permitted by MS for those too stupid to understand what they were asking for. The valid command is cd (Change Directory) and \ is a directory name. It is in there just like dir in Linux works even though it runs ls for you. Dir wasn't a valid command but too many people got to a console and screwed it up so an alias was born.