M
Marc Kelly
Guest
Hi,
I wonder if anyone else has experienced the following weird thing with
synplify_pro..
This is under linux on a dual core AMD machine (32 bit) with the new QT
based synplify's (9.x versions upto and including the latest beta test
version.)
It will run the first time after booting my machine, but if you quit or
it crashes, then it will not run a second time until you reboot. Instead
it sits at the "initializing license" stage forever, but never seems to
talk to the license server.. HOWEVER the command line version will work
normally, making me think its GUI related somehow..
Currently I am running it under Mandriva 2008, which i know is
"unsupported" hence asking here before going to Synplicity. I am trying
to get hold of a RedHat installed machine at work, or as we mainly use
it a Scientific Linux 4/5 machine. Tests on another Mandriva 2008
machines with a single core cpu didn't have any problems.
Anyone else ever come across this before I delve into it deeper and
consider sort out properly testing it under RH before reporting it?
Cheers..
--
/\/\arc
I wonder if anyone else has experienced the following weird thing with
synplify_pro..
This is under linux on a dual core AMD machine (32 bit) with the new QT
based synplify's (9.x versions upto and including the latest beta test
version.)
It will run the first time after booting my machine, but if you quit or
it crashes, then it will not run a second time until you reboot. Instead
it sits at the "initializing license" stage forever, but never seems to
talk to the license server.. HOWEVER the command line version will work
normally, making me think its GUI related somehow..
Currently I am running it under Mandriva 2008, which i know is
"unsupported" hence asking here before going to Synplicity. I am trying
to get hold of a RedHat installed machine at work, or as we mainly use
it a Scientific Linux 4/5 machine. Tests on another Mandriva 2008
machines with a single core cpu didn't have any problems.
Anyone else ever come across this before I delve into it deeper and
consider sort out properly testing it under RH before reporting it?
Cheers..
--
/\/\arc