I have a windows 7 x86 (32-bit) computer.
Downloaded the driver from here: http://www.ftdichip.com/Drivers/D2XX.htm
Chose the Windows driver for x86 and version 2.08.14.
Plugged usb cable in.
I get "USB Device Not Recognized".
I click it.
Tab pops up called "USB Device Not Recognized" and in bold says "Unknown Device".
I double click it, tab pops up called "Unknown Device Properties". Has General, Driver, and Details tabs. I click Driver.
Has 4 buttons. Driver Details, Update Driver, Disable, Uninstall. I click Update Driver.
Another tab pops up, "How do you want to search for driver software?"
"Search automatically"
"Browse my computer"
Click search automatically, driver still remains as "Unknown Device"
Go through all the steps again, get back to search driver software tab. This time I click "Browse my computer". I've downloaded the driver file to C:/ftdi (a folder that I created for the driver). So I redirect it to C:/ftdi [yes, the file is extracted into that folder] (in the ftdi folder is subfolders called amd64, i386, and Static, assuming those are the drivers I leave the redirect at C:/ftdi.)
Still stays as "Unknown Device".
"The best driver software for your device is already installed. Windows has determined the driver software is up to date." << Bullshit, lol.
No, my usb gecko is not broken. I use it on my windows xp laptop, but that laptop is gay and only has 7gb hard drive, LOL.
No, nothing is wrong with my windows 7 laptop because it's a brand new one.
Any suggestions? Help? Is this fixable?
I had this problem a while back, try a different USB cord.
Where can I find one?
EDIT: Just tested with my Windows XP laptop, even that one has the driver installed and it doesn't recognize it. Where can I get a cord for it?
Isn't that just a general USB port cord you can get at most PC shops?
Well I have a camera that has almost the exact same cord except longer and white, and I've tried to use it before and it doesn't work, so either that cord was only made for that camera or the usb gecko requires a certain type of cord.
Odd. I've used different cords for my Gecko and they work fine...
Isn't it just a regular USB to mini USB cord? You can by them anywhere...
Doesn't Win7 have some issues with USBGecko and its drivers?
So back to two possibilies, one, the cord is messed up, or two, the drivers on windows 7 has issues.
I have only tried the white cord with my windows xp computer, and it didn't work. It's worth a shot to test the cord out on my windows 7 computer, and see if it does anything. I'll get back to this...
Attach the device via USB. Ignore or close any prompts to install the driver.
Go to device manager (start -> run -> devmgmt.msc)
Find the device in question, right click, properties. Go to the details tab. Set the dropdown to "Hardware Ids". What do you see?
USB\UNKNOWN
http://prntscr.com/41h4j < Picture.
Plugged it in with the white cord instead, this is what I get: http://prntscr.com/41h70
This is what it installed as: http://prntscr.com/41h96
^Although I'm not sure if this is correct. Can somebody please tell me.
So now I think it was just the cord all along. I remember, when I first got my usb gecko, I got a crappy cord anyways because it has a red wire sticking out (just a little) at the usb part. I'll take a picture and upload to photobucket.
(http://i575.photobucket.com/albums/ss198/Soulxblade/IMG_0914.jpg)
(http://i575.photobucket.com/albums/ss198/Soulxblade/photo.jpg)
Okay, you can also try looking in the same dropdown but instead of "Hardware Ids" look for "Device Instance Id". The ultimate goal is to find a string which says something along the lines of VID 0403 & PID 6001.
When a USB device connects to a PC, the PC interrogates the device for information about what it is. This is called enumeration. The device identifies itself with a VID and PID. Using these numbers, the operating system determines what driver should be used to control the device.
If you merely do not have the correct driver, you will still see the correct VID and PID, the OS just doesn't know where to get a driver for that device.
If, however, the PC cannot even communicate with the device, then you will have no VID and PID. In this case, either the USB port on the PC, the cord, or the device itself are damaged. Using process of elimination is usually the only debugging option.
Problem solved, used a different usb cord and it works with Gecko dotNET
To say, it only works with WiiRd GUI. Gecko dotNET keeps disconnecting randomly, even right after the game has booted up. I don't know if this is a technical issue with Gecko dotNET or not, and I'm using the latest version. WiiRdGUI works perfectly though, and I've been able to make codes with WiiRd, unlike geckodotnet. I'll just stick to continue using WiiRd, which is what I used before.