Hi eigma,
I believe I can upload attachments in this thread, all info will be in txt/log files, so they aren’t going to be huge and take up valuable board resources. Hopefully, either tonight or tomorrow, I shall run it again, providing as much info as I can. That is the following:
-My current OS.
-Altera USB driver version (as provided by Altera)
-OpenOCD version, with the build options I used (my ‘./configure’ command line).
-The configuration file used with OpenOCD.
-The log of OpenOCD.
As I said in my previous post, even though I’m not a programmer (just a hardware guy who doesn’t give up) it seems to me almost all the problems one encounters are down to the drivers used, as well as how openOCD communicates with them. Even though the USB blaster’s drivers are essentially ‘ftd2xx’, because of the unique VID/PID, one cannot use stock drivers from FTDI, which leads me to believe openOCD is having issues talking to it. That or I’ve missed something obvious, which happens a lot 
Steeeep learning curve right here, never used cygwin before… or config scripts…
Ps. A year ago, after playing about with VB.NET (first time coding for a PC…) I managed to write a small app which used the USB blaster to scan JTAG chains, read IDcodes, erase and verify certain CPLD’s. It was pretty basic, but I had no problems whatsoever communicating with the FTDI chip inside the blaster…altohugh I only ever sent a few commands at a time.