AdhocToUSB on Vista/Win7 x64 FAILPROOF METHOD.

Kai Beginner Joined: 20 Apr 2011 Posts: 26

I know I'm not the only one who had problems getting this to work on a 64-bit machine. I'm also sure many of you have either given up or are still trying to get this to work somehow. You may have even gone out and bought an adapter instead.

I will try to keep this very simple and concise. The only problem with this guide for 64-bit users is installing the PSP Type-B USB Driver. Here is a flawless method to getting this driver to work correctly on your machine.

Pre-Steps
Follow the above guide to the point that it requires you to install the PSP Type-B USB Driver. This means you should be running 5.03 Gen firmware or above, have the AdhocToUSB plugin installed and enabled, WinPcap installed, the Microsoft Loopback Adapter installed, and xLink Kai configured. Once all of this has been completed, follow the steps below:

Step 1
Ensure that UAC (user account control) is disabled. This can be done from control panel -> user accounts. It requires a restart.

Step 2
http://www.ngohq.com/home.php?page=dseo
Download and run this tool.
Hit "Next" and then "Yes".
Select "Enable Test Mode", and hit Next. You will receive a confirmation dialogue box. Hit OK.

(OPTIONAL: Select Remove watermarks and hit next. You will be taken to a page where you can download a tool to remove any watermarks that will appear on your desktop due to test mode being enabled. Cosmetic purposes only.)

Restart your machine.

Step 3
http://voxel.dl.sourceforge.net/project/libusb-win32/libusb-win32-releases/1.2.4.0/libusb-win32-bin-1.2.4.0.zip
Download and extract this archive.
Plug in your PSP.
Run bin\inf-wizard.exe from the extracted archive.
Hit next.
Find and select your PSP in the list, and hit next.*
Hit next again and save the generated INF file anywhere you like. It may be deleted afterwards.
Hit Install Now.

*If your PC does not detect the PSP [i.e. it does not appear in the list of devices], your AdhocToUSB configuration is incorrect. Ensure that it is enabled and that you are in-game! Also, the PSP must be plugged in PRIOR to launching inf-wizard.
EDIT: other plugins may be interfering with the USB connection between your PC and PSP. You can try disabling all plugins but AdhocToUSB if inf-wizard refuses to find your PSP after plugging it in. It should be noted that this is not only for install purposes, but these plugins will also interfere when you actually want to play.

Restart your machine.

That is it!

Follow the rest of Hawk_The_Slayer's guide as normal.

Notes on this method:
If you ever plan to install unsigned drivers in the future, you will not have any problems. The tool in step 1 enables driver testing mode permanently. This also means you will not have to disable driver signing enforcement every time you boot!

Kai Spammer Joined: 28 Jan 2009 Posts: 1794

Odd how people keep having this sort of problem since the workaround had already been explained in the guide.

Quote:

FOR 64-BIT WIN 7 USERS:

In case your computer is 64-bit, you'll have to manually install the drivers provided in this link (it's the '.inf' file):

http://www.mediafire.com/?byjotibzj8t92c0

Guess this hasn't been highlighted enough. I don't know, it worked on mine just fine.

Well, let's hope your tip is universal then.

Kai Beginner Joined: 20 Apr 2011 Posts: 26

Nah, I saw it. I had it working that way too. I've had experience however, with installing unsigned drivers manually because I use XBCD to use my xbox 1 controllers on my PC haha. This is a much more guaranteed and simple method IMO.

Aside from being easier, users no longer have to enable unsigned driver support on every boot. That is definitely a plus.

edit: i'd actually like to also say that the inf provided in the link did not work for me, what I had to do was very strange. I had to disable driver signing enforcement, testsign the libusb0 and libusb0_x64 drivers, install libusb0 (which did NOT work), and then rename and copy libusb0_x64 over libusb0 in my system folders. I've come to realize now that I should have also put the dll files in the appropriate folders, which I did not. I don't find it hard to believe at all that not many people were able to get this to work on their 64-bit machines.

Kai Beginner Joined: 21 Apr 2011 Posts: 1

thx for this guide really help me from driving me insane.....

btw is cwcheat.prx and peagasus.prx must really been turn off to make this work ??
isn't both doesn't mess up with the usb connection right ???
since I can't make the inf-wizard.exe to detecting my psp before i turn off both...

Kai Beginner Joined: 20 Apr 2011 Posts: 26

Haha no problem! Very Happy

I'm glad it worked for you.

I'm not familiar with the pegasus plugin or what it does, but I personally have CWCheat and know that, no, it will not interfere with AdhocToUSB.

I guess you could experiment by trying different combinations of plugins active along with AdhocToUSB. I'm glad to see that you were able to find out why your PC wasn't detecting the PSP. I'll add that to the first post!

Kai Spammer Joined: 28 Jan 2009 Posts: 1794

Wait, so did the guide's method work for you or not?

I mean,

Quote:

Nah, I saw it. I had it working that way too

Quote:

edit: i'd actually like to also say that the inf provided in the link did not work for me, what I had to do was very strange.

Anyway, guess Hawk is going to edit his guide with your tip.

I was the one who reported said method, actually. I recall I messed with some settings beforehands but I though they were of no importance, that it still would have had worked for someone who applied it out of a formatting.

Better applying yours then.

Kai Beginner Joined: 20 Apr 2011 Posts: 26

Well, in the guide, all it really mentions is that you'll have to install it manually. Many people reading this may not realize that:
1. you have to disable driver signature enforcement
2. windows is a ^#%$! and won't do it for you anyway.
The first time, I assumed the inf was built properly and what I did was something like this:
- disabled driver signature enforcement
- testsigned both libusb0.sys and libusb0_x64.sys just in case..
- ran the new hardware wizard and pointed it to the provided inf file

no results. I mean, it installed, sure, but I was left with a code 39 error. I found that manually going to the system drivers folder and replacing the installed libusb0.sys with libusb0_x64.sys renamed to libusb0.sys had it working, I think...
The driver was reportedly functioning correctly, however at this point my PSP was still running 5.00 m33-6 and froze and turned off when bridge tried to interact with it.. Embarassed

I then installed the driver in this method and upgraded my PSP firmware at the same time, without testing in between haha but I assume I did have the drivers working properly and it was just the PSP end that was screwing things up.

So basically I did have the driver provided in that download working, but it took some fiddling is what I mean. Not everyone is really fit to be fiddling with drivers and whatnot, and there isn't really any definitive guide out there on manually installing drivers and bypassing 64-bit driver signing enforcement correctly.

This is a much cleaner method than installing manually, and the fact is that most people aren't so good with these things haha and may not be able to get it to work.

Kai Beginner Joined: 08 Jun 2010 Posts: 5

I've posted a guide some time ago that explains in detail how the program works, and yes, it indeed works that way.

click here for the guide

Kai Beginner Joined: 20 Apr 2011 Posts: 26

I actually ran across your thread shortly after posting this guide haha Wink

My guide also uses different drivers though, so it's not exactly the same thing haha. Great program though Wink

Team XLink Administrator Joined: 02 Jul 2006 Posts: 965

As per Narolfs prediction, http://www.teamxlink.co.uk/forum/viewtopic.php?t=39586 updated. Thanks Zedd56 and CaptainFlameGuy Smile

Kai Beginner Joined: 28 Apr 2011 Posts: 9

i can't locate the psp in the lists of devices.
I folowed the tutorial and i'm still confused on how to get it back up.
Please help me D:

Kai Beginner Joined: 28 Apr 2011 Posts: 9

^^
When ever i plug in my psp now, theres no icon that show that its there!
I can't even do anything now

Kai Beginner Joined: 20 Apr 2011 Posts: 26

Sorry I'm kinda late on this!

Hawk, great to see the edit! Very Happy

Two big thumbs up to you and your guide, by the way Smile

5tev3n, I suggest you turn off all other psp plugins, double check to make sure that you've followed step 2 correctly, and make sure you restart your machine when necessary.

The only interfering elements I can think of are other PSP Plugins. Maybe try another usb port or cable as well, I guess.... basic troubleshooting. I can't really tell you what's wrong for sure, but I guess just go real slow and give it another try! Let us know how it goes Smile

Kai Beginner Joined: 17 Mar 2011 Posts: 2

hey guys. I'm running windows 7, 64 bit and I used the .inf method to install type B (I saw it say that) and I tested it with remotejoy and it works, but my psp isn't detected in the bridge (yes, I press the number with the loopback driver). Anyone have any ideas?

Thanks Very Happy

Kai Beginner Joined: 20 Apr 2011 Posts: 26

The inf method failed for me. Without some odd renaming and replacement of files, those drivers won't work normally. Try the installer in this guide!

edit: oh, it works with remotejoy..........? that's rather strange.... hmm
do you have libusb0.dll in the same folder as bridge.exe? Disable remotejoy and try again!

Kai Beginner Joined: 27 Jun 2008 Posts: 1

I had the same problem as 5TEV3N. Got it back to normal by going to device manager and uninstalling the psp under "libusbdevice" (or something along those lines).

Kai Beginner Joined: 09 Jun 2011 Posts: 2

When I installed the file, it detected my PSP as PSP type A instead of PSP type B. My PSP is PSP Go ver. 6.20 TN-D. Is it because my PSP is PSP Go so it is detected as PSP type A? Please help, the bridge file couldn't detect my PSP. Sad

Kai Beginner Joined: 12 Jun 2011 Posts: 5

when im at inf-wizard part, it say my psp was type A. im using psp 3k btw. i cant see others ppl games nor others join my game.
is that the reason im using 3k and make me type A? and others was type B?

Kai Beginner Joined: 20 Apr 2011 Posts: 26

Daveiant and 5TEV3N,

Make sure that your adhoctousb (or ANY plugin that utilizes a low-level USB connection) is NOT enabled for XMB (aka VSH), and is only enabled for GAME and/or POPS.

This way, the plugin won't override or interfere with the normal USB connection that you get in the XMB that allows you to transfer files to/from your memstick and such.

Also make sure that your firmware is a version that's compatible with AdhocToUSB and make sure that you've downloaded the corresponding version of the plugin.

As for the Type-A issues, the libusb drivers should work for both type-a and type-b psp's. It's a universal driver installer and it creates the driver corresponding to your device when you run it (that's why it asks you to select your device) so it should never be incompatible. I'm not sure why bridge isn't picking it up..

Raggy, is bridge detecting your PSP?

Kai Beginner Joined: 30 Jul 2010 Posts: 15

Narolf wrote:

Odd how people keep having this sort of problem since the workaround had already been explained in the guide.

Quote:

FOR 64-BIT WIN 7 USERS:

In case your computer is 64-bit, you'll have to manually install the drivers provided in this link (it's the '.inf' file):

http://www.mediafire.com/?byjotibzj8t92c0

Guess this hasn't been highlighted enough. I don't know, it worked on mine just fine.

Well, let's hope your tip is universal then.

think this is better then using that tool.
make win 7 x64 allow unsign divers all the time.
ReadyDriverPlus

much better then having to press F8 or not knowing if that tool worked.