A common workaround seems to be the USBCtrl command, that allows the user to restart the USB stack (or so it seems) :
Code: Select all
USBCtrl RESTART FORCE
That's the paradox here : I need the mouse to restart the USB stack & re-enable the mouse
1. is this the correct behavior ? Is USBCtrl RESTART FORCE supposed to open a dialog window ?
2. if this is the correct behavior, may I suggest an additionnal option, like "NODIALOG" or "QUIET", that restarts the USB Stack without asking the user to interact with any of the input devices.