At 08:06 AM 11/27/2003 +1300, steve@TLA.CO.NZ wrote:
> > I am thinking that it is not the programmer, but something probably in
> > the USB driver interacting with different versions of Windows.  But I
> > don't know how to narrow this down.
> >
> > I have tried it on the following machines.
> >     Windows XP Pro (no SP) Notebook - works
> >     2x Windows ME (unknown SP) - works
> >     2x Windows XP Pro SP1 desktop - does not work
> >     Windows 2000 SP3 desktop - does not work
> >     Windows XP Home SP1 notebook - does not work
>
>There are issues with WinXP SP1 (it may be the same with Win 2k
>SP3) and the FTDI drivers. See www.ftdi.com for an explanation and a
>long winded fix.
>
>I've just been through this in the last couple of days.
>I found that if you remove any reference to FTDI in the Add/remove
>programs and then specify a location at the driver installation phase, it
>will load up your drivers correctly. There may be situations where that
>doesn't work, but it was enough for my needs.


Hmmmm - I tried those fixes.  What it boils down to is to uninstall the
driver and then reinstall, but to NOT use the Windoze automatic search but
instead install the drivers from the file that you download from
www.ftdichip.com

I had already been careful to point to those downloaded drivers when I
first set up the USB device as I've run into similar issues before with USB
drivers before.  I skeptically tried uninstalling and reinstalling the USB
drivers and as I figured I would I am still having the same problem.

Does anyone have any information as to the protocol between the PC and the
K150 programmer?  Is there a software based USB "sniffer" that I could
employ to see if that protocol is being carried out correctly or to give me
an idea where the problem might be?

Thanks!

Dan

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.