Igor Pechtchanski wrote:
> > An alternative that I've not seen raised before: I was wondering if it
> > would be possible to run XWin as a Windows service (presumably via
> > cygserver).
>
> Services are run by 'cygrunsrv', not 'cygserver'. 'cygserver' provides
> Unix shared memory and IPC servic
On Fri, 8 Apr 2005, Phil Betts wrote:
> On Friday, April 08, 2005 3:58 PM, Igor Pechtchanski wrote:
>
> >Well, I don't recall if XWin has a way of selecting the next available
> >display (I do know it's not on by default, even if it exists), but that
> >would be pretty much a must in coping with a
On Friday, April 08, 2005 3:58 PM, Igor Pechtchanski wrote:
> On Fri, 8 Apr 2005, Phil Betts wrote:
>> An alternative that I've not seen raised before: I was wondering if
it
>> would be possible to run XWin as a Windows service (presumably via
>> cygserver).
>
> Services are run by 'cygrunsrv', no
On Fri, 8 Apr 2005, Phil Betts wrote:
> IIRC, there was talk a while back of making the multiwindow manager an
> external client. I don't know if anythng has been done in this
> direction, but if this were done, there would at least be a consistent
> startup for all WMs.
There is an external MWW
On Thursday, April 07, 2005 8:58 PM, Alexander Gottwald wrote:
>On Thu, 7 Apr 2005, Phil Betts wrote:
>> Is it possible that xinit similarly thinks all is well?
>
> I don't think so.
Good.
> Nothing forks except bash (or cmd or whatever) The xserver on unix
does not
> put itself to background
On Thu, 7 Apr 2005, Phil Betts wrote:
> I'll bow to your superior knowledge, it's about 10 years since I last
> used startx in anger, and that was on Linux, where the X servers only
> exit on closedown. However (I'm just speculating here) the problems I
> was having with xhost/xmodmap were partly
On Thursday, April 07, 2005 1:21 PM, Alexander Gottwald wrote:
>On Thu, 7 Apr 2005, Phil Betts wrote:
>
>> People using startx will need a similar solution, but will be able to
>> use more elegant code instead of the unholy mess that CMD.EXE forced
>> me to write!
>
> No. Startx uses xinit and xin
--On 07 April 2005 14:21 +0200 Alexander Gottwald wrote:
No. Startx uses xinit and xinit tries to connect to the xserver in the
way a client would do and repeats it until the server is ready.
That suggests another way to wait for the server. Run some suitably
harmless (side-effect free) client in
On Thu, 7 Apr 2005, Phil Betts wrote:
> People using startx will need a similar solution, but will be able to
> use more elegant code instead of the unholy mess that CMD.EXE forced
> me to write!
No. Startx uses xinit and xinit tries to connect to the xserver in the way
a client would do and rep
On Thursday, March 31, 2005 7:10 PM, Alexander Gottwald wrote:
>On Thu, 31 Mar 2005, Armbrust, Daniel C. wrote:
>
>> Because I execute the entire script twice, since the first
>> execution doesn't bring up any xterms.
>>
>> Still not sure what is causing it to take so long to launch the
>> xwin.e
On Thu, 31 Mar 2005, Armbrust, Daniel C. wrote:
> Because I execute the entire script twice, since the first execution doesn't
> bring up any xterms.
>
> Still not sure what is causing it to take so long to launch the xwin.exe.
>
> Can I set the timeout values on the xterm's with a flag?
no. U
On Thu, 31 Mar 2005, Scott Cegielski wrote:
> I wasn'y reffering to your situation specifically. Even when the script is
> not
> executed twice, two Xwin.exe processes launch. That is what I described in
> the
> first post of this thread. As I learned, adding the -kb flag makes the second
> X
aunch the xwin.exe.
>
> Can I set the timeout values on the xterm's with a flag?
>
> Dan
>
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
> Behalf Of Scott Cegielski
> Sent: Thursday, March 31, 2005 10:38 AM
> To: cygw
D] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Cegielski
Sent: Thursday, March 31, 2005 10:38 AM
To: cygwin-xfree@cygwin.com
Subject: RE: Multiple XWin.exe programs loading and no xterm
I'm just trying to understand this even though it works for me now. Why are
two X servers launching in
I'm just trying to understand this even though it works for me now. Why are
two X servers launching in the first place?
--- Alexander Gottwald <[EMAIL PROTECTED]> wrote:
> On Wed, 30 Mar 2005, Armbrust, Daniel C. wrote:
>
> > The -kb command helped with one of my machines that was having intermi
On Wed, 30 Mar 2005, Armbrust, Daniel C. wrote:
> The -kb command helped with one of my machines that was having intermittent
> difficulties in launching.
>
>
>
> On another machine, however, I always have to execute the following script
> twice before I get any Xwin windows:
>
> run XWin -m
For me, adding -kb to the xwin command did work. Thanks much for the help.
--- "Armbrust, Daniel C." <[EMAIL PROTECTED]> wrote:
> The -kb command helped with one of my machines that was having intermittent
> difficulties in launching.
>
>
>
> On another machine, however, I always have to execu
The -kb command helped with one of my machines that was having intermittent
difficulties in launching.
On another machine, however, I always have to execute the following script
twice before I get any Xwin windows:
--CUT--
All of the standard startXWin.bat environment setup stuff...
--CUT--
On Tue, 29 Mar 2005, Scott Cegielski wrote:
> For me, putting a pause at the end of startxwin.bat does not make it work.
> However, I have found something that does seem to work for me. When I launch
> statxwin.bat, in addition to the 2 XWin.exe processes, there is also a sh.exe
> process that s
For me, putting a pause at the end of startxwin.bat does not make it work.
However, I have found something that does seem to work for me. When I launch
statxwin.bat, in addition to the 2 XWin.exe processes, there is also a sh.exe
process that starts which I assume is from the MS-DOS shell that th
Armbrust, Daniel C. wrote:
This happens to me all the time - I usually have to launch the X stuff 2 or 3 times before it actually works.
I have to manually kill off all xterm.exe, bash.exe, and other cygwin programs in between the launches. I keep meaning to look into it more, but since I sta
This happens to me all the time - I usually have to launch the X stuff 2 or 3
times before it actually works.
I have to manually kill off all xterm.exe, bash.exe, and other cygwin programs
in between the launches. I keep meaning to look into it more, but since I
start it less than once a w
I did also try startx. Please see my original email for the output of startx.
thanks
--- Steven Boothe <[EMAIL PROTECTED]> wrote:
> Scott Cegielski wrote:
> > Hello,
> > Please help. This is my first time trying to start X windows using cygwin
> > although I have been using cygwin for a while n
On Mon, 28 Mar 2005, Scott Cegielski wrote:
> Hello,
> Please help. This is my first time trying to start X windows using cygwin
> although I have been using cygwin for a while now. I am running it like this:
>
> 1. Open cygwin bash shell
> 2. Type startxwin.bat
>
> The problem is that not m
Scott Cegielski wrote:
Hello,
Please help. This is my first time trying to start X windows using cygwin
although I have been using cygwin for a while now. I am running it like this:
1. Open cygwin bash shell
2. Type startxwin.bat
Try typing startx at the command line. What happens then?
25 matches
Mail list logo
