Which version of Windowblinds are you using and which skin are you applying when running into this issue? If all of your windows are minimized (Windows+M), will the taskbar then roll out when you mouse over it? -Mike [Stardock Support]
You should try updating your video drivers. I've not heard of this specific issue before with Objectdock, but outdated drivers could cause video artifacts such as those. Also make sure there are no active objects on your desktop: -Right click anywhere on your desktop, select Properties -Click the Desktop tab -Click the "Customize Desktop..." button -Click the "Web" tab -Make sure that all checkboxes are desele
What do you mean when you say, "point the cursor in an unoccupied spot of the taskbar"? I've tried reproducing your problem and it looks like the "Keep taskbar on top of other windows" option does alleviate it. Do you notice any change in the taskbar's behavior when toggling this option? Edit: Also, does this issue not arise when unloading Windowblinds? -Mike [Stardock Support]
You get that error message because Windows does not allow changing of the icons in a "classic" start menu, Icon Packager just warns you of this beforehand. You should instead use the Windows XP start menu: -Right click on the taskbar, and select properties. -Click on the "Start Menu" tab -Make sure that the "Start Menu" option is selected and not "Classic Start Menu" As for the icons not showing up issue when using Icon
If you're still experiencing a problem even after turning off all script blocking, know that the development team has just announced that an update should be available soon. -Mike [Stardock Support]
Natural Desktop was written to use Microsoft scripts. Because many antivirus programs prevent scripts from running, this is an obvious problem. You should make sure all script blocking is turned off, as this is the sole cause for Natural Desktop not doing anything (though it's running) on startup. The development team is currently trying to find a workaround for this issue. -Mike [Stardock Support]
gherardo, You hadn't posted your version, and my response was directed at the general audience (the only posted version was 1.01). The development team is aware that other than the left and right mouse buttons and the scroll wheel, no other mouse functions will work on the secondary pc. This includes the wheel button and any buttons other than the primary two. Which versions of windows are you using (including service packs)?<br/
You should try redownloading the program. Windows will give this message when a file is corrupt. -Mike [Stardock Support]
Points go to MountainDragon for this one. (This assumes you own WindowFX) Under WindowFX Properties, go to the Maximize to specific size option. Here you can accomplish everything you were asking for: Under "Limit the size of Maximized windows", the width will be the same as your current resolution's width, but the height = your
I'm still not experiencing the issue over here. I've installed iTunes v5.01, ObjectDock 1.20a.015. There a shortcut I placed in my ObjectDock tray to iTunes, and after launching the program I have not experienced this issue. I've attempted overlapping the window, activating a window that was behind iTunes to completely hide iTunes and then both moving it and minimizing it to reveal iTunes. Finally, I tried minimizing iTunes and then maximizing it again. It sounds like your
The wheel should be working on the secondary pc. You should try updating to the latest version of Multiplicity (1.02.005). This will (hopefully) resolve your issue. -Mike [Stardock Support]
Currently, the only fix for the "icon being covered problem", is to do what Corky_O said. To prevent icons from being manifested at the top left, you could create a "dummy" file. Since the icon will be covered up anyway, it won't matter. I personally never use "auto arrange", but do prefer to keep "align to grid" selected. Having the dimensions of the client area be modified so that maximized windows (and icons) will recognize the
Stardock Forums
Yes, Stardock Central is notified (and then you are) immediately when a new release is available (or even a pre-release if you select that option). It's a very handy tool for getting the job done. It also includes a web-browser, irc client, and much more, all free! -Mike
This delay after your bootskin unloads and the logon skin loads sounds normal as it might be loading resources at this time. If for some reason your logon doesn't display, you can hit ctrl+alt+delete twice to display the standard windows login dialog. You could try applying a different skin and see if that yields success. You could also check out this link: Link and read the tex
I've loaded both up and am not experiencing any problems. Could you elaborate on your situation? Which program do you load first? Do you have to do anything to make this happen? Which version of Object Dock and Windows (including service packs) are you running? -Mike [Stardock Support]
Steve: I haven't come across a resolution for this issue, though it would make sense for what you're requesting to be a part of the program! Let me look into this. -Mike [Stardock Support]
Fairyy~: You should try updating to service pack 2. This patch contains a lot of fixes. (and has cured a lot of headaches!) -Mike [Stardock Support]
Bushman50: What version of DesktopX are you running and how might one reproduce the problem? -Mike [Stardock Support]
Maggot: What version of DesktopX are you running? Are you able to unload WB and get desktopX to work? I take it that since you haven't made any more posts that your problem is hopefully resolved. If you're still encountering the problem, there is another version out now you might try upgrading to. -Mike [Stardock Support]
Yep, this issue can be easily reproduced. I talked to the development team earlier and was told it would hopefully be resolved with the release of Windowblinds 5. -Mike [Stardock Support]
If Black Xero's advice doesn't work. Please email [email protected] with a screenshot of your problem. -Mike [Stardock Support]
Open a command window (Start->Run, type "cmd", press enter) Type "set" You will get a list of all the environment variables. -Mike [Stardock Support]
I've forwarded this issue to the development team. Hopefully we can get this resolved! -Mike [Stardock Support]
I think that's a great idea...there are plenty of styles of widgets for usage monitoring, but none for temperature monitoring (that I see). -Mike
You will actually need to create another widget that will act as the close button. Under "Object Type," select widget and choose "Widget Close" under the drop down menu below that. -Mike [Stardock Support]
WinCustomize Forums