Mouse issue is not caused by system.
Posted: Tue Mar 14, 2017 11:56 am
First, this is not a whinge, but rather a rattling of the cage.TB software is the greatest and I recommend it daily through many outlets. Wouldn't use anything else.
Been trying all the fixes TB recommended with no joy since Dec. '16, when I bought the software. Luckily for me, I'm not one to give up easily.
It's naught to do with BIOS version or startup settings or anything of the like. Think about it, a device works in the OS and with other bootable media/ devices/ programs and not BIBM? Troubleshooting 101 covers that scenario.
Kinda miffed I had to go through all this to get to the root of this issue, but at least I don't have to Tab my way around the software anymore. Both systems that had the issue have it no more, wireless mice do work. It's a work-around, but until TB figure it out, I'll happily deal with it.
Key for me was, on both systems, Tab would work until you nudged the mouse(just a vibration will do it), then BIBM would be unresponsive to any input and had to be hard shut down and re-started without fail. This told me the mouse was enabled according to the system and on some level by BIBM but not enough to function properly. The pointer doesn't budge, no sign the mouse did anything, no error msg. from BIBM, just dead. This drove me mad trying to figure out the cause of the unresponsiveness, a truck driving by could vibrate the mouse enough to cause it. Had to happen a few times to catch it.After that, basic troubleshooting found me a solution.
I'm sitting here with a little angle on my shoulder whispering "Tell them what you found.", but on the other shoulder is a gorilla-sized devil screaming in my ear and steaming up my eyeballs "You've said enough, let them figure it out!" Right now, I'm going with Magilla.
Been trying all the fixes TB recommended with no joy since Dec. '16, when I bought the software. Luckily for me, I'm not one to give up easily.
It's naught to do with BIOS version or startup settings or anything of the like. Think about it, a device works in the OS and with other bootable media/ devices/ programs and not BIBM? Troubleshooting 101 covers that scenario.
Kinda miffed I had to go through all this to get to the root of this issue, but at least I don't have to Tab my way around the software anymore. Both systems that had the issue have it no more, wireless mice do work. It's a work-around, but until TB figure it out, I'll happily deal with it.
Key for me was, on both systems, Tab would work until you nudged the mouse(just a vibration will do it), then BIBM would be unresponsive to any input and had to be hard shut down and re-started without fail. This told me the mouse was enabled according to the system and on some level by BIBM but not enough to function properly. The pointer doesn't budge, no sign the mouse did anything, no error msg. from BIBM, just dead. This drove me mad trying to figure out the cause of the unresponsiveness, a truck driving by could vibrate the mouse enough to cause it. Had to happen a few times to catch it.After that, basic troubleshooting found me a solution.
I'm sitting here with a little angle on my shoulder whispering "Tell them what you found.", but on the other shoulder is a gorilla-sized devil screaming in my ear and steaming up my eyeballs "You've said enough, let them figure it out!" Right now, I'm going with Magilla.