Chris Smolinski wrote:
> >So, with the latest drivers from FTDI, all you have to do, is add this 
> >entry
>>to the registry:
>>
>>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\UsbFlags\IgnoreHWSerNum04036001
>>
>>and set its value to 1. Works like a charm.
>
> I finally tried this yesterday, and managed to render XP unable to
> boot. Eight hours later, after various attempts to repair things, I
> finally did a fresh install.

That's very odd, I'm sorry to hear that. I tried this procedure on several 
machines (including XP & Vista), and it worked fine for me. As another 
poster has pointed out, perhaps you need to run FTClean before making 
changes to the registry.

My reasons for doing this were the same as yours -- we program many hundreds 
of FTDI chips per month, and having to reset the port using a batch file 
prior to programming got really annoying.

> While I was waiting for the installation to finish I took a look at
> the D2XX driver for Mac OS X, and the examples that came with it. In
> about 15 minutes I managed to put together a program to read the
> FT232 EEPROM, make the necessary changes to the values (invert TX
> line and rename the device in my case) and write it back to the chip.
> So now I can do all this on the old iMac sitting down in the lab, and
> not have to touch in infernal windows box for this task. I just wish
> I would have tried doing this *before* messing with the registry.

Normally you would want to back up the registry before messing with it (I 
know, hindsight is 20/20), so you can restore it when things go wrong.

I appreciate you bringing this up, as the solution offered definitely made 
things less tedious for the guys doing the programming.

Best regards,

Vitaliy 

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist