What about this.  Stardock never has yet claimed that OD is 64 bit compatible.  Maybe you should have considered that BEFORE you purchased the software instead of complaining about it AFTER you purchased the software.

That's like buying a toy football helmet and wearing it on a motorcycle, then crashing, busting your head, and blaming the toy football helmet company... even though there was a big sticker on the helmet saying "not a safety device"...

So... does it work on 64 bit 7even ? I was thinking about buying it this morning actually, guess I'll hold off. Suuuure would be nice if it came with OD.

I think you phrased it inappropriately. It's not the OS that is incompatible, but the said proggy. The OS is this global layer and, as it changes, proggies should "roll with the punches". OD, for one, didn't...yet

It's not about that. When I bought OD+, I had no expectations of 64-bit compatibility, I was running XP 32-bit. Now I'm running Win 7 32-bit and seriously considering the 64-bit move. Users' expectations moved on from a few years ago, but the software remained static. Buying OD+ now is like buying it in April 2007, when 1.9 came out. Users cannot be blamed for changing their expectations, you can't just say "You're bad, bad users for upgrading to a new OS because that means that our software won't work on it even if you'd expect it to because other proggies that you use, big or small, had updates to make them compatible".

I guess that's technically true. But when I bought OD+ a year ago it wasn't 32-bit only. It was "64-bit support currently in beta", which is not true anymore.

i'm running it on Windows 7 x64 with no issues

No issues whatsoever? Can we swap PCs?

I'm running it on Windows 7 64bit with no issues too. But that's because I know where the issues are and stay clear of them. If you have a car that break down when you hit 60mph, would you say "it's running without issues" just because all the roads you drive on has a 55mph limit?

No, I put it correctly.

You had XP 32 bit.

You acquired Object Dock for it.

It worked.

You then changed your OS to Windows 7 32bit.

End of story.

I currently have a three-user subscription to Bitdefender 2009.  It is a SUBSCRIPTION that has about 330 days left to run.  It was ME, NOT Bitdefender who changed his OS from XP Professional 32bit to Windows 7 Ultimate 64bit.

Is it Bitdefender's fault that my subscription is next to useless as 2009 does not function correctly on 7?

Did Bitdefender stand over me and force me to change my OS?

As I've mentioned already, if and when Object Dock is suitable for formal public release in a subsequent OS version then it will be available for formal release....and also as mentioned, there are MANY programs that are not immediately compatible with every/all variations of a SERIES of Operating Systems.

Windows 7 is NOT a flow-on from Vista, just as Vista is not a point release of XP.

Depending on the TYPE of program the real differences within each OS can have dramatic consequences to functionality.

Typically GUI interface modifiers [shell extensions] require real changes, unlike most 'normal' executables like PaintShop Pro that don't care what version of an OS they are on.

Yes, the steps that you, Jafo, describe are almost correct. Before moving to Win 7, I also used OD+ on Vista for which OD is claimed to be ready. Yet I experienced and reported bugs that to this day have not been resolved. What is supposed to happen in this type of situation?

Re: Bitdefender, perhaps you should switch to Norton. I had NIS 09 and got a free upgrade to NIS 2010, which I took upon, but 2009 users got updates to make their version compatible with Windows 7 if they did not wish to move to NIS 2010. Clearly some companies are more concerned than others to make sure that their software is fully compatible with Windows 7 (hint hint).

Let's be frank about this. Some programs do require more work than others to make them compatible, like you said. That being said, WindowBlinds which is a more complex piece of software than OD+ yet it is cared for very well indeed. A few months ago I made a prediction about OD not getting a stable update before Christmas. Looks increasinly likely, I wonder how much I would have got at the bookmakers

I dont think bookmakers give odds on software dev.

I will never use Norton again.  They seriously blotted their copy books back when they broke the 'BIT' service in MS requiring a complete reinstall of SP2 in XP.

Meanwhile...with Bitdefender...a little searching and I see it is both now compatible with 7 AND available to subscribers freely.  Back when I first started using 7 it was not compatible at all...so I had since moved on to one which was, as it was my primary OS and thus required protection.

For all the other machines I'll make use of the upgrade to 2010.

OK, let's not get sidetracked here As you've said, Bitdefender is now Win 7 compatible, which is another example of a company who updated their software ahead of Stardock. Also, in not so many words, you suggested that I stop using OD+ on my Win 7 system. That was my interpretation and I'm sceptical if that's the message that you should be sending. Do you use OD+ on your Win 7 PC? What is there to inspire customer confidence in Stardock?

If anyone has issues/finds bugs/is not happy with - a particular program the logical thing to do would be to not use it.

If said person documents any such issues and forwards them to the Dev it may go a little way towards assisting with a possible revision/update.

Either way I wouldn't lose sleep over whether a program was coming or not - it's not in my job description to do so.

There are tens of thousands [literally] of programs that I do not use on my Win 7 machine [all 4 of them]...and OD+ is but one.

Do I personally have confidence in Stardock...as a customer?  Too bloody right I do.  No program of theirs that I choose to run causes me an issue of any kind.  Sure, in-house betas can be fun...but that is the nature of the beast, and once again, probably the third time in this thread, skinners have a better knowledge of Stardock's GUI customizing software and are always going to be the people of choice to do the bug-hunting...so the 'customer' is spared the trouble.

It would be nice to see a list of issues, whether they are being worked on, possible eta's and final resolutions.

I'm fairly confident that several other software dev. companies do this. I believe it would go a long way to easing tensions in the forums and putting the 'customer' more at ease.

I can't see why this would be a bad practice or could not be implemented. I believe, much like like many other things in life that the 'not knowing' is far worse than knowing and being patient.

John....'the customer'....is the use of the singular just freudian slip or merely accurate?....;)

This is very true and would be nice.

Unfortunately though, for those who go about complaining in the repetitive way that some do, it would just serve as a list of things for them to make complaints about (such as: "X has been on the list for X# of days why isn't it fixed yet?" or " X had an eta of x/xx/xx and it is now 3 minutes into the next day why haven't we seen a new version yet?")

A bugtracker is a proven way to manage issues with software though. I've seen enough ETAs for fixes by Stardock to know that they rarely end up true, so stay clear of that bit...

it's working just find on my PC - win7 home edition

Cross my heart that I won't be one of those. Like vStyler said: 'not knowing' is far worse than knowing and being patient. However, with ETAs, Stardock would have to either deliver to those ETAs or update them regularly to reflect the most likely date.

Please see this post: https://forums.stardock.com/367035/get;2430252

I just must log in and mention that this thread contains some of the worst examples I've seen in quite a while when it comes to customer relations.

"Suit yourself!" is generally not a good way to handle customers, however true it might ring.

"We are sorry that we are not currently supporting your operating system of choice and while we do not have a date set for a windows 7 supported version our hope is that it will come soon enough to satisfy you." Would say the same thing but leave the customer a tad bit more satisfied that you care about every single customer.

All that said, I read that there were some work arounds for getting objectdock to work with win7 64 (especially interested in the start button and system tray). If someone could share links to those work arounds I'd appreciate it a lot

I am going to make this very simple. 

1. I do not appreciate Jafo's tone, which in this forum is the tone of Stardock.

2. I apologize to Stardock for attempting to run their software on my 64 bit Windows 7 system. I am sorry that I have a need to run 64 bit and tried to install and use their software as advertised (I realize that it does not state that it is 64 bit compatible, but you get my meaning.)

3. The best work around that was available for all of these issues until today was to DL and install the beta which was only available through Stardock Central, which as of today is no longer active, so I am forced to use an obsolete version of the software, at least until I finish this post and uninstall all Stardock software from my machine.

So, in conclusion. thanks for your help. Jafo and Stardock, you have made my software purchasing decisions a little easier by eliminating one vendor - Stardock.

Have a nice day and to all of you who will continue to use this inferior product, good luck!

BNXMike, I'm sorry you do not appreciate my tone.  It was/is intended as a debate between myself and one other person on this thread about the logic of using a product which has not yet been officially supported by the manufacturer for the OS he uses.

You too appear to have struck the same problem, hence your comment point '2'.

If you require assistance specifically for your software use the appropriate link is support@stardock.com

Certainly a more appropriate course of action for your own problem resolution would be to post more than just this one comment that you are leaving and actually give support the opportunity to assist....:)

Jafo, it seems that you see fault with logic of using a product on an OS for which said product is not supported. Yet many of the bugs mentioned (in the Bugs thread) occur on Vista 32-bit, which is supported. What assistance can support provide for issues that occur on the software level when the only way to mitigate those issues is to fix the code of said software?

I got Windows 7ultimate in, 32bit mode, since a week now. Can somebody post a link or something, where I can find the tutorial to make objectdock 1.9.sth work with the systray?