USB Kick

Usage
USBKick searches all USB hub ports (ROOL or Castle USB only) to find attached devices that aren't enabled. It attempts to enable them by removing and then restoring power to the port. This is similar to how '*USBReset n' resets active devices. It doesn't require any user knowledge of where the device is. Starting with the 'Alt' key held down will override automatic running. Select clicking on the iconbar icon will open the Status window, the 'Kick' process can be initiated here. Adjust clicking opens the Configuration window.

Configuration
Option	Default	Description
Check devices on loading	On	Immediately execute Kick process when loaded.
Open status window	Off	Status window is opened automatically when loaded.
Quit options	Remain loaded	Options only apply to automatic run. If the Status window is open there is a short delay before automatic quit options are applied. Remain loaded - stays on iconbar. Quit only if successful - if all devices enabled correctly. Quit after kick - regardless of outcome.
Attempts	5	Number of times device enable will be attempted (1-9).
Kick 'empty' ports	On	Empty ports will be kicked to check for non-registering devices.
Reset crashed hubs	On	Performs a reset if the hub no longer responds to interrogation. May also reset a hub once if a device refuses to be kicked. Root hubs cannot be reset.
Frozen scanner reset	On	Resets a Epson scanner if it appears it might freeze.
HID refresh	On	Causes HID to rescan the USB devices (if running).
SCSI modules check	On	Warns if SCSI modules weren't loaded during boot sequence
Logging	Off	Creates a log of USBKick actions (!USBKick.Log). Menu option 'Show log' will load the log into an editor.

Acknowledgements


Programming Advice    : Daniel Ellis
Sprite Design         : Richard Hallas

Testing               : Gary Locock

Usage