Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
46 user(s) are online (28 user(s) are browsing Forums)

Members: 0
Guests: 46

more...

Headlines

Report message:*
 

Re: AmiCygnix OS4FE update1 problems?

Subject: Re: AmiCygnix OS4FE update1 problems?
by cygnusEd on 2017/1/24 15:09:50

@xenic
Quote:
I can't make a direct comparison to JosDuchIt's setup because I use a custom script to start AmiCygnix from a shell but a quick test of starting AmiCygnix and running AbiWord didn't cause any crashes.Since others have reported AmiCygnix working too, maybe JosDuchit needs a reinstall of AmiCygnix.


Yes, I think this could help.

Quote:
AmiCygnix is adding several environmental variables including a PATH variable. Other programs (Linux ports?) set the same variable to a different value. Check the topic "CMake progress" here on Amigans.net and you will see that people are being told to set a completely different PATH variable. I recommend changing all the AmiCygnix variables to something like "CYGPATH" or similar.


Since AmiCygnix 1.0 all programs are using environment variables stored in "ENVARC:Cygnix". The other variables including PATH are only set for the unix shell 'sh'. I know, this can be tricky.

BTW: The PATH variable is only set, if it does not exist before.

Quote:
If I run Snoopy after AmiCygnix has started and I open AbiWord I see this constantly repeated:
lxpanel : o.k. = [exec] FindPort("XGeekTransPort.0") [2uS]
openbox : o.k. = [exec] FindPort("XGeekTransPort.0") [2uS]
Is that really necessary?


This occurs, when "quick transfer" is activated. Please launch "Cygnix:S/Utilities/Quick-Transfer-Off.bat" and it should disappear. This feature will be removed in future versions.


Powered by XOOPS 2.0 © 2001-2016 The XOOPS Project