What is up with this? Another case of right click menus not getting skinned....

I'd suggest you and your *friend* contact Stardock support.

dude i'm serious. i'm not saying friend for and excuse... and besides i tried sending an e-mail to Stardock it wouldn't go though for some reason. no offense, but the people around here seem kinda lazy when it comes to this stuff.

yeah, right click menus, Are on the top 2 things I have to worry bout

uh... isn't this what the messege boards are for?

uh... isn't this what the message boards are for?

Which version of WB are you using?

I'm using the right version...which one are you using, Gary?

He called you 'dude' IP, you should feel honoured.

Annie, you're a piece of work ....but I think that's the only answer I'm going to get, so I'll catch ya on another thread

....dude has such a nice ring to it, don't you think....




[Message Edited]

oh shit! not sure if I should kick your ass, or be flatterd

If it gets me an ass kickin', consider it flattery

Fish ON...



[Message Edited]

someone_7, I did not think or mean to imply that you did not mean your friend is having the same problem in the least.

Are you both running the same skin?

Does this happen across all Skins?

Are you running any type of system configuration program that might happen to have a setting on the context menu which is conflicting with Windowblinds?

Do you have an application which you have used to add un-common menu items to your context menu?

Are you using something like IE Tools, IE Protect, IE you name it, which adds or remove thinngs from the context menu which could in fact be causing conflicts?

have you run a system scan for spyware, trojans, virus lately?

have you added, added and removed or removed something form the context menu?

Are you using an applicaiton which allows you to defrag links such as Executive Softwares DiskKeeper?

Another words, Things happen suddenly, but never without reason.

Did you happen to install new software?

Did you un-install old software?

Did this happen after an update to Stardock Software? If so what version where you running before the update and what did you update to?

Just emailing someone and saying "It's broke" in so many words without details will get you no where fast.

As a matter of fact, this board is for skinning and such, not Stardock Product official support. People here run the software and we are more than willing to help if we can. But don't confuse users helping users with this being the support site for Stardock products

Anyway...

back to the topic...

Have you changed anythig before this happened?

Also is it a common skin this is happening in or is it all skins this happens with?

I did have this happen about a year and a half back, it was in fact something that istalled itself into my IE without my even taking part in the installation... Made some changes to my registry to hide itself also, once I finally got it deleted for real, after trying to do just that a number of times, everything went back to normal for me.

Hey...it's Dude

CHINA!

now your playing dirty, DIRTY I say!!!

a woman how can give as good as she gets and knows what Fish On is about!!!!

damn lucky man your hubby, damn lucky

Glad you addressed that John....I wasn't goin' near it

hey i'm not looking for tech support, just seeing what you guys have to say about it and if u have any suggestions. before, there just weren't any replies at all and usually u end up getting a better answer using forums and message boards. hmm... anyway as far as the questions IP was asking; when i said no reason i guess i should have put it in quotation marks as in it didn't happen for any logical reason. i'm not sure what was going on, on my copm when it quit because it happened a long time ago. i DO remember that it happened when i was using WB 3.5. when 4.0 came out i downloaded that and it worked again but then it quit after a while. like i said i don't know what could have affected it since it happened a while ago. as far as on my friend's comp (i'll give u his first name, zach. don't know what else he'd want me to do.) i was burning a cd but i decided to cancel it. i could tell explorer probably crashed and had to restart because everything went blank except the wallpaper for a few seconds (like usual when this would happened). that's when it quit and it was still like that after i restarted the comp. i know this has something to do with it probably but i don't see why. it wouldn't do this any other time. also, this does happen with any skin.

#7 ?

ok, thats a bit more info and probably where the snafu is...

I would go ahead and un-install Windowblinds reboot and re-install it reboot and then make a back up of your registry (restore point if you do not have a good registry tool such as Registry Mechanic or what have you). Once that was done I would go ahead and load it up and see if all is well or not. I am betting that a pointer either in a ini file or somewhere in the registry got dinked. Time could be spent finding it and I am sure it could be found. But if all your wanting to do is get it back up and working 100%, do the re-install...

mmm. you might run a registry checker before un-installing out of curoisty, because it might be a common link in the registry that is hozed up and repairing it might be all it takes...


[Message Edited]

i know this has something to do with it probably but i don't see why. it wouldn't do this any other time

because the registry is opn and explorer has full and total control over it and what is stored in the hives. Meaning, the registry is just a relational database file and when the thing is open and explorer craps out there is a chance it will screw up information in odd places at odd times, but in fact, the context menu is a big part of all disk operations and doing something with the CD is a disk operation so if Explorer hozes at that time, then it would be logical that the if the context menu was screwed, Explorer screwed it, the system was rebooted aftwards at some point and then a new setting was applied to the registry (even if it was a hozed up change it was accepte as being normal)...

ah, did I twist and turn that inside out enough to make you wonder what in hell I said? cause I am now stuck trying to figure that out

its like this....

Explorer screws up a key in the registry, but only enough to screw up the skinning of the context menu. WindowBlinds sees it as being screwed up and will not touch it, but Explorer sees it as being 100% or normal enough that it isn't erroring when it hits it...

So your caught in a catch 22...

Kinda of like when your FM radio shows the Stereo light is on depicting a clear signal, but you get a bunch of static and stuff... Your tuner sees the signal as clean and clear otherwise it would try to adjust to MONO which would allow for cleaner sound, yet it thinks it see a clear connection so it forced the Stereo to be used which diminishes the signal screwing up the sound.

ok i see how explorer could have done that now. surprisingly enough i understood what you said on the first explination

ok IP tell me what you're saying on post #20. it's not really to clear.

I would run a registry checking program to see if it finds a common registry key that is corrupt and can repair it before un-installing and re-installing.

Also, when you un-install it is a good idea to run a reg cleaner and have it compress your registry if there is an option to let it do that. Removes all trash entries and speeds up system response...

SystemMechanic does a good job of it...

http://www.iolo.com

You can download the trial and do a registry scan and delete all invalid entries, it makes a back up incase something starts acting up after it completes and you reboot. It will also default to compressing your registry when you have deleted invalid enteries....

Meaning, When you reboot after cleaning it, SystemMechanic will compress the registry on the next start up, and then re-index your registry and reboot again so the changes are loaded. It will speed things up and remove the trash links and keys/entries left behind from removed temp files, programs and such...