xwin hangs at startup - no xterm display

[kumarchi@comcast.net]

here is the fulll log file.  

Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 6.8.1.0-8

Contact: cygwin-xfree@cygwin.com

XWin was started with the following command line:

XWin -multiwindow -clipboard -silent-dup-error 

ddxProcessArgument - Initializing default screens
winInitializeDefaultScreens - w 1280 h 1024
winInitializeDefaultScreens - Returning
_XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created.
(II) XF86Config is not supported
(II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information
(==) FontPath set to "/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/TTF/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/CID/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/"
winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel
winAllocateFBShadowGDI - Creating DIB with width: 1280 height: 1024 depth: 32
winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp 32
null screen fn ReparentWindow
null screen fn RestackWindow
InitQueue - Calling pthread_mutex_init
InitQueue - pthread_mutex_init returned
InitQueue - Calling pthread_cond_init
InitQueue - pthread_cond_init returned
winInitMultiWindowWM - Hello
winMultiWindowXMsgProc - Hello
winInitMultiWindowWM - Calling pthread_mutex_lock ()
winMultiWindowXMsgProc - Calling pthread_mutex_lock ()
MIT-SHM extension disabled due to lack of kernel support
XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel
(--) Setting autorepeat to delay=500, rate=31
(--) winConfigKeyboard - Layout: "00000409" (00000409) 
(--) Using preset keyboard for "English (USA)" (409), type "4"

kumarchi@comcast.net wrote:

> I do not zonealarm but windows sp2. the behavior is the same even when I turn the built in firewall off
>
> I get the following error in XWin.log
>
> _XSERVTransmkdir: ERROR: euid != 0, directory /tmp/.X11-unix  will not be created

The FAQ states this is not an error at all (although it is labeled so). More
important is the full logfile.