What is up with this? Another case of right click menus not getting skinned....
Friday, November 14, 2003 by someone_7 | Discussion: WinCustomize Talk
Ok well it happened on my computer as I said before and then I was at a friend's and it happened on his comp too. The stupid right click menus on WindowBlinds just suddenly quit skinning. HOW CAN THIS BE FIXED??? I've asked many times and I haven't gotten a reply.
 |
|
Page 2 of 2 | |
|
|---|
someone_7
Reply #22 Saturday, November 15, 2003 10:34 AM
Reply #22 Saturday, November 15, 2003 10:34 AM
ok i see how explorer could have done that now. surprisingly enough i understood what you said on the first explination 
someone_7
Reply #24 Saturday, November 15, 2003 11:11 AM
Reply #24 Saturday, November 15, 2003 11:11 AM
ok IP tell me what you're saying on post #20. it's not really to clear.
IPlural
Reply #25 Saturday, November 15, 2003 12:15 PM
Reply #25 Saturday, November 15, 2003 12:15 PM
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...
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...
Neil Banfield
Reply #26 Saturday, November 15, 2003 3:40 PM
Reply #26 Saturday, November 15, 2003 3:40 PM
Actually the problem is much simpler than that.
The shareware version of WB stops skinning menus after 30 days. The idea is you register the software if you like it and using both 3.5 and 4.0 for more than 30 days would suggest you do like it!
IPlural
Reply #27 Saturday, November 15, 2003 3:58 PM Very true, I guess I should not have assumed that he is working with a purchased package...
Thought never crossed my mind that he is speaking of the shareware version, mainly because it freaking explains what happens after the trial period
[Message Edited]
[Message Edited]
Reply #27 Saturday, November 15, 2003 3:58 PM
Very true, I guess I should not have assumed that he is working with a purchased package...Thought never crossed my mind that he is speaking of the shareware version, mainly because it freaking explains what happens after the trial period
[Message Edited]
[Message Edited]
Please login to comment and/or vote for this skin.
Welcome Guest! Please take the time to register with us.
There are many great features available to you once you register, including:
- Richer content, access to many features that are disabled for guests like commenting on the forums and downloading skins.
- Access to a great community, with a massive database of many, many areas of interest.
- Access to contests & subscription offers like exclusive emails.
- It's simple, and FREE!
|
|
Page 2 of 2 | |
|
|---|
Reply #21 Saturday, November 15, 2003 3:39 AM
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.