--- Quote Start ---
The "DependOnService=parport" issue revealed by wmrsouza explains, why ByteBlaster is working with non-legacy parports in some cases and fails in others. In my case, I have an additional legacy port connected to a printer. So the parport service is also started and AlteraByteBlaster can run without editing registry keys.
The problem must be regarded as a ByteBlaster driver bug, that should be reported to Altera support.
--- Quote End ---
I think this problem is not exactly a ByteBlaster driver bug. The default windows service that takes care of parallel port is called "parport", so Altera ByteBlaster installer uses this "default" service name in the field "DependOnService". If our cards use a service/driver with another "name" is very fair we have to fill in that field ("DependOnService") with the correct nname. Thinking this way the bug isn't in the driver but in absence of information regarding to this fact from Altera quartus_pgm docs.
Honored Contributor
