#12300 - shake - Fri Nov 07, 2003 4:12 am
hello all,
this may seem like a stupid question but....
i have installed the f2a usb driver and everything works perfectly.
but, whenever windows 2000 boots up, i get a "at least one driver or service failed to load, see event viewer for details". checking event viewer does not shed any light on the situation. the flash writer works fine, but this error message is really annoying. i even tried formatting the hard drive and just re-installing the f2a driver and i get the same thing every time. anyone know what is causing this or how to get rid of it?
thanks!
shake
#12303 - tepples - Fri Nov 07, 2003 5:55 am
If a driver fails to load, you'll see a yellow triangle with a black ! mark in Device Manager. To see what services didn't load, try Adminstrative Tools > Services.
_________________
-- Where is he?
-- Who?
-- You know, the human.
-- I think he moved to Tilwick.
#12305 - shake - Fri Nov 07, 2003 7:34 am
i checked the device manager. no triangles with the explanation mark...
#12424 - bizlap - Wed Nov 12, 2003 7:04 am
shake,
im having the exact same problem of the annoying error message on startup.. im running in w2k server.. let me know if you find a solution.. i'll let u know as well..
#12436 - gb_feedback - Thu Nov 13, 2003 10:12 am
Sorry to be so vague on this, but I have a recollection that I have seen a fix to this. Someone I know had the same problem I think, and there is a known fix. I believe that the problem stemmed from 2 copies of the ezusb driver being loaded, both having the same name. The fix involved renaming one of them. Sorry I don't have a link, but knowing it's out there may help. [Hint: check the emulation groups]
_________________
http://www.bookreader.co.uk/
#12438 - shake - Thu Nov 13, 2003 10:35 am
actually,
2 drivers *do* get loaded.
first, i install the f2busb.inf driver after i plug in the f2a cable.
driver installs fine.
when i boot up gba writer (v1.1 i think) it goes through a "detect new hardware" thing and installs *another* driver. does this every time.
i even tried a fresh install of 2000 and *not* installing the f2a driver first. just by launching the f2a writer app, but no go.
maybe we're on to something?
shake
#12440 - gb_feedback - Thu Nov 13, 2003 11:55 am
shake: this may not be a solution to your particular problem, but...
In the http://www.emuboards.com/cgi-bin/ikonboard/ikonboard.cgi forum: Emuboards ? GBAEmu ? Flash2Advance (Parallel & USB) ? usb driver modification (posted May 10th - you'll have to dig) is a possibly related thread. Or possibly not - sorry if it doesn't help.
_________________
http://www.bookreader.co.uk/
#12449 - ecurtz - Fri Nov 14, 2003 6:30 am
Most of the issues people have with the f2a drivers come from the fact that the manufacturer didn't bother to give the device a unique USB vendor/device signature. Instead it uses the generic "ezusb" development kit codes. If you've installed any other hardware where this is also the case (it apparently isn't uncommon) then you can get hardware conflicts.
I don't use Windows so I can't help with specifics, but I'd try unistalling drivers for any old usb devices you're not using. I'd especially look at usb modem drivers, which are notorious for this.
- eli