I wonder how, if it's just a "limitation date limit" in any part of the software, this is not corrected at this time ... ??? so one line of code to get rid off ??? what a long job to do ...

. . . and Photoshop 7.0 stopped working at the same time . . . hmmmmmmmm . . .

Been using WB since it first was introduced and since then have only had to upgrade from OD.Methinks this is an excercise by Stardock to see how many of us are NOT on XP so they can establish whether releasing WB4 is worth the effort of not.It is worth the effort,given the number of messags up here and the thousands that may not have put up a message. XP users comments also noted...don't get elitist on us lower mortals..we love our WB and are not whinging without good reason. We paid for our version of WB too and it ough not to expire.!!Our money is as good as your XP and probalby funded the WB4 improvements cum to that

I can assure you it was not intentional and we are working on the fix.

While its only 3-4 lines thats causing the issue, we have to test it and build installers & test those out before we can update it.  Plus the problem occured over a weekend which also delayed things.

Release the WB4 to compensate for our suffering!

They can't release something they don't have yet.

You people are such whiners! They've found the problem and are working on a fix, for which you should be grateful. They already apologized for any inconvenience.

Everybody who's never made a mistake before, raise your hand.... Yeah, that's what I thought.

Thanks, Stardock, for your quick response to unforunate
incident, considering the weekend, you all did a fine job.

We shouldn't be grateful for something that is our right. Remember that when we paid for that program the least thing that we expected is for it to work properly.

I believe I've got all the enhanced, ODNT, and Stardock Central installers properly updated now. Use the form at https://www.stardock.com/support to get the enhanced links and serials or your CM/SDC as appropriate.

Customers who's ODNT subscriptions have expired, please contact [email protected] with your serial. They have a link that you can use with the CM to get 3.51.

Any other specific questions on this, email [email protected] rather than support. They have enough with the people who aren't reading here for info on this matter.

NOTE!!!!

FOR EVERYONE WAITING TO GET UPDATE ON WB3.5 ITS OUT NOW!!! YOU HAVE TO DOWNLOAD STARDOCK CENTRAL AND UPDATE THE WHOLE THING FROM THERE...

THEY ARE REALLY AMASING...

THANX A LOT FOR EVERYTHING...

So did I miss something Bender50 - what quick response? I still don't see an fixed version posted anywhere.

Einstein - I have loads of shareware on my computer that the original purchase price included updates for a year or more. It pisses me off that I have to fork over more money for the updated version only 4 or 5 months after I purchased WindowBlinds.

Thanks Ogy Ego - yup that was pretty fast correction of the problem.
Good work Stardock staff.

You do NOT have to use Stardock Central to update, though we do encourage it. The standalone builds are available for registered users as always and the build on the older CM has been updated as well.

Put me down as another confused WindowBlinds user - I've just reinstalled a Norton Ghost copy of my harddisk and was shocked to see that my WindowBlinds wasn't working correctly - even when I installed it on a different machine - I was also afraid that I might have inadvertly gotten a virus - thank goodness that it wasn't as serious as I had thought. Now I've just got to download the updated files.

I attempted going through SDC (getting the necessary SDC update and then updating DesktopX, ObjectBar, WindowBlinds to 3.51, and a few others). Now seems that NONE of the programs updated function- WB still continues to just change color, and DesktopX just comes up with an initialization error before aborting altogether. ObjectBar does the same thing. Luckily ObjectEdit still works (so editing LiteStep is a go!). Anyone else getting this?

Nevermind!!! c242 got me pointed in the right direction- Uninstalled everything and made sure I had the v1.00 SDC installed. Everything came up fine after that, and WindowBlinds is again working (and quite well, I might add!) WOOHOO!!!

Dagoz,

Be careful that you know where you stand when you talk about your rights. You didn't buy the program, you only bought the right to use it, and it is offered "AS IS". From the EULA: "Stardock disclaims all warranties, expressed or implied, including, without limitation, the warranties of merchantability and of fitness for any purpose." Which means you didn't pay for the right to use the perfected program, you paid for the right to use whatever version was out there at the time.

What we should be grateful for is that they don't just throw up their hands in frustration and walk away from the whole thing when we treat them like dirt, quite frankly, and make unreasonable demands, and then expect that they will treat us like their best friends in the whole world. Which, admirably, they still do; through excellent customer service.

And don't get me started on whether gratitude or rights under the law is more important to the well-being of human society...

Ok, so I download SDH 1.0 final release, then I uninstalled 3.5a, because SDH was not showing the update, and now I can not install 3.51, because I'm running WinNT4.0, and SDH says your out of luck "Windows98 or better"? I know that WindowBlinds3 was not in the OS list of compatibility, but I have been running this program on NT4.0 since it release with know problems. Please Help.

I'm having trouble figuring out exactly what setting I need to get it happy with NT4 installs. What's something on Stardock Central that is installing properly on NT for you?

OK, I think I've got NT4 happy for it.

Yes, It's Happy. Thanks for your quick response. I had used the old CM and installed 3.41 for the time being.

I have installed the new released WB3.51
Everything is working again.
Thank you?
I will think about it.
Juan

Graagh,

It seems like you're looking for a job as a lawyer of Stardock. Just don't forget that the "AS IS" clause specified in the EULA agreement doesn't totally except companies from their responsabilities of their products. In my opinion, it's a way for companies to cover their asses.

Good luck