Il giorno domenica 1 settembre 2019 alle 18:12:53 UTC+2 silverdr ha scritto:
> On 2018-06-13 03:02:50 +0000, abner...@ieee.org said:
>
> > On Wednesday, June 15, 2016 at 9:41:35 AM UTC-6, silverdr wrote:
> >> So far I downloaded and installed the ispLEVER from Lattice, which is
> >> still available and supports "obsolete" devices like GALs. The problem
> >> is that when I try to do some synthesis using
> >> ispLEVER/PureVHDL/Synplify/ project I get output like:
> >>
> >> *******
> >> Starting: 'C:\ispLEVER_Classic2_0\ispcpld\bin\Synpwrap.exe -e r512vhdl
> >> -target ispGAL -pro '
> >>
> >>
> >> Copyright (c) 1991-2010 Lattice Semiconductor Corporation, All rights
> >> reserved.
> >> Version : 2.0.00.17.20.15
> >>
> >> Done sucessfully with exit code 1.
> >> Error output EDIF file c:/documents and settings/silverdr/my
> >> documents/sources/vhdl/r512/r512vhdl.edi
> >> Error executing Synplicity VHDL/Verilog HDL Synthesizer with code 2
> >>
> >> Done: failed with exit code: 0002.
> >> *******
> >>
> >
> > I have the same problem... when I do Synthesize there appears the next error:
> > Error output EDIF file c:/isplever_classic2_0/examples/ESumRes.edi
> > Error executing Synplicity VHDL/Verilog HDL Synthesizer with code 2
> >
> > ...
> > How did you fix it?
> After spending indecent amount of time trying to troubleshoot the
> problem, insrtalling, reinstalling, and exchanging emails with friendly
> people from Lattice, I worked the issue around by running the software
> in question in a Wine based Windows emulation. As strange as it may
> sound, that was the best option for me but below is a summary of my
> "research" on the subject:
>
> - Windows XP Home SP2 (fresh install) – no luck
> - Windows XP Pro SP3 (fresh install and available updates) – no luck
> - Wine based Windows XP emulation – runs (sic!)
> - Windows 10 Pro 64 bit installed from scratch in a virtual machine – runs
> - Windows 10 Pro 32 bit installed from scratch in a virtual machine - runs
>
> Looks like there's some kind of problem with "native" Windows XP support.

Hi,

after facing same problem, I got it working in XP by installing: .NET Framework 3.5SP1, .NET Framework 4.0, VCredist x86 from 2003 to 2012

Regards
D