Re: Can't open display

[Enoch Wu <ewu at eskimo dot com>]

Check the OS environment variable. Compare that with the environment variable
assumption in startxwin.bat? Are they in agreement? 

EW


On Fri, Apr 06, 2001 at 06:25:14AM -0700, Kevin DeKorte wrote:
> Harold, 
> 
> Here is the line I am using in startxwin. I also tried
> replacing Xwin with Xwin95 but had the same result
> 
> if "%OS%" == "Windows_NT" start /B XWin -engine 1
> -screen 0 1024x768x16
> 
> The result from running startxwin with the command
> above. I have very high screen rez. 1400x1050 (an IBM
> T21 laptop) 
> 
> startxwin
> 
> _XSERVTransmkdir: Owner of /tmp/.X11-unix should be
> set
> to root
> twm:  unable to open display "127.0.0.1:0.0"
> xterm Xt error: Can't open display: 127.0.0.1:0.0
> winDetectSupportedEngines () - Windows NT/2000
> winDetectSupportedEngines () - DirectDraw installed
> winDetectSupportedEngines () - Allowing PrimaryDD
> winDetectSupportedEngines () - DirectDraw4 installed
> winDetectSupportedEngines () - Returning, supported
> engines 0000000f
> winSetEngine () - Using user's preference: 1
> winScreenInit () - dwBPP: 16
> winCreateBoundingWindowWindowed () - WorkArea width
> 1400 height 997
> winCreateBoundingWindowWindowed () - Adjusted width:
> 1024 height: 768
> winWindowProc () - Screen privates are null, msg: 36
> winWindowProc () - Screen privates are null, msg: 129
> winWindowProc () - Screen privates are null, msg: 131
> winWindowProc () - Screen privates are null, msg: 1
> winStoreModeKeyStates () - dwModeKeyStates: 00000000
> winCreateBoundingWindowWindowed () - WindowClient
> width 1024 height 768
> winRestoreModeKeyStates ()
> winCreateBoundingWindowWindowed () - Returning
> 
> winClearVisualTypes ()
> winAllocateFBShadowGDI () - Shadow buffer allocated
> winAllocateFBShadowGDI () - Dibsection width: 1024
> height: 768
> winAllocateFBShadowGDI () - Attempting a shadow blit
> winAllocateFBShadowGDI () - Shadow blit success
> winInitVisualsGDI () - Masks: 0000f800 000007e0
> 0000001f bpRGB: 6
> winInitVisualsGDI () - Returning
> winScreenInit () - Returned from winInitVisuals ()
> winScreenInit () - Calling fbScreenInit ()
> winScreenInit () - Returned from fbScreenInit ()
> winScreenInit () - Calling shadowInit ()
> winScreenInit () - Returned from shadowInit ()
> error opening security policy file
> /usr/X11R6/lib/X11/xserver/SecurityPolicy
> InitInput ()
> winSaveScreen ()
> winStoreModeKeyStates () - dwModeKeyStates: 00000000
> 
> With the xserver up I try and run xterm and get the
> following. I can move the X cursor around the screen
> no problem and I see a window with the Cygwin/XFree86
> name and it looks like it is filled with a black and
> white checker board pattern.
> 
> C:\cygwin\usr\X11R6\bin>xterm
> xterm Xt error: Can't open display: 127.0.0.1:0.0
> 
> C:\cygwin\usr\X11R6\bin>ping 127.0.0.1
> 
> Pinging 127.0.0.1 with 32 bytes of data:
> 
> Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
> Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
> Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
> Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
> 
> Ping statistics for 127.0.0.1:
>     Packets: Sent = 4, Received = 4, Lost = 0 (0%
> loss),
> Approximate round trip times in milli-seconds:
>     Minimum = 0ms, Maximum =  0ms, Average =  0ms
> 
> 
> Could it be a port issue in my \winnt\system32\drivers
> \etc\services file? What port does X connect on?
> 
> Kevin
> 
> 
> 
> 
> =====
> ---------------------------------
> Kevin DeKorte
> kdekorte@yahoo.com
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Get email at your own domain with Yahoo! Mail. 
> http://personal.mail.yahoo.com/
>