It's better to let someone think you are an Idiot than to open your mouth and prove it. What was that?... maybe you're just too young to remember them. They no longer make a lot of electronics, but here's a link to a DVD player... WWW Link Maybe I should have just said Mr. Mynameisamakeroffishinggear to keep the young people from proving they are too young. <img
Mr. Glasshalfempty strikes again. Hey Mr. Mynameisamakerofoldschoolstereos, I got something for you... :middlefinger:
Go to Override Default Settings in WindowBlinds and look in the middle of the page. Change the taskbar size away from "Skin Decides Taskbar Size" to something else. This should allow you to change the size of the taskbar. I agree with you that WB should leave the taskbar the size you set it as for freak sake. Why can't it just skin the thing the same way that XP Themes do and let it keep whatever size you set it to? Yet another one of those "stupid" things.
We may add the option to delete a wallpaper from the wallpapers page, but we will not be automatically deleting the wallpapers when you delete a skin as I do not believe this is something most people would want. How about an option (like a check in settings) that allows for auto delete of the wallpaper when you delete the skin? That way people that want it like this don't have to do extra work and people that don't want it to do this can just uncheck th
There's an issue with WB5.5 and wallpapers that are included in skins. Apperently when you install a windowblind theme in WB5.5 any wallpapers that are included with the skin are extracted or cached to the wallpaper directory under Windowblinds. Well, the issue is that when you delete the skin it doesn't delete the wallpaper associated with it. This may not be a big deal with some people, but I think it's a shorcoming of the system. This goes right in line with my initial questions as to why
Just to confirm this... I uninstalled .23 and went back to .21 and it's fine. No more errors. Updated again to .23 and the memory range error on shutdown happens again. Went back to .21 and it's fine. Something wacky is going on with this new version...
Are your video card drivers up to date? Get the latest off NVidia's website.
^^ I don't like that one. The fake buttons on the start menu are a no no for me. Also, the ugly turn off and log off buttons superimposed on the search field look nasty. It's just unclean. I like Ironjer's the best because I think he got the overall feel of Vista without implementing any of the visual aspects of vista which deal with functionality. (i.e. he doesn't have anything in the skin that looks like Vista, but doesn't work.) That's why I think Ironjer's is really the best. I haven'
Guess what? I updated to .023 just for shits and grins and now on shutdown I get an SVCHOST error for unable to read some memory range. Gota love that... How hard is it to make a stable build of WB Stardock!?!?!?!?!
This one is much better. Made by Ironjer. WWW Link
Wow, look at that. Someone else besides me that wants the feature back. Hummm, what do you know...?
Good thing I've made it a habit to check this site before "blindly" trusting the upgrade versions on SDC. I think the ol' Windowblinds 5.5 (not really 5.5) of a month ago helped in the development of that habit...
Too bad the trial version is not yet available of 5.5.
So is Stardock going to fix this?
Just for giggles, put a check under Don't user Per Pixel on any Skin and see if that fixes your issues.
Repost the info page with the new drivers. I've ran into this before myself, but it was on a older P3 PC with a junky Intel video chipset. It eventually went away, but I think it went away because WB got updated a while back... I don't think I've had that problem since I went to WB5.1 on that PC. Have you tried it with a different skin or reinstalling WB?
I'm running the Current Omega Drivers on an X1600 512mb and I haven't had any problems. In fact they seem to have cleared up an issue where my screen gets red scanlines, computer freezes and system reboots all by itself which I'm convinced is related to the graphics card. Your video card is different so that's already one too many variables. (i.e. You're not comparing apples to oranges.)
Your WB files look right. Problem could be related to your Omega drivers. SD will not guarantee successful function of WB without WHQL drivers. My suggestion... try the ATI ones and see where you are. If the problem goes away you have your answer, if not, you have ammo against claims that it could be Omega driver related.
Your computer has a Windows Experience Index base score of 1 You sure you REALLY want to run Vista?
Thats the problem, I have contacted them, been waiting here for 2 days now. And people on here wonder why I post bugs/issues on here instead of sending them email. You should have come here first dude. Uninstall WindowBlinds and reinstall it via SDC. All will be fine. Read through this entire thread and it'll make sense.
Some of the things you've mentioned seem to be caused by the fact that the skins you're using weren't designed "For Vista". They were designed for XP and since Vista is very different in layout some things won't be perfect. Only way to change this is to wait on the new skins built for Vista specifically. I have a feeling that once WB5.5 is final (holding my breath for next week) more devs will probably go back and update their "popular" skins to work with Vista as well.
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. 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 doe
Ok, if you say so. RC and BETA versions so far have been 5.49(x)b. The version available for download was clearly 5.5.x.x. Even so, the file the server was handing out wasn't even a mislabled 5.49 (RC or BETA)... it was the 5.1 download. Whatever, I'm not going to keep arguing about it... BTW, is command prompt skinning in XP a "major issue" as you put it?
The forums really shouldn't be the place for rants like this. Emails to support and private emails to stardock are the place for this type of thing. The forums are for community support and friendship. It's worth the investment. While I agree wholeheartedly with this one other thing is also true. If people complain directly to a company in "private" correspondence about a problem it will more then likely stay that way... quiet and unresolved.
Well it's a beta version. If you can't handle the heat, don't use beta versions. And stop whining, wait for the release version. IT's CALLED A BETA FOR A REASON!!!!!!! DONT LIKE HAVING PROBLEMS USE THE OLD VERSION THATS WHY SDC KEEPS IT THERE.... You guys or gals have reading comprehension skill problems. I complained about SD not testing stuff before release because the VERSION NUMBER WAS