11. The Bus Controller receives RT1's status word, and sees that the transmit command has been received and actioned without a problem. 12. I see a " Universal Serial Bus Controller " and a " USB Virtualization " drop-down-list, both already open. 13. All communication on the bus is under the control of the Bus Controller using commands from the BC to the RTs to receive or transmit. 14. The Bus Controller receives RT2's status word and sees that the receive command and data have been received and actioned without a problem. 15. This allows the Backup Bus Controller to " hit the ground running ", if it is called upon to become the active Bus Controller. 16. This allows the Backup Bus Controller to " hit the ground running ", if it is called upon to become the active Bus Controller . 17. Large VAX systems primarily used the Hierarchical Storage Controller ( HSC ) series but Unibus and BI Bus controllers to SDI were built as well. 18. This means that during a transfer, all communication is started by the Bus Controller , and a terminal device cannot start a data transfer on its own. 19. I've also seen this happen because of a faulty bus controller -which also caused errors in sound, but also did not report any error anywhere. 20. However, this inter-message gap can be, and often is, much larger than 4 ?s, even up to 1 ms with some older Bus Controllers .
