Are you getting any error messages, and if so, when?

What does WindowBlinds do when you try to run it?

Might matter (?) - which version of Vista are you using?

Is there more than one logon for the machine - does it run under whatever Vista's equivalent of XP's "Administrator Rights" (where you would want to be when you install it) but not under a more limited user?

I'm completely unfamiliar with Vista. What you're describing though sounds an awful lot like what might happen when trying to use XP with limited user accounts before manually modifying the security settings for the Stardock programs.

I'm sure it'll be helpful if you provide more details on what is happening to you, particularly with the WindowBlinds because it has such a wider user base. At this point I'll just have to ask for someone else who has a better clue than me of Vista to chime in here.

Sounds like you know how to get around on your machine pretty well.

Your Visa IS 32bit, right? The WB6 beta is not to be loaded on 64bit Vista, per the WindowBlinds 6 Beta Feedback sticky thread in this forum, just in case you didn't catch that. I don't know what it might act like on 64bit. If it is 64bit Vista I'd uninstall the WB6beta and install the WB5 version. Don't know if any of this stuff will actually run right under 64-bit for that matter, if it is Vista 64bit I'd be looking around for that answer.

Here's a somewhat dated thread on Vista compatibility, you might have a look at it and any others to see if it aligns with what you're experiencing:

https://forums.wincustomize.com/?forumid=19&aid=153286

If it's 32bit, since you can at least run Windowblinds you should cut and paste the system info Windowblinds reports into this thread ("this thread" being the one we're having now, not the one referenced above). Go into WindowBlinds Configuration, System info tab, copy and paste. It won't help me at all, but if someone who actually knows what they're doing gets involved with this they'll likely want to see it and it might promote response and save you some time. I don't think you'll see anything in there that would make you hesitate to post it.

The Stardock programs are a compilation of individual little programs as opposed to one big program with several completely integrated little components, so issues between them is not necessarily consistant and you might have a lot better luck focusing on one at a time. (I do find the user permissions issue to be somewhat common though). Again I'd start with the WindowBlinds.

Since you can actually load the WB, it sounds like the actual executable file wbconfig.exe has at least limited-user read enabled, which is more than I get upon initial installation or update. The inability to load skins makes me wonder about the skins directory and the files within them. Not sure where that is on Vista, on XP for WB6 it's in the C:\Docs&Setting\AllUsers\Docs\Stardock\WB (abbreviated). Wherever it puts them is where it requires them to be, in case you got the urge to move them, or got the urge to tighten permissions on the directory.

After that, can you even switch between the skins that come with WB6 - at least Molten and Diamond? (I'm sure there are others but I've lost track.) Ruling out that the problem is in the download/addition of skins, though that's not a problem for me.

I'd still wonder about the user permissions. The problem I experience is that upon installation/update the individual files may not inherent the limited-user-read-enabled permissions I've established in the appropriate folder, so if you've looked at the folder permissions but not verified (at least sampled) the individual files you may have been misled. However, this tends to happen on the program files and not the skins, and you wouldn't think (?) it would be a problem in a shared directory. I'd look at a few files in both places though.

One other thing that comes to mind is that the Stardock Central needs to be at it's current version before you install the WB6beta, was it? Stardock Central should prompt you to update when you first go into it if there's one available, there is a checkbox in Stardock Central's Tools/Settings that I'd check to be sure that was enabled. I wouldn't think that would affect all of your non-WB issues though.

If you've fallen asleep reading this, at least verify that your Vista is 32-bit, have a look at the compatibilty thread I referenced above, and post your WB System info screen.

I'm rapidly running out of rope with which to hang myself, other than the old standard "try unintalling WB, rebooting, and re-installing WB". Again, I'm still hoping someone familiar with Vista or at least more adept with the Stardock software will jump in here. Anytime.

Hi DaveRI,

Yes, running the 32-bit version of Vista. Here’s the system info from WB6B:

Your computer has a Windows Experience Index base score of 5.5
Your Windows Graphics Experience score is 5.9
WindowBlinds version : WindowBlinds 6 (6.0 (beta build 43 x86 - Vista Edition))
WindowBlinds is installed correctly on this PC
WindowBlinds appears to be activated on this PC
(SyncMaster 206BW,SyncMaster Magic CX206BW(Digital)) 1 is attached to NVIDIA GeForce 7950 GT
Wblind.dll 2007/09/17 15:40:20
Wbsrv.dll 2007/09/18 15:20:27
Wbconfig.exe 2007/09/18 15:20:55
Wbload.exe 2007/09/17 14:34:51
Wbhelp.dll 2007/08/27 11:54:07
Tray.dll 2007/09/12 17:58:21
Wbload.dll 2007/09/12 17:58:28

Yes, I do know my way around these machines & their OS’s pretty well, I’ve been doing it for over 25 years. “Under the hood” never intimidated me. I’m aware of the Stardock suite of programs be individual programs which may well have common elements, but are not just one large program with many smaller functions. Taking that, & the fact that both WB & Theme Manager questioned me upon installation as to my desired use, whether just me or everyone on this computer, I answered everyone, & the installer placed/created files in a Public folder (C:\Users\Public\Public Documents\Stardock\... & then Theme Manager or Window Blinds), I checked for security rights on those folders & any basic files. I found the folders rights were fine, the files under WB to be extensive & didn’t check them, however the theme files under TM were protected except to the Administrator. I changed those. I then opened TM & tried applying a skin via WB from there, it crashed TM. Now in WB (not from within TM) after you select a skin, no matter which way you choose to apply the skin, buttons don’t “depress” or anything to indicate the action is being attempted & the curser does not show as busy.

The executable file wbconfig.exe has full rights for my desktop enabled & my desktop has ownership. As I mentioned above, WB created the folder where it keeps skins & moved any from the original location, C:\Program Files\Stardock… etc., to where it currently keeps them. The skins displayed within WB allow me to look at them within the preview, I just cannot apply them. This is true for those stock ones like Molten as well as any I may download.

Stardock Central is set to check for updates each time it’s started & to automatically download any.

I both understand & relate to the rope analogy. I will only begin one of these threads after my rope is gone, & I know one or two things about fixin’ installations. I do appreciate the help you’ve offered.

Thanks,
Arnold

Hello Zubaz,

Above you’ll find some of your requests answered, & yes SDC/Object Desktop are properly activated as per the Registration Info dialog. Each individual app under OD has been checked &, if available, updated.

Taskman shows these programs as running, unless I’ve noted otherwise: Stardock Central, Windows Blinds, Windows FX (if run & then unloaded, crashes Explorer), Tweak Vista, Tweak Shell, Tab Launch Pad, Theme Manager, Virtual Desktops, Bitmaps (doesn’t run), Sound Packager Beta, Skin Studio, Right Click (doesn’t run), Object Media (crashes upon opening), Object Bar (doesn’t run), Object Sweeper, Object Edit, Object Desktop Launchpad (crashes upon opening), Logon Studio Vista (works well), Object Dock (works well), Keyboard Launchpad, Icon X (doesn’t run), Icon Packager, Icon Developer, Enhanced File Dialog, Desktop X (doesn’t run), Desktop Gadgets (doesn’t run), Deskscapes (works well), Control Center, Component Tray (doesn’t run).

Granted some of the apps don’t show up in Taskman under running programs, but, rather, under processes as running. Unless I've noted a program as "works well", I haven't really gotten into using it yet, meaning it may open, but whether it works properly beyond that I don't yet know.

Thanks for any help,
Arnold

Hi Zubaz,
I do realize some of the apps are still for XP. A good example being Windows FX. It runs & does change some things in Vista, but not properly. In fact, it can do a good job of disabling alot of Vista, only because you can't see anything anymore. Because I was so pleased with Object Dock, Deskscapes & Logon Studio, which I either purchased or are free, I decided to subscribe to the entire suite. I realize Windows Blinds has its new Vista version coming available in less than two weeks, however, I find the beta doesn't work. Windows Blinds, Windows FX, Icon X & Desktop X interested me. However, they don't work. Perhaps they will be updated for Vista. The long & short of it is that perhaps a subscription to the suite was completely unnecessary. I do have other machines, 2 XP desktops, 1 Mac laptop, & 1 Linux desktop (used for backup & storage), which I have not tried Object Desktop on. I'm sure the XP machines will run it fine. I don't know if OD will run on a Mac, & I don't need it on a Linux storage machine.

I’m going to check out the links you’ve suggested. I’m hoping & looking forward to those programs which do interest me either being able to be tweaked so they work, or being properly updated to work on Vista.

Anyway, thanks again for your help,
Arnold

I really hope that you get good use of your ODNT subscription as Visat matures and more apps become native for it.  None of the Stardock apps will work on Mac.  Only Multiplicity is scheduled for Mac support.

I'd be interested in how you like ODNT on your XP machines.  I think you'll be pleased and hopefully that will satisfy you as the other apps become Vista-ready.

DaveRI . . . at this point, unless avk has ADDED extra security he contact support@stardock.com.  The behavior of the apps is atypical and may need more support than we can provide.

All the released and Vista-ready apps should run without crazy admin tweaking.  That's how they are designed; for grandma, not her DeVry graduated grandson.    The XP-ready apps . . aren't there and any amount of tweaking may or may not help and can only add to frustration if they don't.

avk, if you think you switched over to ODNT too soon, you might want to talk to sales@stardock.com about a refund.  I wouldn't at this point, I think you still have your money's worth, but if you don't agree . . . there it is.

Okeydokey.

[twang..dangle](That would be the sound of my "rope with which to hang myself" running out.)  

Okay guys,

Thanks for all the input. Stardock & all of its child objects is located under C:\Program Files, also C:\Program Data, C:\Users\Public Files, & C:\Users… each individual user including the Administrator, & under each its under the Documents folder, …App Data\Local… & Roaming… Remember a number of these folders are hidden. However, I have changed ownership to my normal desktop, eliminated “read only”, & given myself (as well as the Administrator) full privileges with all of these locations. No luck. With regards to WB, I’m simply going to wait right now until the new version comes out. I’ve sent an email to their tech support. Hopefully things will find their own level. I’ll certainly give things a run for the money on one of the XP machines.

Like I said before, found Object Dock gorgeous & a lot of fun. It allowed organization to take over my machine. Logon Studio provides a very pleasant change. Look forward to a couple of these other apps adding to the eye candy. Not concerned about the cost of the subscription, these programs are quite cost effective for users.

Thanks again,
Arnold