Harold: I guess curosity got me going to try your suggestions on my laptop. The bottom line is: the X server still crashed. I used Test 76 this time. The script is:
___________________________________________________________________________ @echo off REM SET DISPLAY=:0.0 SET DISPLAY=127.0.0.1:0.0 REM REM The path in the CYGWIN_ROOT environment variable assignment assume REM that Cygwin is installed in a directory called 'cygwin' in the root REM directory of the current drive. You will only need to modify REM CYGWIN_ROOT if you have installed Cygwin in another directory. For REM example, if you installed Cygwin in \foo\bar\baz\cygwin, you will need REM to change \cygwin to \foo\bar\baz\cygwin. REM REM This batch file will almost always be run from the same drive (and REM directory) as the drive that contains Cygwin/XFree86, therefore you will REM not need to add a drive letter to CYGWIN_ROOT. For example, you do REM not need to change \cygwin to c:\cygwin if you are running this REM batch file from the C drive. REM SET CYGWIN_ROOT=\cygwin SET PATH=%CYGWIN_ROOT%\bin;%CYGWIN_ROOT%\usr\X11R6\bin;%CYGWIN_ROOT%\usr\local\bin;%PATH% REM REM Cleanup after last run. REM if not exist %CYGWIN_ROOT%\tmp\.X11-unix\X0 goto CLEANUP-FINISH attrib -s %CYGWIN_ROOT%\tmp\.X11-unix\X0 del %CYGWIN_ROOT%\tmp\.X11-unix\X0 :CLEANUP-FINISH if exist %CYGWIN_ROOT%\tmp\.X11-unix rmdir %CYGWIN_ROOT%\tmp\.X11-unix REM REM Startup the X Server, the twm window manager, and an xterm. REM REM Notice that the window manager and the xterm will wait for REM the server to finish starting before trying to connect; the REM error "Cannot Open Display: 127.0.0.1:0.0" is not due to the REM clients attempting to connect before the server has started, rather REM that error is due to a bug in some versions of cygwin1.dll. Upgrade REM to the latest cygwin1.dll if you get the "Cannot Open Display" error. REM See the Cygwin/XFree86 FAQ for more information: REM http://xfree86.cygwin.com/docs/faq/ REM REM The error "Fatal server error: could not open default font 'fixed'" is REM caused by using a DOS mode mount for the mount that the Cygwin/XFree86 REM fonts are accessed through. See the Cygwin/XFree86 FAQ for more REM information: REM http://xfree86.cygwin.com/docs/faq/cygwin-xfree-faq.html#q-error-font-eof REM if "%OS%" == "Windows_NT" goto OS_NT REM Windows 95/98/Me echo startxwin.bat - Starting on Windows 95/98/Me goto STARTUP :OS_NT REM Windows NT/2000/XP echo startxwin.bat - Starting on Windows NT/2000/XP :STARTUP REM REM Startup the programs REM REM Startup the X Server. start XWin -multiwindow -clipboard REM Startup an xterm, using bash as the shell. run xterm -sl 1024 -sb -font 9x15 -fg black -bg white -title xterm -e bash REM run xterm -sl 1000 -sb -rightbar -ms red -fg yellow -bg black -e /usr/bin/bash REM Startup the twm window manager. REM run twm REM run openbox REM Set a background color. run xsetroot -solid aquamarine4 __________________________________________________________________________ Here is the XWinrl.log file: _________________________________________________________________________ ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1024 h 768 winInitializeDefaultScreens - Returning OsVendorInit - Creating bogus screen 0 (EE) Unable to locate/open config file InitOutput - Error reading config file winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - Allowing PrimaryDD winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 0000001f InitOutput - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 winSetEngine - Multi Window => ShadowGDI winAdjustVideoModeShadowGDI - Using Windows display depth of 16 bits per pixel winCreateBoundingWindowWindowed - User w: 1024 h: 768 winCreateBoundingWindowWindowed - Current w: 1024 h: 768 winAdjustForAutoHide - Original WorkArea: 0 0 740 1024 winAdjustForAutoHide - Adjusted WorkArea: 0 0 740 1024 winCreateBoundingWindowWindowed - WindowClient w 1024 h 740 r 1024 l 0 b 740 t 0 winCreateBoundingWindowWindowed - Returning winAllocateFBShadowGDI - Creating DIB with width: 1024 height: 740 depth: 16 winAllocateFBShadowGDI - Dibsection width: 1024 height: 740 depth: 16 size image: 1515520 winAllocateFBShadowGDI - Created shadow stride: 1024 winFinishScreenInitFB - Masks: 0000f800 000007e0 0000001f winInitVisualsShadowGDI - Masks 0000f800 000007e0 0000001f BPRGB 6 d 16 bpp 16 winCreateDefColormap - Deferring to fbCreateDefColormap () null screen fn ReparentWindow null screen fn RestackWindow winFinishScreenInitFB - Calling winInitWM. InitQueue - Calling pthread_mutex_init InitQueue - pthread_mutex_init returned InitQueue - Calling pthread_cond_init InitQueue - pthread_cond_init returned winInitWM - Returning. winFinishScreenInitFB - Calling winInitClipboard. winInitClipboard () winFinishScreenInitFB - returning winScreenInit - returning InitOutput - Returning. winInitMultiWindowWM - Hello winInitMultiWindowWM - Calling pthread_mutex_lock () winClipboardProc - Hello winClipboardProc - Calling pthread_mutex_lock () (EE) No primary keyboard configured (==) Using compiletime defaults for keyboard Rules = "xfree86" Model = "pc101" Layout = "us" Variant = "(null)" Options = "(null)" winBlockHandler - Releasing pmServerStarted winInitMultiWindowWM - pthread_mutex_lock () returned. winInitMultiWindowWM - pthread_mutex_unlock () returned. winInitMultiWindowWM - XInitThreads () returned. DetectUnicodeSupport - Windows NT/2000/XP winInitMultiWindowWM - Calling setlocale () winClipboardProc - pthread_mutex_lock () returned. winClipboardProc - pthread_mutex_unlock () returned. winClipboardProc - XInitThreads () returned. DetectUnicodeSupport - Windows NT/2000/XP winClipboardProc - Calling setlocale () winBlockHandler - pthread_mutex_unlock () returned _____________________________________________________________________________ It does look like xwinclip started, but the X server did not survive. Raymond
