--- Quote Start ---
Great!
Huh? The FTDI drivers and DLL install fine under Windows. Its getting it to allow the DLL to access the USB-Blaster that I'm not sure how to do, given that the add VID/PID DLL call does not exist under Windows.
--- Quote End ---
Yes, that is sort of what I meant - yes the drivers and dll work great, but I can only load devices with different PIDs in XP, in Windows 7 I have to change the PIDS back to the standard value.
But the ftdi dll seems to be able to access the usb blaster fine :
ftlstndev
1
ftgetdescriptions
USB-Blaster
ftopen 0
FTDI USB device 0 opened, Handle : 40973760
40973760
But now I am not sure what will happen to any data I write to the handle ....
ftclose 40973760
0
--- Quote Start ---
A pretty simple solution is to use FT_PROG to capture the EEPROM settings from your USB-Blaster, and then erase the EEPROM. Then your USB-Blaster will appear as an FT245BM device, and you can access it using the DLLs directly (since the VID/PID will be FTDI).
--- Quote End ---
Scary, but that sounds good. I have had no problems using the EEPROM erase and write to-date. Do I then have just an 8-bit port in effect ? I will read up the info you pointed me to. Thanks!
Honored Contributor
