Fix Rocketdock Stack Docklets in Windows 7
by walter on Jan.24, 2010, under Windows
Visited 15126 times, 27 so far today
There’s a glitch in RocketDock that only shows itself in Windows 7 where stack docklets lose their settings when the computer is restarted. The problem is related to Win7 security and is easily fixed. Here’s how.
This post won’t get into how to install a stack docklet in RocketDock, but will only show how to keep Windows 7 from making RocketDock forget the stack’s settings.
Open your Computer and select the C drive.
Find RocketDock within Program Files (possibly Program Files (x86)) and right click to set the Properties.
Select the Security Tab and look for a User with your name. Edit it and choose “Allow” for Full control.
That’s it. Now redo the stack docklet and it will retain its settings.
4 Comments for this entry
-
Welcome to NeutralAxis
TED talks- TED: Mike deGruy: Hooked by an octopus - Mike deGruy (2010)
- TED: Danny Hillis: Back to the future (of 1994) - Danny Hillis (1994)
- TED: Erica Frenkel: The universal anesthesia machine - Erica Frenkel (2011)
- TED: Shawn Achor: The happy secret to better work - Shawn Achor (2011)
- TED: Bill Doyle: Treating cancer with electric fields - Bill Doyle (2011)
September 14th, 2010 on 4:15 pm
Will somebody please post a real solution to this, please, or publish a stack docklet that actually friggin’ works?
This fix only reduces the frequency of stack-blanking to once every 3rd or 4th reboot, it does NOT eliminate it completely. And the only other stack docklet published online that I can find is a totally unreliable piece of junk. Grrrrrr!
September 14th, 2010 on 4:24 pm
Sorry your having trouble. Since doing this, I haven’t had any further trouble.
June 30th, 2010 on 10:39 pm
Doing this is a really bad idea. It pretty much leaves you’re computer wide open for viruses. You should never change permissions of anything in Program Files like that. Ever.
July 1st, 2010 on 12:35 am
Given that I’m only changing permission for myself and only for that one program, I didn’t consider it a security risk.