After months--I was overly optimistic in my initial review about this product. I played with it but it never went to a fully "operational" state on my system. Perhaps I was demanding too much, as I wanted it to run as a service, which could be done but never really worked satisfactorily. My impression is that D-link pushed out a minimal effort, to fill a product niche, that was overpriced for $60. Might be okay for $15-$20--it's really a cheap piece of hardware, but don't expect nearly anything out of this product that you'll get from a VOIP Gateway device these days for $40-$70. Unimaginative. The internals are off the shelf and the associated drivers are okay, but not great. The device works okay as advertised. I would now put 2-stars on this product (1 star at $60, 2 stars at $30, and 3 stars at $20. Maybe 4 stars at $10-$15.)
------------------------
Here's my earlier review.
The adapter hardware is good, but the driver needs work. I found the autorun installation program clunky. The developers put a visually classy but functionally clunky proprietary user interface on the autorun install program, and for some reason the "choice" buttons are DOA on my XP Professional machine. Cannot even close the autorun install program.
If you have that problem, just run the Setup.exe program directly instead of relying on the UI. Do not plug in the adapter before you run it. Skype should be running before you run setup. But not a fatal error--just rerun the Setup.exe if you're spacey like me. I really gotta read the instructions. My phone hooked up great!
Now my BIG COMPLAINT. This is a telephone adapter that should work 24-7, no matter who is logged in on my multi-user installation, right? Wrong! The driver doesn't install as a Windows service, but runs as a startup application (specified in the Windows registry) under the current user credentials, and requires an Administrator account.
There is an article in the Skype forum that describes how to install the driver as a Windows service. (And it works with similar product drivers from other manufacturers.) You need to do that to support a multiuser configuration in Windows. Otherwise, you'll lose connected calls when you log out. You'll also be unable to use the phone unless a user is logged in as an administrator. If you need to support multiuser logins, or you just want to run the adapter as a service independent of the user login credentials, then I suggest searching for "Dlink DPH-50U Adapter" in the Skype forum, and follow the instructions there to install the adapter application as a Windows service. A note of caution: The article is very detailed, but it's still an advanced user configuration, so if you're timid about opening the Windows registry, get a friend who likes messing around with Windows to help you.
POST SCRIPT to this review:
The hardware is fine. The driver is flaky. If you have installed this product and are dissatisfied with the problems described by various reviewers, uninstall the DLink driver and use the US Robotics driver (
USRobotics USB Telephone Adapter (NAM)). Yes, the US Robotics driver works with this hardware device. On their product web page, click the Support link. 1) Download the appropriate (XP or Vista) US Robotics USB Telephone Adapter Utility from their Web site. 2) Unzip its files to a folder on your local drive. 3) follow their quick installation guide instructions (also available in PDF format on their Web site). When Windows gives you a choice to install automatically or to specify a location, choose to specify the location, and paste in the full path to the folder containing the unzipped US Robotics driver. Make sure that Skype is running before you install the driver and do not connect the adapter until after setup prompts you to (so Windows doesn't attempt a separate driver installation). After I switched to the US Robotics driver I stopped getting dropped calls, inability to dial, and so forth. The DLink driver can only run under an administrator user account. The US Robotics driver, I'm told, can also run under a non-administrator account. The US Robotics driver also appears to support multiple languages, although I haven't configured it for anything another than English, so I cannot confirm. US Robotics, DLink, Kinamax, AU and some similar Skype phone adapters apparently all use the same chip set, as their drivers are interchangeable. US Robotics has a pretty well written Web-based user manual that you can refer to for setup, usage, and configuration. Go to the Skype forums if you get into intractable problems.
Also, if you do install another manufacturer's driver, make sure that you use Add/Remove Programs to remove the original driver before doing an install or you may have problems with the device (or worse--I won't go into my story as most of you aren't as foolish as me, but it required opening Windows in safe mode and reverting to the last successful configuration to get back where I started). Remove the files manually if that doesn't work or if they are left in the installation folder. And if you're comfortable editing the Windows registry, you may want to search for and remove any "TLinkAgent" entries from the registry. For those of you complaining about TLinkAgent appearing on Windows task bar, that's where it's originating--clean them all out and reinstall the drivers.
Post Script to the Post Script:
The support page at Dlink now lists a Vista driver for this hardware device. However, the XP driver appears to still be the original flakey 1.0 driver.
FINAL THOUGHT:
This is an immature technology, so requires some patience and indulgence on the part of consumers. I worked with software developers on version 1 of the Windows IP telephony (at a little software company in Redmond WA), and we're a world ahead now. In just a few more years all dialing will be local. Contrary to what the Telcos might want us to believe, for some years now there has been little cost differential between calling your neighbor across the street and calling the other side of the world. Monopolies have been soaking our pocket books; extracting excessive rents from other (more efficient) areas of the economy. And that goes for all the "special" services cell phone companies now provide--incremental charges for most of those services far exceed the incremental cost of providing them. That's why I love a little gadget like this. Leaves my pocket book fatter than it might have been without the gadget.