Gaurav Khuntale wrote: > > Start Case: ID 16.26:1.5: Standard Streaming\Rendering Pin Tests\Reset > Pin while streaming data > KSPIN_DATAFLOW_IN pin is currently in state KSSTATE_PAUSE; want > it to be in state KSSTATE_RUN > Setting KSPIN_DATAFLOW_IN pin to state KSSTATE_RUN > Position reported before issuing KSRESET_BEGIN = 121 bytes > KSPIN_DATAFLOW_IN pin is currently in state KSSTATE_RUN; want it > to be in state KSSTATE_RUN > Resetting Pin state: IOCTL_KS_RESET_STATE (KSRESET_BEGIN) > Position reported after issuing KSRESET_BEGIN = 0 bytes > Submitting IOCTL_KS_WRITE_STREAM IRP ... > GetLastError did not return ERROR_IO_PENDING even though the pin > is paused Looking at this again, I guess I'm a bit confused. The IOCTL_KS_RESET_STATE command should be handled by the port class port driver. I don't think it feeds down to the miniport at all. The key thing this seems to be complaining about is that your driver allowed a "write" to occur even though it is paused. Again, I'm not sure that is under your control. The MSVAD driver only checks for the "paused" state in a very few circumstances. -- Tim Roberts, timr@xxxxxxxxx Providenza & Boekelheide, Inc. ****************** 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/