Clipboard problems with xemacs whole-line selection

2004-08-10 Thread Ed Avis
winProcessXEventsTimeout - Call to select () failed: 0.  Bailing.
winClipboardFlushXEvents - SelectionRequest - GetClipboardData () failed: 2749
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for 
CompoundText, aborting: 1
winProcessXEventsTimeout - Call to select () failed: 0.  Bailing.
winClipboardFlushXEvents - SelectionRequest - GetClipboardData () failed: 2749
winProcessXEventsTimeout - Call to select () failed: 0.  Bailing.
winClipboardFlushXEvents - SelectionRequest - GetClipboardData () failed: 2749
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for 
UTF8String, aborting: 1
winProcessXEventsTimeout - Call to select () failed: 0.  Bailing.
winClipboardFlushXEvents - SelectionRequest - GetClipboardData () failed: 2749
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for 
CompoundText, aborting: 1
winProcessXEventsTimeout - Call to select () failed: 0.  Bailing.
winClipboardFlushXEvents - SelectionRequest - GetClipboardData () failed: 2749
winProcessXEventsTimeout - Call to select () failed: 0.  Bailing.
winClipboardFlushXEvents - SelectionRequest - GetClipboardData () failed: 2749
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for 
CompoundText, aborting: 1
winProcessXEventsTimeout - Call to select () failed: 0.  Bailing.
winClipboardFlushXEvents - SelectionRequest - GetClipboardData () failed: 2749
winProcessXEventsTimeout - Call to select () failed: 0.  Bailing.
winClipboardFlushXEvents - SelectionRequest - GetClipboardData () failed: 2749
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for 
CompoundText, aborting: 1
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for 
UTF8String, aborting: 1
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for 
CompoundText, aborting: 1
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for 
CompoundText, aborting: 1
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for 
CompoundText, aborting: 1
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for 
UTF8String, aborting: 1
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for 
CompoundText, aborting: 1


-- 
Ed Avis [EMAIL PROTECTED]




Re: X server window resizes after remote desktop, and can't resize back

2004-08-08 Thread Ed Avis
Here is another example of the problem where remote desktop causes the
X server window to resize but on logging in locally it doesn't get
restored to its former size.

If the bug is tricky to fix, a possible workaround would be to let the
user manually override the size of the X server window, for example by
enabling the Maximize button.

Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 6.7.0.0-12

Contact: [EMAIL PROTECTED]

XWin was started with the following command line:

/usr/X11R6/bin/XWin -clipboard -engine 1 -br 

ddxProcessArgument - Initializing default screens
winInitializeDefaultScreens - w 1200 h 1600
winInitializeDefaultScreens - Returning
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 - Using user's preference: 1
winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel
winAllocateFBShadowGDI - Creating DIB with width: 1194 height: 1547 depth: 32
winFinishScreenInitFB - Masks: 00ff ff00 00ff
winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32
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=250, rate=31
(--) winConfigKeyboard - Layout: 0809 (0809) 
(--) Using preset keyboard for English (United Kingdom) (809), type 4
Rules = xorg Model = pc105 Layout = gb Variant = (null) Options = (null)
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list!
winPointerWarpCursor - Discarding first warp: 597 773
winProcEstablishConnection - Hello
winInitClipboard ()
winProcEstablishConnection - winInitClipboard returned.
winClipboardProc - Hello
DetectUnicodeSupport - Windows NT/2000/XP
winClipboardProc - DISPLAY=127.0.0.1:0.0
winClipboardProc - XOpenDisplay () returned and successfully opened the display.
winProcSetSelectionOwner - Clipboard not yet started, aborting.
winProcSetSelectionOwner - Clipboard not yet started, aborting.
winProcessXEventsTimeout - Call to select () failed: 0.  Bailing.
winProcessXEventsTimeout - Call to select () failed: 0.  Bailing.
winProcessXEventsTimeout - Call to select () failed: 0.  Bailing.
winProcessXEventsTimeout - Call to select () failed: 0.  Bailing.
winProcessXEventsTimeout - Call to select () failed: 0.  Bailing.
winProcessXEventsTimeout - Call to select () failed: 0.  Bailing.
winProcessXEventsTimeout - Call to select () failed: 0.  Bailing.
winProcessXEventsTimeout - Call to select () failed: 0.  Bailing.
winWindowProc - WM_DISPLAYCHANGE - orig bpp: 32, last bpp: 32, new bpp: 8
winWindowProc - WM_DISPLAYCHANGE - new width: 1024 new height: 720
winWindowProc - WM_DISPLAYCHANGE - orig bpp: 32, last bpp: 8, new bpp: 32
winWindowProc - WM_DISPLAYCHANGE - new width: 1200 new height: 1600
winClipboardProc - winClipboardFlushWindowsMessageQueue trapped WM_QUIT message, 
exiting main loop.
winClipboardProc - XDestroyWindow succeeded.
winDeinitMultiWindowWM - Noting shutdown in progress
 

-- 
Ed Avis [EMAIL PROTECTED]




Re: Mouse pointer disappears

2004-05-12 Thread Ed Avis
Wilks, Dan [EMAIL PROTECTED] writes:

I have noticed that the mouse pointer disappears when the window has
focus.

Do you happen to use remote desktop or anything like it?

Yes, I occasionally remote desktop into the machine.

-- 
Ed Avis [EMAIL PROTECTED]



Re: X server window resizes after remote desktop, and can't resize back

2004-05-12 Thread Ed Avis
Ed Avis [EMAIL PROTECTED] writes:

I remote desktop'd into my XP machine using a smaller display size
than the monitor connected locally.  When I went back in front of the
machine I found that the X server window had shrunk to roughly the
size of the remote desktop screen, but had not grown back again when
I logged in locally.

Here is a second XWin.log showing the problem.  I tried changing the
display size from control panel back and forth a few times, but the X
server window refused to grow back to its former size.

Maybe there could be some logging saying 'I noticed a change in
Windows display size and I am resizing the X window accordingly' or 'I
noticed a change in Windows display size but will not change the X
window size'.  Then one could see what is the intended behaviour.

Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 6.7.0.0-7

Contact: [EMAIL PROTECTED]

XWin was started with the following command line:

/usr/X11R6/bin/XWin -clipboard -engine 1 -br 

ddxProcessArgument - Initializing default screens
winInitializeDefaultScreens - w 1200 h 1600
winInitializeDefaultScreens - Returning
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
winScreenInit - dwWidth: 1200 dwHeight: 1600
winSetEngine - Using user's preference: 1
winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel
winAllocateFBShadowGDI - Creating DIB with width: 1194 height: 1547 depth: 32
winAllocateFBShadowGDI - Dibsection width: 1194 height: 1547 depth: 32 size image: 
7388472
winAllocateFBShadowGDI - Created shadow stride: 1194
winFinishScreenInitFB - Masks: 00ff ff00 00ff
winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32
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=250, rate=31
(--) winConfigKeyboard - Layout: 0809 (0809) 
(--) Using preset keyboard for English (United Kingdom) (809), type 4
Rules = xorg Model = pc105 Layout = gb Variant = (null) Options = (null)
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list!
winPointerWarpCursor - Discarding first warp: 597 773
winProcEstablishConnection - Hello
winInitClipboard ()
winProcEstablishConnection - winInitClipboard returned.
winClipboardProc - Hello
DetectUnicodeSupport - Windows NT/2000/XP
winClipboardProc - DISPLAY=127.0.0.1:0.0
winClipboardProc - XOpenDisplay () returned and successfully opened the display.
winProcSetSelectionOwner - Clipboard not yet started, aborting.
winProcSetSelectionOwner - Clipboard not yet started, aborting.
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for 
CompoundText, aborting: 1
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for 
UTF8String, aborting: 1
winProcessXEventsTimeout - Call to select () failed: 0.  Bailing.
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for 
CompoundText, aborting: 1
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for 
UTF8String, aborting: 1
winProcessXEventsTimeout - Call to select () failed: 0.  Bailing.
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for 
CompoundText, aborting: 1
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for 
UTF8String, aborting: 1
winProcessXEventsTimeout - Call to select () failed: 0.  Bailing.
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for 
CompoundText, aborting: 1
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for 
UTF8String, aborting: 1
winProcessXEventsTimeout - Call to select () failed: 0.  Bailing.
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for 
CompoundText, aborting: 1
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for 
UTF8String, aborting: 1
winProcessXEventsTimeout - Call to select () failed: 0.  Bailing.
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for 
CompoundText, aborting: 1
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for 
UTF8String, aborting: 1
winProcessXEventsTimeout - Call to select () failed: 0.  Bailing.
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for 
CompoundText, aborting: 1
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for 
UTF8String, aborting: 1
winProcessXEventsTimeout - Call to select () failed: 0.  Bailing.
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed

Mouse pointer disappears

2004-05-11 Thread Ed Avis
With the current Cygwin X server (or what is as close as I can get to
the current one, because cygwin.com is unreachable for me) I have
noticed that the mouse pointer disappears when the window has focus.
If I just move the pointer over the X server window and it isn't
focused then the pointer changes into a correct X pointer for the
application running in the X server (for example it changes into an
up-down arrow when hovering over the modeline in xemacs).  But as soon
as I click in the X server window to give it focus, the mouse pointer
disappears and remains disappeared as long as the pointer location is
above the X server window, and that window is focused.

I can't reproduce this every time but I have seen it on a few
occasions.  Here is a log file:

Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 6.7.0.0-7

Contact: [EMAIL PROTECTED]

XWin was started with the following command line:

/usr/X11R6/bin/XWin -clipboard -engine 1 -br 

ddxProcessArgument - Initializing default screens
winInitializeDefaultScreens - w 1200 h 1600
winInitializeDefaultScreens - Returning
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
winScreenInit - dwWidth: 1200 dwHeight: 1600
winSetEngine - Using user's preference: 1
winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel
winAllocateFBShadowGDI - Creating DIB with width: 1194 height: 1547 depth: 32
winAllocateFBShadowGDI - Dibsection width: 1194 height: 1547 depth: 32 size image: 
7388472
winAllocateFBShadowGDI - Created shadow stride: 1194
winFinishScreenInitFB - Masks: 00ff ff00 00ff
winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32
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=250, rate=31
(--) winConfigKeyboard - Layout: 0809 (0809) 
(--) Using preset keyboard for English (United Kingdom) (809), type 4
Rules = xorg Model = pc105 Layout = gb Variant = (null) Options = (null)
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list!
winPointerWarpCursor - Discarding first warp: 597 773
winProcEstablishConnection - Hello
winInitClipboard ()
winProcEstablishConnection - winInitClipboard returned.
winClipboardProc - Hello
DetectUnicodeSupport - Windows NT/2000/XP
winClipboardProc - DISPLAY=127.0.0.1:0.0
winClipboardProc - XOpenDisplay () returned and successfully opened the display.


-- 
Ed Avis [EMAIL PROTECTED]




X server hangs when pasting into Windows apps

2004-05-11 Thread Ed Avis
 for 
CompoundText, aborting: 1


-- 
Ed Avis [EMAIL PROTECTED]




X server window resizes after remote desktop, and can't resize back

2004-05-04 Thread Ed Avis
I remote desktop'd into my XP machine using a smaller display size
than the monitor connected locally.  When I went back in front of the
machine I found that the X server window had shrunk to roughly the
size of the remote desktop screen, but had not grown back again when I
logged in locally.

The maximize button on the window is greyed out and I can't resize the
window using its borders, so there seems to be no way to restore the
original size.  The log (shown below) indicates that the X server did
notice the change of screen size, but for whatever reason didn't
resize its window.

I think it is a bug that the window didn't get restored to its
original size, but I'd also like to request some kind of manual
resizing option (perhaps ungreying the maximize button) so the server
can be fixed if the problem happens again.

Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 6.7.0.0-4

Contact: [EMAIL PROTECTED]

XWin was started with the following command line:

/usr/X11R6/bin/XWin -clipboard -engine 1 -br 

ddxProcessArgument - Initializing default screens
winInitializeDefaultScreens - w 1200 h 1600
winInitializeDefaultScreens - Returning
OsVendorInit - Creating bogus screen 0
winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1
winValidateArgs - Returning.
(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
winScreenInit - dwWidth: 1200 dwHeight: 1600
winSetEngine - Using user's preference: 1
winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel
winCreateBoundingWindowWindowed - User w: 1200 h: 1600
winCreateBoundingWindowWindowed - Current w: 1200 h: 1600
winAdjustForAutoHide - Original WorkArea: 0 0 1572 1200
winAdjustForAutoHide - Adjusted WorkArea: 0 0 1572 1200
winCreateBoundingWindowWindowed - WindowClient w 1194 h 1547 r 1194 l 0 b 1547 t 0
winCreateBoundingWindowWindowed -  Returning
winAllocateFBShadowGDI - Creating DIB with width: 1194 height: 1547 depth: 32
winAllocateFBShadowGDI - Dibsection width: 1194 height: 1547 depth: 32 size image: 
7388472
winAllocateFBShadowGDI - Created shadow stride: 1194
winFinishScreenInitFB - Masks: 00ff ff00 00ff
winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32
winRandRInit ()
winCreateDefColormap - Deferring to fbCreateDefColormap ()
winFinishScreenInitFB - returning
winScreenInit - returning
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=250, rate=31
(--) winConfigKeyboard - Layout: 0809 (0809) 
(--) Using preset keyboard for English (United Kingdom) (809), type 4
Rules = xorg Model = pc105 Layout = gb Variant = (null) Options = (null)
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list!
winPointerWarpCursor - Discarding first warp: 597 773
winBlockHandler - Releasing pmServerStarted
winBlockHandler - pthread_mutex_unlock () returned
winProcEstablishConnection - Hello
winInitClipboard ()
winProcEstablishConnection - winInitClipboard returned.
winClipboardProc - Hello
DetectUnicodeSupport - Windows NT/2000/XP
winClipboardProc - DISPLAY=127.0.0.1:0.0
winClipboardProc - XOpenDisplay () returned and successfully opened the display.
winClipboardWindowProc - WM_DRAWCLIPBOARD - Initializing - Returning.
winProcSetSelectionOwner - Clipboard not yet started, aborting.
winProcSetSelectionOwner - Clipboard not yet started, aborting.
winWindowProc - WM_DISPLAYCHANGE - orig bpp: 32, last bpp: 32, new bpp: 32
winWindowProc - WM_DISPLAYCHANGE - new width: 1600 new height: 1200
winWindowProc - WM_DISPLAYCHANGE - orig bpp: 32, last bpp: 32, new bpp: 32
winWindowProc - WM_DISPLAYCHANGE - new width: 1200 new height: 1600
winWindowProc - WM_DISPLAYCHANGE - orig bpp: 32, last bpp: 32, new bpp: 8
winWindowProc - WM_DISPLAYCHANGE - new width: 1152 new height: 864
winWindowProc - WM_DISPLAYCHANGE - orig bpp: 32, last bpp: 8, new bpp: 8
winWindowProc - WM_DISPLAYCHANGE - new width: 1200 new height: 900
winWindowProc - WM_DISPLAYCHANGE - orig bpp: 32, last bpp: 8, new bpp: 32
winWindowProc - WM_DISPLAYCHANGE - new width: 1200 new height: 1600


-- 
Ed Avis [EMAIL PROTECTED]




Clipboard mini-hangs with 6.7.0.0-4

2004-04-19 Thread Ed Avis
winProcessXEventsTimeout - Call to select () failed: 0.  Bailing.
winClipboardFlushXEvents - SelectionRequest - GetClipboardData () failed: 2749
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for 
CompoundText, aborting: 1
winProcessXEventsTimeout - Call to select () failed: 0.  Bailing.
winClipboardFlushXEvents - SelectionRequest - GetClipboardData () failed: 2749

-- 
Ed Avis [EMAIL PROTECTED]




--help option for run.exe and XWin.exe

2004-04-17 Thread Ed Avis
It would be useful if run.exe and XWin.exe had a --help option.  XWin
will print usage if it sees an unrecognized option, but the message
goes to stderr + popup window; --help normally means print usage to
stdout and exit successfully.

-- 
Ed Avis [EMAIL PROTECTED]




Re: Crash when remote desktop changes screen resolutions

2004-04-14 Thread Ed Avis
 - XConvertSelection () failed for 
UTF8String, aborting: 1
winProcessXEventsTimeout - Call to select () failed: 0.  Bailing.
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for 
CompoundText, aborting: 1
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for 
UTF8String, aborting: 1
winProcessXEventsTimeout - Call to select () failed: 0.  Bailing.
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for 
CompoundText, aborting: 1
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for 
UTF8String, aborting: 1
winProcessXEventsTimeout - Call to select () failed: 0.  Bailing.
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for 
CompoundText, aborting: 1
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for 
UTF8String, aborting: 1
winProcessXEventsTimeout - Call to select () failed: 0.  Bailing.
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for 
CompoundText, aborting: 1
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for 
UTF8String, aborting: 1
winProcessXEventsTimeout - Call to select () failed: 0.  Bailing.
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for 
CompoundText, aborting: 1
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for 
UTF8String, aborting: 1
winProcessXEventsTimeout - Call to select () failed: 0.  Bailing.
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for 
CompoundText, aborting: 1
winClipboardFlushXEvents - SelectionNotify - XConvertSelection () failed for 
UTF8String, aborting: 1
winProcessXEventsTimeout - Call to select () failed: 0.  Bailing.
winWindowProc - WM_DISPLAYCHANGE - orig bpp: 32, last bpp: 32, new bpp: 8
winWindowProc - WM_DISPLAYCHANGE - new width: 800 new height: 600
winWindowProc - WM_DISPLAYCHANGE - orig bpp: 32, last bpp: 8, new bpp: 32
winWindowProc - WM_DISPLAYCHANGE - new width: 1280 new height: 1024

-- 
Ed Avis [EMAIL PROTECTED]



Double-clicking on tray icon

2004-04-08 Thread Ed Avis
Double-clicking on the 'X' icon in the Windows system tray brings up a
dialogue box asking if you want to kill the X server, but I think it
should bring the X window to the foreground (if single-window mode).

-- 
Ed Avis [EMAIL PROTECTED]




Re: Crash when remote desktop changes screen resolutions

2004-04-07 Thread Ed Avis

-- 
Ed Avis [EMAIL PROTECTED]




Crash when remote desktop changes screen resolutions

2004-04-06 Thread Ed Avis
 reported that the primary 
surface was lost, trying to restore, retry: 2
winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Restore returned: DD_OK
winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary 
surface was lost, trying to restore, retry: 1
winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Restore returned: DD_OK
winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary 
surface was lost, trying to restore, retry: 2
winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Restore returned: DD_OK
winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary 
surface was lost, trying to restore, retry: 1
winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Restore returned: DD_OK
winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary 
surface was lost, trying to restore, retry: 1
winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Restore returned: DD_OK
winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary 
surface was lost, trying to restore, retry: 1
winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Restore returned: DD_OK
winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary 
surface was lost, trying to restore, retry: 2
winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Restore returned: DD_OK
winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary 
surface was lost, trying to restore, retry: 1
winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Restore returned: DD_OK
winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary 
surface was lost, trying to restore, retry: 1
winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Restore returned: DD_OK
winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary 
surface was lost, trying to restore, retry: 2
winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Restore returned: DD_OK
winWindowProc - WM_DISPLAYCHANGE - orig bpp: 32, last bpp: 32, new bpp: 8
winWindowProc - WM_DISPLAYCHANGE - new width: 1024 new height: 720
winWindowProc - Disruptive change in depth
winDisplayDepthChangeDialog - DialogBox returned: 8585334
winDisplayDepthChangeDialog - GetLastError: 6
winReleasePrimarySurfaceShadowDDNL - Hello
winReleasePrimarySurfaceShadowDDNL - Detached clipper
winReleasePrimarySurfaceShadowDDNL - Released primary surface
winCreatePrimarySurfaceShadowDDNL - Creating primary surface
winCreatePrimarySurfaceShadowDDNL - Could not create primary surface: 8876024e
winWindowProc - WM_ACTIVATE - Bad depth, trying to override window activation
winWindowProc - WM_ACTIVATE - Bad depth, trying to override window activation
winWindowProc - WM_ACTIVATE - Bad depth, trying to override window activation
winWindowProc - WM_ACTIVATE - Bad depth, trying to override window activation
winWindowProc - WM_ACTIVATE - Bad depth, trying to override window activation
winChangeDelthDlgProc - wParam == s_pScreenInfo-dwBPP
winWindowProc - WM_DISPLAYCHANGE - orig bpp: 32, last bpp: 8, new bpp: 32
winWindowProc - WM_DISPLAYCHANGE - new width: 1280 new height: 1024
winReleasePrimarySurfaceShadowDDNL - Hello
winReleasePrimarySurfaceShadowDDNL - Released primary surface
winCreatePrimarySurfaceShadowDDNL - Creating primary surface
winCreatePrimarySurfaceShadowDDNL - Could not create primary surface: 8876024e
winClipboardProc - Call to select () failed: -1.  Bailing.
winClipboardProc - XDestroyWindow succeeded.


-- 
Ed Avis [EMAIL PROTECTED]




Re: test case for clipboard hang?

2004-03-29 Thread Ed Avis
Harold L Hunt II huntharo at msu.edu writes:

1) Reboot
2) start a fresh xwin, xterm, notepad, and put some text in the xterm and 
   notepad
3) select, ^C copy from notepad, middle-click in xterm. it pastes 
   successfully
4) select in xterm, leave the text reverse-videoed
5) ^V paste into notepad (successfully)
6) drop the selection in xterm (by left clicking somewhere)
7) ^V paste into notepad (successfully, even though the selection is 
   dropped)
8) select a different piece of text in xterm.
9) drop the selection in xterm
10) ^V paste into notepad: it hangs for a few seconds and doesn't paste. 
(The paste menu option is NOT greyed out at this point).

I'd really appreciate some feedback on the new fix in 
XFree86-xserv-4.3.0-63, which should be hitting mirrors within a few hours.

Yes, I can reproduce the hang with 4.3.0-50 (actually, I used xemacs not xterm)
but it does not hang in 4.3.0-63.  After I drop the X selection it is no longer
in the Windows clipboard, so that I cannot paste into Notepad.  I don't know if
this is consistent with cut and paste on a native X desktop, but it is a massive
improvement over hanging.  Thanks!

-- 
Ed Avis [EMAIL PROTECTED]



Re: Still clipboard deadlock with 4.3.0-50

2004-03-09 Thread Ed Avis
Igor Pechtchanski writes:

The log that you show below confirms that you *do not* have 4.3.0-50
installed,

That's what I suspected, but the setup program is quite sure it
installed -50...

Please configure your mailer to not quote raw e-mail addresses in
replies -- the spam harvesters have it too easy as it is.

As far as I know it quotes only the From header of the previous
message, which is already publicly readable?  I have hidden your
address in this case but I don't think you can require others to keep
hidden something which you have publicly disclosed.

If you're referring to the web archive, and the fact that it applies
some simple obfuscation to From: but not to message bodies, then I'll
change my mailer's behaviour if the list owner requests it.

Also, if you had a copy of XWin.exe running at the time you did the
install, setup was not able to replace it, but instead scheduled a
replace-on-reboot for it.  Search /var/log/setup.log for Scheduled
reboot replacement.

Yes, I see it.  But I did reboot my machine, as the setup program
suggested.

Anyway I moved XWin.exe.new to XWin.exe and I am now running the
latest version.

-- 
Ed Avis [EMAIL PROTECTED]



Really still clipboard deadlock with 4.3.0-50

2004-03-09 Thread Ed Avis
winProcSetSelectionOwner - OpenClipboard () failed: 
winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary 
surface was lost, trying to restore, retry: 1
winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Restore returned: 

-- 
Ed Avis [EMAIL PROTECTED]




Still clipboard deadlock with 4.3.0-50

2004-03-08 Thread Ed Avis
Ed Avis [EMAIL PROTECTED] writes:

Harold L Hunt II [EMAIL PROTECTED] writes:

XFree86-xserv-4.3.0-49 has some changes that may help to recover
from and/or to prevent the deadlock situations.  Please try it and
let me know if it improves things or not.

Thanks for looking at this - I will try 4.3.0-50.

Unfortunately even after updating with the setup program and
rebooting, running XWin.exe -clipboard can hang Windows apps when I
try to paste into them.  However I am not sure that I'm even running
the -50 release because I don't see any version banner in XWin.log.
The setup program says I have -50 installed, but is it telling the
truth?  The XWin.log follows.

ddxProcessArgument - Initializing default screens
winInitializeDefaultScreens - w 1280 h 1024
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 001f
InitOutput - g_iNumScreens: 1 iMaxConsecutiveScreen: 1
winScreenInit - dwWidth: 1280 dwHeight: 1024
winSetEngine - Using Shadow DirectDraw NonLocking
winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits per pixel
winCreateBoundingWindowWindowed - User w: 1280 h: 1024
winCreateBoundingWindowWindowed - Current w: 1280 h: 1024
winAdjustForAutoHide - Original WorkArea: 0 0 996 1280
winAdjustForAutoHide - Adjusted WorkArea: 0 0 996 1280
winCreateBoundingWindowWindowed - WindowClient w 1274 h 971 r 1274 l 0 b 971 t 0
winCreateBoundingWindowWindowed -  Returning
winCreatePrimarySurfaceShadowDDNL - Creating primary surface
winCreatePrimarySurfaceShadowDDNL - Created primary surface
winCreatePrimarySurfaceShadowDDNL - Attached clipper to primary surface
winAllocateFBShadowDDNL - lPitch: 5096
winAllocateFBShadowDDNL - Created shadow pitch: 5096
winAllocateFBShadowDDNL - Created shadow stride: 1274
winFinishScreenInitFB - Masks: 00ff ff00 00ff
winInitVisualsShadowDDNL - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32
winCreateDefColormap - Deferring to fbCreateDefColormap ()
winFinishScreenInitFB - returning
winScreenInit - returning
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=250, rate=31
(--) winConfigKeyboard - Layout: 0809 (0809) 
(--) Using preset keyboard for English (United Kingdom) (809), type 4
(EE) No primary keyboard configured
(==) Using compiletime defaults for keyboard
Rules = xfree86 Model = pc105 Layout = gb Variant = (null) Options = (null)
winPointerWarpCursor - Discarding first warp: 637 485
winBlockHandler - Releasing pmServerStarted
winBlockHandler - pthread_mutex_unlock () returned
winProcEstablishConnection - Hello
winInitClipboard ()
winProcEstablishConnection - winInitClipboard returned.
winClipboardProc - Hello
DetectUnicodeSupport - Windows NT/2000/XP
OsVendorReset - Hello
(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 001f
InitOutput - g_iNumScreens: 1 iMaxConsecutiveScreen: 1
winScreenInit - dwWidth: 1274 dwHeight: 971
winSetEngine - Using Shadow DirectDraw NonLocking
winCreateBoundingWindowWindowed - User w: 1280 h: 1024
winCreateBoundingWindowWindowed - Current w: 1274 h: 971
winAdjustForAutoHide - Original WorkArea: 0 0 996 1280
winAdjustForAutoHide - Adjusted WorkArea: 0 0 996 1280
winCreateBoundingWindowWindowed - WindowClient w 1274 h 971 r 1274 l 0 b 971 t 0
winCreateBoundingWindowWindowed -  Returning
winClipboardProc - DISPLAY=127.0.0.1:0.0
winCreatePrimarySurfaceShadowDDNL - Creating primary surface
winCreatePrimarySurfaceShadowDDNL - Created primary surface
winCreatePrimarySurfaceShadowDDNL - Attached clipper to primary surface
winAllocateFBShadowDDNL - lPitch: 5096
winAllocateFBShadowDDNL - Created shadow pitch: 5096
winAllocateFBShadowDDNL - Created shadow stride: 1274
winFinishScreenInitFB - Masks: 00ff ff00 00ff
winInitVisualsShadowDDNL - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32
winCreateDefColormap - Deferring to fbCreateDefColormap ()
winFinishScreenInitFB - returning
winScreenInit - returning
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=250, rate=31
(--) winConfigKeyboard - Layout: 0809 (0809

Re: Still clipboard deadlock with 4.3.0-50

2004-03-08 Thread Ed Avis
Harold L Hunt II [EMAIL PROTECTED] writes:

XFree86-xserv-4.3.0-49 has some changes that may help to recover
from and/or to prevent the deadlock situations.

Unfortunately even after updating with the setup program and
rebooting, running XWin.exe -clipboard can hang Windows apps when I
try to paste into them.

Did you ever confirm for me that you are *not* also running xwinclip
at the same time as using -clipboard?

I have used -clipboard and I have used xwinclip, but never both at the
same time.

The log that you show below confirms that you *do not* have 4.3.0-50
installed, or that you are running some other version from your
startup scripts.  There should be a 5 line block at the top of the
log file since 4.3.0-49, but your log doesn't have it.

That's what I suspected, but the setup program is quite sure it
installed -50... I will check the timestamp on Xwin.exe and make sure
I'm not running an old copy.

-- 
Ed Avis [EMAIL PROTECTED]



Re: Feature request: version report

2004-03-03 Thread Ed Avis
Harold L Hunt II [EMAIL PROTECTED] writes:

If you could add some means to manually kill and/or restart the
clipboard code inside the X server then I could switch back without
the risk of losing work,

I would add a manual kill/restart as a last resort in a few months.
Until then I would prefer to swat bugs rather than try to work around
the problem.

I agree that fixing the bugs is better, but as well as testing XWin to
find bugs I also try to use it for work, and if Windows apps hang
unrecoverably then I can't use the clipboard support.  So you may be
able to swat bugs faster if users can use the software with less risk.

XFree86-xserv-4.3.0-49 has some changes that may help to recover from
and/or to prevent the deadlock situations.  Please try it and let me
know if it improves things or not.

Thanks for looking at this - I will try 4.3.0-50.  (And try running
with -clipboard once again.)

-- 
Ed Avis [EMAIL PROTECTED]



Feature request: version report

2004-03-02 Thread Ed Avis
I hope the developers will consider adding the following features to
make bug reporting easier:

- Version number of the X server printed at the top of XWin.log

- xwinclip --version

-- 
Ed Avis [EMAIL PROTECTED]




xwinclip consistently unable to open clipboard

2004-03-02 Thread Ed Avis
Because of experiencing hangs when using the built-in clipboard
support (see other threads), I have switched to running xwinclip.exe
separately.  It normally works but recently, with the X server having
been running for a while, xwinclip died with 'unable to open
clipboard'.  The full output was

UnicodeSupport - Windows NT/2000/XP
Unicode clipboard I/O
SelectionNotify - Reasserted ownership of ATOM: PRIMARY
[above line repeated many times]
OpenClipboard () failed: 

Previously, I've had xwinclip crash but been able to restart it.  But
now when I try to restart xwinclip it dies immediately:

UnicodeSupport - Windows NT/2000/XP
Unicode clipboard I/O
OpenClipboard () failed: 

Hmm, I was going to say, this happens every time I run it.  But during
the course of writing this message I pasted some text from the command
prompt window into PuTTY, and that seems to have cured the problem -
xwinclip is now chugging away happily.

So I just mention this in case it is interesting - sorry that I can't
reproduce the problem every time.  I am running XFree86-xserv 4.3.0-44
and XFree86-xwinclip 4.3.0-2.

-- 
Ed Avis [EMAIL PROTECTED]




Re: Minor progress on Windows clipboard deadlock

2004-03-02 Thread Ed Avis
Oyvind Harboe [EMAIL PROTECTED] writes:

[pasting from X to Windows hangs the Windows app]

I would say that there is inconclusive evidence that this this
deadlock does not occur under W2K with a single monitor, but only on
a XP machine w/multiple monitors.

Yes, I am using XP and two monitors, and I was pasting from the X
server displayed on one monitor to an app displayed in the other.  I
think.

I have not tested that the deadlock does not occur when not using two
monitors.

-- 
Ed Avis [EMAIL PROTECTED]



Re: Feature request: version report

2004-03-02 Thread Ed Avis
Harold L Hunt II [EMAIL PROTECTED] writes:

Regarding xwinclip, you should really be using (XWin -clipboard)

There are a couple of problems with -clipboard (discussed earlier on
this list) which have led me to switch back to xwinclip:

- Clipboard support seems to die, that is, the Windows clipboard and
  the X selection stop affecting one another.  xwinclip also tends to
  die occasionally but when this happens it can be restarted.

- Windows apps hanging when I try to paste into them.  This seems to
  have started since I began using two displays (though I am not 100%
  sure).  This bug reliably kills any Windows application so it is too
  dangerous for me to run XWin with clipboard enabled.  I have not
  seen this problem with xwinclip.

If you could add some means to manually kill and/or restart the
clipboard code inside the X server then I could switch back without
the risk of losing work, and I'd be happy to report the contents of
Xwin.log on the occasions when such a manual restart was necessary.

(In general, I think the clipboard support could be a bit noisier in
its logging since the contents of XWin.log never seems to give much
away about clipboard or selection change events - but maybe it is more
informative to you than to me.)

-- 
Ed Avis [EMAIL PROTECTED]



Re: XWin causes Windows apps to hang(?)

2004-02-20 Thread Ed Avis
Harold L Hunt II [EMAIL PROTECTED] writes:

[Windows app hangs when pasting to it from X]

Yes, the OpenClipboard failure is probably causing your crash.  Try
editing your startxwin.bat and removing the -clipboard parameter
being passed to XWin.exe.

If I do that then I can run a separate xwinclip.exe.  If xwinclip gets
into a wedged state then it can be killed and restarted.

There is likely a bug in XWin.exe's clipboard support that will need
to be fixed.

Let me know if you would like me to do something to help reproduce or
track down this bug.

-- 
Ed Avis [EMAIL PROTECTED]



Re: XWin causes Windows apps to hang(?)

2004-02-19 Thread Ed Avis
Ed Avis [EMAIL PROTECTED] writes:

- I copied a URL from an email message in Evolution
- When I paste into a Windows app, that Windows app is stuck. This
happened w/iexplorer and explorer.exe.

It appears as if the Windows app is stuck indefinitely waiting for
the pastable from XWin.

I am seeing this too.  I tried pasting into several different
applications, in all cases it caused the app to hang and I had to
kill it using the task manager.

Here is the XWin.log for an X session that does this.  The server is
running happily but it will crash any Windows app I try to paste into
from the X selection.  I wonder if it might be the line

winProcSetSelectionOwner - OpenClipboard () failed: 

The log follows.

ddxProcessArgument - Initializing default screens
winInitializeDefaultScreens - w 1280 h 1024
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 001f
InitOutput - g_iNumScreens: 1 iMaxConsecutiveScreen: 1
winScreenInit - dwWidth: 1280 dwHeight: 1024
winSetEngine - Using Shadow DirectDraw NonLocking
winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits per pixel
winCreateBoundingWindowWindowed - User w: 1280 h: 1024
winCreateBoundingWindowWindowed - Current w: 1280 h: 1024
winAdjustForAutoHide - Original WorkArea: 0 0 996 1280
winAdjustForAutoHide - Adjusted WorkArea: 0 0 996 1280
winCreateBoundingWindowWindowed - WindowClient w 1274 h 971 r 1274 l 0 b 971 t 0
winCreateBoundingWindowWindowed -  Returning
winCreatePrimarySurfaceShadowDDNL - Creating primary surface
winCreatePrimarySurfaceShadowDDNL - Created primary surface
winCreatePrimarySurfaceShadowDDNL - Attached clipper to primary surface
winAllocateFBShadowDDNL - lPitch: 5096
winAllocateFBShadowDDNL - Created shadow pitch: 5096
winAllocateFBShadowDDNL - Created shadow stride: 1274
winFinishScreenInitFB - Masks: 00ff ff00 00ff
winInitVisualsShadowDDNL - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32
winCreateDefColormap - Deferring to fbCreateDefColormap ()
winFinishScreenInitFB - returning
winScreenInit - returning
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=250, rate=31
(--) winConfigKeyboard - Layout: 0809 (0809) 
(--) Using preset keyboard for English (United Kingdom) (809), type 4
(EE) No primary keyboard configured
(==) Using compiletime defaults for keyboard
Rules = xfree86 Model = pc105 Layout = gb Variant = (null) Options = (null)
winPointerWarpCursor - Discarding first warp: 637 485
winBlockHandler - Releasing pmServerStarted
winBlockHandler - pthread_mutex_unlock () returned
winProcEstablishConnection - Hello
winInitClipboard ()
winProcEstablishConnection - winInitClipboard returned.
winClipboardProc - Hello
DetectUnicodeSupport - Windows NT/2000/XP
winClipboardProc - DISPLAY=127.0.0.1:0.0
winClipboardProc - XOpenDisplay () returned and successfully opened the display.
winClipboardWindowProc - WM_DRAWCLIPBOARD - Initializing - Returning.
winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary 
surface was lost, trying to restore, retry: 1
winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Restore returned: 
winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary 
surface was lost, trying to restore, retry: 1
winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Restore returned: 
winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary 
surface was lost, trying to restore, retry: 1
winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Restore returned: 
winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary 
surface was lost, trying to restore, retry: 1
winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Restore returned: 
winProcSetSelectionOwner - OpenClipboard () failed: 
winProcSetSelectionOwner - OpenClipboard () failed: 
winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary 
surface was lost, trying to restore, retry: 1
winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Restore returned: 
winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary 
surface was lost, trying to restore, retry: 1
winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Restore returned: 
winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary 
surface was lost, trying to restore, retry: 1
winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Restore returned

Re: remote xemacs and selection problem (using XWin -clipboard)

2004-02-12 Thread Ed Avis
Kris Thielemans [EMAIL PROTECTED] writes:

I have a problem running XEmacs remotely. When I press ctrl-space, I
do get 'mark set', but when I then press Ctrl-w to cut something, I
get 'The region is not active now'.

The problem disappears when I remove the -clipboard option from Xwin.

I think you can fix this by setting transient-mark-mode.  I know I had
the same problem with my XEmacs, and fixed it somehow, but strangely I
can't find any mention of transient-mark-mode in my ~/.emacs or
~/.xemacs/ although I do get the behaviour it turns on - not
highlighting the region when it is selected with the keyboard.

-- 
Ed Avis [EMAIL PROTECTED]



Re: Clipboard related failure

2004-02-12 Thread Ed Avis
[EMAIL PROTECTED] writes:

I just had and clipboard related problem, and a Windows notpad like
program stopped working (not responsive), along with it.

What did you do to cause the program to stop responding?  Others have
seen a problem where _pasting_ into a Windows application from the X
server causes the Windows app to hang.  See
http://article.gmane.org/gmane.os.cygwin.xfree/9829.

-- 
Ed Avis [EMAIL PROTECTED]