PAUL James wrote:
> I checked the FTDI website and found that the Ap Note to look at is
> AN232B-10 Advanced Driver Options.
> Here is the link..
> http://www.ftdichip.com/Documents/AppNotes/AN232B-10_Advanced_Driver_Opt
> ions.pdf.
>
> Also, check the knowledge base at FTDI for more info.

Yes, I've already checked the knowledgebase, I've read the app note you 
referenced, I even read the MProg manual to try to find the solution.

Adding the IgnoreHWSerNum04036001 key doesnt' work, the COM Arbiter entry in 
the registry still gets incremented. Notice that in the text Xiafan quoted, 
it says:

> Another solution (for in-house testing environments only!) is to edit
> ftdibus.inf to cause Windows to assign the VCP driver only to devices
> attached to a specified physical port or ports, and to cause Windows
> to create a single COM port for all of these devices, even if they
> have different serial numbers. FTDI Chip provides an application note
> with details about how to edit the INF file to accomplish this

and the app note you and Gerhard referred me to, states:

"Note that IgnoreHWSerNum cannot be setup in FTDIBUS.INF or FTDIPORT.INF, it 
must be
setup by editing the registry manually or by an installation utility BEFORE 
installing the
driver."

so it's the wrong app note.

:(

Vitaliy 

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