I can offer at least a technical explination of what Vegas and the
system are reporting.

Vegas made a request of the driver as some point and the driver
failed to respond at the kernel level. The user mode portion of the
driver timed out and reported back an error to Vegas. After this
event, the driver refuses to respond to any further requests. The
final message - failing to complete and I/O request - is produced by
NT in response to the driver not returning/completing a queued i/o
request. The NT kernel and i/o subsystem handles all i/o requests
through a single consistant API - basically the file i/o API. If a
kernel mode driver failes to respond to a queued request, the system
eventually cancels the request. This cancel can take a long time.
Once canceled, the driver may or may not be active. It should be
active if implemented correctly, but some drivers don't.

I am checking with MIDIMan to see what is going on here.

Do you have a consistant repro of this problem? (Step by step?)

Thanks
Peter


Erich Grube wrote:
>>Anyone else using Vegas w/ a MAudio Delta 66 under Windows
>>NT4.0 (sp 5)? I'm having some pretty hairy problems right
>>now. I'm getting errors while playing back saying that the
>>driver is busy. Then I get an error with 'vegas.exe -
>>Cancel Timeout' in the title bar saying basically that the
>>delta driver failed to complete a I/O request in the
>>allotted time.
>>
>>I've talked to a person at Delta and he says that they are
>>looking into it w/SF people.
>>
>>Erich