System Tray Icons Dissapearing and 100% CPU Thread last updated on 2005-11-01 22:19:35

Posted by member 278479 on 2005-10-26 20:46:06

I am using Windows Xp (Service pack 1), the latest litestep build and austerity. A seperate problem is that sometimes litestep uses up 98%-100% CPU. If I recycle it at that point, the bar disapears as do the desktop icons but fail to re-appear. Also, litestep is still running and taking up 100% CPU. If I close it and re-run it via the task manager then the system tray icons are gone.

I think that my system tray icons may dissapear at other times as well. Also, when the icons are gone, every few seconds they appear for a split second and dissapear again.

How can I fix these things?

P.S. I think that the 100% CPU problem occured after I installed xDesktop. However, the icon problem was there before. I have made some minor changes to the configuration files (and I could easily have messed them up). Is this the problem?

I really like litestep and much prefer it to explorer except for these problems.

Thank you for your time.

EDIT: I accidentally wrote quick launch icons instead of system try icons.

Posted by member 248213 on 2005-10-26 20:51:04 link

What exactly is the "latest litestep build" you mention?

Posted by member 278479 on 2005-10-26 20:52:53 link

litestep 0.24.7 RC 1.
I downloaded Omar's installer about a week ago. Sorry for not being more specific.

Posted by member 212670 on 2005-10-26 22:01:21 link

There's actually newer builds based on RC3 at ls-universe.info, and the RC3 build itself is on this site in the downloads area.

Posted by member 278479 on 2005-10-26 22:37:46 link

I updated to RC3 and the problems seems to have gone away.
Also, litestep is MUCH faster overall. The update was worth it even though I accidentally deleted all my configuration changes. (Oops)
Thank you.

Posted by member 248213 on 2005-10-26 23:36:16 link

The moral of the story? Always state your build, even if you think its the latest.

Posted by member 5575 on 2005-10-27 08:11:44 link

I'm average height, about 162 lbs, and I'm using andymon's 0.25.0.

Posted by member 248213 on 2005-10-27 22:05:59 link

Perfect. But not my type.

And welcome to ls.net Boreas :), it is Brian right?

Posted by member 5575 on 2005-10-28 01:52:56 link

Yep, that's me. I haven't visited here much lately, but I got back into active theme-updating when I converted all my scripts to lua. I'm still learning and tweaking, but lua's a lot nicer to work with than mzscript. It's like... a real language.

There's a lot of lua scripting in that logic.dream theme, eh? =P

Posted by member 248213 on 2005-10-28 17:06:51 link

well, I wouldnt call it "scripting" more, lua short handing type lazy !execute [][][][][] stuff ;)

Yeah, lua is teh shit!, once someone gets loadlib() to work, it will be the end all of LS :]

Some of the lua modules out there are insanely wicked.
Like the win32 one (cant remember the name), it has basically all the misc LS modules rapped into one lua module :o

And it has windows registry support!

That would be killer for LS.
and thats just the stuff I am interested in, tnl and doy and the rest have been scoping out even more "geek" type lua modules they could use with ls.

Someone should really make that a priority, it might even pull some lua geeks into LS, or something... :D

Posted by member 5575 on 2005-10-28 21:13:33 link

Hmmm, I've been integrating some vbscript registry things into my lua functions. I do the system color updating that way, and I just got a script working that shows the top 10 processes in terms of memory and/or pagefile use in my 'sysinfo' label. Basically it shows what you'd see in the XP task manager, if you have those columns selected. I still need to work on the formatting a bit, but it looks like this (lower right corner):

http://83.151.29.44/jochen/files/screenshots/files/Chameleon.jpg

Posted by member 248213 on 2005-10-29 03:20:21 link

I must insist you release these scripts as snippets at ls-u.
You always tell me how you do cool stuff with VBS but never seen anything hard.

:)

Please, this would really help me/others I am sure (top ten processes? damn cool!)

Also I tried emailing you about writing OTS3 utils in VBS, wether its possible, a good idea etc.

What do you think? (If you write simple utils in VBS for LOSI, then Tobbe can focus on writing/debugging the actual installer ;) )

Posted by member 5575 on 2005-10-29 12:21:23 link

OK, I'll post a few snippets. IIRC I posted the system color registry stuff on the LSML a little while back, but that list doesn't get the traffic it used to get these days.


... And now they have been submitted, one for the process info, one for system colors. It's up to the site admins now. ;)

Posted by member 7 on 2005-10-29 16:02:57 link

Actually, the LSML is "just" broken. For the last 10 days or so all mails are bounced after a few hours.

Posted by member 5575 on 2005-10-29 17:56:04 link

Hmmm, gmane problem?

Posted by member 7 on 2005-10-30 03:19:43 link

I doubt it, given the error message below. Do you know of any way to contact Bryan other than bryan@wuzzle.org?

----- Transcript of session follows -----
451 4.4.1 reply: read error from litestep.wuzzle.org.
... Deferred: Connection timed out with litestep.wuzzle.org.
Message could not be delivered for 2 hours
Message will be deleted from queue


But this is all going way off topic. =)

Posted by member 5575 on 2005-10-30 12:50:12 link

Not really - perhaps visit wuzzle.org? I poked around there a bit, but didn't see any additional ways to contact him - just more links to bryan@wuzzle.org. He also has an mholmesiv identity - that nick seems familiar somehow.

Posted by member 248213 on 2005-10-31 05:45:16 link

man alive, how long does it take for your snippets to arrive!?

Posted by member 5575 on 2005-10-31 09:06:59 link

I dunno - that's up to the ls-universe guys.

Posted by member 5575 on 2005-11-01 01:14:36 link

Well, one of them is up there now - the process info stuff. Still no sign of the system color script though. Patience. =)

Posted by member 248213 on 2005-11-01 20:32:21 link

probably want to check all the code seeing as its VBS (virus) ;P

Checking out the process one

Posted by member 5575 on 2005-11-01 22:19:35 link

Yeah, it's nasty stuff. Lots of... *sysadmins* use it. Gross. =P