Wrong version after the update of WindowBlinds 5.50.017!!!!
Thursday, February 15, 2007 by SteveGosselin | Discussion: WindowBlinds
After the upgrade of WindowBlinds build 5.49s beta to 5.50.017 via Stardock Central, the build number is 5.1. Before the update: 5.49s beta.
I try this tip: «I would suggest changing download servers under Tools->Settings and in the Internet Section. You might also want to 'Refresh XML Data' as well.»
Same problem.
But, WindowBlinds show me via "System Information": WindowBlinds 5.1.
I'm really disappointed!!!!
Thanx in advance
-----
Stardock Support Center //Ticket ID: SCD-491477.
Reply #82 Saturday, February 17, 2007 10:09 PM
I keep getting the feeling that the more that CMD skinning is yelled about, the longer we will have to wait for its resolution.
The harder the push the higher the resistance...
Reply #83 Sunday, February 18, 2007 1:58 AM
This threat: Wrong version after the update of WindowBlinds 5.50.017.
Before in SDC...
WindowBlinds 5.50.017 = 5.10.017
WindowBlinds 5.49t
Now in SCD...
WindowBlinds 5.10.017 = 5.10.017
WindowBlinds 5.49t
If you have installed wB 5.50.017 (5.10.017), impossible to downgrade without uninstalling the wrong build. But now, the problem is gone.
YOU FEEL BETTER NOW, YOU SAID YOU LOST ALOT OF WASTED TIME WAITING FOR IT TO BE FIXED BUT YET HERE YOU STILL ARE POSTING, YOU [edited - admin]...
PS: WHAT THE HLL IS IT WITH YOUR HELLO! YOUR NOT ON THE PHONE [and again]
Reply #84 Sunday, February 18, 2007 2:15 AM
CerebroJD sets thread mode to +Patience

Reply #85 Sunday, February 18, 2007 2:32 AM
Ok. Thanks for the nice comments.
Reply #86 Sunday, February 18, 2007 2:45 AM
Don't pay any attention to him Darken, I'm sure that not-so-appropriate comment will be dealt with.
Reply #87 Sunday, February 18, 2007 3:15 AM
Okay.
Reply #89 Sunday, February 18, 2007 4:47 AM
Typing in all caps is considered rude and is not encouraged....but may be endured.
Personal attack upon your fellow site member is neither 'endured' nor endorsed...
Reply #90 Sunday, February 18, 2007 6:30 AM
When I ask...boom...everybody is right there. Helped solve a problem I had with Logon Studio and other things. I even used previous betas, at one time when I first started with Object Desktop I had 8,EIGHT, betas on my machine. Everyone worked without so much as a hiccup. I do not understand why some people are having all these problems. My machine is four years old. Everything works. Some have rigs that make mine look ancient. How come?!?
Reply #91 Sunday, February 18, 2007 5:33 PM
It's not a major issue.
It's not a major issue in terms of functionality. It IS a major issue with it comes to "completeness" of skinning. Not skinning an app is like "half-assing" something. It just shows a shortcomming. I just don't understand why it's so difficult to skin the command prompt, but not any other app known to man. Crap, Vista does it all day long. (Granted vista's GUI is differently coded, but still. Next we're going to hear that WB5.5 won't be able to do per-pixle or command prompt skinning in Vista Home Basic "Because it's not a native feature of Vista HB to begin with". What the blazes?
I wish more people would understand what my point it. It just looks ugly when I open up a command prompt to do stuff (ever hear of tracert... yes, network admins need the command prompt) and the thing looks ugly not being skinned. IT LOOKS INCOMPLETE. How about skinning it without per-pixel... I don't care, just make the window match the current skin. I don't care if the bar is transparent or not.... for now anyway.
Reply #92 Sunday, February 18, 2007 6:29 PM
Why is that you can't accept the judgment of those who do understand? Sure, it would be nice if the command prompt could be reliably skinned. It would also be nice if we could levitate but wishing it so isn't gonna make it happen. When it can be skinned without issues, I expect it will be. This horse has been dead so long there's nothin' but bones left.
Reply #93 Wednesday, February 21, 2007 10:40 AM
No need to repeat that as it doesn't solve anything.
Even a statement as mild as this is stomped on by the stardock fanboys.
I guess negative feedback is totally ignored here, except to persecute the bearer of such feedback. See:
https://forums.stardock.com/?forumid=166&aid=144365
and
https://forums.stardock.com/?forumid=166&aid=144620
Dan Dunn
Reply #94 Wednesday, February 21, 2007 10:43 AM
Unless the attacked person has something negative to say about stardock; then you can call them a liar, a thief and a fool with impunity.
see:
https://forums.stardock.com/?forumid=166&aid=144365
and
https://forums.stardock.com/?forumid=166&aid=144620
Reply #95 Wednesday, February 21, 2007 11:30 AM
Reply #96 Wednesday, February 21, 2007 11:46 AM
I'm not looking for any sympathy; I'm just pointing out the hypocrisy of Jafo (a manager at stardock I'm told)
Dan Dunn
Reply #97 Wednesday, February 21, 2007 2:52 PM
I'll wait until you start being a positive contributor before I give you too much effort.
Reply #98 Wednesday, February 21, 2007 2:56 PM
Vista's Aero skins the command prompt. WB should too.

Reply #99 Wednesday, February 21, 2007 3:21 PM
Unless you have something to actually contribute to this thread beyond trolling over your dissatisfaction with Stardock, say it and move on.
Additionally, Jafo is not a manager at Stardock, he's a community volunteer who has given his free time for years to help us in administering this site.
Reply #100 Wednesday, February 21, 2007 4:10 PM
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 #81 Saturday, February 17, 2007 10:01 PM
LMAO
Asked and answered a LONG time ago.
Most people don't use CMD. Most people dig per-pixel windows. There was a conflict. Per-pixel won.
It's not a major issue.
(But good try [again])