@thonassen - Sounds like a good idea. I have answers to most of the issues I raised (thanks to you) and the troll will starve if nobody feeds him.
Stephen Soymonoff
@thomassen - Thank you for the link - I shall look at it now. @John Hamp - I wrote one complaint post. That's all. Anything else I have posted has been a reply to a comment in this thread. If you consider that to be multiple complaints then that's your right - I won't argue it with you, but I will respectfully disagree. As for the bugs I mentioned, most of the problems I am experiencing (with one major exception, inv
I get to this forum via Stardock Central not via WC, so I probably don't see everything that the people on the website see. If you have a URL to the post that addresses these issues, then I'd be more than happy to take a look at it.
Oh, I should also mention - I don't read the WC site anyway as I have absolutely no interest in WinCustomise. I will occasionally look at the Stardock site, but that's usually only when I'm looking for a solution to a problem. Why would you expect me to have just stumbled across some announcement about a product I don't use or want on a site I don't read? All the information I had was in that email I mentioned - if there was more that Stardo
I was around in the early days of the Stardock OS/2 products - still have some of the disks here. I was on the OS/2 support desk for IBM. Stardock were really good then. Not to say they aren't now, but their focus has necessarily slipped with their growth and the number of products. Especially as they still seem to be using the same methods for product control and bug tracking as they did then. If I'd had bugs outstanding in my products for
No, I responded to the email sent to me. I don't see why I should have to trolling through the site looking for extra information when Stardock sent me the email - I didn't go asking to be a tester. Personally I couldn't give a rat's about TD or whether it's tested or even developed. I want the bugs - some of them extremely long-standing - in existing products fixed first.
So, what you're telling me is that I can volunteer to put my data and machine at risk by helping you to test out what is almost certain to be buggy software (given the nature of beta software in general and Stardock's own track record for enormous bugs in your actual releases) and then I'm supposed to *pay* for the privilege afterwards? Well, please excuse me if I don't rush to take advantage of your offer. Most companies that I