Just crashes here.

I've tried it with all of the different video driver options. I guess I'll just have to play with it a bit more.

Is it a problem to use the P96pip video driver on a 32bit Workbench screen (when the most Cygnix is capable of is 16bit)?

Working great here on AmigaOS 4.0, very impressive.

@ PEB

> Is it a problem to use the P96pip video driver on
> a 32bit Workbench screen (when the most Cygnix is
> capable of is 16bit)?

Looks like 16 bit is the way to go for now, from the AmiCygnix-en.guide:

24 and 32 bit screenmodes are not working and mostly the 8 bit modes too. This is a problem of the X server.

@ PEB

When does it crash? Does the server crash immediately? You could try to launch the programs one after the other in a shell window to find it out. You also will see error messages there.

Example:
> Cygnix:CygnixPPC/X11R6.3/bin/XGeekPPC :0 -pri 0 -screen CyberGraphX@1024x768x16
> Cygnix:CygnixPPC/sbin/esd -port 16001 -nobeeps
> Cygnix:CygnixPPC/X11R6.3/bin/Esetroot -scale /Cygnix/CygnixPPC/share/pixmaps/backgrounds/AmiCygnix_1024x768.png
> Cygnix:CygnixPPC/bin/openbox
> Cygnix:CygnixPPC/bin/lxpanel
> Cygnix:CygnixPPC/bin/idesk


As the workbench window is an overlay window, you should be able to use a 16bit window on a 32bit Workbench without problems.

@PEB

Also you must not install it on JXFS. It crashes here too.

On SFS2: perfect.

@CygnusED

Fassssst!!! Wonderful job.

Works fine also here on my Sam

Thanks

@Elwood

Quote:

Thanks for pointing this out. That was the problem. Upon reinstalling it to an SFS partition, I noticed the important ReadMe window that pops up mentions this very thing. Unfornutely, on my initial install, I did not read this important ReadMe window

Anyway, all is good now. Thanks, Edgar, for this great piece of software!

@nubechecorre

How is speed on the SAM, is it fast enough?

@Elwood

Quote:




@all

Have fun

I've just installed the new AmiCygnix V1.0. The installation process was easy and without problems. Unfortunately, for me it doesn't work as good as the previous Cygnix version.

I mainly used Cygnix to display remote programs like skype, firefox, etc. For this i opend a amiga shell and typed:

ssh -X login@X_remote_machine

and then I could start my X applications.

With the new AmiCygnix it doesn't work anymore. I get the error:

"xterm Xt error: Can't open display:
xterm: DISPLAY is not set"

So it seems, that the new AmiCygnix is not recognized as X-server?

Anyone knows what the problem here is?

Regarding the speed issue, I think on Sam440ep, AmiCygnix is too slow. I tried to use NetSurf in order to post this comment here. It was not possible. Keybard input was too slow to type anything??? Though, with the previous Cygnix version and an remotely started firefox I was able to post somthing ..
I have not used Abiword on any Cagnix version so far and therefore, I can't say if there's a speed difference here.

What I really miss with AmiCygnix is an Xterm (or any other unix terminal) Any chance for compiling one? From my imagination, this should be easier than compiling abiword or NetSurf

Anyway, great job! But i guess, i will use the previous cygnix version again if I can't start remote applications with AmiCygnix.

nexus

@nexus

I think the problem is, that the DISPLAY environment variable is not set. The environment vars for AmiCygnix are stored in a subdirectory (ENVARC:Cygnix). Try to set the variable by hand:

setenv SAVE DISPLAY <hostname>:0


The speed problem is new to me. I have no idea, what's wrong here. The X server is not as fast as native amiga programs, but fast enough to type in text without problems. Are any other network programs running at the same time?

You could try to refresh the cache files. Call this script (when AmiCygnix is not running): "Cygnix:S/Utilities/Refresh-ALL-Caches.bat"


I really like to have xterm too, but the problem is, that I don't have a unix compatible terminal device. Ixemul has a builtin one. I was not able to implement it by myself.

CygnusEd

The variable:

Cygnix/DISPLAY

ist set to:

localhost:0

and hostname is set to localhost as well.

I pretty sure, this was the case for the old cygnix version, too.
I set DISPLAY to "<ip-address>:0". It still doesnt work.

thanks for your quick response!

nexus.

I set that DISPLAY environment variable during AmiCygnix was already running.

After trying to shut down X (by pressing the shutdown-button in the X environment), AOS4.1 froze!
Rebooting and restarting AmiCygnix caused AOS4.1 to freeze again. I rebooted and tried again. No luck. Then I relized, AOS4.1 always freezes during starting of AmiCygnix unless the DISPLAY environment variable was set to "localhost:0" again!

With localhost:0, starting and shuting down X works perfectly. Changing the variable to <ip-adress>:0, causes AOS4.1 to freeze!

Weird?

nexus

@nexus

Hmm - yes, weird.

You could contact Yakov Mindelis (Jack) for this. He uses AmiCygnix for remote programs too and it works for him. I have not much experience here.

Hello CygnusED

for user like me, actually on AOS3.x classic amiga, what mean:

1. AmiCygnix is a Unix environment ??? (A new linux like debian or an amiga coded program who launch unix programs)

2. Porting easily unix program ?? (need compile unix program on a C compiler on amiga or just change program settings- or between). I'm curious to know the skill needed to port something on amicygnix (even if I'm not a coder at all).

@Mrodfr

To 1: Unix environment means, that the data is organized in the same way as under Unix:

- AmiCygnix provides a typical unix dir tree. This includes a home directory for the active user.
- The data is stored into the dir tree like under a Unix system.
- The typical environment variables are also available.

To 2: You need to compile the programs with a C compiler. The result is a native binary.
Everything mentioned above makes porting easier. But the main advantage of AmiCygnix is the availability of the GUI toolkits like GTK2, wxWidgets or Motif. A simple program can be compiled with "./configure, make, make install" just like under Unix.

Wohoo .. got AmiCygnix to work with remote applications

You have to set DISPLAY environment variable not in Cygnix/DISPLAY.

setenv SAVE DISPLAY=localhost:0

does the job and you can forward x-applications, like skype to AmiCygnix! Great!

Thanks for this great and usefull Application


Now an local xterm and the possibility to start X-apps directly on the workbench and not only on an separate screen (or within one window), and I call you divine CygnusEd

nexus

P.S Merry Christmas!

@nexus:

Quote:

ssh uses DISPLAY. just set DISPLAY's content to the value of Cygnix/DISPLAY, I did it permanently.
The value can be either localhost (127.0.0.1) or the hostname (net card's IP address).
The later gave better peformance in earlier versions of cygnix with some local apps (see FAQ).
It's not SSH fault, but side effect of grouping cygnix' env vars in a separate directory.

Authorization when forwarding is standard:
xhost + remote_IP (once under AOS)
"setenv DISPLAY " or "export DISPLAY=" followed by your_IP:0 in every login instance you want to froward graphics from.

Or instead of "xhost + ":
12.AOS4.1:> more Cygnix:CygnixPPC/etc/X0.hosts
localhost
aetpy
cart
aeone


If some remote apps such as mozilla/firefox/seamonkey and grip fail (don't remember the err message atm). Solution is to disable keyboard extension, I modified the launch script:

12.AOS4.1:> grep -n kb Cygnix:s/Start_XGeek.bat
20: Run >NIL: <NIL: Cygnix:CygnixPPC/X11R6.3/bin/XGeekPPC :{DISPLAYNUM} -kb -pri 0 -screen CyberGraphX@800x600x16
23: Run >NIL: <NIL: Cygnix:CygnixPPC/X11R6.3/bin/XGeekPPC :{DISPLAYNUM} -kb -pri 0 -screen `GetEnv Cygnix/CYGNIX_SCREEN_MODE`

And last one, to extend keyboard functionality, I enabled startup script in config gui (the script is Cygnix:s/User-Startup) and put there this:

12.AOS4.1:> tail -n 1 Cygnix:s/User-Startup
xmodmap /home/.xmodmap

where:

12.AOS4.1:> type home:.xmodmap
keycode 80 = Page_Up
keycode 81 = Page_Down
keycode 83 = F11
keycode 119 = F12
keycode 120 = Home
keycode 121 = End

xev was used to find out the keycodes , see it's and xmodmap's man pages for more details.

Jack

Hi Jack,

If i set Cygnix/HOSTNAME to my local ip address and Cygnix/DISPLAY to HOSTNAME:0 then AmiCygnix doesn't start anymore but the whole AOS4.1 freezes as soon as the grey background of the X-Server appears.

I have to set everything to localhost:0. Then it works.

greetings,
nexus

Add lines "localhost" and "your-ip-number" (two lines) to cygnix:cygnixppc/etc/X0.hosts.
There's no harm (security-wise) in doing so on single-user machine running AOS.
BTW: there's no need to do that except when having the situation of very singular slowdowns in local apps when opening menus and doing other manipulation of gui objects (this was true with some earlier releases, with current AmiCygnix and AOS4.1 it doesn't appear, at least here).


Jack

@Jack

thanks, this works

But using AmiCygnix on my Sam e.g. with NetSurf is still faaar too slow. Posting this comment here was impossible.

Anyway, I can use remotly skype and some other useful apps on my Amiga. That's simply great! Thanks a lot

nexus

P.S. In NetSurf&AmiCygnix, text in input-fields (in order to post comments) is not rendered until the full browser window is updated (e.g. by scrolling down the content of the browser window).

@nexus

You can also use remotely opera/firefox/seamonkey/konqueror/etc.
And set yourself a passwordless ssh (using key-based authentication)

I can't live here without ssh/X11 (I work a lot from home and all computers at work are unices).


Jack