[wdmaudiodev] Re: WLK tests behave VERY strange

  • From: Eugene Muzychenko <eugene@xxxxxxxxxxxxxx>
  • To: Tim Roberts <wdmaudiodev@xxxxxxxxxxxxx>
  • Date: Fri, 28 Oct 2011 02:42:41 +0700

Hello Tim,

> The fee is refunded once the problem is identified as Microsoft's fault.

I don't think that it is a good practice. A fee-based support is
adequate if there is an exhaustive documentation but users don't want
to learn and/or cannot describe their problems exactly and technically, 
preferring to
give a simple description, answer some leading questions and finally
get a well-described solution. In such case, a support officer
performs a personal work for such user and this work should be paid.

It is not a secret that Kernel Streaming is not documented well,
despite its long history (from 1997-1998). Therefore, developers
cannot learn good about it from official documentation; they are
forced to learn about some details by guessing and experimenting.

WLK tests are not described well too. Audio tests are almost not
described. For example, mididrv.exe has a lot of description:


But wavetest.exe and kstoptest.exe are not described at all:


Of course, most FAIL messages contain useful information but exact
PASS conditions are not documented so some fails are not easy to
understand. In some other cases, test logic is not clear from its
messages (for example, case 1.10 from wavetest that I mentioned).

In such situation, I think that offering only a fee-based (and with
relatively high fees) support to developers is not really nice.

> Also, if you have an MSDN subscription (most of us do), you're entitled
> to 10 free support incidents.

Hmmm, where did you see 10 incidents? I see no more than 4:


I'm MSDN OS subscriber and have 2 incidents possible. BTW, these
incidents are not cumulative; I'm a subscriber for five years and
never used support incidents but I still have no more than 2

And these incidents are not easy to use - you must make a phone call
first to obtain a contract/ID. Such things should be more convenient.



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


Other related posts: