From: Wilhelm Person [EMAIL PROTECTED]
Subject: Re: Problems using CYGwin
Date: Sun, 5 May 2002 23:33:17 +0200 (CEST)
127.0.0.1 (localhost) is just a reference to your own computer, it's
supposed to be that way. You shouldn't have to change anything in your
configuration to fix that part.
The mwm from lesstif eats up 99 % of CPU time, both in the binary package
and in a self-compiled version. I found that the select() calls in events.c
do not wait but immediately fail with errno = EBADF, although fd_width is 256
and x_fd is 3 or 4 (printed out in mwm.c). I have not yet found the
Hi all.
I have installed cygwin, and cygwin-xfree 4.2.0,
but it does not work. Startx produces the gray background with a
big cross, it stops at that. The xterm terminates giving a core
dump. The Xwin.log file is attached below.
i thing the problem lies here
_XSERVTransSocketUNIXAccept:
Hi
I have been using Cygwin for the last 4 months now and find it reasonably
good to use, however.
I have been having continuous problems getting it to connect to the server
box.
The configuration is Server: Redhat 7.2 (was7.1) running xdm Win2K Server.
Sometimes it will connect sometimes it
Hi
I have been using Cygwin for the last 4 months now and find it reasonably
good to use, however.
I have been having continuous problems getting it to connect to the server
box.
The configuration is Server: Redhat 7.2 (was7.1) running xdm Win2K Server.
Sometimes it will connect sometimes it
Harold == Harold Hunt [EMAIL PROTECTED] writes:
Harold Viliam,
I have found my misunderstanding.
I have started the startx instead of startxwin.sh .
The startx (I am not in linux) is pointing to the not existing xinitrc
file.
Therefore the windows manager twm was
I have been using Cygwin for the last 4 months now and find it reasonably
good to use, however.
I have been having continuous problems getting it to connect to the server
box.
The configuration is Server: Redhat 7.2 (was7.1) running xdm Win2K Server.
Sometimes it will connect sometimes it
I have just came across a problem when connected to KDE 3 running on a
Redhat 7.2 box via XDMCP. While trying to get my uk keyboard to work I
connected this time using the command:
startxwin.exe -query server name
instead of my usual XWin -query server name which works fine.
everything
Mike,
Take a look at /tmp/XWin.log for errors. Send in the relevant errors if you
find any (probably just the bottom few lines of the file).
Do you have more than one network card or a token-ring network card?
Harold
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL
Scott,
startxwin.exe -query server name
I don't understand, there is no startxwin.exe file distributed with
Cygwin/XFree86. You must be talking about startxwin.bat or startxwin.sh,
but neither of those can be passed parameters. What are you talking
about
Failed assertion, fds_on_hold
Hi Harold,
Sorry for the confusion its been a bit blurry since the weekend but a few
coffees later and I'm better now. I was talking about startxwin.sh(bat) as
you guessed. Upon closer inspection I have modified this file at a previous
time and that's the reason that the remote connection was
- Original Message -
From: Michael [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, April 05, 2002 7:48 AM
Subject: Missing terminfo data in XFree86 4.2.0
Hi
I ran into the following problem with the current XFree86 distribution,
but
could not find any mention of any solution
I'm sorry, but it seems it's not a good answear.
Once again :
- I cannot change the configuration of the AIX Server
(the main reason is that in fact, I have MANY servers,
some AIX, some Solaris, some Linux,...)
- I just can change the local configuration, that is to
say the client for
The definition of key_t in newlib is a 32bit int, for cygdaemon it needs
to be 64 bit to store the inode and the index cleanly. Redefining that
will break every cygipc linked application when they are rebuilt, until
cygipc is rebuilt against the new source. However rebuilding cygipc will
-Original Message-
From: Ralf Habacker [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 07, 2002 7:41 AM
What about using a new type respective casts for cygdaemon.
This would not break key_t compatibility and allows to
migrate single application to cygdaemon, while others works
Robert Collins wrote:
-Original Message-
From: Ralf Habacker [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 07, 2002 7:41 AM
What about using a new type respective casts for cygdaemon.
This would not break key_t compatibility and allows to
migrate single application to cygdaemon,
Kurt,
You don't ask me these things, you ask the [EMAIL PROTECTED] mailing
list, where I have forwarded your email.
Harold
-Original Message-
From: Kurt Strüvy [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 06, 2002 2:42 PM
To: Harold Hunt
Subject: RE: Problems using CYGwin
Hi
Hi,
I have the exactly same problem with AIX and Czech keyboard. I have a
workarround
- I run xmodmap on AIX machine everytimes I logon - I have alias for that,
so I don't have
to type the whole command. I couldn't add this command to some profile,
because it messes
keyboard on console (and I
get a xmodmap.fr file and add the following line (after the xwin command)
in the start shell :
xmodmap location of your xmodmap file/xmodmap.fr
Trust me - it works - you can also transfer a xmodmap.fr file to your AIX
machines and run the same command on them - X doesn't care if you run the
19 matches
Mail list logo
