RE: expelled wangle page sourwood
What are you talking about, Erin, This makes no sense and its not about cygwin-xfree. Off topic. If you want to takr about Cygwin Xfree, be my guest. This makes no sense at all. And I know. Because rumor has it, that I don't make sense at all either. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Erin Koenig Sent: Monday, August 16, 2004 10:10 AM To: [EMAIL PROTECTED] Subject: expelled wangle page sourwood attest pericles
RE: expelled wangle page sourwood
off topic. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Erin Koenig Sent: Monday, August 16, 2004 10:10 AM To: [EMAIL PROTECTED] Subject: expelled wangle page sourwood attest pericles
RE: expelled wangle page sourwood
Erin is not recieving mail, but she sure can mess up here with off topic email. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Bobby McNulty Junior Sent: Monday, August 16, 2004 11:13 AM To: [EMAIL PROTECTED]; Erin Koenig Subject: RE: expelled wangle page sourwood off topic. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Erin Koenig Sent: Monday, August 16, 2004 10:10 AM To: [EMAIL PROTECTED] Subject: expelled wangle page sourwood attest pericles
-multiwindow crash under XP
Hello, I am running the most recent version of the cygwin package under Windows XP. Everytime I try to start an Xwin session in -multiwindow mode my Cygwin-X crashes. This is where the hang-up occurs: (WM) /tmp mounted int textmode _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 (II) XF86Config is not supported (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 0007 winSetEngine - Multi Window or Rootless = ShadowGDI winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel winAllocateFBShadowGDI - Creating DIB with width: 1280 height: 960 depth: 32 winFinishScreenInitFB - Masks: 00ff ff00 00ff winInitVisualsShadowGDI - Masks 00ff ff00 00ff 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 Thanks for any help.
Re: -multiwindow crash under XP
A cursory search of the cygwin-xfree mailing list would have returned http://sources.redhat.com/ml/cygwin-xfree/2004-06/msg00100.html (and more) which talks about a variety of reasons for X failing including mounts, firewalls, and others. If you have already read and followed these suggestions, knowing this would have helped, as would reading and following http://www.cygwin.com/problems.html fullejr wrote: Hello, I am running the most recent version of the cygwin package under Windows XP. Everytime I try to start an Xwin session in -multiwindow mode my Cygwin-X crashes. This is where the hang-up occurs: (WM) /tmp mounted int textmode _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 (II) XF86Config is not supported (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 0007 winSetEngine - Multi Window or Rootless = ShadowGDI winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel winAllocateFBShadowGDI - Creating DIB with width: 1280 height: 960 depth: 32 winFinishScreenInitFB - Masks: 00ff ff00 00ff winInitVisualsShadowGDI - Masks 00ff ff00 00ff 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 Thanks for any help.
Testing CygWin XFree86 with multiple monitors
I'm using CygWin XFree86 with a dual monitor setup and a single monitor setup. In my experience there are, not surprisingly, more problems with the dual monitor setup. This made me think a bit about how multi-monitor CygWin XFree86 could get more testing. Is there any interest amongst CygWin XFree86 testers/develoeprs in a virtual device driver that will do the following? - allow adding of any number of virtual video cards. E.g. test CygWin XFree86 with 10 video cards? No problem! :-) - the video cards are visible indirectly by using e.g. the Accessibility-Magnifier - resolution is currently fixed at ~4000x2000x32bit, but it could be made configurable - the virtual device driver works by allocating a RAM buffer where all rendering takes place. Windows does all the rendering and it seems to be feature complete. OpenGL works, though I wouldn't hold my breath for DirectX apps. The source code is currently collecting dust, and I'm sure I could convince the owner to contribute it to the open source community if there is enough interest. -- Øyvind Harboe http://www.zylin.com
Re: startx hangs on WinXP, xinit doesn't
More details - I tried to debug the problem (as much as I could) and this is what I found out. First I found out how startx calls xinit - xinit /usr/X11R6/lib/X11/xinit/xinitrc -- \ -multiwindow -clipboard Since this exact command starts X every time with no problem I looked at the output when running startx and xinit - the only difference is that with xinit I call more routines - here is the diff --- $ diff startx.out xinit.out 46a47,51 winInitClipboard () winProcEstablishConnection - winInitClipboard returned. winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winClipboardProc - DISPLAY=127.0.0.1:0.0 51a57,62 winClipboardProc - XOpenDisplay () returned and successfully opened the display. winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. winProcSetSelectionOwner - Clipboard not yet started, aborting. winProcSetSelectionOwner - Clipboard not yet started, aborting. winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the display. - The only difference in the execution of the two is the environment so I experimented and finally I commented this portion of startx script - if [ x$XAUTHORITY = x ]; then XAUTHORITY=$HOME/.Xauthority export XAUTHORITY fi Once I commented that out I get X to start correctly and the output is the same as it is with xinit on its own. It's been long time since I worked with X - any ideas why XAUTHORITY set makes startx to hang ? thanks --pv __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com