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 [email protected]

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?

I have always heard that the sys tray and start menu issues were with 64-bit versions of Windows. Sys tray & start menu functionality were perfect on Vista 32, but non-functional on Vista 64.

I run w7 64-bit, so I can't say for sure how it works on w7 32 bit; just that it doesn't work for me.

WinCustomize wiki, ObjectDock section: http://wiki.wincustomize.com/wiki/ObjectDock

Systray section of that:  https://www.wincustomize.com/articles.aspx?aid=98648

Section 1 of that refers to "Adding SDMCP.exe..." .  I believe that is outdated and no longer applies, I believe you would skip that step.

öhm... yes... there is written how the system tray icon thing works... but.... in windows 7 there is a problem with that. i read about patching some files back or something. system tray doesn't work in windows 7 and i just wanted to know the "trick" how you can "make it work" ^^

would be great

thanks

Sorry, can't help you with that.  Anybody else?

can u give me a link please? i can't find anything......