Yuck! Proprietary USB Cables
Chris Pirillo makes a good point in this video. Before I say anything further, you should watch it:
There, now that you've seen his ire, you can read my reasoning.
Plenty of us know that proprietary anything is usually bad for the consumer. Proprietary data formats force us to use the same program (switching would be a pain -- manual re-entry -- because the software company didn't make a converter or export function). Proprietary procedures mean patents, trademarks, copyrights, or whatever, and mean no two companies will necessarily do things the same way. And proprietary connectors lock in an accessory market, with purchases often costing more than generic products would simply because the company that makes them has you in a death grip.
Now, while Chris's reaction is an emotional one (no doubt inspired by a conversation on his IRC channel), he makes a very, very good point. Proprietary connectors do nothing but irritate the consumer. Finding which USB connector fits which USB device is a nightmare. I'm happy to say that my camera uses a standard Mini USB cable. My iPAQ uses a proprietary connector, but that's because it performs more functions than just charging and synchronizing.
Microsoft and Sony use proprietary connectors for their gaming devices (these are only a couple examples), and as a result, you have to buy their authorized accessories. The prices can be whole factors higher (twice as much or more) than standard cables and connections.
Lego is also a user of proprietary connections. Within its Mindstorms robotics line, the cables used to connect the NXT computer with the various sensors and motors look, at first glance, like ordinary RJ-11 wiring, but the release tabs are pushed to the side, making them incompatible with other devices and standard cables incompatible with Lego's products.
I haven't had to replace any NXT cables yet, but there's a definite boon to companies like Canon (and Olympus; my mom's five-year-old camera also uses a Mini USB plug) using accepted standards. I could use the cable from either camera in the other in a pinch, or buy a standard camera cable at any electronics store should I lose or damage the one that I got in the box. It also means that if I have multiple devices that use the same connector, such as a camera, a phone, a PDA, and an external storage device, I can share one or two cables between all of them, as I'm unlikely to use more than a couple devices at a time.
So you see, standards are a good thing for the consumer. Even if the companies make a little less money, they'll make up for it in consumer happiness.
Thanks for the inspiration, Chris!
HP Doesn’t Support Weird Problems
As you all should know if you've been following this blog for a while (well, actually, since my first post, which is doubtful), I have an HP iPAQ with Wi-Fi that hasn't worked for a long time now. That was nearly two years ago, and since then, I've been through several conversations with HP's technical support team, over various media, with no solution.
First I tried a chat, then an email, then another chat, and another, but nobody has been able to solve my problem. In fact, the email support request was rejected for some odd reason.
Before the most recent chat attempt, I isolated the problem for them. All by myself, with no instructions. I got the idea that since the Wi-Fi works after a hard reset (which clears all data and programs installed after manufacturing), but it fails after restoring a backup, there must have been something changed inadvertently. I set to work on that hypothesis, and found that the problem lies somewhere in the Registry, Windows' worst feature ever.
Armed with that knowledge, I asked HP what keys and values I should restore to their original state to make the wireless work again. I was met with denial. Apparently they don't give out that information (or they don't know it). I asked what manufacturer produced the networking chip, and was again met with ignorance (though I did get some suggestions). After failing in attempts to contact the possible manufacturers, I had to give up.
So, I've done all this legwork and still have no answers. The fact that I can no longer synchronize with my computer (another thing that broke, and which HP was unable to fix) doesn't help, since I can't lose the data and programs on the device. My only hope now is for someone at HP to read this and do something nice, out of the ordinary. All I need is a few pieces of Registry information, but I can't even get that.
For anyone who might be able to help, I have an HP iPAQ hx2755 from October 2005, running Windows Mobile 2003SE (the WM5 upgrade, which I aborted before it could actually start, was what broke the syncing capability).
HP iPAQ WiFi Woes
I got an HP iPAQ (model hx2755) last October, and it's been great. Now, with no settings modifications or any other provocation, the Wi-Fi has suddenly stopped connecting to networks. I am open to any comments.






