More questions about xfree

["ted byers" <ted dot byers at sympatico dot ca>]

Please help me understand the differences between shartxwin.sh and startx.
I also see an item in X11r6/bin called X which is clearly a link to
something, but I have not been able to figure out what it is linked to.
Would I break anything if I created an alias which ran startx or
startxwin.sh when 'x' is used as a command?

Please consider the appended output taken from the bash window in which X,
startx and startxwin.sh were each run.

Both 'X' and startx produce a message "_XSERVTransmkdir: Owner of
/tmp/.X11-unix should be set to root"  What does this mean, and why do they
produce it when startxwin.sh does not?  But 'X' seems to be rather useless
because it does not create any windows in which I can enter commands.

startx is unique inthat it gives a series of "cat: /home/Bted/.Xauthority:
No such file or directory" messages.  What is this, what does it mean, and
what, if anything should I do about it?

The xterm error messages are interesting int hat it appears that not all of
the windows in which I can enter commands were created equal in startx.  In
both startx and startxwin.sh, if I exit all windows before using <alt><f4>,
then no xterm errors appear.  But, if I have used startx, and I enter the
exit command in the leftmost window first, the whole session ends and the
xterm errors shown occur for the other two windows.  Why?  Is this something
I ought to be concerned about?

More troubling, for me, because I do not know what these errors mean, is
that if I have closed all of the command windows when I have used startx, I
get the following error message:

waiting for X server to shut down XIO:  fatal IO error 104 (Connection reset
by peer) on X server ":
0.0"
      after 624 requests (619 known processed) with 2 events remaining.

Otherwise, if one or more command windows are left open, with startx and
with startxwin.sh, I get the following error message:

XIO:  fatal IO error 110 (errno ESHUTDOWN triggered) on X server ":0.0"
      after 675 requests (673 known processed) with 9 events remaining.

And in this case, startx also gives a login error message.

If the command window created by startxwin.sh is closed before using
<alt><f4>, then it does not give any error messages.

Do all these error messages mean that something in my installation of xfree
is broken, or is it the case that 'X' and startx do a couple things that are
not appropriate on NT+cygwin?

I generally like what startx does better than startxwin.sh, except that the
clock is about a quarter of the size it ought to be (I have a high
resolution monitor), and except for all the errors it produces!  And I still
haven't been able to figure out how to change the colour scheme.  And I find
that if I use startx, I can still shut down the bash window I started it
from in the usual way, whereas if I use startxwin.sh I must resort to the
'X' icon at the top right corner of the window frame.  How can I change
startxwin.sh so that it reproduces the appearance, and closing behaviour,
that startx does; or equivalently, how can I change startx so that I get rid
of all the errors it produces, change the colours it uses, and increase the
size of the clock (so I do not have to do it manually)?

Any insights will be greatly appreciated.

Thanks,

Ted

R.E. Byers
ted.byers@sympatico.ca

=========output from the scripts used to start X Windows====


Bted@OHBOY ~
$ X
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
winDetectSupportedEngines () - Windows NT/2000
winDetectSupportedEngines () - DirectDraw installed
winDetectSupportedEngines () - Allowing PrimaryDD
winDetectSupportedEngines () - Returning, supported engines 0000001b
winSetEngine () - Using Shadow DirectDraw
winAdjustVideoModeShadowDD () - Using Windows display depth of 24 bits per
pixel
winCreateBoundingWindowWindowed () - WindowClient w 1594 h 1134 r 1594 l 0 b
1134 t 0
winInitVisualsShadowDD () - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24
winCreateDefColormap () - Deferring to fbCreateDefColormap ()


$ startx

ddxProcessArgument ()
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
winDetectSupportedEngines () - Windows NT/2000
winDetectSupportedEngines () - DirectDraw installed
winDetectSupportedEngines () - Allowing PrimaryDD
winDetectSupportedEngines () - Returning, supported engines 0000001b
winSetEngine () - Using Shadow DirectDraw
winAdjustVideoModeShadowDD () - Using Windows display depth of 24 bits per
pixel
winCreateBoundingWindowWindowed () - WindowClient w 1594 h 1134 r 1594 l 0 b
1134 t 0
winInitVisualsShadowDD () - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24
winCreateDefColormap () - Deferring to fbCreateDefColormap ()
cat: /home/Bted/.Xauthority: No such file or directory
cat: /home/Bted/.Xauthority: No such file or directory
cat: /home/Bted/.Xauthority: No such file or directory
cat: /home/Bted/.Xauthority: No such file or directory
cat: /home/Bted/.Xauthority: No such file or directory
cat: /home/Bted/.Xauthority: No such file or directory
winWindowProc () - Closekey hit, quitting
XIO:  fatal IO error 110 (errno ESHUTDOWN triggered) on X server ":0.0"
      after 675 requests (673 known processed) with 9 events remaining.
winKeybdReleaseModifierKeys - Releasing VK_LMENU
xterm:  fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
xterm:  fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
login:  fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
xinit:  connection to X server lost.


Bted@OHBOY ~
$ startxwin.sh
Agent pid 337
ddxProcessArgument ()
ddxProcessArgument () - screen - argc: 5 i: 1
winDetectSupportedEngines () - Windows NT/2000
winDetectSupportedEngines () - DirectDraw installed
winDetectSupportedEngines () - Allowing PrimaryDD
winDetectSupportedEngines () - Returning, supported engines 0000001b
winSetEngine () - Using Shadow DirectDraw
winAdjustVideoModeShadowDD () - Using Windows display depth of 24 bits per
pixel
winCreateBoundingWindowWindowed () - WindowClient w 1024 h 768 r 1024 l 0 b
768 t 0
winInitVisualsShadowDD () - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24
winCreateDefColormap () - Deferring to fbCreateDefColormap ()

Bted@OHBOY ~
$ winWindowProc () - Closekey hit, quitting
winKeybdReleaseModifierKeys - Releasing VK_LMENU
XIO:  fatal IO error 110 (errno ESHUTDOWN triggered) on X server
"127.0.0.1:0.0"
      after 276 requests (274 known processed) with 3 events remaining.
xterm:  fatal IO error 32 (Broken pipe) or KillClient on X server
"127.0.0.1:0.0"