Um yea, WindowBlinds stopped applying skins

from Stardock Forums
G'day, new user to Stardock 'n all, and not having great success. Windows blinds was working alright, love that cyclops blind, or blind cyclops however u wanna put it hehe, except all of a sudden it stopped applying per pixel skins, whatever the hell they are. It's the trial version but I've only had it for a day! It's been uninstalled and reinstalled about 15 times tho. Whatever happened to the good ol' days in windows where u just copied a file into the right directory and bam, there was your startup and shutdown screens, whatever bloody pic u choose! Stupid bloody microsoft. You'd think it'd all be easier by now. So anyways, I love the concept of these programs, they would be so great if they just worked on my pc. I've read about all the BIOS problems and how it's our pcs and stuff...i dunno, sounds a bit sus to me as I would have thought progs should be built to cater to the masses with not as many problems as these ones. I'm not dissing it tho, it's just a pity, damn shame. So anyways, here's my details, if anyone can help that would be great. I'm also having dramas with Bootskin, I've tried all 3 versions and by what I've read in the forums looks like I might as well give up. I would like to buy Object Desktop but I just don't want to pay for something that I've experienced doesn't work on my machine. Oh well, here it all is:

WindowBlinds 5.1 System Information Report:

STATUS : WB+ SRV+ HLP+ UI+ TRAY+

WindowBlinds is installed correctly on this PC.

Your machine supports per pixel borders on WindowBlinds skins.

You have one monitor in total.

(Plug and Play Monitor) 1 is attached to NVIDIA GeForce 6200 TurboCache(TM)

Wblind.dll 2006/10/09 12:32:26
Wblind64.dll 2006/10/09 12:46:55
Wbsrv.dll 2006/10/10 17:53:58
Wbconfig.exe 2006/10/10 16:49:57
Wbload.exe 2005/12/21 01:04:47
Wbhelp.dll 2004/09/18 16:37:07
Wbui.dll 2005/11/26 19:09:25
Tray.dll 2006/04/28 19:27:49

PS - on a good note, LogonStudio is working well, though sometimes when I import the screens they come out funny and I have to edit them to what they're supposed to look like. Pretty sus if u ask me, but eh, miracles can happen, and I hope one does, coz my '24' XP environment is coming along very well! I'm not keen to venture into using the other programs either, and all I can say is 'damn, damn, damn, damn, damn!!' But hey, good luck to all you users who can make it work, I'm so jealous.

Peace out
5,297 views 14 replies
Reply #1 from WinCustomize Forums Top
I've tried all 3 bootskins off and on, never got it to work - but at least i never got the BSOD either.

I've been running the pd version of ODNT for 3 yrs with no major issues

don't know why WB would quit - everything I've read says it only quits when the trial is up - doesn't matter if you reinstall - the 60 days starts from day 1 of the 1st install

normally we see issues within the files (borked or other) when posted which causes problems, but your files look okay for 5.1 trial version
Reply #2 from WinCustomize Forums Top
It's the trial version but I've only had it for a day! It's been uninstalled and reinstalled about 15 times tho.

Most likely the problem.
Ashes of the Singularity II
Reply #4 from WinCustomize Forums Top
It's been uninstalled and reinstalled about 15 times tho.


Why?
Reply #5 from WinCustomize Forums Top
First off - I hope when you uninstall windowblinds you reboot. You need to reboot again once it's reinstalled. Clean installation is key and the boot thing seems to be a major issue. I've been using object desktop for a long time and have been very pleased. I do find one issue tho and it's not from the programs - it's microsoft. Whenever I get the automatic updates things go screwy for a day or two. Always resolves itself but can be very annoying.

Another issue - I don't see what version of windows you are using. Wndows Media Center is horrible as far as I'm concerned. Often when I turn my machine back on I have to apply the media center skin from properties and then reapply windowblinds.. My other machines don't do that. Many games and programs just refuse to work correctly with it. However, XP home and XP Pro seem to work flawlessly with Object Desktop.

My only real suggestion is to update all you video drivers right away. And per-pixel needs to be turned on in windowblinds configuration or you won't have it. Just be patient and learn the programs. They really are very complex.

Good luck - hopefully some of this helps. If you need to email me feel free to. [email protected]
Reply #6 from WinCustomize Forums Top
but at least i never got the BSOD either.


I don't understand this comment

pd version of ODNT


paid version of Object Desktop...NT?

Most likely the problem


what, that it's the trial version or that I've reinstalled it so many times?

Why?


long story...first time I installed bootskin and LogonStudio, I didn't reboot and after it crashed the first time I tried it, I had trouble uninstalling Webshots. At one system restore point AVG virus scanner wouldn't work but Webshots would uninstall, and at another point AVG worked but Webshots wouldn't uninstall. After stuffing around with lots of system restore points I eventually went to the point where AVG worked and figured out the best way to uninstall Webshots was to reinstall it over the top, then uninstall it and that worked. Throughout this exercise Webshot blinds was uninstalled and reinstalled a few times. Then after I fixed all this it was just a case of I kept trying and trying to uninstall and reinstall WindowBlinds to see if it worked but it still doesn't work. It says "Shareware: Per pixel will be disabled".

hope when you uninstall windowblinds you reboot


After the uninstall it automatically reboots, but I wasn't rebooting after the reinstall. I just tried that though, and no change in the situation.

automatic updates


I don't use automatic update, I'm stuck on the initial install of XP SP2 with no automatic updates (don't ask why   you can probably figure it out for yourself). Maybe this is the problem.

update all your video drivers right away. And per pixel needs to be turned on in windowblinds configuration or you won't have it.


naturally I have "Never use per pixel" unchecked on the system info screen, but in the preview pane of the different skins it says "Shareware: Per pixel will be disabled"

Thanks for your email addy, I'll see how I go.

Peace
Reply #7 from WinCustomize Forums Top
actually, I'm not that good at technical stuff, I don't honestly know how to update my video drivers!
Reply #8 from WinCustomize Forums Top

As the message on the preview says, in the shareware version those per pixel skins are not supported.

This message will show on any per pixel skin that was not included with the WB trial itself.  There should also be a nag screen appearing when you try to apply those skins informing you of this.

Reply #9 from WinCustomize Forums Top
yea but thing is they did work at first, then they just stopped working. what you're saying is promising as it would mean if I purchased the software then it would work, but I'm still skeptical.

no nag screens though
Reply #10 from WinCustomize Forums Top
no nag screens though
The purchased version does not have any nag screens.
Reply #11 from WinCustomize Forums Top
but at least i never got the BSOD either.


I don't understand this comment


Blue
Screen
Of
Death


paid version of Object Desktop...NT?


yes. been running most of the programs including Windowblinds for 3 yrs
Reply #12 from WinCustomize Forums Top
been running most of the programs including Windowblinds for 3 yrs


around 5 years here.
Reply #13 from WinCustomize Forums Top
I wouldn't be without it! It is well worth the money and no nag screens. Running about 3 years here.
Reply #14 from WinCustomize Forums Top

Sufficeth2Say,

It may be that the System Restore created a problem in the trial 'clock' - as it were. Neil Banfield (reply #8) would know if this is possible as he is the primary developer for WindowBlinds.

If I were you, I would try the following:

1 - Backup any downloaded skin/theme files that were not included with the Stardock programs, and any Stardock program installer files.

2 - Unload all Stardock programs and restore the Windows XP default theme including icons, logon screen, and boot screen - then reboot the computer.

3 - Download this utility https://www.stardock.com/files/ODNT_zapper.exe and save to your desktop. Double-click the utility to load it > use the 'Unload' tab to select and unload any programs listed as loaded > use the 'Uninstall' tab to select and uninstall the listed Stardock programs.

4 - Reboot your machine and uninstall any Stardock programs that the 'ODNT Zapper' utility did not offer to uninstall and reboot once more (do this using the 'Add or Remove Programs' applet in the Control Panel).

5 - Delete any Stardock or ObjectDesktop folders from the following locations:

- C:\Program Files

- C:\Program Files\Common Files

- C:\Documents and Settings\All Users\Start Menu\Programs

- C:\Documents and Settings\USERNAME\Start Menu\Programs (where 'USERNAME' is the name on your account).

- C:\Documents and Settings\USERNAME\Local Settings\Application Data (where 'USERNAME' is the name on your account). Note - the 'Local Settings' folder is a hidden folder. For instructions on removing the 'Stardock' folder from this location, you can read my mini tutorial here http://corkyo.wincustomize.com/articles.aspx?aid=82461#929595

Your computer should now be clean of the Stardock programs (with the exception of registry entries which is beyond the scope of this comment).

Now, download and install a fresh copy of WindowBlinds 'trial' version. I suggest temporarily disconnecting from the internet so you can safely disable (temporarily) the AVG program during the WindowBlinds installation.

After installing, wait about 30 seconds to see if WindowBlinds displays a dialog, and then close the dialog to reboot (or simply reboot if the dialog does not appear).

After rebooting, load WindowBlinds and see if you can apply a skin successfully. If so, you can reinstall LogonStudio (suggest you leave Bootskin behind due to apparent lack of compatibility).

If WindowBlinds still does not load a skin, then the issue is probably better addressed by Neil (or someone more competent than myself).

If you want to update your video drivers, you can go here http://www.nvidia.com/object/winxp_2k_93.71.html and download the latest drivers. Assuming your GeForce 6200 is either an 'AGP' slot or 'PCI-express' slot card, and not an integrated video (a chip on the motherboard) - then the driver release notes indicate they are compatible.

The normal procedure is to double-click the downloaded driver installer file to run the installer and follow the onscreen directions. Note - I recommend doing this while running the Windows XP defaults to alleviate any possible issues with other programs. It is also advisable to read the 'Driver installation hints document' link on the page before proceding.

Note - my solutions are usually very conservative and involve removing possible conflicts before attempting a procedure (e.g., the restoring defaults and uninstalling programs).

That's it for me.