public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Lester Ingber <ingber@ingber.com> To: cygwin-xfree@cygwin.com Subject: can't start latest XWIN.exe 39 on XP/Pro Date: Mon, 12 Jan 2004 22:09:00 -0000 [thread overview] Message-ID: <20040112220931.GA400@ingber.com> (raw) I can't start the latest XWIN.exe. I get an OS error from XP/Pro that XWIN.exe can't be started. I have all the latest-current cygwin files as well XP Pro patches, etc. Here is the error directed to a logfile: ------------8<------------ top cut -> bottom ------------->8------------ XIO: fatal IO error 104 (Connection reset by peer) on X server "localhost:0.0" after 9 requests (8 known processed) with 0 events remaining. XIO: fatal IO error 104 (Connection reset by peer) on X server "localhost:0.0" after 10 requests (9 known processed) with 0 events remaining. XIO: fatal IO error 104 (Connection reset by peer) on X server "localhost:0.0" ------------8<------------ bottom cut <- top ------------->8------------ after 8 requests (7 known processed) with 0 events remaining. I tried this 3 ways in my startxwinMW.sh file, where I uncommented both export lines, and just one at a time, without any effect ------------8<------------ top cut -> bottom ------------->8------------ #! /bin/sh #export DISPLAY=127.0.0.1:0.0 #export DISPLAY=localhost:0.0 rm -rf /tmp/.X11-unix XWin -unixkill -emulate3buttons -clipboard -multiwindow & xbiff & xterm -sb -bg white -fg darkblue -cr red -ms red -bd red -geometry 80x84+592+0 -name center & xterm -sb -bg white -fg darkblue -cr red -ms red -bd red -geometry 80x84-0+0 -name right & exit ------------8<------------ bottom cut <- top ------------->8------------ Below is the XWin.log file: ------------8<------------ top cut -> bottom ------------->8------------ ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1600 h 1200 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 winScreenInit - dwWidth: 1600 dwHeight: 1200 winSetEngine - Multi Window => ShadowGDI winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel winCreateBoundingWindowWindowed - User w: 1600 h: 1200 winCreateBoundingWindowWindowed - Current w: 1600 h: 1200 winAdjustForAutoHide - Original WorkArea: 0 0 1200 1600 winAdjustForAutoHide - Taskbar is auto hide winAdjustForAutoHide - Found BOTTOM auto-hide taskbar winAdjustForAutoHide - Adjusted WorkArea: 0 0 1199 1600 winCreateBoundingWindowWindowed - WindowClient w 1600 h 1199 r 1600 l 0 b 1199 t 0 winCreateBoundingWindowWindowed - Returning winAllocateFBShadowGDI - Creating DIB with width: 1600 height: 1199 depth: 32 winAllocateFBShadowGDI - Dibsection width: 1600 height: 1199 depth: 32 size image: 7673600 winAllocateFBShadowGDI - Created shadow stride: 1600 winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp 32 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 - returning winScreenInit - returning winInitMultiWindowWM - Hello winInitMultiWindowWM - Calling pthread_mutex_lock () winMultiWindowXMsgProc - Hello winMultiWindowXMsgProc - Calling pthread_mutex_lock () InitOutput - Returning. 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) (EE) No primary keyboard configured (==) Using compiletime defaults for keyboard Rules = "xfree86" Model = "pc101" Layout = "us" Variant = "(null)" Options = "(null)" winPointerWarpCursor - Discarding first warp: 800 599 winBlockHandler - Releasing pmServerStarted winInitMultiWindowWM - pthread_mutex_lock () returned. winInitMultiWindowWM - Calling setlocale () winBlockHandler - pthread_mutex_unlock () returned winProcEstablishConnection - Hello winInitClipboard () winProcEstablishConnection - winInitClipboard returned. winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winClipboardProc - Calling setlocale () winInitMultiWindowWM - setlocale () returned ------------8<------------ bottom cut <- top ------------->8------------ I'm going back to an earlier version. Thanks. Lester -- Prof. Lester Ingber ingber@ingber.com ingber@alumni.caltech.edu www.ingber.com www.alumni.caltech.edu/~ingber
next reply other threads:[~2004-01-12 22:09 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-01-12 22:09 Lester Ingber [this message] 2004-01-12 22:15 ` Harold L Hunt II 2004-01-13 0:49 Lester Ingber 2004-01-13 0:57 ` Harold L Hunt II 2004-01-13 2:21 Lester Ingber 2004-01-13 5:38 ` Harold L Hunt II
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20040112220931.GA400@ingber.com \ --to=ingber@ingber.com \ --cc=cygwin-xfree@cygwin.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).