Forum Discussion
Altera_Forum
Honored Contributor
15 years agoAfter 3 weeks of tech support, I've given up and gone back to running Quarus 9.1 SP2, which appears to be more stable. The best gues appears to be some problems with conflict with HP PCL6 print spoolers if you have the wrong HP drivers are installed. I ran Quatus using the Visual C++ 2008 debugger, and found:
My working Quartus 10 installation generated numerous first chance exceptions of the form: First-chance exception at 0x7c812afb in quartus.exe: Microsoft C++ exception: long at memory location 0x0012ccd8.. First-chance exception at 0x7c812afb in quartus.exe: Microsoft C++ exception: CExceptSetLastErr at memory location 0x0012ccbc. My non-working Quartus 10 installation reported loading and unloading of HP PCL6 print spool drivers here (Why? I don't understand) 'quartus.exe': Loaded 'C:\WINDOWS\SYSTEM32\spool\drivers\w32x86\2\HPBAFD32.DLL', Binary was not built with debug information. 'quartus.exe': Unloaded 'C:\WINDOWS\SYSTEM32\spool\drivers\w32x86\2\HPBAFD32.DLL' Quartus 9 does neither of these things. Best guess, is that Quartus QT package gets confused about linking up some spooler requirements, and this process needs to fail, or the command/report pipeline gets disrupted. This could be why Quartus cannot capture any reports or output from the modules. Speculation at best...