This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
RE: xwinclip usage?
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 mean
> > that you manually selected version 4.2.0-21 of XFree86-xserv? If not, then
> > you did not get the latest TEST release of the Cygwin/XFree86 X Server.
> >
> > Harold
> >
> > -----Original Message-----
> > From: cygwin-xfree-owner@cygwin.com
> > [mailto:cygwin-xfree-owner@cygwin.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 on
> > several Windows machines to connect to a Linux server.
> >
> > I recently noticed the announcement that xwinclip functionality has been
> > integrated into Xwin (with -clipboard) and so I thought I would give it
> > 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?
>