RE: still having a problem with xwinclip
Hi, could you please try to use: start /B XWin -ac -screen sleep 15 (or set a 'pause' and wait for about 15 Secs, now press any key) start /B xwinclip.exe best regards, Darko Palic Hi I used this in my start.bat: @echo off SET DISPLAY=127.0.0.1:0.0 SET PATH=d:\cygwin\usr\X11R6\bin;d:\cygwin\bin;d:\cygwin\usr\bin;%PATH% start XWin -screen 0 1280 1024 -depth 32 -engine 4 -kb -query myAIXmachine -fp tcp/myfontserver:7500 -fullscreen -once -ac start /B xwinclip.exe and it worked, but there is another problem - when I use xwinclip such way, it's impossible to logoff correctly and I have to shutdown XWin using Alt-F4 key. So I avoided using xwinclip. Pavel Harold Hunt [EMAIL PROTECTED] To: Eli Kleinman [EMAIL PROTECTED], [EMAIL PROTECTED] Sent by: cc: cygwin-xfree-owner@Subject: RE: still having a problem with xwinclip cygwin.com 10.04.2002 23:48 Eli, xwinclip is going to have problems in your scenario because CDE owns the display when you use XDMCP. I think someone may have figured out how to use xwinclip at the same time as an XDMCP session... you can search the mailing list archives for an answer to that. http://cygwin.com/ml/cygwin-xfree/ Harold -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Eli Kleinman Sent: Wednesday, April 10, 2002 5:47 PM To: [EMAIL PROTECTED] Subject: still having a problem with xwinclip I tried setting DISPLAY to :0.0 but this did not solve my problem this is what I use to start CDE $ export DISPLAY=192.9.200.136:0.0 xwin -noreset -screen 0 1152 864 -query 192.9.200.6 -fp tcp/192.9.200.6:7100 -from 192.9.200.136 [1] 600 this is what I try to use to start xwinclip and this is what i get $ export DISPLAY=:0.0 $ xwinclip.exe Xlib: connection to :0.0 refused by server Xlib: No protocol specified Could not open display Could some one please help me
RE: Problems installing cygwin-xfree86 on a Dell WIN2K box
If you read the Cygwin/XFree86 User's Guide instructions on installation then you would know exactly what to do. http://xfree86.cygwin.com/docs/ug/ Harold -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Christopher Faylor Sent: Thursday, April 11, 2002 11:40 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Problems installing cygwin-xfree86 on a Dell WIN2K box Redirecting to the proper mailing list. cgf On Thu, Apr 11, 2002 at 10:17:28AM -0500, Dr. Lawrence Ward Spradley wrote: Sirs: This is a (hopefully more illuminating) follow-up to a post from yesterday. I am midstroke in installing cygwin-XFree86 on a Dell Win2000 box. As of yesterday, I had followed the directions on the webpage detailing the installation process verbatim. This meant that I had a limited cygwin install (no vi, no grep, etc.). I have installed more of the tools as of this A.M. and am able to provide more info on my status as of now. I attach the output of cygcheck -s -r -v to describe my install as of now. I also looked through the Xinstall.sh script to try to assess why it was stopping. It appears to need a program called extract, which I think is part of the XFree86 download. The script also contains comments about linking extract to gnu-tar. I did an ls -l on my bin directory, which contains the extract executable as well as the tar executable, observed that they are different (different sizes date stamps). I want the XFree86 to be able to use rxvt as a shell to begin with, but we will be possibly wanting to do more later. I am still stuck in the XFree86 install with error messages from the Xinstall.sh script complaining about the extract program being bad. Thanks in advance for your time. I will be happy to provide any more info if needed. Cygwin Win95/NT Configuration Diagnostics Current System Time: Thu Apr 11 09:56:29 2002 Windows 2000 Professional Ver 5.0 Build 2195 Service Pack 1 Path:C:\cygwin\usr\local\bin C:\cygwin\bin C:\cygwin\bin c:\Program Files\Microsoft Visual Studio\Common\Tools c:\Program Files\Microsoft Visual Studio\Common\Msdev98\BIN c:\Program Files\Microsoft Visual Studio\DF98\BIN c:\Program Files\Microsoft Visual Studio\VC98\BIN c:\WINNT\system32 c:\WINNT c:\WINNT\System32\Wbem c:\ c:\dell c:\Program Files\Dell\Resolution Assistant\Common\bin c:\TEC75\BIN c:\ABSOFT\BIN SysDir: C:\WINNT\System32 WinDir: C:\WINNT HOME = `c:\' MAKE_MODE = `unix' PWD = `/cygdrive/c/cygwin' USER = `lws' ABSOFT = `C:\ABSOFT' ALLUSERSPROFILE = `C:\Documents and Settings\All Users' APPDATA = `C:\Documents and Settings\Dr. Lawrence W. Spra\Application Data' COMMONPROGRAMFILES = `C:\Program Files\Common Files' COMPUTERNAME = `DELL' COMSPEC = `C:\WINNT\system32\cmd.exe' CPU = `i386' HOMEDRIVE = `C:' HOMEPATH = `\' INCLUDE = `C:\ABSOFT\CINCLUDE' LIB = `C:\ABSOFT\LIB' LINK_F90 = `imsl.lib imsls_err.lib imslmpistub.lib' LOGONSERVER = `\\DELL' MANPATH = `:/usr/ssl/man' NUMBER_OF_PROCESSORS = `1' OLDPWD = `/cygdrive/c/cygwin/tmp' OS2LIBPATH = `C:\WINNT\system32\os2\dll;' OS = `Windows_NT' PATHEXT = `.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH' PROCESSOR_ARCHITECTURE = `x86' PROCESSOR_IDENTIFIER = `x86 Family 6 Model 8 Stepping 6, GenuineIntel' PROCESSOR_LEVEL = `6' PROCESSOR_REVISION = `0806' PROGRAMFILES = `C:\Program Files' PROMPT = `$P$G' PS1 = `\[\033]0;\w\007 \033[32m\]\u@\h \[\033[33m\w\033[0m\] $ ' SHLVL = `1' SYSTEMDRIVE = `C:' SYSTEMROOT = `C:\WINNT' TEC75HOME = `C:\TEC75' TEMP = `c:\DOCUME~1\DRLAWR~1.SPR\LOCALS~1\Temp' TERM = `cygwin' TMP = `c:\DOCUME~1\DRLAWR~1.SPR\LOCALS~1\Temp' TMPDIR = `c:\DOCUME~1\DRLAWR~1.SPR\LOCALS~1\Temp' USERDOMAIN = `DELL' USERNAME = `lws' USERPROFILE = `C:\Documents and Settings\Dr. Lawrence W. Spra' VIM = `C:\PGI\cygusr\share\vim' VNI_F90_MSG = `C:\Program Files\Microsoft Visual Studio\DF98\IMSL\MESSAGE' WINDIR = `C:\WINNT' _ = `/usr/bin/cygcheck.exe' HKEY_CURRENT_USER\Software\Cygnus Solutions HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2 (default) = `/cygdrive' cygdrive flags = 0x0022 HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\Program Options HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\00 (default) = `C:' unix = `/' fbinary = 0x fsilent = 0x HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/
Re: Problems installing cygwin-xfree86 on a Dell WIN2K box
Redirecting to the proper mailing list. cgf On Thu, Apr 11, 2002 at 10:17:28AM -0500, Dr. Lawrence Ward Spradley wrote: Sirs: This is a (hopefully more illuminating) follow-up to a post from yesterday. I am midstroke in installing cygwin-XFree86 on a Dell Win2000 box. As of yesterday, I had followed the directions on the webpage detailing the installation process verbatim. This meant that I had a limited cygwin install (no vi, no grep, etc.). I have installed more of the tools as of this A.M. and am able to provide more info on my status as of now. I attach the output of cygcheck -s -r -v to describe my install as of now. I also looked through the Xinstall.sh script to try to assess why it was stopping. It appears to need a program called extract, which I think is part of the XFree86 download. The script also contains comments about linking extract to gnu-tar. I did an ls -l on my bin directory, which contains the extract executable as well as the tar executable, observed that they are different (different sizes date stamps). I want the XFree86 to be able to use rxvt as a shell to begin with, but we will be possibly wanting to do more later. I am still stuck in the XFree86 install with error messages from the Xinstall.sh script complaining about the extract program being bad. Thanks in advance for your time. I will be happy to provide any more info if needed. Cygwin Win95/NT Configuration Diagnostics Current System Time: Thu Apr 11 09:56:29 2002 Windows 2000 Professional Ver 5.0 Build 2195 Service Pack 1 Path: C:\cygwin\usr\local\bin C:\cygwin\bin C:\cygwin\bin c:\Program Files\Microsoft Visual Studio\Common\Tools c:\Program Files\Microsoft Visual Studio\Common\Msdev98\BIN c:\Program Files\Microsoft Visual Studio\DF98\BIN c:\Program Files\Microsoft Visual Studio\VC98\BIN c:\WINNT\system32 c:\WINNT c:\WINNT\System32\Wbem c:\ c:\dell c:\Program Files\Dell\Resolution Assistant\Common\bin c:\TEC75\BIN c:\ABSOFT\BIN SysDir: C:\WINNT\System32 WinDir: C:\WINNT HOME = `c:\' MAKE_MODE = `unix' PWD = `/cygdrive/c/cygwin' USER = `lws' ABSOFT = `C:\ABSOFT' ALLUSERSPROFILE = `C:\Documents and Settings\All Users' APPDATA = `C:\Documents and Settings\Dr. Lawrence W. Spra\Application Data' COMMONPROGRAMFILES = `C:\Program Files\Common Files' COMPUTERNAME = `DELL' COMSPEC = `C:\WINNT\system32\cmd.exe' CPU = `i386' HOMEDRIVE = `C:' HOMEPATH = `\' INCLUDE = `C:\ABSOFT\CINCLUDE' LIB = `C:\ABSOFT\LIB' LINK_F90 = `imsl.lib imsls_err.lib imslmpistub.lib' LOGONSERVER = `\\DELL' MANPATH = `:/usr/ssl/man' NUMBER_OF_PROCESSORS = `1' OLDPWD = `/cygdrive/c/cygwin/tmp' OS2LIBPATH = `C:\WINNT\system32\os2\dll;' OS = `Windows_NT' PATHEXT = `.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH' PROCESSOR_ARCHITECTURE = `x86' PROCESSOR_IDENTIFIER = `x86 Family 6 Model 8 Stepping 6, GenuineIntel' PROCESSOR_LEVEL = `6' PROCESSOR_REVISION = `0806' PROGRAMFILES = `C:\Program Files' PROMPT = `$P$G' PS1 = `\[\033]0;\w\007 \033[32m\]\u@\h \[\033[33m\w\033[0m\] $ ' SHLVL = `1' SYSTEMDRIVE = `C:' SYSTEMROOT = `C:\WINNT' TEC75HOME = `C:\TEC75' TEMP = `c:\DOCUME~1\DRLAWR~1.SPR\LOCALS~1\Temp' TERM = `cygwin' TMP = `c:\DOCUME~1\DRLAWR~1.SPR\LOCALS~1\Temp' TMPDIR = `c:\DOCUME~1\DRLAWR~1.SPR\LOCALS~1\Temp' USERDOMAIN = `DELL' USERNAME = `lws' USERPROFILE = `C:\Documents and Settings\Dr. Lawrence W. Spra' VIM = `C:\PGI\cygusr\share\vim' VNI_F90_MSG = `C:\Program Files\Microsoft Visual Studio\DF98\IMSL\MESSAGE' WINDIR = `C:\WINNT' _ = `/usr/bin/cygcheck.exe' HKEY_CURRENT_USER\Software\Cygnus Solutions HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2 (default) = `/cygdrive' cygdrive flags = 0x0022 HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\Program Options HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\00 (default) = `C:' unix = `/' fbinary = 0x fsilent = 0x HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/ (default) = `C:\cygwin' flags = 0x000a HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/bin (default) = `C:\cygwin/bin' flags = 0x000a HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/lib (default) = `C:\cygwin/lib' flags = 0x000a HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\Program Options HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\CYGWIN.DLL setup\b15.0 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus
Re: xfree packages
Harold Hunt wrote: That sounds fine. Can I also request that you use a seperate variable for the server version number? I'd ask that because the server will tend to get updated often while most of the other packages will never be updated. I'm really looking forward to these packages getting finished. Do you think you've got a handle on creating the symlinks that Xinstall.sh creates? Did you notice any symlinks that were missing? The build.sh script is supposed to create and package the links that Xinstall.sh makes. I don't think Xinstall.sh behaviour is quite right for the xkb files. I posted the xfree86-xwin package and modified xfree86-base to my web site. I have appended the new setup.hint files. - Ian -- [EMAIL PROTECTED] http://www.znark.com/ xfree86-base: sdesc: Cygwin/XFree86 base category: XFree86 requires: cygwin ash xfree86-fonts xfree86-xwin ldesc: Cygwin/XFree86 is a port of the X Window System to Cygwin. This package contains the programs, libraries, and config files needed to run an X server and clients. It also include the X clients from the standard X distribution like xterm and twm. You will need to install the xfree86-xwin package with the Windows X server. The xfree86-fonts package is also required. The other packages contain headers, programs, and documentation for development. xfree86-xwin: sdesc: Cygwin/XFree86 Windows X server category: XFree86 requires: cygwin xfree86-base ldesc: XWin is the X server for Windows. It can run in two different modes, full screen or inside Windows window. It has four different engines to drawing, Shadow GDI, Shadow DirectDraw, and Native GDI.
Re: xfree packages
Christopher Faylor [EMAIL PROTECTED] writes: AFAICT, both Red Hat and Debian allow upper/lower case, so there's no reason for us to restrict things. All Debian packages are lower case, of course. TAB completion is a silly argument against using mixed case, but I just couldn't imagine anyone would want mixed case package names, if they had a choice. Probably a matter of taste, I'll try to get used to it :-) Jan. -- Jan Nieuwenhuizen [EMAIL PROTECTED] | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org
Re: xfree packages
On Wed, Apr 10, 2002 at 05:27:14PM -0400, Charles Wilson wrote: Ian, Chris wants the setup hint files IN the mailing list archive permanently. Not sitting on an external, subject-to-change website. I've pasted them here. These look ok except the version: field is a no-op in setup.hint and should be removed. Has anyone looked at the packages themselves? cgf --- xfree86-base --- sdesc: Cygwin/XFree86 base category: XFree86 requires: cygwin ash xfree86-fonts ldesc: Cygwin/XFree86 is a port of the X Window System to Cygwin. The X server runs under Windows and displays X clients running on the local or other machines. It can run in full screen and single window modes. This package contains the programs, libraries, and config files to run the X server and other X clients. The xfree86-fonts package is also required. The other packages contain headers, programs, and documentation for development. --- xfree86-devel --- sdesc: Cygwin/XFree86 development files category: XFree86 requires: xfree86-base ldesc: This package contains the libraries, headers, and man pages for compiling X Windows programs. --- xfree86-doc --- sdesc: Cygwin/XFree86 text documentation category: XFree86 ldesc: XFree86 development documentation in text, HTML, and PostScript formats. --- xfree86-fonts --- sdesc: Cygwin-XFree86 fonts category: XFree86 requires: xfree86-base ldesc: This package contains fonts for XFree86. It contains the 100dpi, 75dpi, misc, scaled, and cyrillic sets. This package is required. --- xfree86-xfs --- sdesc: Cygwin/XFree86 font server category: XFree86 requires: cygwin xfree86-base version: 4.2.0-1 ldesc: This package contains the font server for XFree86. --- xfree86-xnest --- sdesc: Cygwin/XFree86 nested server category: XFree86 requires: cygwin xfree86-base version: 4.2.0-1 ldesc: Xnest is an X server that runs as a client for another X server. It is used for testing X clients and servers. --- xfree86-xprt --- sdesc: Cygwin/XFree86 printing server category: XFree86 requires: cygwin xfree86-base version: 4.2.0-1 ldesc: Xprt is an X server that prints the display to a PostScript file. --- xfree86-xvfb --- sdesc: Cygwin-XFree86 virtual framebuffer server category: XFree86 requires: cygwin xfree86-base version: 4.2.0-1 ldesc: Xvfb is an X server that runs without any display using a virtual framebuffer. This server runs without any display. It is used for testing X clients and servers.
RE: xfree packages
Ian, Good idea. I'm going to call it xfree86-xwin though. I think I'll put the startup-scripts.tgz in this package. That sounds fine. Can I also request that you use a seperate variable for the server version number? I'd ask that because the server will tend to get updated often while most of the other packages will never be updated. I'm really looking forward to these packages getting finished. Do you think you've got a handle on creating the symlinks that Xinstall.sh creates? Harold -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ian Burrell Sent: Wednesday, April 10, 2002 5:38 PM To: Harold Hunt Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: xfree packages Harold Hunt wrote: Yes, we try to keep things regularized around here, so XFree86 is the way that the package names need to be spelled. Also, I request that you keep the XFree86-xserv package, as that will allow us to realize the immediate benefit of being able to release the Test-** server or updates to the stable server as small downloads that everyone can keep up to date with. Good idea. I'm going to call it xfree86-xwin though. I think I'll put the startup-scripts.tgz in this package. - Ian -- [EMAIL PROTECTED] http://www.znark.com/
