As much as I hate to admit it, I've been using Xming from sourceforge.net as
my X server, along with all the regular cygwin progams.
XWin.exe used to go 100% cpu every once in a while, but Xming has been
running great!
Dave
Michael PARKER [EMAIL PROTECTED] wrote in message
news:[EMAIL
William Bierman schrieb:
I made myself a shortcut (though I get the same behavior no matter how
I start X) to run X by executing:
C:\cygwin\usr\X11R6\bin\run.exe -p /usr/X11R6/bin Xwin -multiwindow
Try to start with -engine 1 -once . It worked for me, but i'm not using
multiwindow.
--
That works without -multiwindow. When I add -multiwindow back it
continues to happen.
On 2/25/07, Holger Krull [EMAIL PROTECTED] wrote:
William Bierman schrieb:
I made myself a shortcut (though I get the same behavior no matter how
I start X) to run X by executing:
William Bierman wrote:
Greetings.
I made myself a shortcut (though I get the same behavior no matter how
I start X) to run X by executing:
C:\cygwin\usr\X11R6\bin\run.exe -p /usr/X11R6/bin Xwin -multiwindow
X starts up fine and seems to run fine. When I right click on the X
icon in the
Greetings.
I made myself a shortcut (though I get the same behavior no matter how
I start X) to run X by executing:
C:\cygwin\usr\X11R6\bin\run.exe -p /usr/X11R6/bin Xwin -multiwindow
X starts up fine and seems to run fine. When I right click on the X
icon in the system tray, however, and