Context Navigation

Changes between Initial Version and Version 1 of Ticket #93, comment 16

initial	v1
2	2
3	3	As to TEST C: that cannot be an audio device driver issue. When you plug in the USB mouse, this device will also be offered to USBAUDIO for service because the USB stack initially does not know what type of device has been plugged in. It just asks all class/client drivers.\\
4		But USBAUDIO successfully rejects that device. It must be an issue with the rest of the USB stack. If possible, try my complete USB stack. You can always revert to the ArcaOS stack later on (my stack is limited to USB 2.x though).
	4	But USBAUDIO successfully rejects that device and that is ALL that it does. It must be an issue with the rest of the USB stack. If possible, try my complete USB stack. You can always revert to the ArcaOS stack later on (my stack is limited to USB 2.x though).
5	5
6	6	As to TEST D: what you could check with "killstream" is, if you can successfully kill stream Number 1 AFTER you have restarted to play the sound file again. If that is successful and if the stream still continues to play (you can still hear sound), then we know there is a problem with the system managing streams because that would mean that the system has started a new stream Number 2 (for playing the sound file again) but without properly terminating stream Number 1.