![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Dell solved all the remote problems for me, by sending a board and new UK-spec remote yesterday. It arrived today; fitting the board was a delight as the M2010 is basically SO HUGE that it'd be impossible to get it wrong.
Well, apart from the cosmetic covers.
See, the M2010 is basically a laptop motherboard in a Beo-esque casing, (The B&O Beocomputer 2000?), and as such, it's very roomy, and assembled from the bottom up. So off come two covers, which are really cleverly done. They are attached via a series of catches that pull the covers flush and sort of bite into hooks. Release those with a screwdriver in the rear panel, and Robert is your mother's brother, so to speak.
Except the plastics are made of cheese. And the catches are made of cheese wire. So refitting is a bastard. The catches sort of "bite" into the catches and stick, they can't be budged. My solution, after much swearing, was to adjust the position of the catches under the top panel, but that means the covers aren't quite as flush as they should be; new covers would have sorted the issue perfectly and if I obtain some I can always push the catches to their old position and make it all line up.
Regardless; the board is fitted, and works.
What didn't work, was nearly 2 hours of swearing as Vista went bananas with the Bluetooth. It seemed to lose the device when I wanted to re-pair the keyboard, and something very odd went on with drivers; I now have the two Bluetooth network drivers declaring themselves to be #6 for example.
How do you deal with Windows doing that? When it detects another of the same device, but in fact it was the same one and it just got confused? I'm sure it's not an issue, I just don't quite understand why Windows doesn't fully unload the old one and reload it.
Anyway, glitches aside; I can now control Media Centre (and indeed, start it) from the remote even without line of site, and the little LCD does indeed display an iPod-esque music browser, which is pretty neat actually. Fingers crossed that the last Firmware update, which made Bluetooth behave properly with Windows "sleep" (Apple can get this right, so why it seems to be such an issue on Windows defeats me).
Well, apart from the cosmetic covers.
See, the M2010 is basically a laptop motherboard in a Beo-esque casing, (The B&O Beocomputer 2000?), and as such, it's very roomy, and assembled from the bottom up. So off come two covers, which are really cleverly done. They are attached via a series of catches that pull the covers flush and sort of bite into hooks. Release those with a screwdriver in the rear panel, and Robert is your mother's brother, so to speak.
Except the plastics are made of cheese. And the catches are made of cheese wire. So refitting is a bastard. The catches sort of "bite" into the catches and stick, they can't be budged. My solution, after much swearing, was to adjust the position of the catches under the top panel, but that means the covers aren't quite as flush as they should be; new covers would have sorted the issue perfectly and if I obtain some I can always push the catches to their old position and make it all line up.
Regardless; the board is fitted, and works.
What didn't work, was nearly 2 hours of swearing as Vista went bananas with the Bluetooth. It seemed to lose the device when I wanted to re-pair the keyboard, and something very odd went on with drivers; I now have the two Bluetooth network drivers declaring themselves to be #6 for example.
How do you deal with Windows doing that? When it detects another of the same device, but in fact it was the same one and it just got confused? I'm sure it's not an issue, I just don't quite understand why Windows doesn't fully unload the old one and reload it.
Anyway, glitches aside; I can now control Media Centre (and indeed, start it) from the remote even without line of site, and the little LCD does indeed display an iPod-esque music browser, which is pretty neat actually. Fingers crossed that the last Firmware update, which made Bluetooth behave properly with Windows "sleep" (Apple can get this right, so why it seems to be such an issue on Windows defeats me).
