I just installed the latest test version of XWin.exe (4.2.0-8) using the Cygwin setup program and found that it is doing something very funky!
I'm running XWin in windowed mode (with -nodecoration flag) under Windows 2000 @ 1024x768 and 24bpp. I tried it in fullscreen mode @ 24bpp and there is no difference. I tried it in fullscreen mode @ 16bpp and 8bpp and it looked fine. Words can't do justice to what's going on. Here's a screenshot: http://members.tripod.com/tomandlaura0/cygwin/XWin-4.2.0-8_screenshot.gif Here are the contents of the log file. Nothing all that revealing, I'm afraid: ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1024 h 768 winInitializeDefaultScreens - Returning _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root winDetectSupportedEngines - Windows NT/2000 winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - Allowing PrimaryDD winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 0000001f winSetEngine - Using Shadow DirectDraw NonLocking winAdjustVideoModeShadowDDNL - Using Windows display depth of 24 bits per pixel winAdjustForAutoHide - Original WorkArea: 0 0 768 1024 winAdjustForAutoHide - Taskbar is auto hide winAdjustForAutoHide - Found BOTTOM auto-hide taskbar winAdjustForAutoHide - Adjusted WorkArea: 0 0 767 1024 winCreateBoundingWindowWindowed - WindowClient w 1024 h 767 r 1024 l 0 b 767 t 0 winCreateBoundingWindowWindowed - Returning winAllocateFBShadowDDNL - lPitch: 4096 winInitVisualsShadowDDNL - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp 24 winCreateDefColormap - Deferring to fbCreateDefColormap () winScreenInit - returning winCloseScreenShadowDDNL - Freeing screen resources _________________________________________________________________ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx
