Fri Jan 24 23:08:00 GMT 2003
Thanks for replying. Since I have more time on my hands than sense, I
decided to play with various versions of XWin.exe and xwinclip.exe to
see if your guess is correct. Hate to tell you this, but your guess was
not correct. The older version of XWin.exe does indeed work.
Here's the setup:
XWIN.exe (2 versions):
xwinclip.exe (2 versions):
Batch file to start XWin and xwinclip
(don't recall what the -ac switch is for):
start c:\cygwin\usr\x11r6\bin\xwin -ac -query 192.168.0.10
start /m xwinclip
Results of 4 combinations:
#1 & #3 - works
#2 & #3 - does not work
#1 & #4 - works
#2 & #4 - does not work
*Works - can copy/paste
*Does not work - can not copy/paste
So you can see that the version of xwinclip doesn't seem to matter.
It's the version of XWin.exe that determines if my copy/paste
functionality works or not. The batch file remained the same for all
There was a slight difference in the way xwinclip exited after closing
down my xdmcp session. The newer one seems to take a lot longer to
realize that the xdmcp session has closed and thus takes longer to close
itself. So I think I'll stick with the older xwinclip.exe as well as
the older XWin.exe.
Anyway, thought you'd like to know just in case it helps to get
clipboard functionality sorted out. I'll keep watching for any updates
to test. Getting that -clipboard switch working would be swell!
On Fri, 2003-01-24 at 15:21, Harold L Hunt II wrote:
> All I can tell you right now is that it has always been a pain to get
> xwinclip (or any local X client for that matter) to work with XWin.exe when
> you are using -query for an XDMCP session.
> I can also tell you that I doubt that the new version of XWin.exe is causing
> the stand-alone xwinclip not to work. That just doesn't make sense. More
> likely is that you accidentally were doing something differently that you
> have now forgotten to do. To prove me wrong, download one of those test
> versions that would have been in place in October. It looks like you should
> try Test64 or Test68... but I bet your results will be the same.
> I really need an XDMCP/X security expert to explain this to me COMPLETELY.
> Sure, others have mentioned a few things that might be causing the problem,
> which generally is of no benefit to me. I need someone to sit down for
> three hours and actually test the various modes that xwinclip can be started
> in and what you have to do in order to get xwinclip (or any local X client)
> to connect to XWin.exe when using -query. I don't want suggestions, I don't
> want speculation, I want someone to tell me what needs to be done to take
> care of this once and for all. I admit, I cannot fix this problem. Someone
> will have to fix it for me, and they will have to do a good job of it
> otherwise it will not be of any benefit to me.
> Until that someone steps forward, I am fresh out of ideas,
> -----Original Message-----
> From: firstname.lastname@example.org
> [mailto:email@example.com]On Behalf Of Marc Williams
> Sent: Friday, January 24, 2003 3:21 PM
> To: Cygwin list
> Subject: RE: xwinclip usage?
> Ok, now I'm begging for help.
> I installed Test74 this morning and I still can't get my sessions to
> copy/paste to/from each other.
> xwinclip should work as a seperate invocation following XWin.exe as long
> as I remove -clipboard as a switch from XWin, right? I tried that and
> it doesn't work either. XWin starts the xdmcp session fine but then
> starting xwinclip gives me this:
> UnicodeSupport - Windows 95/98/Me
> Could not open display, try: 1, sleeping: 4
> Could not open display, try: 2, sleeping: 4
> Could not open display, try: 3, sleeping: 4
> Failed opening the display, giving up
> So for right now, I can't get xwinclip to work either as a stand alone
> or as a switch on XWin.
> Please help!!!
> p.s. xwinclip was working well from a build of last October so I know
> it's possible...
> On Thu, 2003-01-23 at 16:57, Marc Williams wrote:
> > Since I'm still looking for ideas why my copy n paste isn't working for
> > me, here's my log (I suppose it'll wrap and look crappy):
> > ddxProcessArgument - Initializing default screens
> > winInitializeDefaultScreens - w 1024 h 768
> > winInitializeDefaultScreens - Returning
> > OsVendorInit - Creating bogus screen 0
> > _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
> > (EE) Unable to locate/open config file
> > InitOutput - Error reading config file
> > winDetectSupportedEngines - Windows 95/98/Me
> > winDetectSupportedEngines - DirectDraw installed
> > winDetectSupportedEngines - DirectDraw4 installed
> > winDetectSupportedEngines - Returning, supported engines 00000017
> > InitOutput - g_iNumScreens: 1 iMaxConsecutiveScreen: 1
> > winSetEngine - Using Shadow DirectDraw NonLocking
> > winAdjustVideoModeShadowDDNL - Using Windows display depth of 24 bits
> > per pixel
> > winCreateBoundingWindowWindowed - Initial w: 1024 h: 768
> > 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 1018 h 742 r 1018 l 0 b
> > 742 t 0
> > winCreateBoundingWindowWindowed - Returning
> > winCreatePrimarySurfaceShadowDDNL - Creating primary surface
> > winCreatePrimarySurfaceShadowDDNL - Created primary surface
> > winCreatePrimarySurfaceShadowDDNL - Attached clipper to primary surface
> > winAllocateFBShadowDDNL - lPitch: 4072
> > winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff
> > winInitVisualsShadowDDNL - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24
> > bpp 24
> > winCreateDefColormap - Deferring to fbCreateDefColormap ()
> > winInitClipboard ()
> > winScreenInit - returning
> > (EE) No primary keyboard configured
> > (==) Using compiletime defaults for keyboard
> > Rules = "xfree86" Model = "pc101" Layout = "us" Variant = "(null)"
> > Options = "(null)"
> > winBlockHandler - Signalling pcServerStarted
> > Thanks for any ideas...
> > On Thu, 2003-01-23 at 12:01, Marc Williams wrote:
> > > My mistake, but...
> > >
> > > I indeed didn't realize that there was a newer XWin.exe. I grabbed and
> > > installed it and the -clipboard switch now doesn't stop the process. Ny
> > > remote screen appears just fine. Sorry about my oversight.
> > >
> > > However, the clipboard doesn't seem to function. I can't seem to copy
> > > and/or paste from either remote <-> local. I tried windowed and
> > > fullscreen with the same results. Here's my bat file:
> > >
> > > SET PATH=c:\cygwin\usr\X11R6\bin;c:\cygwin\bin;c:\cygwin\usr\bin;%PATH%
> > > SET DISPLAY=127.0.0.1:0.0
> > > start c:\cygwin\usr\x11r6\bin\xwin -query 192.168.0.10 -clipboard
> > > exit
> > >
> > > Pretty basic. Any tips?
> > > Thanks!
> > >
> > >
> > > On Thu, 2003-01-23 at 10:54, Harold L Hunt II wrote:
> > > > Marc,
> > > >
> > > > Oh, and by downloading all the newest Cygwin and XFree86 stuff did you
> > > > that you manually selected version 4.2.0-21 of XFree86-xserv? If not,
> > > > you did not get the latest TEST release of the Cygwin/XFree86 X
> > > >
> > > > Harold
> > > >
> > > > -----Original Message-----
> > > > From: firstname.lastname@example.org
> > > > [mailto:email@example.com]On Behalf Of Marc Williams
> > > > Sent: Thursday, January 23, 2003 11:02 AM
> > > > To: Cygwin list
> > > > Subject: xwinclip usage?
> > > >
> > > >
> > > > For quite some time now I've been successfully running xdmcp via Xwin
> > > > several Windows machines to connect to a Linux server.
> > > >
> > > > I recently noticed the announcement that xwinclip functionality has
> > > > integrated into Xwin (with -clipboard) and so I thought I would give
> > > > a shot. I downloaded and installed all the newest cygwin and xfree
> > > > stuff. Everything went fine and everything seems to work just great.
> > > > Except xwinclip. It doesn't work as a Xwin switch. At least not with
> > > > my -query switch. When -clipboard is added to the CL, nothing starts.
> > > > Just sits there. When -clipboard is removed leaving my original cl,
> > > > Xwin works fine as expected.
> > > >
> > > > Is it possible I'm doing something wrong or is this a known issue? If
> > > > so, any plans to fix it?
> > >
More information about the Cygwin-xfree