Hello Tim, > You do have the option of the "Microsoft Connect" site at > http://connect.microsoft.com. That is a site dedicated to allowing > folks to submit bug reports against Microsoft products, in a pipeline > that goes directly to the development team. I have posted several VS 2005 bug reports in 2006 on the Visual Studio portal. First answer arrived in 2007, last one arrived in 2009. Almost all answers were like the "We confirm this bug but won't fix it in VS 2005. Will be fixed in VS 2008". So you need a year or more to get an answer to bug reports about the product you have paid for, and you need to pay again to upgrade to a new version to have these bugs (possibly) fixed (and get new bugs that will be (possibly) fixed in a next version). > If you want guaranteed support, you need to call in with a paid > support incident. That's the way to get their attention? So there are only two options: - Paid (and costly) immediate phone support; - Free web support with a months/years timeline. Do you really think that this scheme is adequate? I think there should be a third scheme, like an inexpensive email support for technicians within 1-2 weeks. > I guarantee you that none of the other commercial software products you > use have hundreds of millions of users. These hundreds of millions of users bring MS their money, right? And due to them MS is such gigantic company. If a big company like VMware is able to support its users adequately, why a gigantic company could not be able? The more customers, the biggest company, the more money, the more employees, the more support employees. > That, plus the fact that 90% of the users are idiots who are still > looking for the "any" key (as in "press any key to continue"). In your opinion, what percent of idiots and "any key finders" exists among MSDN subscribers? :) You are quite right saying about *ALL* users. But I mean *ONLY* qualified technicians. A ticket system could, for example, offer some questions like "how many bytes are contained in QWORD?" or "can a PCTSTR pointer contents be modified?". It is so simple, really. Regards, Eugene ****************** WDMAUDIODEV addresses: Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx URL to WDMAUDIODEV page: http://www.wdmaudiodev.com/