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...?
WinCustomize Forums
JRSCCivic98: There was a bug in the code that was to move the files over, it would fail in some cases. We're working hard to resolve it. I'm glad to hear that. BTW, one last thing. I don't like how your program "extracts and cache's" the animated desktop files to the new "%HOMEPATH%\Documents\Stardock\*" location. I don't have a problem with it caching stuff as it needs it because it obviously needs some working room, but I do have a problem with it
WinCustomize Forums
Some help to those who's existing Dreams weren't automatically moved over for them! Try the following: Open up the run dialog, enter in the following and press enter: "%ALLUSERSPROFILE%\Stardock\DeskScapes\Dreams" This will take you to the old place Dreams were stored. (That above path is equivalent to your "C:\ProgramData\Stardock\DeskScapes\Dreams" where "C:\" is the drive Vista is installed onto) Do the same with the following: "%HOMEPATH%
WinCustomize Forums
\programdata\stardock\Deskscapes Yeah, because that's a much better place then the following. transfer them to user name\docs\stardock\dreams Who comes up with these decisions anyway? I haven't checked to see if this is correct, but why would they put in under personal files? They should have programmed it in such a way that it keeps the dream files in the same freaking place that MS's side of things
WinCustomize Forums
There's an issue with the install of 1.01. Yeah, I know, what else is new right? Anyway, the install seems to delete your preexisting dreams that you have installed... even ones you downloaded after installing 1.00. Kinda stupid if you ask me... still can't belive that the testers mis the little stuff like this.
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.
This should be more along the lines of "Consumers had no choice when buying a new PC at a retail store." If you still want XP you have to buy online now and specify that you still want XP. Pretty soon that'll probably go away as well.
So is Stardock going to fix this?
And this is new how? Big deal. They will just state that whoever is responsible for updating the sites "unintentionally" made a mistake and get out of it. Have you ever read any of the "details" of hardware items for PCs on the public Bestbuy.com site? Some of the info on there is BLATANTLY incorrect. Transfer rates of hard drives is not correct, etc. They will blame it on human error. Error on the part of someone is unintentional and unless someone is going to dig up any corporate corres
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.
If you think that's bad check this problem out that I had. So I installed Synaptics's touchpad drivers for Vista on my test setup of Vista Ultimate. (Keep in mind that these drivers/touchpad app was written for Vista.) Well, on EVERY startup of Windows I get a prompt to allow syntpenh.exe to run. It's part of the driver that runs at startup in a registry entry under run. Anyway, I though it was a little anoying (It wasn't a UAC prompt, but rather one of those "This application comes from an
I just checked it for you, it does not prompt me. Right clicked on the desktop, and went right in. No UAC bugging me. I double checked, yes I have UAC activated. Go in and change the resolution. Or better yet, click on advanced in that screen and go to where you can create a system restore point. You will get a prompt.
Microsoft had a perfectly good model upon which to base UAC, had they been able to get over their "not invented here" mentality--the way that Linux does it. When you install most Linux distros, you have to set up a ROOT password, in addition to the password for each user account. Users don't run as ROOT; they run as USERS. When something needs to be done that requires ROOT access, you get a pop-up that prompts you for the ROOT password. This does not lock up the rest o
Your computer has a Windows Experience Index base score of 1 You sure you REALLY want to run Vista?
Something to add... it's 2/22/07 (A week+ further then when SD was going to release WB5.5). Maybe they can finish that project first before they try fixing someone else's software. How about that idea?... does that work for you? Also, the whole "a regular user needs admin access to do things" is the real problem here. The problem stems from the fact that Windows natively is misdesigned. The failure in the design is around the fact that it has a registry and shared locations for syst
I have a better idea. How about MS treat software installs or program running without UAC much like web browsers tread secure sites with SSL. The PC has a list of Root Certificates that it knows are "proven good". Others will cause a prompt that it's not a "certified certificate". The UAC can act the same way. Software vendors have to deal with MS anyway when it comes to compatability dev tools for each OS... well, those same companies can turn arround and hand MS a checksum of the software
Stardock Forums