I had seen a topic like this in another thread, but it was old and a bit buried, so I thought I'd post a new one.
Basically, when I power my PC on, I can't use the PS3IR-1000 with the software utilities until I unplug it and replug it, despite the fact that Windows knows it's there (it shows up in Device Manager), and the light on the device is on. This is a bit of a vulnerable thing for me because I'm trying to get a remote environment set up, where I might not be on the same coast or even in the same country with the PS3. Clearly, I can't take a flight back home just to replug a USB cable.
I can hope that my PC will maintain power, but stuff happens (power failures, etc).
I have tried this on two different computers, one a Dell desktop PC with Windows Vista Ultimate (SP2), and the other a Dell laptop with Windows XP Professional (SP3). Both exhibit the problem.
The problem I see is that the utilities come up with the red bar on the bottom saying "Please connect your PS3IR-1000", and on both systems, the apps become "not responding". This is a different state from when the device is simply not plugged in. In that case, I still get the red bar and the message, but the apps are responsive. In fact, when I boot up with the device plugged in and the utility apps go unresponsive, if I unplug the device at that point, then the apps become responsive again. So they are doing *something* with the device. Again, it shows up in Device Manager, so even Windows knows about it.
I made some attempts to find a workaround for this. My thought was: can I simulate a USB disconnect and reconnect? I was able to do that eventually, but it didn't solve the problem. I'll describe that because it might provide some clues as to what's going on.
I found a Microsoft utility called "devcon". (http://support.microsoft.com/kb/311272
) With this tool, I can remove and rescan USB devices, based on name (using "devcon remove xxxxxx" and then "devcon rescan").
What I found is that if a utility app is running, then devcon will say "remove at reboot", since it is not able to actually remove the device at the time. And the device (obviously) is not removed. If a utility app is *not* running, then the device is removed directly. To my programmer brain, this means the utility app does indeed have the device opened, and Windows/devcon is not able to remove it at that time because it's "busy". So... the utility app has found the device. Why does it think it's not plugged in then?
Well, perhaps it's not a question of it not knowing the device isn't plugged in. Perhaps the app finds the device and attempts to talk to it, but something in the communication protocol is going awry, and the app ends up hanging. If the device is unplugged, then the app stops trying to communicate and becomes responsive again, and when the device is replugged, everyone is happy.
I don't know if this a utility app issue or a firmware issue, but it's a definite issue. There is clearly a difference in state between the device being already plugged in at boot time and the device being plugged in post-boot.
When I get devcon to remove the device, the utility app becomes responsive again. So I have, in effect, removed the device. And when I do "devcon rescan", I see the little windows popping up saying it's installing my device. And then it shows up in Device Manager again. But the utility apps still don't work. Something about physically plugging it in is putting things in a different state.
Any thoughts on how to resolve this (even a workaround I can do) will be much appreciated. Otherwise, I may need to look for another solution.