#44978 - blkdog7 - Tue Jun 07, 2005 1:31 am
I went out and purchased the FOXCONN WLL-3350 PCI wireless card for the sole purpose of uploading the E3 demos to my DS.
This card is a RALINK card and is on the list of compatible cards per the link at the Firefly site.
However, I can't make Firefly's driver install properly. I keep getting the little "!" symbol next over the DS icon in device manager.
I am able to install the driver but when I look under the status in the device manager it says:
"Device Cannot Start (Code 10)" and it has the menacing "!" symbol over the DS icon.
when I run WMB.exe it says:
"DeviceFind() failed"
Any ideas? I was so excited to do this today, and I can't get it to work!
Thanks in advance!!
#44979 - blkdog7 - Tue Jun 07, 2005 1:36 am
BTW -- I did check everything out with PCItree and it shows up as it should.
Help!
I am running Windows XP on a 800mz Athlon with SP1.
#44981 - doublec - Tue Jun 07, 2005 1:42 am
Have you made sure there are no other wireless card drivers installed? I had problems when I installed the cards original drivers first. I had to uninstall them (not just disable them) and re-install the DS ones.
#44983 - blkdog7 - Tue Jun 07, 2005 2:06 am
Actually, that's a problem I am having. I can't prevent XP from installing the default driver for this card. Everytime I uninstall the driver/card and then restart or look for new hardware XP finds it and automatically installs the default driver that ships with XP.
Any ideas as to how to prevent this?
#44985 - Sektor - Tue Jun 07, 2005 2:11 am
Try going to the properties of the normal driver, choose update driver and select firefly's driver.
#44986 - blkdog7 - Tue Jun 07, 2005 2:14 am
Sektor, I tried that about 10 times (or more).
I am still getting the little "!" symbol in the device manager.
I get the correct device menu with the DS logo and all of that, but still have that "!' symbol.
#44993 - strager - Tue Jun 07, 2005 2:45 am
I am having the same problem (word-for-word) with another wireless card (PCMIA) on my laptop.
Help us!
#45008 - blkdog7 - Tue Jun 07, 2005 3:35 am
This is driving me nuts, help!
#45009 - FourScience - Tue Jun 07, 2005 3:37 am
Say help again. I dare you.
strager, what card do you have?
blkdog, you said it shows the DS logo in the device listing now. Please confirm that your Device Manager and Driver Details for the Ralink RT2560 Device show the following: http://kleinw.students.cs.ccsu.edu/driverdetails.JPG
If anyone has trouble installing over the "original" drivers for their wireless card, try the following (there's other ways to do this, but this is the brute force approach):
1) Uninstall your driver. Shutdown.
2) Remove the card from your computer. Boot up.
3) Log in to Windows. Shutdown.
4) Reinstall the card. Boot up.
5) Make sure you select manual selection of your driver when it boots up. If it still automatically loads the original driver, this is a Windows XP issue and you must change a few system settings. Look up operating systems support info elsewhere.
_________________
Work in progress: Dual-Soft.com
#45017 - blkdog7 - Tue Jun 07, 2005 4:02 am
I looked everywhere, you can't prevent XP from loading the default driver. It's part of XP.
And yes, that's what my driver is listed as. Exactly that.
#45018 - FourScience - Tue Jun 07, 2005 4:11 am
| blkdog7 wrote: |
I looked everywhere, you can't prevent XP from loading the default driver. It's part of XP.
And yes, that's what my driver is listed as. Exactly that. |
That doesn't make any sense. You are saying that XP is loading the "default driver" (as in original manufacturer's driver), but that your installed driver is listed as the hacked one. Which is it?
_________________
Work in progress: Dual-Soft.com
#45019 - blkdog7 - Tue Jun 07, 2005 4:14 am
BOTH
XP is installing the default driver as soon as I boot the machine or uninstall the driver and then search for new hardware. I never get a chance to not have it install the default driver as soon as it detects uninstalled hardware.
The only way I can get the hacked driver on is to replace the default driver by selecting "update driver". After I do that, I see the hacked driver that your screenshot shows only it has a "!" next to it.
#45020 - FourScience - Tue Jun 07, 2005 4:16 am
| blkdog7 wrote: |
BOTH
XP is installing the default driver as soon as I boot the machine or uninstall the driver and then search for new hardware. I never get a chance to not have it install the default driver.
The only way I can get the hacked driver on is to replace the default driver by selecting "update driver". |
Well it probably won't take effect until you restart. So... use the tool recommended by Sektor in this post: http://forum.gbadev.org/viewtopic.php?t=5941
EDIT:
Step by step instructions:
1) get it here: http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q311272
2) Run:
devcon -m:\\<your_computer_name> hwids *
... this will supply your hardware ID
3) Run:
devcon update <driverpath>rt2560.inf PCI\<hardwareid>
Example:
devcon update c:\ds\driver\winxp\i386\rt2560.inf PCI\CC_0280
Let me know how it goes.
_________________
Work in progress: Dual-Soft.com
Last edited by FourScience on Tue Jun 07, 2005 4:20 am; edited 1 time in total
#45021 - blkdog7 - Tue Jun 07, 2005 4:17 am
When I restart it replaces the hacked driver back with the default OEM one. I'll check out that tool.
#45023 - blkdog7 - Tue Jun 07, 2005 4:20 am
That little app simply automates the "update driver" routine which is what I have been doing. And, i don't need the option to have two drivers. I just want the hacked one, I don't need this wi-fi card for anything other than DS activity. This computer is on the internet via ethernet.
#45024 - FourScience - Tue Jun 07, 2005 4:22 am
Let me get this straight. Before you restart, the device is NOT listed under Network Adapters, but separately as a Nintendo DS - 802.11 -> Ralink RT2560 Device. After restart, it shows up under Network Adapters, and the Nintendo DS - 802.11 entry is gone?
_________________
Work in progress: Dual-Soft.com
#45027 - blkdog7 - Tue Jun 07, 2005 4:28 am
Ok, I just restarted and the card is still listed as a separate item (Nintendo DS - 802.11) and not under network adapters. The driver is sticking, it just has that "!" symbol.
Driver details are as your screenshot that was posted.
#45028 - FourScience - Tue Jun 07, 2005 4:32 am
Please send me a screenshot (post link, or PM me).
_________________
Work in progress: Dual-Soft.com
#45031 - blkdog7 - Tue Jun 07, 2005 4:49 am
Ok, I just did the devcon thing, same results. The big "!"
I'll post a screenshot
#45033 - blkdog7 - Tue Jun 07, 2005 4:56 am
#45039 - zubiac - Tue Jun 07, 2005 8:18 am
wow that's indeed odd.
Doesn't windows ask you if it should install the original driver?
_________________
Abusing Cube and DS with all sorts of homebrew and hacks.
#45044 - Sektor - Tue Jun 07, 2005 8:33 am
Try installing updated drivers for your card, instead of what is included with windows, then update those to firefly's. No reason behind this, it's just what I did.
If it's a PCI card, then try it in a different slot. The ! has to go before it will ever work.
#45067 - blkdog7 - Tue Jun 07, 2005 1:51 pm
| Sektor wrote: |
Try installing updated drivers for your card, instead of what is included with windows, then update those to firefly's. No reason behind this, it's just what I did.
If it's a PCI card, then try it in a different slot. The ! has to go before it will ever work. |
I actually did try this, I installed the driver CD and then installed the card with that driver and then replaced the new driver with the hacked driver.
I'll try another PCI slot, I was thinking that too.
Thanks for the help! If anyone else has any tips, please let me know.
#45272 - blkdog7 - Thu Jun 09, 2005 3:43 am
If anyone cares, I finally got the card working.
I stuck it in another PCI slot and bam! It worked. :)
I must have wasted 3 hours trying to get it to work and all I needed to do was try another PCI slot, ugh!
#45280 - FourScience - Thu Jun 09, 2005 4:09 am
| blkdog7 wrote: |
If anyone cares, I finally got the card working.
I stuck it in another PCI slot and bam! It worked. :)
I must have wasted 3 hours trying to get it to work and all I needed to do was try another PCI slot, ugh! |
Yeah and you wasted our time too, doofus. =D
Just kidding, glad you got it straightened out, man. We all know that in the future, using a different PCI slot is a good idea for similar problems.
_________________
Work in progress: Dual-Soft.com
#45351 - DarkCube - Thu Jun 09, 2005 10:12 pm
had a sound card once with the same problem, device could not start, swapped PCI slots and worked like a charm...