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
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 intermittent
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?
Dan
-Original Message-
From: [EMAIL PROTECTED]
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
Xwin.exe die shortly after the initial launch, but my
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
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. Use
