Start Button Hangs
Wednesday, December 14, 2005 by Patrick Garrison | Discussion: WindowBlinds
Got a weird one with Windowblinds 5 beta 6 - SDC (Stardock central isn't showing me the final version with my Object Desktop subscription, at least not yet - or do I have to purchase something else?)
Anyway = as soon as I switch to any screen other than Windows Classic the start button doesn't work! Nor does the windows key on the keyboard bring it up, nor the shortcut combo of ctrl-escape! Sometimes I'll see a pale outline of it but no information - other times if I turn off wallpaper it will come up for a time or two then not work - looks like the image is getting lost in some layers of desktop stuff before it can make it to the top of the screen. Not sure if it's a setting issue or just an incompatible skin - maybe I'll install a couple more and see if the results are consistent - meanwhile any suggestions appreciated!
Thanks!
Anyway = as soon as I switch to any screen other than Windows Classic the start button doesn't work! Nor does the windows key on the keyboard bring it up, nor the shortcut combo of ctrl-escape! Sometimes I'll see a pale outline of it but no information - other times if I turn off wallpaper it will come up for a time or two then not work - looks like the image is getting lost in some layers of desktop stuff before it can make it to the top of the screen. Not sure if it's a setting issue or just an incompatible skin - maybe I'll install a couple more and see if the results are consistent - meanwhile any suggestions appreciated!
Thanks!
butrkup
Reply #2 Sunday, December 18, 2005 5:04 AM
Reply #2 Sunday, December 18, 2005 5:04 AM
Same problem with start button hanging; I have uninstalled WB5 & am sticking with 4. I have a NVidia GeForce FX Go 5200 32MB video card on my toshiba portege m200 tablet, 768 mb ram, xp sp2, 1.5 ghz centrino.
Riscon
Reply #4 Sunday, December 18, 2005 9:27 AM
Reply #4 Sunday, December 18, 2005 9:27 AM
Well I get a pretty consitent 2% of CPU usage with WindowsBlinds, is this normal? Happens with any skin and i notice its csrsse.exe which is the one taking the time. I was on the understanding that it would not use resources from CPU? Happens even with the default skin and this is a clean install.
This doubles naturally with Cool and Quiet enabled, since cpu speed is cut in half.
This doubles naturally with Cool and Quiet enabled, since cpu speed is cut in half.
Neil Banfield
Reply #5 Sunday, December 18, 2005 10:01 AM
Reply #5 Sunday, December 18, 2005 10:01 AM
Taskmanager itself uses cpu when it updates its cpu usage indicator. Which might be where 2% cpu is going. (plus the taskbar repainting for the cpu meter icon)
butrkup
Reply #6 Monday, December 19, 2005 6:00 AM
Reply #6 Monday, December 19, 2005 6:00 AM
The problem is on startup for me, when SDMCP loads, until I end the process it makes my start button/sys tray hang (the cursor over them is an hourglass). When I end it, the problem goes away.
However, WB 5 doesn't work at all on my system--the desktop wallpaper appears, but all my toolbars/taskbar reverts to Win Classic as someone else has mentioned.
However, WB 5 doesn't work at all on my system--the desktop wallpaper appears, but all my toolbars/taskbar reverts to Win Classic as someone else has mentioned.
legokid201
Reply #7 Monday, December 19, 2005 9:00 AM
Reply #7 Monday, December 19, 2005 9:00 AM
none of the navigational bars work on mine and it is a legit copy but i deleted my email because of certain reasons and i dont have an email right now
Patrick Garrison
Reply #9 Monday, December 19, 2005 11:26 PM
Reply #9 Monday, December 19, 2005 11:26 PM
Happens with all skins OTHER than the Windows classic, yes.
butrkup
Reply #10 Tuesday, December 20, 2005 12:28 AM
Reply #10 Tuesday, December 20, 2005 12:28 AM
So, any idea what the problem is here? I'm pretty disappointed, having paid $80 for the OD ensemble and not being able to use one of the main attractions (WB).
Fedorov999
Reply #11 Tuesday, December 20, 2005 4:40 AM
Reply #11 Tuesday, December 20, 2005 4:40 AM
My Start button/taskbar has also recently started *hanging* when I first power up my machine and log on, takes almost 2 minutes before clicking the start button works, it's an hourglass when you move over the taskbar...
Would really like to know what this is as it's my only issue and it's so annoying not being able to get access to the start menu for 2 minutes.
Thanks, Fedorov.
Would really like to know what this is as it's my only issue and it's so annoying not being able to get access to the start menu for 2 minutes.
Thanks, Fedorov.
Neil Banfield
Reply #12 Tuesday, December 20, 2005 4:42 AM
Reply #12 Tuesday, December 20, 2005 4:42 AM
Usually that means explorer is too busy processing something else
Fedorov999
Reply #13 Tuesday, December 20, 2005 10:39 AM
Reply #13 Tuesday, December 20, 2005 10:39 AM
Similar to a posting above, If I ctrl-alt-del and end the SDMCP process I get my taskbar back immediately. What is SDMCP needed for? Things are running without it okay I think....
Thanks.
Thanks.
Patrick Garrison
Reply #14 Tuesday, December 20, 2005 8:26 PM
Reply #14 Tuesday, December 20, 2005 8:26 PM
>Similar to a posting above, If I ctrl-alt-del and end the SDMCP
>process I get my taskbar back immediately. What is SDMCP needed >for?
SDMCP is the Stardock process that drives WindowBlinds and who knows what all else - once you kill it, the system goes back to the pre-Stardock state, so, the taskbar will work as it should, since the Stardock "filter" is now off.
>process I get my taskbar back immediately. What is SDMCP needed >for?
SDMCP is the Stardock process that drives WindowBlinds and who knows what all else - once you kill it, the system goes back to the pre-Stardock state, so, the taskbar will work as it should, since the Stardock "filter" is now off.
Neil Banfield
Reply #15 Tuesday, December 20, 2005 8:33 PM
Reply #15 Tuesday, December 20, 2005 8:33 PM
SDMCP does nothing for WindowBlinds.
That process provides tray services to ObjectBar, DesktopX & ObjectDock as well as auto start functionality for those processes.
Fedorov999
Reply #16 Wednesday, December 21, 2005 5:15 AM
Reply #16 Wednesday, December 21, 2005 5:15 AM
Neil, I offer my apologies as I appear to have fixed my issue although it's such a weird one!
I have hotkeys assigned to most programs/shortcuts on my system for quick launching anything I need - recently a very annoying problem began where there would be a 1/2 second delay from pressing any hotkey to seeing the eggtimer and my program being launched. By pure chance last night I'd been running Tune-Up utilities and one thing it hightlighted to me was my no-ip.com client which runs in the background was using 27mb or RAM!
Further investigation reveals that my OutPost firewall rules were blocking this program from getting out to the no-ip.com servers but also a bug was causing their program to increase memory usage and looks like was causing my hotkey slowdown!
I updated the no-ip.com client to the very latest, sorted the firewall rule and my hotkey speed is back to being instantaneous!!!
The other good news is that the taskbar now does not freeze for 2 minutes upon starting my machine with WB5
So I'm hoping it was all just related to that and hopefully all is running fine again (fingers crossed).
SDMCP was obviously causing some issues with the above problem because EVERYtime I ended that process I got my taskbar working again immediately.
Neil, if SDMCP has nothing to do with WB5 running then is there a simple way to stop it even being loaded upon startup please - I see no point in having any extra baggage running on my lean machine...
Also, maybe others with this frozen taskbar issue have some OTHER Windows processes that are having issues upon startup like my no-ip.com client had, causing extra cpu cycles or something....
Fedorov.
I have hotkeys assigned to most programs/shortcuts on my system for quick launching anything I need - recently a very annoying problem began where there would be a 1/2 second delay from pressing any hotkey to seeing the eggtimer and my program being launched. By pure chance last night I'd been running Tune-Up utilities and one thing it hightlighted to me was my no-ip.com client which runs in the background was using 27mb or RAM!
Further investigation reveals that my OutPost firewall rules were blocking this program from getting out to the no-ip.com servers but also a bug was causing their program to increase memory usage and looks like was causing my hotkey slowdown!
I updated the no-ip.com client to the very latest, sorted the firewall rule and my hotkey speed is back to being instantaneous!!!
The other good news is that the taskbar now does not freeze for 2 minutes upon starting my machine with WB5
So I'm hoping it was all just related to that and hopefully all is running fine again (fingers crossed).
SDMCP was obviously causing some issues with the above problem because EVERYtime I ended that process I got my taskbar working again immediately.
Neil, if SDMCP has nothing to do with WB5 running then is there a simple way to stop it even being loaded upon startup please - I see no point in having any extra baggage running on my lean machine...
Also, maybe others with this frozen taskbar issue have some OTHER Windows processes that are having issues upon startup like my no-ip.com client had, causing extra cpu cycles or something....
Fedorov.
Please login to comment and/or vote for this skin.
Welcome Guest! Please take the time to register with us.
There are many great features available to you once you register, including:
- Richer content, access to many features that are disabled for guests like commenting on the forums and downloading skins.
- Access to a great community, with a massive database of many, many areas of interest.
- Access to contests & subscription offers like exclusive emails.
- It's simple, and FREE!
Reply #1 Thursday, December 15, 2005 8:28 AM
Another item - the RIGHT-click option on the start button works fine on all skins - to get explorer, open menu, etc. It's only the primary functions when you click with the left mouse button that the menu display is woefully inconsistent.