@white

There's the command "whoami" on Linux and maybe also on your system.
But I'm not sure if this helps you with your problem.

@white

Quote:
There are no wrong questions

Please notice, that AmiCygnix uses different drivers for different gfx card driver software like "Picasso96", "Cybergraphics" or the new OS4 routines. AmiCygnix does not support a gfx card directly!
So if a gfx card is supported by a driver software, it is also supported by AmiCygnix. Just choose the desired gfx card in the screenmode settings in myX11Setup.

@white

Quote:
I'm afraid I cannot help you. I don't know much about ALSA. But I guess, that the problem is on Linux side, even if the message appears in the amigaos shell.

From where does the sound come from? As the X server cannot handle sound, it should be played on the Linux system side.

@white

I'm not sure where the problem is - I cannot test it here. But I think the reason is, that all communication between the client and the server is going through the network, even the mouse movements and the key prints.

In other words: A basic problem of AmiCygnix is, that the GUI becomes slow, when there is a lot of traffic in the network. And in this case, the client (Firefox) gets the video data on the Linux side and sends it over the network to the X-Server on the Amiga side.

Unfortunately I cannot change this.

@white

Quote:
It is faster to run the client (Firefox) on a Linux machine and open the window in AmiCygnix than running both on AmigaOS. In my experience this is always the case, if you run a client and the server on OS4.

Especially with older versions of X11 (like R6.3 on AmiCygnix), the client has more to do than in newer versions. This is because newer X server have more extensions to do render (and other) jobs independantly from the client. This reduces traffic between the client and the server. But if you run the client on a Linux machine, which has a better performance than AmigaOS, the older version of X11 on the Amiga side could be an advantage.

The graphics driver on a Linux machine has no effect when you open the window on AmiCygnix. The complete handling of the gfx card is done on the server side,

@white

The driver I suggested was "picasso96clonewb" without "db" at the end. This driver has a screenbar and is like "cybergraphx".

Please notice, that AmiCygnix uses the old version R6.3 of X11, which misses a lot of modern extensions like "RandR", "Xinerama" and "GLX".
If you want to see the supported extensions, type "xdpyinfo" into a shell.

Quote:

I cannot say much about WinUAE, sorry.

@white

Impressing videos - I like it

What about "picasso96clonewb"? Should have the same performance as "cybergraphx" as it uses the same render routines. But as I've said, I never tried WinUAE.

There are several ways to switch back to the workbench screen:
* Press the keys "left Amiga + n"
* Go to the top right corner of the screen an click the left mouse button

Or you create a file named "wb.desktop" in "Cygnix:CygnixPPC/share/applications" and put this in (example):



Afterwards you can find a new entry in the menu "system tools" of the desktop panel.

@white

It is not possible to open the shell on an AmiCygnix display that uses CyberGraphx. The window would destroy the content of the screen. Only the newer "...db" driver would work, but i wasn't able to open a shell window on a custom screen so far.

AmiCygnix was never tested on WinUAE.

@drHirudo

Tried it here and I have no problems.

By default the AmiCygnix desktop launches an sound server. You could try to disable it by setting an environment variable this way:

setenv SAVE Cygnix/CYGNIX_LAUNCH_SOUND_SERVER 0

You have to make a reset afterwards.

But I'm afraid, that the display driver could be the reason for this. You could try to use the display driver "picasso96clonewb". You will have wrong colours with this driver, but maybe no jittering.
If this is the case, I have no solution for this.

@ChrisH

This is the way I solved this problem in my Makefiles:



THREADFLAGS contains the needed flags if g++ major version is higher or equal to 8. And you can use THREADS_SUPPORTED for additional control.

@328gts

Basically all GTK 2 applications on AmiCygnix support the Amiga-C and Amiga-V keys. Only if you choose a menu item like "Edit/Copy", the text is not copied into the Amiga clipboard.

But it can happen, that it does not work, if you copy text with non latin chars in it (or something else, which is not supported). AmiCygnix tries to convert the UTF-8 text to ISO-8559-1 and if it fails, you have no content in the Amiga clipboard.

@rjd324


Did you set the environment variable "Cygnix/TZ" correctly? For Germany it must be set to "Europe/Berlin". See the
directory "Cygnix:CygnixPPC/etc/zoneinfo" for your correct setting.

I must admit, that it is a bit confusing, as the time management in AmiCygnix depends sometimes on Cygnix/TZ and
sometimes on the OS system time. So both settings must be conform! The reason is, that libaos4util does not
implement/replace the full set of functions available in Newlib.

I tried this here on my system and it works:

* Opened the "Locale" settings of OS4 and set country to "United States" and the timezone to UTC - 5.
* Opened the "Time" settings of OS4 and set the time using the time server.
* Set the timezone for AmiCygnix with: "setenv Cygnix/TZ America/New_York"

@NinjaCyborg

An AmigaDOS script or a batch file.

@rjd324

The problem is, that normally the start script does not change the current directory. This could be an alternative start script, which sets a fixed directory (change the directory to your needs):

@VooDoo

You could contact Antique. He was able to login to Facebook.

I'm afraid, that you have to disable the 2-factor-authentification.

@VooDoo

Maybe this helps:

https://superuser.com/questions/281134 ... two-factor-authentication

@rjd324

You should be able to copy something in Leafpad and paste it into Notepad for example. But it only works with latin characters. If there is for example an UTF-8 encoded character in the copied text that cannot be converted, you cannot paste it into an Amiga program.

Second is: You only can exchange the clipboard buffer by using the key combinations "RAmiga+C" and so on. If you copy text in Leafpad by using the menu item, it will not be copied into the Amiga clipboard. Clipboard support is not fully implemented in GTK+.

There are some clipboard functions in my utility library "libaos4util":

- int __cygnix_write_text_to_amiga_clipboard(char *text, int cbunit);
- char *__cygnix_read_text_from_amiga_clipboard(int cbunit);

I think they are easy to understand. They are using the iffparse.library.

And especially for GTK+:

- void __cygnix_write_amiga_clipboard_gtk2(void); (copies the content of the Amiga clipboard into the GTK+ clipboard)
- int __cygnix_read_amiga_clipboard_gtk2(void); (copies the content of the GTK+ clipboard to the Amiga clipboard)

Sources are in the "amicygnix-base-src.lha" package on OS4-depot.
You can find the GTK+ clipboard code in "Cygnix:CygnixPPC/src/X11R6.3/xc/aos4/misc/__cygnix_init_gtk2.c".

@Antique

Don't know exactly, The discord plugin is a bit tricky. Maybe I make a new release with broken discord first. Do you use discord?

If you like, I can make a test package for you so you can test if facebook works for you?

@pjs

Whow - what a surprise! Thank you very very much

I think I have to increase my speed of working on AmiCygnix

But first a beer and a pizza...

@Antique

Which protocol did you use? I guess it was "facebook". This is broken in the current release, but will be fixed in the next one.
It will be released, when the also broken "discord" protocol is working.