Intel® Quartus® Prime Software
Intel® Quartus® Prime Design Software, Design Entry, Synthesis, Simulation, Verification, Timing Analysis, System Design (Platform Designer, formerly Qsys)
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
17268 Discussions

Installing Quartus II 11.1 SP2 Web Edition to WinXP SP2 x64 Pro

Altera_Forum
Honored Contributor II
‎09-25-2012 08:59 PM
1,400 Views

I've been able to install Quartus 11.1 SP2 Web Edition on a machine running WinXP SP2 32-bit. However, when I try to install the same exact file to a machine running WinXP SP2 x64 Professional Edition, I encounter the following error almost immediately during the installation: 

 

"WindowsError: [Error 5] Access is denied" 

 

After a bit of googling, I've learned it may be that this is related to running a 32-bit python installer on a 64-bit machine. Apparently there are some issues with 32-bit python accessing the registry in this situation. I don't know if this truly is the source of the problem, but I thought I'd throw it out there. 

 

Has anyone been able to install the 32-bit version of Quartus to a 64-bit version of WinXP? If so, how did you do it? 

 

Thanks, 

--tim
0 Kudos

Link Copied

2 Replies
Altera_Forum
Honored Contributor II
‎09-28-2012 12:11 PM
674 Views

I've opened up an SR for this. The response from them has been poor at best.  

 

Has anybody else out there tried to install Quartus II Web Edition to a machine running WinXP x64? I can't be the only one here, can I? 

 

--tim
0 Kudos
Copy link
Altera_Forum
Honored Contributor II
‎10-02-2012 12:20 PM
674 Views

After contacting support, I was asked to attempt the workaround suggested here. That seems to have cured my problem. 

 

http://support.microsoft.com/kb/925336 

 

In case that URL disappears, you need to edit the registry by going to: 

 

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Safer\CodeIdentifiers 

 

Change PolicyScope from 0 to 1. After installation, change it back to 0. 

 

--tim
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.