Where did my display properties go?

Yes I do, I've trying for a couple od days to get it back. Un-installing WB doesn't even get it back. Neither does copying the .cpl from another system.

Um... I just read on a board where someone uninstalled WB and it came back... but it hasnt worked for me.
I have been working some hours on this problem now and have gotten no where other than "wipe your HD and start again"...

This really disturbs me seeing how I have just coughed up quite a bit of money for this software. >

samuelsweet.... if this problem was caused by version 4.10 then you have every right to be disturbed. If this problem was caused by any of the beta builds, well that's the price one pays for running betas, sometimes it goes south. I'm getting ready to start from sratch also due to the recent betas, and I am frustrated, but I guess I love to re-install XP, coz I continue to run beta software. What I'm trying to say is...... If betas cause a problems, don't get mad at Stardock, they didn't force you to use it. That's what the betas are for, people use them, and report any issues that pop up, so the programmers can address them. As I said, I understand the frustration when this stuff happens, but no one forced me to use it. This is actually the first time any WB betas caused such a major problem for me. They're usually very stable. 

Being a software developer... I can understand and empathise with what you are saying. However... the fact of the matter is that uninstalling any software (beta or not) should return your system back to what it was prior to installation. There is no way around the fact. The program is beta... the installation process shouldnt be. Their program has apparently changed something with my system outside of the scope of their program and it hasnt returned it once it was removed.
The post that I was refering to earlier was actually made 2 months ago. I am suprised this issue hasnt been raised yet.
Redoing my system isnt much of an option as it will take days to return it back to its working state... hell... Its a brand new box that I just finished installing all my bits on last week

Surely this must be a solution? A reg setting somewhere that was changed suring installation and not returned back?

I see your point, and I confess I hadn't thought of it that way. You are correct of course, the uninstall should have returned the system to the previous state. My system instead is now acting weird, and many of the skins I had, are trashed.. (files missing in the folders). 

Leave WB installed on your machine and re-install your graphics driver.

Well...
I installed a new card and updated the driver and that did nada.

Is it a 'nVidia' or 'ATI' card?

....and who's card is it?





[Message Edited]

nVidia... Geforce4 titanium 128meg I think... it's on my other system.

Who made the card, what site did you get the driver and which driver version did you install?

Gary, are you saying all nVIDIA cards aren't made by nVIDIA??

Hi Randy...nVidia doesn't make any cards, only chipsets. The card would be made by MSI, Gainward, Asus, etc.

Here's a list to give you an idea...http://www.newegg.com/app/manufactory.asp?catalog=48&DEPA=1
[Message Edited]

best as I can tell... Sparkle. I had this problem before this card as well. The other was a built in Intel chipset.

I used the WB 4x beta, and discovered I could not add WB's through the Skins section or load them using Display Properties. I switched back to 3.51 and everything worked again in Display Properties.
But it did take a cold boot to do it.

Interesting though, I somehow have retained the newer Windowblinds configuration panel.

Hi... this is still a no go. Can someone from support please assist me (it's kind of wearing me thin)

Thnaks

Amen to that. I tried rebooting, uninstalling and reInstalling 4 and 3.5, mixing the two and even removal of windowblinds Dir. and still nothing. Neil, someone please Help......

If you want support why don't you contact Stardock support instead of posting here? This is a messageboard only.

Questions asked here may be answered by other users willing to help but it's the wrong place for official support so you are unlikely to get an official response

*sigh*....this is not a WB bug. When your Display Properties do not come up it means you're missing a .cpl file in your System32 folder. Re-install your graphics drivers! If that doesn't restore it then do a repair on your XP system.......

Eh? This IS a bug. The fact is... it was there... it isnt now... that means WB did something.
BTW: I do have a backup on my system of the .cpl files. The one in question (desk.cpl) is there. BOTH the backup AND the live one will not work.

It has piddly to do with the graphics driver as I have installed a completely new card since and it STILL wont work.

My guess is that WB Adds tabs to the cpl applet via reg calls. If that conks out whislt trying to load then whammo... the box crashes out.
Even after uninstalling... I run Regmon to view all the WB reg calls (there are a poop load). Most are to a WB.5 key... Then the last we see of it are calls to winlogon process.... then thats all she wrote.

You appear to have all the answers so my guess is you'll have this fixed in no time.

um. gee. thanks... more answers than some I guess. Can anyone else help?

Insert boot disk. At the A: prompt type 'format C:' - problem solved...

*sigh* your insights into this problem just get better and better. Ever think of starting a consultancy?

On a side note... I think this software sucks rectums in a serious way. I submitted a 'support' ticket two days ago. I am told I have 2-3 working days before I hear anything. That means that the soonest I will hear anything is Monday which translates to damn near a week since their program screwed my computer. What a waste of $50... piece of sh*t.
>

I think yrag gave you the answer...Pop in your XP CD and do a repair...Problem should be solved in a couple minutes