Sorry to be so basic here. But I don't think this was really covered in the "Cygnix . . . doesn't do anything" thread.
How long should it take for Cygnix to show its screen once the startup script is executed? Usually I get a pop up saying the X-server couldn't be started. Then some time after clicking that away, I get an X11 screen. But all it is is a crudely dithered gray (alternating chunky black and white "pixels") with no real output.
Then if I click back to the Workbench screen and execute the start Xami.bat script, it will finally bring up the actual X screen.
I have an icon out for the Abiword startup.bat script. If that's the first thing to get clicked, the process follows the same pattern described above.
So, in essence:
1. How long should it take for Cygnix to show up? 2. I just installed the 4.1 SDK in hopes it might make a difference, but it doesn't change anything in the Cygnix startup. 3. Note I have no real complaints about using Cygnix once it's running. I mainly use Abiword, and iyt's reasonably fast considering the "dual" environment setting it's running under.
AmiCygnix needs about 8 seconds here from double click on the icon to a fully initialized desktop. Config: AOne XE G4/800Mhz.
I guess you use the script "Start_AmiCygnix.bat" to launch AmiCygnix? Then the problem is, that the X server cannot be started. Please try to launch the server from a shell with:
xgeekppc :0 -screen Picasso96@1024x768x16
You should see an error message if there is a problem.
If you use the script "Start_XAmi.bat", then you have probably installed the XAmi package somewhere and this X server is used for AmiCygnix. This server is limited and slower than the server provided with AmiCygnix.
AmiCygnix needs about 8 seconds here from double click on the icon to a fully initialized desktop. Config: AOne XE G4/800Mhz.
Same harddware here. 512 RAM. Takes about 2 minutes for a blank xscreen to appear tonight if I click the Abiword start icon. But so far Abiword itself hasn't started.
Quote:
I guess you use the script "Start_AmiCygnix.bat" to launch AmiCygnix? Then the problem is, that the X server cannot be started. Please try to launch the server from a shell with:
xgeekppc :0 -screen Picasso96@1024x768x16
You should see an error message if there is a problem.
Using this from a shell, actually nothing happens, whether I run it from the prompt set at the cygnix directory or from the Amiga system prompt. (I've added the Cygnix stuff to the path in the startup-sequence}
Quote:
If you use the script "Start_XAmi.bat", then you have probably installed the XAmi package somewhere and this X server is used for AmiCygnix. This server is limited and slower than the server provided with AmiCygnix.
Since my first question here, I have removed everything Cygnix related (as far as I know) and re-installed from scratch. This time it didn't put ANYTHING in user-startup. I copied back what I posted above and put it in user-startup again.
BTW, that X window that came up when I started this message finished up loading the panels, background, etc within seconds of clicking on the Xami-startup script.
Was Xami part of the 1st gen Cygnix stuff? Otherwise, I don't remember installing any Xserver stuff since I tried Wolf Faust's stuff years ago on my A4000.
a million times thanks. i havent playet much with amicygnix,but i tryet the x11 thing.. maby i just dident know how to do it..
is it very complicatet ??
i am thinking of making a menu in the start bar with the name amicygnix and then start bat?s to all the program, with a pre setup to a custum screen or maby window mode for some of the small apps, for eath program
Thanks! Hmm - that's slow. Are the AmiCygnix programs usable for you?
@daff
Quote:
On my Pegasos 2, it takes only 4 seconds to display the full desktop with full of software's icons.
4 seconds??? Damn - I want a Pegasos 2
@TiredOfLife
How fast is it on your SAM?
@TSK
Quote:
I don't have any problems with SDK and AmiCygnix. I uploaded a crashlog of Idesk to os4depot because it crashes quite often on my system.
Had a look at the crashlog, but it didn't help me much. Could you do the same with an unstripped binary? I'll send you a PM with a link to a binary with debugging informations.
Same harddware here. 512 RAM. Takes about 2 minutes for a blank xscreen to appear tonight if I click the Abiword start icon. But so far Abiword itself hasn't started.
Quote:
Using this from a shell, actually nothing happens, whether I run it from the prompt set at the cygnix directory or from the Amiga system prompt. (I've added the Cygnix stuff to the path in the startup-sequence}
What does nothing mean? Does the command return to the shell or does it freeze? I suggest to use Snoopy to find out what happens while startup. Can you post a log here?
Quote:
Since my first question here, I have removed everything Cygnix related (as far as I know) and re-installed from scratch. This time it didn't put ANYTHING in user-startup. I copied back what I posted above and put it in user-startup again.
There is something deeply wrong. Did you use the installer script for installation? Which mode did you use (advanced, expert)?
Quote:
Was Xami part of the 1st gen Cygnix stuff? Otherwise, I don't remember installing any Xserver stuff since I tried Wolf Faust's stuff years ago on my A4000.
No, Xami was never part of Cygnix/AmiCygnix. There was only this startup script for XAmi users.
i havent playet much with amicygnix,but i tryet the x11 thing.. maby i just dident know how to do it..
What do you mean with X11 thing?? AmiCygnix works wonly with X window.
Quote:
i am thinking of making a menu in the start bar with the name amicygnix and then start bat?s to all the program, with a pre setup to a custum screen or maby window mode for some of the small apps, for eath program
sorry for my bad english
There are several way to do this. You could create a special script to launch AbiWord in a WB display.
Example:
Echo "Launching X server..."
Run >NIL: Cygnix:CygnixPPC/X11R6.3/bin/XGeekPPC :0 -pri 0 -screen Picasso96PIP@832x600x16
Didn't think I'd be coming back to this thread. But a really odd thing happened.
AmiCygnix now opens in a matter of about 2-3 seconds for me. That's as opposed to 2-3 minutes or more before.
Before what, you ask? The router on my home system died. After I replaced it, suddenly AmiCygnix was working like a champ. General surfing was a lot faster, too. But this unintended and unexpected result with Cygnix is just weird! (nice weird, but still weird)