This content has been marked as final. Show 14 replies
You provide ZERO information for anyone to help... and then you ask about conflicts, but still don't give anyone any idea of what you have
My computer is described at http://www.pacifier.com/~jtsmith/ADOBE.HTM
Read, and then come back and describe your computer, and all software, so someone may have some ideas
Upgrade to WindowBlinds 6 or exclude the Premiere Pro executable from being skinned by WB5.
Ok.. sorry... my bad.
Im running a windows XP machine with the following specs :
2gb OCZ ddr2-800
EVGA 7900 GT
Asus P5B mobo
@Jeff : I have windowsblind installed on my computer, does that cause a problem with adobe premier??
WindowBlinds 5 and earlier won't skin PPro CS3 properly. WindowBlinds 6 fixes the issue.
why on earth would someone want to use something like windowblinds on an editing computer?
uninstall all the unnecessary crap, take it off the internet, remove everything from the desktop and then expect it to work...
I've used WB for years, as well as Cursor XP, ObjectDock, Icon Packager and several other Stardock products. I have encountered only 2 issues during that time, and they were easily remedied by changing a setting and later, by upgrading to the next version of Stardock's products (which are constantly being improved and updated). This is one of those 2 issues.
I have no performance problems at all. I have a 3.0 GHz P4 with 2 GB RAM, so we're not talking about a Star Wars system that can simply throw immense resources at a problem and make it go away.
I make pretty pictures and eye-candy videos as a side business. I like my working environment to be pleasing to the eye as well. Making Windows XP into the barren, spartan interface that it can be is not necessary, nor, for me, is it desirable at all.
Had I chosen differently all those years ago, I probably would be on a Mac right now, but back then, cost was critical and PCs were cheaper. So here I am.
You're pretty knowledgeable about computer's though, Jeff. As a general rule, Ben's advice is sound. Install nothing on your edit rig you don't absolutely need to get the job done.
You are correct, Jim.
I started with all unnecessary background processes, Windows services and OEM software either shut off or uninstalled.
Then I added stuff a little bit at a time, making sure that everything in my mission-critical apps still worked. After a while (maybe a long while), I arrived at a configuration that suits me and gets the job done.
Ben's post implied an absolute prohibition on having anything non-post-production ever running on anyone's system. I wanted to provide a counterpoint.
But the underlying message is clear: when you have an issue, any issue, start troubleshooting by turning off everything that's not mission-critical. I reported this bug to Stardock (there may have been other reports) after I discovered that turning everything off made this issue go away. When I let WindowBlinds skin PPro CS3 again, the problem returned.
>I wanted to provide a counterpoint.
Fair enough. Just be sure to provide it with a "Don't try this at home kids" disclaimer for those who are less technically inclined.
Considering Alex made no mention of the program in his initial questions that was very well parsed Jim.
Considering Alex made no mention of the program in his initial questions that was very well parsed Jeff.
Thanks, but parsing it was all too easy. Alex's issue is very specific, and is only caused by the older WindowBlinds version conflict. :)
And I was beginning to think Jeff was psychic...