Dead mouse and keyboard...

by **badgeronkeys** » Thu Jan 16, 2020 2:31 am

Last night we suffered a number of power cuts, 2 or 3 of which occurred whilst my d8b was up and running and worse still whilst it was booting up. Today I started it up and it came back to life however neither the keyboard or mouse work. I’ve reseated both cables and rebooted to no avail.

Thinking the BIOS may be corrupted, I tried again booting whilst pressing DEL but can’t get into the BIOS.

Has anyone come across this and solved it?

My next plan is to take my spare d8b which is a full clone (and working last time I used it ~3 years ago) and swap out the mouse and keyboard PCI boards. If that still doesn’t work, I will extract the HD’s and swap in the hope that the (hopefully still) good HD brings her back to life.

Interestingly, the transport buttons are working fine with Logic so MIDI communication is working fine. So it appears to be a peripheral device problem. Also, all comms from the board to the GUI work ok (fader movements, pan, mute, solo, etc. all drive the GUI) but I obviously can’t drive it from the PC or access any saved sessions, etc. If I try loading sessions from the board or loading plugins, no sessions are displayed and it tells me all effects slots are empty. Makes me wonder if the HD is damaged/corrupted or worse still the power outage has fried all my effects boards as well.

Any help would be greatly appreciated!

by **badgeronkeys** » Thu Jan 16, 2020 2:50 am

Update: I can actually load session files and see the effects plugins by driving the buttons on the board. I've never used these before so stumbled around at first. So on the face of it, the HD looks to be OK. Am thinking it's more likely a peripheral PCI board problem...

by **badgeronkeys** » Thu Jan 16, 2020 4:03 am

PROBLEM SOLVED....

I am embarrassed to admit this... Having pulled all cables out of the d8b due to the power cut I managed to hook the mouse and keyboard the wrong way around! I have a USB keyboard with an adapter to the old DIN style connector which just so happens to allow the mouse to fit the keyboard port and vice versa. Solved by... checking the user manual... :roll: