11-03-2012 13:22 - edited 11-03-2012 20:07
I purchased a new Skype cordless phone (this one). The phone requires use of a program called SkypeMate, but is marketed as not needing specific drivers. Basically, at cold boot, the cordless phone fails to work correctly.
- Initially, the taskbar popup appears which states that there is an unrecognised USB device
- SkypeMate says that the USB cable needs to be connected in the system tray
- The phone's handset display just continues to show the USB logo (the pitchfork), just as if I hadn't powered up my computer i.e. it looks like it's never given a signal to "wake up"
- In the Windows device manager, my cordless phone is listed, but it has the telltale yellow problem icon, and its status is given as "This device cannot start. (Code 10)" in the details
- In USBDeview.exe, the device is "Connected: No", "Disabled: No", "Safe to unplug: Yes" at Port_#0004.Hub_#0001
... yet removing the phone's USB cable and plugging it back in makes the device work perfectly, every time. I can make calls, receive calls, it's all great. And if I then reboot, the phone works fine too, until the next time I power down my computer and do a cold boot, e.g. the next morning. ARGH!
(This is especially frustrating since I intended Skype to be used for a family member who isn't technically savvy at all, I just wanted to let it all load automatically after I set it up.)
Other points of note:
- Looking in USBDeview, I can see that once I literally replug it in, the phone is listed as a USB Composite Device, using Microsoft USB Generic Parent Driver v6.0.6002.18005.
- The cordless phone is plugged directly into my computer, not via an external USB hub. All other devices work correctly when using this port. The other items plugged into the in-built USB hub on the tower are my mouse, keyboard and headphones. The power level to this USB hub is 500 mA, at least that's what's given in USBDeview.
- SkypeMate is the latest version (v126.96.36.199, device version 0ACB), and Skype is the latest too (v188.8.131.52).
- My motherboard's BIOS screen has an option to say "yes" or "no" on whether the OS supports plug and play. Toggling this between the two options doesn't seem to make any difference in behaviour. Note that my MOBO BIOS version is the most recent.
Anyway, to resolve this, I did a little batch script that runs on me logging in - you know, basically just mimic the unplug/replug action for me. But that doesn't work, I've tried a few things e.g. disable/enable that particular port, or even remove the internal hub and rescan for hardware - none of that works.
echo Removing the 4-port internal hub...
C:\devcon.exe remove *ROOT_HUB20*
echo Rescanning for hardware
echo Waiting for 30 seconds
ping 127.0.0.1 -n 30 -w 1000> nul
echo Try a disable/enable toggle...
C:\USBDeview.exe /disable Port_#0004.Hub_#0001
C:\USBDeview.exe /enable Port_#0004.Hub_#0001
- Can anyone tell me how I might begin to resolve the fact that my cordless phone doesn't work on a cold boot?
- ... or, failing that, some sort of idea on how I can mimic the physical replugging of the phone's cable? I've done extensive reading on this but can't get this "Plan B" idea to work
Okay, I've also found this Error Report in the Windows event viewer, if it helps to troubleshoot:
Log Name: Application
Source: Windows Error Reporting
Date: 11/03/2012 19:06:34
Event ID: 1001
Task Category: None
Fault bucket 601134676, type 5
Event Name: PnPDeviceProblemCode
Cab Id: 0
These files may be available here:
<Provider Name="Windows Error Reporting" />
<TimeCreated SystemTime="2012-03-11T19:06:34.000Z" />
Upon checking C:\ProgramData\Microsoft\Windows\WER\ReportArchive
Sig.Name=Setup class GUID
Sig.Name=PnP problem code
FriendlyEventName=Could not load driver software
AppName=USB Audio Device
ReportDescription=Windows was able to successfully install device driver software, but the driver software encountered a problem when it tried to run. The problem code is 10.