Dynex Optical Mouse and Multimedia Keyboard Combo

My wireless mouse and keyboard died last night. I replaced the batteries, and got nowhere with it; since I needed the keyboard and mouse for work today and this was the THIRD wireless mouse to die in the last two years for me, I made a quick trip to my local Best Buy to buy a wired keyboard and mouse combo. I sit near my computer, so it made sense (why keep wasting batteries?).

Wired keyboards and mice are hard combo to find; there was really only one option at the store, and it was the Dynex Optical Mouse and Multimedia Keyboard. I’ve never been a big fan of Dynex products (you’ll find out why in a minute), but since I really had no choice, I decided to pick one up. It was cheap (you get what you pay for), and the display model looked OK. I bought it, and left it on my desk for installation this morning.

Install went fine (mostly); I plugged in the keyboard and the mouse into the USB connections on my KVM switch, and I immediately had a basic keyboard and mouse functioning. However, this is a MULTIMEDIA keyboard and mouse combo; there’s extra buttons on both, and I wanted to make them work. Since there was no install disk, I headed over to the Dynex web site to find drivers. I’ve done this before for other Dynex products (hence my distaste for the brand), so I thought it was going to be relatively easy.

Well, the combo wasn’t listed as an option for download, so I looked for drivers for the individual components; the mouse was easy: DX-WMSE, and there’s the driver right on the page. Download, unzip, install. Done. The keyboard? DX-WKBD. No driver on the page. Hmmm. Click the Drivers link on the bottom left of the page, and then the Input Devices drop down. No listing for my keyboard; also, no listing for the mouse driver either. At this point, I begin swearing softly.

They have a support number, which I call, and I speak to a very nice representative named Mike, who proceeds to tell me that the keyboard doesn’t require a driver. I tell him that the basic functions are working, but none of the multimedia keys work; he asks me to uninstall the keyboard and reinstall, and then finally utters that panacea of support technicians everywhere – REBOOT. I tried all of those, and got nowhere. I thanked him for his time, and hung up. Since I don’t need the multimedia functions, I can make do until I need a replacement. When I do need a replacement, it probably won’t be a Dynex.

PROS: Cheap keyboard and mouse combo. Basic functions work well.

CONS: No drivers available for the multimedia functionality. Other reviews seem to indicate that it does work out of the box, but I couldn’t get it to work for me.

EDIT: I’ve revised my rating, because I determined that the USB switch on my KVM switch was interfering with the device discovery; when I plugged the keyboard directly into a PC, the functionality worked. I still think that there should be some sort of drivers associated with the keyboard, but it’s unfair to give this a low rating because of that.

2 of 5 stars 4 of 5 stars

SQL and Relational Theory: How to Write Accurate SQL Code

When I first got this book I was very excited; the author, C.J. Date is one of those names that you hear tossed around with Codd. I was hoping that this book would be a good refresher on basic SQL theorems and relational design, and while I was not disappointed, I was a bit overwhelmed by the third chapter. Having recently seen the latest incarnation of Star Trek, I thought a science-fiction metaphor might be appropriate.

Reading this book made me realize that I’m an engineer; I am Scotty. I know how my particular environment works, I know when “I’m giving her all she’s got”, and I know how to tweak the system to keep it afloat when pressed with stressful situations. SQL Server is a wonderful platform, but like all database systems, it’s got its own peculiar quirks. Like all good engineers, you can learn to make the best of those quirks, but it doesn’t mean you understand how the engine is supposed to work.

Date is definitely Spock; beyond the logical comparisons (pardon the pun), Date’s focus is on the theory of how the relational model is supposed to work, not necessarily how SQL is implemented in the various database platforms. Very early on, he distinguishes between the relational model and SQL, and it became increasingly clear as I read this book that SQL <> relational model. Date tries his best to explain a very complex subject in a very thorough method, but I’m afraid that I’m not one of his best students.

The math involved in the relational model is very complex, and at times, I found myself frustrated with a passage because I knew how to do something in SQL, but had no clue as to what Date was saying in a relational language. That’s both sad and liberating in a way; I walked away from this book knowing first that I’m comfortable being an engineer, and second that I need to re-read this material occasionally. Date is like broccoli; he’ll never be my favorite author, but I know that what he’s writing is good for me.

4 out of 5 stars.

Joe Celko's SQL Programming Style

Just finished this book and it's really worth the read. You sometimes know that you are supposed to do things a certain way or avoid other ways. This gives you insight into why and brings up things you didn't think of. Even if you don't agree with everything, it's still worthwhile to get a different perspective.