Re: FTDI driver installation problems
- From: Mike Harrison <mike@xxxxxxxxxxxxxxx>
- Date: Mon, 30 May 2005 08:51:27 GMT
On Sun, 29 May 2005 22:48:37 -0500, "James M. Knox" <jknox@xxxxxxxxxxx> wrote:
>I found a similar problem in an earlier thread, but not really a
>solution...
>
>I am trying to install the FTDI FT232BM VCP driver on a Windows 98 system.
>The system won't "pick up" the driver. It recognizes the USB device
>(unknown) when I plug it in. It then insists on automatically attaching
>its own USB driver. I can tell it to "update driver" and point it to the
>directory where the FTDI driver is located. However, it insists that it
>knows better (the best driver is already installed) and won't update.
>
>I've tried removing the "unknown device" and doing it over, no change...
>
>Any ideas? [FWIW, I am currently using the FTDI FT232BM without an
>EEPROM.]
>
>tnx, jmk
It makes life a whole lot easier if you use the eeprom and prorogram a product ID (PID) into it
(FTDI will allocate you one if you ask them). You just need to update the driver .INF files
(described in th ehelp files of FTDI's MPROG eeprom-programming utility). That way it will always
look for a driver for your specific PID and ignore any previously installed drivers.
.
- Follow-Ups:
- Re: FTDI driver installation problems
- From: James M. Knox
- Re: FTDI driver installation problems
- References:
- FTDI driver installation problems
- From: James M. Knox
- FTDI driver installation problems
- Prev by Date: Re: FTDI driver installation problems
- Next by Date: Re: ATtiny13 replaces tiny11/tiny12?
- Previous by thread: Re: FTDI driver installation problems
- Next by thread: Re: FTDI driver installation problems
- Index(es):
Relevant Pages
|