OK, the last part I take back, but the first still holds true. I hadn't noticed the option to Save the color changes.... it's kind of in a non-obvious place. I'd expect it to be on the color change screen.
There's a small bug with the colorizing screen in WB6. This probably goes in line with my other complaint about NEEDING to actually be able to hit APPLY on those screens before WB6 saves the settings as apposed to "auto/live saving" which is kind of stupid and there's no reason for it. Anyway, if you use coloring HSL stuff you can change the colors and then drag the color bars to pick a color, but you actually have to hit APPLY to actually color the skin with the new choice. Well, guess what,
[quote]I agree with you that I'd like to see it back too. But I wouldn't trade per-pixel for it. [/quote] Someone please give me a blantant example of what per-pixel does visually for us? I can't seem to find a definative answer to this to form a proper viewpoint on it. More specifically, tell me what you couldn't do without it that you can do now? Specifics please. Pictures would help.
[quote]Windows Vista has major limitations on skinning those windows. [/quote] Not arguing on a "technical level", but let's look at face value. Vista Aero=Skin Console.... Vista WB6=No Skin Console.
Must just be with other countries. What about cellular wireless? Do your cell phone carriers allow you unlimited data on their network with a cell card or with your smartphones tethered? I guess I take some of my stuff for granted, but I think I'd shoot myself before I had to deal with slow ass dial-up. I'd rather move then not have my broadband at least.
[quote]I though Microsoft would no longer certify programs which stored data in Program Files and that was the reason skins were moved.[/quote] It would be interesting if that is the case. I hadn't heard of that, but I kind of like that move from MS. In the end, I don't care how it's done, but I certainly don't like having my skins in a public folder like that. There has got to be a better way for you guys to do this and put them in the private folders. I have seldomly, if at all, s
OK, not to be offensive, but Dial-up?.... come on guys, it's almost 2008. I don't understand why people are surprised with corrupt packets or interrupted downloads on dial-up. Anyone remember zmodem setting for your old BBS software to alow you to "resume" a download when your line dropped. Now those were the times... :lol:
[quote]We picked that location because we needed a location that could be seen by all users and common documents is such a location. The other suitable location is the application data directory which is very well hidden on XP and Vista. If you run an app as another user (runas) it is important that the skin can be located or you would get odd results.[/quote] OK, that's basically what I thought and depicted in my post. However, leaving the skins in the Program File Windowblinds d
Can you guys please standardize on the location for the skins. I don't think the public folder location is a good place to put it at all. For one, in Vista this is a location that gets shared on a network if you set the network location preference to Private. Others can copy your skins or even corrupt/delete them accidentaly. Also, for DeskScapes you obviously are using the private user folder for storing the backgrounds/dreams. So, you obviously changed the location for one possibl
I see this issue on both an XP and Vista machine here each with the 6.00[b].099 Beta. I will let the developers know. -Mike [Stardock Support] Thanks milk man.
6.00[ b].099 is the version I have, and is the latest shown by SDC Thanks Captain Obvious. I have access to SDC as well and can update the version if I wish. The little "b" stands for Beta, so what's your point. I just wish NOT to run the Beta versions.... hell, even the non-beta versions have problems, but I just don't trust the Betas as of late.
Fuzzy, you have the same issue as me because you too are not running the newest Beta. With that said, back to my question.... when will the next "non-beta" release be out? Thanks.
This was resolved in the beta that went up last week. I no longer run the betas since I had some issues with them in 5.x. What is the date of your wbconfig.exe? Wbconfig.exe 2007/10/01 17:35:33
Do you guys know if you're going to fix this on the next update? Also, when will that update be... do you have plans to just wait until you can address some of the issues in 005 before you release the next update?
I didn't say that anything else should be requiered. I didn't say that SD shouldn't fix hte animation. All I indicated is that with OD, this behavior doesn't happen. Therefore it "wins" Deep breaths JRS, it's still early in the day. Actually, it's funny you said that because I just realized that it's probably not hard to believe that a lot if not all the SD staff testers for WB or other SD apps have these other OD apps running. It's very possi
Yes, yes, yes!!! Finally, someone else that noticed this. Yeah, I noticed this and reported it, but was shot down by people saying they didn't have this. It happens with any skin really. You just have to maximize and minimize quickly and after a few times the animations stop working either for that window or all windows. I'm on Vista Ultimate. And Zubaz, seriously dude, should people have to buy all the SD programs because one thing breaks another. Give me a break man... listen to
No offense, but that system is anything but Vista capable as HP puts it. That's funny. Anyhow, I'm willing to bet the video is shared memeory and with only 512 to work with, meh. BTW, I'd be very surprised if your "new" 160GB drive was faster then 7200 rpm. I'd be very surprised if someone saw fit to install a 10k drive in that. If they did, congrats, it's the fastest component in the system. In the end, the shared memory video may or may not be able to do Per Pixel and the Celeron + 512MB
How to skin the command prompt....run eConsole ....it will simply be skinned by the WB of your choice.... AND it IS a command prompt. This example has the window set to transparent....but it doesn't have to be....just an extra perk.... Jafo cree! :lol: Like the guy above stated, why should I have to load up another program to do something that can be done natively? Also, the eConsole transparency thing is not "true" transparency. If it was true tr
BTW, this looks the best with the Diamond Skin since the frame in that skin is basically Aero anyway.
Well, at least you were happy it got "skin-hacked".
^^^ Dunno where you got that quote from man, but if it's in any way related to this topic then "Gung Ho!!" However, this issue is not related to any AV product for your info. At least it wasn't back in the XP/WB5.x days when I first noticed this.
Well gang, I'm sure there's at least a few of you out there disappointed by StarDock's WB6 inability to skin the command prompt even now in 2007. So, with that said, there's a way to get it skinned... sort of. Here's the process. Go into WB6 and go under Settings/Advanced User Settings. Put a check in I want to use Aero window frames but keep the rest of the skin . This will allow WB6 to skin the command prompt... that's the good news, but the bad news is that the frames will
Daiwa and others ask why I'm so harsh with my questions or smartass remarks. This is why. When I ask nicely why something "still" doesn't work, I get the "no comment" lines. So I will ask again... nicely... why is this still a "by design bug" in WB6.0? When can we expect all these things to behave "normally"? Thanks.
If he can get to recovery console, he should be able to run chkdsk /r He could, but running that could also cause more corruption then there already is on the drive... especially if we're talking about bad sectors, it could spread. Really the recovery process in this case should be to pull the drive, make a copy of it, and then figure out if it's a failing drive or simply some kind of OS corruption. Then deal with that from there. Safeguarding of hi
OK, how about this? I'll go ahead and make an assumption that WB6 still has this "freeze" in it due to it's Per Pixle coding. Now, I'm willing to bet that the coding has to be kept the same for WB6 as it was in WB5.x in order for it to allow it to work in XP still. That being said, let's say that you could change this to better mimic how Aero skins windows. If you did that would it be safe to assume that you could solve this little problem for Vista users, but not for XP users, or rather the