Please post your bugs with Release Candidate 1 here. This will make it easier for the devs and other users to find.
only bug i can find has been present since before even IndieLS.
some modules flat out don't want to show in the revision IDs section of the !about box.
very tight build :)
I brought that up to ilmcuts when he give it me to test. Unfortunatly it was an issue with modules not reporting it.
LSMail (4.3, vendicator) is no longer visible using RC1 on my system but it is loaded and working. Tried to get it back by ontop settings aso without success. LSMail seems to be somehow different in window-handling?
Humm, when I tested last popup2 release (last week), I had an error box saying that this module requires msvcpxx.dll... and I didn't took the time to look for it. Then I switched back to popup2-2.1.1
Now, with the RC1, if I try to load popup2-2.1.2, I simply have the "module could not be load" error box. Now, I have no mean to know which dll is missing
just have a strange error while trying to create a working script and using timer.dll in it. this is reproducable, seems not to cause any problem though: the script and timer get caught in an endless loop, which can only be left be !recycle. after that, i get an error message saying
LiteStep :: !Amp_Rew :: Error
Exeption during bang command execution. Please contact the module author.
note that not in any of my config files !Amp_Rew is called.
sorry if this is no ls but a module bug, thought this doesn't look like a module error.
WEll.. i upgraded from .26 and before i got a popup message with a runtime error complaining about some variable.. now it just hangs after the login screen. I have to Ctrl+Alt+Delete.. kill the app, then open it again.
I'm on XP Pro, with a welcome screen.
uhmm...define the variable?
3ph try turning off the welcome screen.
I have a multimedia keyboard and it have no leds for the num, caps, scroll lock, it displays an icon on the systray everytime one of those key are pressed. With the latest Indiestep these icons are not displayed in the systray and with the RC1 they are (just like in explorer), but apparently now I'm getting errors and Litestep crash. I didn't have the time to test it more accuratly, but switching back to Indiestep solve that problem, I have no icons displayed anymore, but at least the crash problem went away. BTW.: I'm running WinME on a PII with 128RAM.
Nothing. It says that Litestep has made an illegal operation and will be closed. At first I thought it was a problem with ckvwm 1.40, but everything is working fine with Indiestep and the only uncommon software I'm using it's the one for controling the keyboard.
psynapse: Modules are free to report version information (or not). Obviously some do and some don't. :P
ruhmkorff: Is there absolutely no way to get it to show up? Not even if you set it "alwaysontop"?
ElkMonster: The error message you get is probably the result of litestep.exe running out of stack space... in an endless loop this is bound to happen sooner or later. I'm not sure why the error message would be delayed until after the !recycle though. The fix of course is to remove the endless loop. Using !recycle to break out of something like this is a bad idea, the situation should have been avoided from the start.
Al: If you're coming from Indie LS you should remove liteman.dll from your personal.rc. If that doesn't help you'll probably have to track down the module causing the illegal operation. Once you know the culprit we can try to fix the bug.
Ok Ilmcuts I'll do it asap. Thanks :)
I just upgraded from 24.6 to 24.7RC1 and the bigest problem i have found is.
My DCOM isint very stable and whenever it has an error litestep jsut quits with no message or error.
normaly this wouldent be a problem but it causes lots of errors with multiple workspaces and menny windows disapeer and can't be restored.
Hi Ilmcuts, I did what you recommended and had another 2 error messages. This time when I recycle I had a message like this: Litestep has made an unknown error in KERNEL. Then I click ok and Litestep didn't crash as I was expecting, but load with no problem. When I recycle it again it gave me the same message and behave the same way. I'm running the same theme with the same configuration on a WinXP machine with no errors. I'll gonna comment out module by module and try to find what's wrong. This post is just to let you know what happened since your post from yesterday. ;)
Unfortunately, RC1 is much less stable for me than b4. With no apparent rhyme or reason, LS will just crash; Windows pops up the, what is it, illegal instruction or exception box... with the white cross in the solid red circle. It just happens out of nowhere. :(
I'm running 98SE and have gone back to b4 which, from memory, is quite stable for me.
Electron05: Any reason why your "DCOM isn't stable"? This *should* have nothing to do with LS...
9x users: RC1 seems to be a bit unstable on 9x. The biggest problem is that I don't have a 9x machine any more, so I can't narrow down the bug over here. If you have the time, try to downgrade to Beta 4. If Beta 4 works try using litestep.exe from RC 1 and lsapi.dll from Beta 4; and vice versa. One of them ought to make the system unstable. Post back here with the results.
Ok, will test different combinations and let you know.
ilmcuts: I'm using 98SE, and I have noticed some instability issues, however, they don't seem to be reproduceable; Litestep just crashes seemingly randomly. I'm also having issues with Explorer(file manager) crashing randomly (while using Litestep). As I've been spending 12+ hours a day at school, 8 days a week, I don't really have time to look in to this further.
Crashes are symptomatic of using the RC1 litestep.exe. No crashes observed when using the RC1 lsapi.dll.
A little extra info on my random crashes. The error message says "litestep.exe caused an error in msvcrt.dll...".
ilmcuts: No way to get LSMail back with alwaysontop or show-bangs. It is also not dependent on jdesk, desktop2 or any vwm. However, any 24.7-release earlier to RC1 doesn't have this problem. No helpful log entries.
ruhmkorff: In case you have the time, could you write a small testcase so I can reproduce this? Ie. a step.rc with nothing but LSMail and its settings plus a shortcut or two where LSMail can "hide" behind. Otherwise can you send me your LSMail settings and/or post a download link of the affected theme?
ilmcuts: I tried to load LSMail and RC1 without any other module and it didn't show up, even with alwaysontop. So just LSMail and RC1 are necessary to reproduce it on my computer (XP with nvidia gforce2go on a toshiba laptop). I then added jdesk only, but LSMail remains hidden.
I made a module myself using the code of LSMail (a much older version) as a template some time ago and I noticed strange z-order behaviour of my module window. It was sponanously jumping ontop. I tried to fix it (WS_POPUP vs. WS_CHILD usw.), but I couldn't find the bug. I know vendicator completely overhauled the LSMail module after that, and I had no problems with it until I used RC1.
Here are my settings:
LSMailNewMailCmd $UtilDir$Speak.exe You got mail!
*LSMailServer 30 6 Mail med.id.***-u.ac.jp *** *** LSMailAlwaysOnTop
LSMailErrorCmd !LabelSetText hint "[line('C:\\Litestep\\tips.txt', 31)]"
I also tried "LSMailStartHidden" set false explicitely, without success.
ruhmkorff: WFM... I just copied&pasted all your settings, added *NetLoadModule lsmail-4.3 and replaced none.bmp with a random image of my current theme. Voilà, it shows up at the right edge of the screen...
Perhaps LSImageFolder has spaces in it for ruhmkorff, and since there are no quotes it doesn't work? off the wall guess...
I wonder about none.bmp. It infers to me that there is no image.
i never had something like this before, please take a look here uni-weimar.de/~liebsch/stuff/strangething.jpg
don't know when this occured, was just suddenly there.
oh, by the way, i don't mean this ugly theme i obviously use ;) , but these repeating window resize buttons. on the left, a skinbox is covered with it, on the right, it's several lsbox shortcuts.
went away after recycle, so no biggie ... whatever...
elkmonster: i have had the same thing happen to me about twice since rc1, except mine were replaced with the scroll bar down arrow. this affected tasks.dll and shortcut2.dll, but not label, lsxcommand, ckvwm, or systray2. the problem went away on recycle for me as well.
ilmcuts: Danke fürs herumprobieren.
Its strange. Tried again with freshly downloaded LSMail. MD5-sum 7681dc900dd908c05dad44c286a81e92. After pasting RC1 and restarting LS - gone again. LSImageFolder has no spaces, simply C:\Litestep\Images. none.bmp is not empty, but a simple panel for use with labels. Converted none.bmp to none.png, same result. No background - same result. Removed negative coords for simplicity - same result.
Now some detective work: WinDowse, window informations tracker:
Process ID 000006E8
Exe filename LITESTEP.EXE
App instance 00BD0000
Parent handle 001A0056
Menu handle 00000000
Coords in parent left:0, top:0, right:400, bottom:25
Coords in screen left:0, top:0, right:400, bottom:25
Window size width:400, height:25
Client area size width:400, height:25
Extended style 00000080
ws_overlapped | ws_popup | ws_visible | ws_clipsiblings | ws_ex_toolwindow |
ws_ex_left | ws_ex_ltrreading | ws_ex_rightscrollbar
Width and parent coords are different from the settings. There is no window at that position.
Reload 0.24.7 beta.
LSMail shows up.
Process ID 00000790
Exe filename LITESTEP.EXE
App instance 00B30000
Parent handle 000A0186
Menu handle 00000000
Coords in parent left:209, top:171, right:309, bottom:196
Coords in screen left:209, top:171, right:309, bottom:196
Window size width:100, height:25
Client area size width:100, height:25
Extended style 00000080
ws_overlapped | ws_popup | ws_visible | ws_clipsiblings | ws_ex_toolwindow |
ws_ex_left | ws_ex_ltrreading | ws_ex_rightscrollbar
This metrics and position are correct.
So, in RC1 the window metrics and position gets strange.
PS: Its in the lsapi.dll. When I load RC1 with the lsapi.dll of 24.7 beta, everything works.
system tray icons vanish as if never existed, instead you see the background shining through the area, where those were supposed to be (happened when I disabled tray icon for winamp) I am on XP pro, litestep freshly installed, no changes made after that. No error messages come up. The area, where icons were supposed to be does not repond to clicking, so I assume they are not just invisible. On starting up they were there. Will try to replicate. Or is it a common bug and I just don't know? (newb)
Sounds like a bug in the systray module to me. Is it reproducable? systray2 or vtray?
it did not happen again so I am not sure for the reproducability since I changed the themes. As for the module - it is the one, which comes with the build's default theme, since I did not do any changes to it before the issue came up.
Ive been running Lightstep on Win98SE and havent had any problems with it except for 2 things.
Macromedia Flash Games (Dark Fall) the hotspots and bar all glitch
Themes, about 3 of every 4 themes i try to run glitch or dont work (missing .DLL's that I know i have)
Setup is IBM ThinkPad t21
Pent 3 800MHZ
windows xp corp sp1
Pentium 4 HT 2.6c @ 2611Mhz
Thermalright SP-94 HeatSink w/ Thermaltake A1357 Smart Case Fan
512 Mb Buffalo RAM DDR PC3700 w/ Heat Spreader
ATI AIW Radeon 9800 PRO 128
Gigabyte GA8lk1100 Motherboard
just some stats..
Running latest omar litestep i can find.
modified theme of studio 28. works fine except when i check email, 9 times out of ten litestep goes to 90% processor usage and just dies.. i have to close it out and restart it through ctrl alt del.. also noticed "ccapp.exe" from norton AV 2004 causing similar issues when checking mail, which did not happen in normal windows.
overall its just annoying as hell to have to close and restart litestep all the time because of this. it happens alot, most of the time with email but other times as well. its not the theme, and its not litestep installed incorrectly, as i have tried other themes and reinstalled litestep a couple times. i wouldnt care except the damn system tray doesnt ever come back all the way. i have never gotten an error saying litestep must close just processor heat goes from the normal 36ish to 43 and the fan kicks into high gear. the two litestep bars i have created one on top and one on the bottom of my screen are both unresponsive, both to clicks and also the data, say from winamp or system monitoring appz. windows that are visible still function correctly except my windowsfx and StyleXP skins are disabled and the top bar of the program looks like windows 200 or earlier.. just a solid color.
anyways.. any help on this in the next versions would rock. for no reason whatsoever it just goes to extreme processor usage. the memory especially is used up rather quickly.
Don't know if this is a bug or not with the version or something else, but it seems like it is. It's not actually _causing_ any problems that I'm aware of (and it's now been a few weeks) but it _is_ sort of a bee-in-the-bonnet issue.
WinXP Pro on Omar's 3.0.2 (which is 0.24.7 RC1), 143lssteps OTS2 conversion of [noir] gives me 3 shortcut's listed as running in the Ctrl+Alt+Del. I don't recall this showing up on the previous version of LiteStep (Omars 2.9.5) that I used under XP, or at worst, only showing ONE shortcut application running. So why is it showing three and should it be?
Also: On prior version under XP, I had a smaller amount of memory in use on a fresh boot to the desktop than I do now. Even disabling all startup/boot applications doesn't really seem to give me much back. I can use MemTurbo and scrub my ram to get it back to what it was before, but that usually doesn't last very long. 2.9.5 MemInUse @ Desktop: 62.5mb. Current MemInUse @ Desktop: 110mb. Same theme, same modules, same module version numbers.
Also #2: I never had XP delay so long in shutting down the computer. The delay only kicks in if I'm doing a shutdown, not a reboot. It takes close to a minute to a minute and a half to finally process to the saving my settings and then finally shutting off. Before, it would process and shut down normally, even clearing the screen before shutting off the system. Now, the screen doesn't clear UNTIL the system shuts down. When I switch back to explorer as shell, this problem goes away and it never existed under the previous version.
XP Pro Build 2600. Single User Usage (Administrator Only).
Bootup Applications (when there are any): Rage3D Tweak (v 3.9), VirtualWin (mutiple desktop's similar to XWindows edge-switching, much better than VWM imo), SaitekAutoConfigure, HotSync (palm pilot).
Duron 950, 2x128 PC133 & 1x256 PC133 @100 FSB on Abit KT7A-R (Rev 1.2)
Radeon 9200 (Single Monitor),
SB Live! 5.1,
Linksys v.4.2 10/100
*Theme Note: Though [noir] comes with LSMail, I disable and remove it from the theme as I don't use it. So far this is the only modification to the theme that I make (with the exception of commenting out the loading of grdTransparent if I'm in 98)
*Attempted Fixes: using various versions of Shortcut2 that [noir] uses still result in 3 instances of shortcut showing in Task Managers applications screen. Haven't tried shortcut3 as it would require changing all of the commands, but I'm not adverse to copying the theme to test sc3 with.
Are you sure those aren't modules/theme issues? Try to load the Litestep core without any modules; if the issues disappear the culprit is one of your modules (or several modules).
I wish i could pinpoint it because i have complete faith you could fix it.. but its not anything in particular that i can see. tonight i came out of a game, chatted a bit on IRC then switched over to an explorer window and heard the pc fan kick into high gear meaning my temp went over 40 degrees. but when i check the rainmeter settings they are all frozen at like 38 degrees or something. then i try to right click and get the popup menu.. nothing. cant switch between open windows using the taskbar. nothing. it just completely freezes. ill try to shut the modules down.. any ideas which of these might be the problem? like i said its not easy to replicate because theres no indication im doing anything the same each time.
*NetLoadModule rainmeter-0.9 load rainmeter.dll
wallz is recent and isnt the reason, as it happenned before that one. cleanuppro i believe was also recently added and it was doing it before. any of these a known problem? if it would help i can email you my whole directory to show you what im running. barely anything is dynamic i my scrips, most stuff is directly linked to paths.. like c:\Litestep instead of $litestepdir$ etc.. not sure if that matters.
ah well ill work on shutting them down one by one but its gonna take a week or so im sure.
Just add a ; in front of the *NetLoadModule line and recycle... Note that this doesn't get rid of _all_ modules, as NLM and your hotkey module will still be loaded, but maybe it's enough.
Found a bug -- Folder icons aren't updating properly.
I have StyleXP installed, using Explorer as my File manager. I can't, for the life of me, get my default folder icons and disk icons to convert. I got everything to work when I switched to the explorer shell, but everything went right back when switching back to LiteStep.
guice: That's a known bug which afaik affects all alternate shells. Apparently the custom folder loading routine is somewhere inside explorer.exe - and it's undocumented of course. :\
9x/ME users: There finally is a potential fix for the crashes. Send me an email or post back here if you want a test build. :)
ilmcuts: Possibly why AstonShell includes it's own icond manager then, eh? That sucks. :(
No idea. Are you implying that the custom icons work if you use Aston? Doesn't Aston run an explorer instance in the background?
Aston has a built in Icon manager. That means that in Aston themes, you can add icon information and Aston will manage the icons itself. StyleXP managing icons doesn't work in Aston either, however, I can manage icons through Aston itself.
If you look at it from that angle, you can add icon information to LS themes too... it's as simple as ".extract" or ".icon" etc. I certainly wouldn't call that an "Icon manager" though. Or are you talking about icons that show up if you run explorer.exe for example?
I have a bug to report. If you use a Logitech MX 500/700 series mouse and tries to use the switch-app button that exists on the mouse (works like alt+tab in windows, but it is a list instead) it will make Litestep crash. Occured 10 times of 10 tries.
I just installed 0.24.7 RC1 on my XP Pro machine, and when it starts up, the "start menu" area and such load for a second, and then stop... AIM pops up at start up, and using the windows key and "e" i can open up explorer to get to everything, but the start menu area never finishes loading...
But then, I went to task manager, and saw that a process called KHOST was using all the CPU, and so I ended that process and voila, the bar loaded up fine.
Anyone know what KHOST is and how to fix the problem??
Came across this bug tonight.
thats no good...
That's not a bug. Should be
W/o quotes, you have spaces. With spaces, you get multiple parameters.
Aye, my bad!!! Thanks Cerbie.
OS: XP no SP
LiteStep 0.24.7 Build Beta 4 (Not Sure if this qualifies as RC 1)
Problem: Most themes will not run.
They Show in EZChange but when i click on them the "Switch" button becomes "Whited" out, the theme does'nt load and Proyect1 runs in the TaskManager using 90 some % of my Processor..help...please?
Phash: the problem is the installer, not litestep, get omar's installer (and beta 4 is pre rc1).
brand new to ls, not sure if there's a crash log I can check.
XP pro, sp1
When I choose system/control panel/network connections, my LS just exits. no crash or anything, just quits.
to start again, I ctrl alt delete, task man, new task and run litestep.exe and everything comes back where it was. occurs under all themes. latest build 24.7 rc 3
dedmeetius: That certainly shouldn't happen. I'm not sure whether it's a core or a module bug though. Is LSUseSystemDDE enabled on your setup? Check C:\Litestep\personal\personal.rc. Toggle that setting and restart litestep.exe. If it still happens, try different popup2 versions (assuming you're not using menu.dll).