Help ADB Drivers on XP, How?

[njohnstone]

I have a Galaxy Wifi Player 5 (basically a Galaxy S without the phone part).

Try as I might it will not install the ADB driver on Windows XP (Sp2). I can get it to connect to Kies, as a mass storage device etc. but not as an ADB device.

I've been going through Samsungs provided drivers, and I notice they are using WinUSB.inf which is Microsoft's generic kernel USB driver... the trouble is that this was shipped with Vista onwards, it has to be installed on WinXP and they don't include it (at least that's what I think from note 3 of Microsofts WinUSB page):

Search for [winusb site:msdn.microsoft.com] to see the WinUSB page, I don't have enough posts to post a direct link to the page.

I've played with Google's USB driver and it has the same problem, references winusb.inf which isn't on this Win XP box.

Any suggestions? I read the sticky above, which didn't help.

 

[njohnstone]

Found a fix.

Firstly, WinUSB is contained inside the WdfCoInstaller01007.dll file, this file installs winusb on machines that don't have it.

There's log files during setup to find the problem which I read
c:\windows\setupact.log
c:\windows\setupapi.log

I found that it was trying to install an executable in this folder and failing
C:\WINDOWS\Temp\Win16.tmp\

When I unzip this executable, I found it was an installer for WinUsb.

Running update.exe in this (now unzipped) installer failed saying the "inf integrity couldn't be verified."

I found this link
You cannot install some updates or programs

Method 1 was already correct, cryptographic services are already running.
Method 2, I found cryptographic services would not shut down, I have to kill ZoneAlarm.
However once I got method 2 to work, it fixed the problem.

I could then run the installer to install WinUsb and that installer then worked without the error.

As per the sticky at the top of this forum, I then plugged in the device again, used 'USBViewer' to delete everything related to this device.

Then unplugged it, plugged it in again, then found it installed correctly, and now shows up as an ADB device.

If you have a similar problem perhaps these steps help.