Discussion:
'run xterm' fails to open a window
(too old to reply)
Ken Brown
2009-11-03 14:27:23 UTC
Permalink
I don't know if this is a problem with run, or xterm, or something else.
If I start the X server and then type 'run xterm' in an xterm window,
the xterm process starts but does not open a window. Here's what 'ps'
shows before and after 'run xterm':

$ ps
PID PPID PGID WINPID TTY UID STIME COMMAND
780 1 780 780 ? 1006 08:50:17 /usr/bin/mintty
I 2932 780 2932 1480 0 1006 08:50:17 /usr/bin/bash
384 1 1708 2740 0 1006 08:50:32 /usr/bin/XWin
2648 384 2648 3064 ? 1006 08:51:07 /usr/bin/xterm
528 2648 528 3016 1 1006 08:51:11 /usr/bin/bash
3144 528 3144 1464 1 1006 09:05:28 /usr/bin/ps

$ run xterm

$ ps
PID PPID PGID WINPID TTY UID STIME COMMAND
780 1 780 780 ? 1006 08:50:17 /usr/bin/mintty
I 2932 780 2932 1480 0 1006 08:50:17 /usr/bin/bash
384 1 1708 2740 0 1006 08:50:32 /usr/bin/XWin
2648 384 2648 3064 ? 1006 08:51:07 /usr/bin/xterm
528 2648 528 3016 1 1006 08:51:11 /usr/bin/bash
3452 1 3452 3452 con 1006 09:05:57 /usr/bin/xterm
4088 528 4088 3664 1 1006 09:06:01 /usr/bin/ps

Obviously I have no good reason to want to start an xterm via 'run
xterm' in an xterm window, but this issue is causing problems in a
script I'm writing. [Briefly, I have a desktop shortcut with target
'\path\to\run.exe bash -c foo.sh'. The script foo.sh calls xterm, which
starts with no visible window, exactly as above.]

I've attached cygcheck output and the XWin log.

Ken
Gery Herbozo Jimenez
2009-11-03 14:35:45 UTC
Permalink
Have you tried just starting the XWin server first and the the xterm? it looks like the X server doesn't recognize that line command.



> Date: Tue, 3 Nov 2009 09:27:23 -0500
> From: ***@cornell.edu
> To: cygwin-***@cygwin.com
> Subject: 'run xterm' fails to open a window
>
> I don't know if this is a problem with run, or xterm, or something else.
> If I start the X server and then type 'run xterm' in an xterm window,
> the xterm process starts but does not open a window. Here's what 'ps'
> shows before and after 'run xterm':
>
> $ ps
> PID PPID PGID WINPID TTY UID STIME COMMAND
> 780 1 780 780 ? 1006 08:50:17 /usr/bin/mintty
> I 2932 780 2932 1480 0 1006 08:50:17 /usr/bin/bash
> 384 1 1708 2740 0 1006 08:50:32 /usr/bin/XWin
> 2648 384 2648 3064 ? 1006 08:51:07 /usr/bin/xterm
> 528 2648 528 3016 1 1006 08:51:11 /usr/bin/bash
> 3144 528 3144 1464 1 1006 09:05:28 /usr/bin/ps
>
> $ run xterm
>
> $ ps
> PID PPID PGID WINPID TTY UID STIME COMMAND
> 780 1 780 780 ? 1006 08:50:17 /usr/bin/mintty
> I 2932 780 2932 1480 0 1006 08:50:17 /usr/bin/bash
> 384 1 1708 2740 0 1006 08:50:32 /usr/bin/XWin
> 2648 384 2648 3064 ? 1006 08:51:07 /usr/bin/xterm
> 528 2648 528 3016 1 1006 08:51:11 /usr/bin/bash
> 3452 1 3452 3452 con 1006 09:05:57 /usr/bin/xterm
> 4088 528 4088 3664 1 1006 09:06:01 /usr/bin/ps
>
> Obviously I have no good reason to want to start an xterm via 'run
> xterm' in an xterm window, but this issue is causing problems in a
> script I'm writing. [Briefly, I have a desktop shortcut with target
> '\path\to\run.exe bash -c foo.sh'. The script foo.sh calls xterm, which
> starts with no visible window, exactly as above.]
>
> I've attached cygcheck output and the XWin log.
>
> Ken
>
>
_________________________________________________________________
Date una vuelta por Sietes y conoce el pueblo de los expertos en Windows 7
http://www.sietesunpueblodeexpertos.com/

--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
Florent Fievez
2009-11-03 15:13:13 UTC
Permalink
Hello,

I've exactly the same issue, so if you find a solution, please post it ! ;-)

Best regards,

2009/11/3 Ken Brown <***@cornell.edu>:
> I don't know if this is a problem with run, or xterm, or something else.  If
> I start the X server and then type 'run xterm' in an xterm window, the xterm
> process starts but does not open a window.  Here's what 'ps' shows before
> and after 'run xterm':
>
> $ ps
>      PID    PPID    PGID     WINPID  TTY  UID    STIME COMMAND
>      780       1     780        780    ? 1006 08:50:17 /usr/bin/mintty
> I    2932     780    2932       1480    0 1006 08:50:17 /usr/bin/bash
>      384       1    1708       2740    0 1006 08:50:32 /usr/bin/XWin
>     2648     384    2648       3064    ? 1006 08:51:07 /usr/bin/xterm
>      528    2648     528       3016    1 1006 08:51:11 /usr/bin/bash
>     3144     528    3144       1464    1 1006 09:05:28 /usr/bin/ps
>
> $ run xterm
>
> $ ps
>      PID    PPID    PGID     WINPID  TTY  UID    STIME COMMAND
>      780       1     780        780    ? 1006 08:50:17 /usr/bin/mintty
> I    2932     780    2932       1480    0 1006 08:50:17 /usr/bin/bash
>      384       1    1708       2740    0 1006 08:50:32 /usr/bin/XWin
>     2648     384    2648       3064    ? 1006 08:51:07 /usr/bin/xterm
>      528    2648     528       3016    1 1006 08:51:11 /usr/bin/bash
>     3452       1    3452       3452  con 1006 09:05:57 /usr/bin/xterm
>     4088     528    4088       3664    1 1006 09:06:01 /usr/bin/ps
>
> Obviously I have no good reason to want to start an xterm via 'run xterm' in
> an xterm window, but this issue is causing problems in a script I'm writing.
>  [Briefly, I have a desktop shortcut with target '\path\to\run.exe bash -c
> foo.sh'.  The script foo.sh calls xterm, which starts with no visible
> window, exactly as above.]
>
> I've attached cygcheck output and the XWin log.
>
> Ken
>
>
>
>
> Cygwin Configuration Diagnostics
> Current System Time: Tue Nov 03 14:22:16 2009
>
> Windows XP Professional Ver 5.1 Build 2600 Service Pack 3
>
> Path:   D:\cygwin-1.7\usr\local\texlive\2009\bin\i386-cygwin
>        D:\cygwin-1.7\usr\local\bin
>        D:\cygwin-1.7\bin
>        C:\Program Files\ThinkPad\Utilities
>        C:\WINDOWS\system32
>        C:\WINDOWS
>        C:\WINDOWS\System32\Wbem
>        C:\Program Files\Intel\Wireless\Bin\
>        C:\Program Files\IBM ThinkVantage\Client Security Solution
>        C:\Program Files\ThinkPad\ConnectUtilities
>        C:\Program Files\QuickTime\QTSystem\
>        C:\Program Files\Common Files\Lenovo
>        D:\cygwin-1.7\bin
>        D:\cygwin-1.7\lib\lapack
>
> Output from D:\cygwin-1.7\bin\id.exe (nontsec)
> UID: 1007(kbrown-admin) GID: 513(None)
> 0(root)                 544(Administrators)     545(Users)
> 513(None)               544(Administrators)     545(Users)
> 513(None)
>
> Output from D:\cygwin-1.7\bin\id.exe (ntsec)
> UID: 1007(kbrown-admin) GID: 513(None)
> 0(root)                 544(Administrators)     545(Users)
> 513(None)               544(Administrators)     545(Users)
> 513(None)
>
> SysDir: C:\WINDOWS\system32
> WinDir: C:\WINDOWS
>
> USER = 'kbrown-admin'
> PWD = '/home/kbrown-admin'
> HOME = '/home/kbrown-admin'
>
> HOMEPATH = '\cygwin-1.7\home\kbrown-admin'
> MANPATH =
> '/usr/local/texlive/2009/texmf/doc/man:/usr/local/share/man:usr/local/man:/usr/share/man:/usr/man:/usr/ssl/man'
> HOSTNAME = 'markov'
> TERM = 'xterm'
> SHELL = '/bin/bash'
> PROCESSOR_IDENTIFIER = 'x86 Family 6 Model 14 Stepping 8, GenuineIntel'
> WINDIR = 'C:\WINDOWS'
> SSH_CLIENT = '::1 1025 22'
> OLDPWD = '/home/kbrown-admin'
> USERDOMAIN = 'MARKOV'
> SSH_TTY = '/dev/tty2'
> OS = 'Windows_NT'
> ALLUSERSPROFILE = 'C:\Documents and Settings\All Users'
> TEMP = '/c/WINDOWS/TEMP'
> COMMONPROGRAMFILES = 'C:\Program Files\Common Files'
> G_SLICE = 'always-malloc'
> USERNAME = 'kbrown-admin'
> PROCESSOR_LEVEL = '6'
> MAIL = '/var/spool/mail/kbrown-admin'
> SYSTEMDRIVE = 'C:'
> TZ = 'America/New_York'
> PS1 = '\[\e]0;\w\a\]\n\[\e[32m\]\u@\h \[\e[33m\]\w\[\e[0m\]\n\$ '
> LOGONSERVER = '\\MARKOV'
> HISTIGNORE = '[   ]*:&:bg:fg:exit'
> PROCESSOR_ARCHITECTURE = 'x86'
> HISTCONTROL = 'ignoredups'
> SHLVL = '1'
> PATHEXT = '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH'
> HOMEDRIVE = 'D:'
> COMSPEC = 'C:\WINDOWS\system32\cmd.exe'
> LOGNAME = 'kbrown-admin'
> TMP = '/c/WINDOWS/TEMP'
> SYSTEMROOT = 'C:\WINDOWS'
> PRINTER = 'CutePDF Writer'
> CVS_RSH = '/bin/ssh'
> PROCESSOR_REVISION = '0e08'
> SSH_CONNECTION = '::1 1025 ::1 22'
> INFOPATH =
> '/usr/local/texlive/2009/texmf/doc/info:/usr/local/share/info:/usr/local/info:/usr/share/info:/usr/info'
> PROGRAMFILES = 'C:\Program Files'
> NUMBER_OF_PROCESSORS = '2'
> COMPUTERNAME = 'MARKOV'
> _ = '/usr/bin/cygcheck'
>
> HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin
> HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2
> HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\Program Options
> HKEY_CURRENT_USER\Software\Cygwin
> HKEY_CURRENT_USER\Software\Cygwin\Program Options
> HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin
> HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2
>  (default) = '/cygdrive'
>  cygdrive flags = 0x00000022
> HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/
>  (default) = 'D:\cygwin'
>  flags = 0x0000000a
> HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/c
>  (default) = 'c:'
>  flags = 0x0000000a
> HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/d
>  (default) = 'd:'
>  flags = 0x0000000a
> HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/Users
>  (default) = 'C:\Documents and Settings'
>  flags = 0x0000000a
> HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/bin
>  (default) = 'D:\cygwin/bin'
>  flags = 0x0000000a
> HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/lib
>  (default) = 'D:\cygwin/lib'
>  flags = 0x0000000a
> HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\Program Options
> HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin
> HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\Program Options
> HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\setup
>  (default) = 'D:\cygwin-1.7'
>
> obcaseinsensitive set to 1
>
> c:  hd  NTFS     24999Mb  72% CP CS UN PA FC     IBM_PRELOAD
> d:  hd  NTFS     27282Mb  76% CP CS UN PA FC
>
> D:\cygwin-1.7              /          system  binary,auto
> C:\Documents and Settings  /Users     system  binary
> C:                         /c         system  binary
> D:                         /d         system  binary
> D:\cygwin-1.7\bin          /usr/bin   system  binary,auto
> D:\cygwin-1.7\lib          /usr/lib   system  binary,auto
> cygdrive prefix            /cygdrive  user    binary,auto
>
> Found: D:\cygwin-1.7\bin\awk.exe
> Found: D:\cygwin-1.7\bin\awk.exe
>  -> D:\cygwin-1.7\bin\gawk.exe
> Found: D:\cygwin-1.7\bin\bash.exe
> Found: D:\cygwin-1.7\bin\bash.exe
> Found: D:\cygwin-1.7\bin\cat.exe
> Found: D:\cygwin-1.7\bin\cat.exe
> Found: D:\cygwin-1.7\bin\cp.exe
> Found: D:\cygwin-1.7\bin\cp.exe
> Found: D:\cygwin-1.7\bin\cpp.exe
> Found: D:\cygwin-1.7\bin\cpp.exe
>  -> D:\cygwin-1.7\etc\alternatives\cpp
>  -> D:\cygwin-1.7\bin\cpp-4.exe
> Not Found: crontab
> Found: D:\cygwin-1.7\bin\find.exe
> Found: C:\WINDOWS\system32\find.exe
> Warning: D:\cygwin-1.7\bin\find.exe hides C:\WINDOWS\system32\find.exe
> Found: D:\cygwin-1.7\bin\find.exe
> Found: D:\cygwin-1.7\bin\gcc.exe
> Found: D:\cygwin-1.7\bin\gcc.exe
>  -> D:\cygwin-1.7\etc\alternatives\gcc
>  -> D:\cygwin-1.7\bin\gcc-4.exe
> Found: D:\cygwin-1.7\bin\gdb.exe
> Found: D:\cygwin-1.7\bin\gdb.exe
> Found: D:\cygwin-1.7\bin\grep.exe
> Found: D:\cygwin-1.7\bin\grep.exe
> Found: D:\cygwin-1.7\bin\kill.exe
> Found: D:\cygwin-1.7\bin\kill.exe
> Found: D:\cygwin-1.7\bin\ld.exe
> Found: D:\cygwin-1.7\bin\ld.exe
> Found: D:\cygwin-1.7\bin\ls.exe
> Found: D:\cygwin-1.7\bin\ls.exe
> Found: D:\cygwin-1.7\bin\make.exe
> Found: D:\cygwin-1.7\bin\make.exe
> Found: D:\cygwin-1.7\bin\mv.exe
> Found: D:\cygwin-1.7\bin\mv.exe
> Found: D:\cygwin-1.7\bin\patch.exe
> Found: D:\cygwin-1.7\bin\patch.exe
> Found: D:\cygwin-1.7\bin\perl.exe
> Found: D:\cygwin-1.7\bin\perl.exe
> Found: D:\cygwin-1.7\bin\rm.exe
> Found: D:\cygwin-1.7\bin\rm.exe
> Found: D:\cygwin-1.7\bin\sed.exe
> Found: D:\cygwin-1.7\bin\sed.exe
> Found: D:\cygwin-1.7\bin\ssh.exe
> Found: D:\cygwin-1.7\bin\ssh.exe
> Found: D:\cygwin-1.7\bin\sh.exe
> Found: D:\cygwin-1.7\bin\sh.exe
> Found: D:\cygwin-1.7\bin\tar.exe
> Found: D:\cygwin-1.7\bin\tar.exe
> Found: D:\cygwin-1.7\bin\test.exe
> Found: D:\cygwin-1.7\bin\test.exe
> Not Found: vi
> Not Found: vim
>
>  111k 2009/08/07 D:\cygwin-1.7\bin\cygapr-1-0.dll - os=4.0 img=1.0 sys=4.0
>                  "cygapr-1-0.dll" v0.0 ts=2009/8/7 20:58
>   87k 2009/08/07 D:\cygwin-1.7\bin\cygaprutil-1-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygaprutil-1-0.dll" v0.0 ts=2009/8/7 21:46
>  704k 2007/12/18 D:\cygwin-1.7\bin\cygaspell-15.dll - os=4.0 img=1.0 sys=4.0
>                  "cygaspell-15.dll" v0.0 ts=2007/12/18 11:39
>   88k 2009/03/24 D:\cygwin-1.7\bin\cygatk-1.0-0.dll - os=4.0 img=1.0 sys=4.0
>                  "cygatk-1.0-0.dll" v0.0 ts=2009/3/25 0:36
>  351k 2008/01/14 D:\cygwin-1.7\bin\cygboost_date_time-gcc-mt-1_33_1.dll -
> os=4.0 img=1.33 sys=4.0
>                  "cygboost_date_time-gcc-mt-1_33_1.dll" v0.0 ts=2008/1/14
> 8:36
>  120k 2008/01/14 D:\cygwin-1.7\bin\cygboost_filesystem-gcc-mt-1_33_1.dll -
> os=4.0 img=1.33 sys=4.0
>                  "cygboost_filesystem-gcc-mt-1_33_1.dll" v0.0 ts=2008/1/14
> 8:36
>   79k 2008/01/14 D:\cygwin-1.7\bin\cygboost_iostreams-gcc-mt-1_33_1.dll -
> os=4.0 img=1.33 sys=4.0
>                  "cygboost_iostreams-gcc-mt-1_33_1.dll" v0.0 ts=2008/1/14
> 8:37
>  526k 2008/01/14
> D:\cygwin-1.7\bin\cygboost_program_options-gcc-mt-1_33_1.dll - os=4.0
> img=1.33 sys=4.0
>                  "cygboost_program_options-gcc-mt-1_33_1.dll" v0.0
> ts=2008/1/14 8:38
>  564k 2008/01/14 D:\cygwin-1.7\bin\cygboost_python-gcc-mt-1_33_1.dll -
> os=4.0 img=1.33 sys=4.0
>                  "cygboost_python-gcc-mt-1_33_1.dll" v0.0 ts=2008/1/14 8:39
>  678k 2008/01/14 D:\cygwin-1.7\bin\cygboost_regex-gcc-mt-1_33_1.dll - os=4.0
> img=1.33 sys=4.0
>                  "cygboost_regex-gcc-mt-1_33_1.dll" v0.0 ts=2008/1/14 8:41
>  621k 2008/01/14 D:\cygwin-1.7\bin\cygboost_serialization-gcc-mt-1_33_1.dll
> - os=4.0 img=1.33 sys=4.0
>                  "cygboost_serialization-gcc-mt-1_33_1.dll" v0.0
> ts=2008/1/14 8:44
>  118k 2008/01/14 D:\cygwin-1.7\bin\cygboost_signals-gcc-mt-1_33_1.dll -
> os=4.0 img=1.33 sys=4.0
>                  "cygboost_signals-gcc-mt-1_33_1.dll" v0.0 ts=2008/1/14 8:44
>   91k 2008/01/14 D:\cygwin-1.7\bin\cygboost_thread-gcc-mt-1_33_1.dll -
> os=4.0 img=1.33 sys=4.0
>                  "cygboost_thread-gcc-mt-1_33_1.dll" v0.0 ts=2008/1/14 8:47
>   61k 2009/03/02 D:\cygwin-1.7\bin\cygbz2-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygbz2-1.dll" v0.0 ts=2009/3/2 3:11
>  456k 2009/06/25 D:\cygwin-1.7\bin\cygcairo-2.dll - os=4.0 img=1.0 sys=4.0
>                  "cygcairo-2.dll" v0.0 ts=2009/6/25 7:25
>    7k 2009/05/30 D:\cygwin-1.7\bin\cygcharset-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygcharset-1.dll" v0.0 ts=2009/5/30 20:05
>    7k 2003/10/19 D:\cygwin-1.7\bin\cygcrypt-0.dll - os=4.0 img=1.0 sys=4.0
>                  "cygcrypt-0.dll" v0.0 ts=2003/10/19 8:57
>  1074k 2009/03/25 D:\cygwin-1.7\bin\cygcrypto-0.9.8.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygcrypto-0.9.8.dll" v0.0 ts=2009/3/25 17:45
>  254k 2009/08/23 D:\cygwin-1.7\bin\cygcurl-4.dll - os=4.0 img=1.0 sys=4.0
>                  "cygcurl-4.dll" v0.0 ts=2009/8/23 6:25
>  703k 2007/12/17 D:\cygwin-1.7\bin\cygdb-4.2.dll - os=4.0 img=1.0 sys=4.0
>                  "cygdb-4.2.dll" v0.0 ts=2007/12/17 11:58
>  943k 2007/12/17 D:\cygwin-1.7\bin\cygdb-4.5.dll - os=4.0 img=1.0 sys=4.0
>                  "cygdb-4.5.dll" v0.0 ts=2007/12/17 13:12
>  1036k 2007/12/17 D:\cygwin-1.7\bin\cygdb_cxx-4.2.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygdb_cxx-4.2.dll" v0.0 ts=2007/12/17 11:58
>  1296k 2007/12/17 D:\cygwin-1.7\bin\cygdb_cxx-4.5.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygdb_cxx-4.5.dll" v0.0 ts=2007/12/17 13:12
>  118k 2007/04/06 D:\cygwin-1.7\bin\cygexpat-0.dll - os=4.0 img=1.0 sys=4.0
>                  "cygexpat-0.dll" v0.0 ts=2007/4/6 21:43
>  118k 2008/05/09 D:\cygwin-1.7\bin\cygexpat-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygexpat-1.dll" v0.0 ts=2008/5/9 5:03
>   28k 2009/03/22 D:\cygwin-1.7\bin\cygfam-0.dll - os=4.0 img=1.0 sys=4.0
>                  "cygfam-0.dll" v0.0 ts=2009/3/22 19:56
>  286k 2006/08/06 D:\cygwin-1.7\bin\cygfcgi++-0.dll - os=4.0 img=1.0 sys=4.0
>                  "cygfcgi++-0.dll" v0.0 ts=2006/8/6 21:09
>   30k 2006/08/06 D:\cygwin-1.7\bin\cygfcgi-0.dll - os=4.0 img=1.0 sys=4.0
>                  "cygfcgi-0.dll" v0.0 ts=2006/8/6 21:09
>   22k 2009/09/29 D:\cygwin-1.7\bin\cygffi-4.dll - os=4.0 img=1.0 sys=4.0
>                  "cygffi-4.dll" v0.0 ts=2009/9/14 16:50
>  784k 2009/07/28 D:\cygwin-1.7\bin\cygfftw3-3.dll - os=4.0 img=1.0 sys=4.0
>                  "cygfftw3-3.dll" v0.0 ts=2009/7/28 20:14
>  758k 2009/07/28 D:\cygwin-1.7\bin\cygfftw3f-3.dll - os=4.0 img=1.0 sys=4.0
>                  "cygfftw3f-3.dll" v0.0 ts=2009/7/28 20:05
>   19k 2009/07/28 D:\cygwin-1.7\bin\cygfftw3f_threads-3.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygfftw3f_threads-3.dll" v0.0 ts=2009/7/28 20:05
>   19k 2009/07/28 D:\cygwin-1.7\bin\cygfftw3_threads-3.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygfftw3_threads-3.dll" v0.0 ts=2009/7/28 20:14
>  174k 2009/09/25 D:\cygwin-1.7\bin\cygfontconfig-1.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygfontconfig-1.dll" v0.0 ts=2009/9/25 3:05
>   21k 2009/10/14 D:\cygwin-1.7\bin\cygfontenc-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygfontenc-1.dll" v0.0 ts=2009/10/14 2:04
>   40k 2009/03/01 D:\cygwin-1.7\bin\cygform-8.dll - os=4.0 img=1.0 sys=4.0
>                  "cygform-8.dll" v0.0 ts=2009/3/1 6:32
>   41k 2009/10/26 D:\cygwin-1.7\bin\cygform-9.dll - os=4.0 img=1.0 sys=4.0
>                  "cygform-9.dll" v0.0 ts=2009/10/26 23:02
>   48k 2003/08/09 D:\cygwin-1.7\bin\cygform7.dll - os=4.0 img=1.0 sys=4.0
>                  "cygform7.dll" v0.0 ts=2003/8/9 10:25
>  489k 2009/10/15 D:\cygwin-1.7\bin\cygfreetype-6.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygfreetype-6.dll" v0.0 ts=2009/10/15 2:22
>   44k 2009/09/29 D:\cygwin-1.7\bin\cyggcc_s-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cyggcc_s-1.dll" v0.0 ts=2009/9/14 16:42
>   41k 2008/09/12 D:\cygwin-1.7\bin\cyggcc_s.dll - os=4.0 img=1.0 sys=4.0
>                  "cyggcc_s.dll" v0.0 ts=2008/9/11 7:43
>   19k 2009/02/26 D:\cygwin-1.7\bin\cyggdbm-4.dll - os=4.0 img=1.0 sys=4.0
>                  "cyggdbm-4.dll" v0.0 ts=2009/2/26 7:58
>    8k 2009/02/26 D:\cygwin-1.7\bin\cyggdbm_compat-4.dll - os=4.0 img=1.0
> sys=4.0
>                  "cyggdbm_compat-4.dll" v0.0 ts=2009/2/26 7:58
>  193k 2009/03/23 D:\cygwin-1.7\bin\cyggdk-1-2-0.dll - os=4.0 img=1.0 sys=4.0
>                  "cyggdk-1-2-0.dll" v0.0 ts=2009/3/23 15:24
>  504k 2009/09/08 D:\cygwin-1.7\bin\cyggdk-x11-2.0-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cyggdk-x11-2.0-0.dll" v0.0 ts=2009/9/7 7:34
>   90k 2009/09/08 D:\cygwin-1.7\bin\cyggdk_pixbuf-2.0-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cyggdk_pixbuf-2.0-0.dll" v0.0 ts=2009/9/7 7:32
>  954k 2009/04/03 D:\cygwin-1.7\bin\cyggettextlib-0-17.dll - os=4.0 img=1.0
> sys=4.0
>                  "cyggettextlib-0-17.dll" v0.0 ts=2009/4/3 2:21
>  218k 2009/04/03 D:\cygwin-1.7\bin\cyggettextpo-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cyggettextpo-0.dll" v0.0 ts=2009/4/3 2:29
>  203k 2009/04/03 D:\cygwin-1.7\bin\cyggettextsrc-0-17.dll - os=4.0 img=1.0
> sys=4.0
>                  "cyggettextsrc-0-17.dll" v0.0 ts=2009/4/3 2:24
>  642k 2009/09/29 D:\cygwin-1.7\bin\cyggfortran-3.dll - os=4.0 img=1.0
> sys=4.0
>                  "cyggfortran-3.dll" v0.0 ts=2009/9/14 17:42
>   29k 2009/03/23 D:\cygwin-1.7\bin\cyggif-4.dll - os=4.0 img=1.0 sys=4.0
>                  "cyggif-4.dll" v0.0 ts=2009/3/23 19:55
>  367k 2009/09/07 D:\cygwin-1.7\bin\cyggio-2.0-0.dll - os=4.0 img=1.0 sys=4.0
>                  "cyggio-2.0-0.dll" v0.0 ts=2009/9/7 5:10
>  2311k 2009/10/16 D:\cygwin-1.7\bin\cygGL-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygGL-1.dll" v0.0 ts=2009/10/16 10:17
>  133k 2009/03/25 D:\cygwin-1.7\bin\cygglib-1-2-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygglib-1-2-0.dll" v0.0 ts=2009/3/23 15:12
>  678k 2009/09/07 D:\cygwin-1.7\bin\cygglib-2.0-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygglib-2.0-0.dll" v0.0 ts=2009/9/7 5:07
>  141k 2009/03/30 D:\cygwin-1.7\bin\cygglitz-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygglitz-1.dll" v0.0 ts=2009/3/30 17:22
>   21k 2009/03/30 D:\cygwin-1.7\bin\cygglitz-glx-1.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygglitz-glx-1.dll" v0.0 ts=2009/3/30 17:23
>  445k 2009/10/16 D:\cygwin-1.7\bin\cygGLU-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygGLU-1.dll" v0.0 ts=2009/10/16 10:17
>   12k 2009/03/25 D:\cygwin-1.7\bin\cyggmodule-1-2-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cyggmodule-1-2-0.dll" v0.0 ts=2009/3/23 15:12
>   13k 2009/09/07 D:\cygwin-1.7\bin\cyggmodule-2.0-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cyggmodule-2.0-0.dll" v0.0 ts=2009/9/7 5:08
>  315k 2009/06/06 D:\cygwin-1.7\bin\cyggmp-3.dll - os=4.0 img=1.0 sys=4.0
>                  "cyggmp-3.dll" v0.0 ts=2009/6/6 12:23
>  226k 2009/09/07 D:\cygwin-1.7\bin\cyggobject-2.0-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cyggobject-2.0-0.dll" v0.0 ts=2009/9/7 5:08
>   24k 2009/09/29 D:\cygwin-1.7\bin\cyggomp-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cyggomp-1.dll" v0.0 ts=2009/9/14 16:51
>  5491k 2008/11/27 D:\cygwin-1.7\bin\cyggs-8.dll - os=4.0 img=1.0 sys=4.0
>                  "cyggs-8.dll" v0.0 ts=2008/11/27 13:24
>  1640k 2009/09/20 D:\cygwin-1.7\bin\cyggsl-0.dll - os=4.0 img=1.0 sys=4.0
>                  "cyggsl-0.dll" v0.0 ts=2009/9/20 15:39
>  186k 2009/09/20 D:\cygwin-1.7\bin\cyggslcblas-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cyggslcblas-0.dll" v0.0 ts=2009/9/20 15:29
>    9k 2009/03/25 D:\cygwin-1.7\bin\cyggthread-1-2-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cyggthread-1-2-0.dll" v0.0 ts=2009/3/23 15:13
>   15k 2009/09/07 D:\cygwin-1.7\bin\cyggthread-2.0-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cyggthread-2.0-0.dll" v0.0 ts=2009/9/7 5:08
>  1258k 2009/03/23 D:\cygwin-1.7\bin\cyggtk-1-2-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cyggtk-1-2-0.dll" v0.0 ts=2009/3/23 15:29
>  3502k 2009/09/08 D:\cygwin-1.7\bin\cyggtk-x11-2.0-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cyggtk-x11-2.0-0.dll" v0.0 ts=2009/9/7 7:40
>   24k 2009/06/23 D:\cygwin-1.7\bin\cyghistory6.dll - os=4.0 img=1.0 sys=4.0
>                  "cyghistory6.dll" v0.0 ts=2009/6/23 13:20
>   25k 2009/07/06 D:\cygwin-1.7\bin\cyghistory7.dll - os=4.0 img=1.0 sys=4.0
>                  "cyghistory7.dll" v0.0 ts=2009/7/5 15:45
>   73k 2009/09/02 D:\cygwin-1.7\bin\cygICE-6.dll - os=4.0 img=1.0 sys=4.0
>                  "cygICE-6.dll" v0.0 ts=2009/9/2 22:39
>  270k 2009/05/07 D:\cygwin-1.7\bin\cygicons-0.dll - os=4.0 img=1.0 sys=4.0
>                  "cygicons-0.dll" v0.0 ts=2009/5/7 1:58
>  981k 2009/05/30 D:\cygwin-1.7\bin\cygiconv-2.dll - os=4.0 img=1.0 sys=4.0
>                  "cygiconv-2.dll" v0.0 ts=2009/5/30 20:05
> 10918k 2008/11/10 D:\cygwin-1.7\bin\cygicudata38.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygicudata38.dll" v0.0 ts=2008/11/10 11:06
>  1246k 2008/11/10 D:\cygwin-1.7\bin\cygicui18n38.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygicui18n38.dll" v0.0 ts=2008/11/10 10:59
>  243k 2008/11/10 D:\cygwin-1.7\bin\cygicuio38.dll - os=4.0 img=1.0 sys=4.0
>                  "cygicuio38.dll" v0.0 ts=2008/11/10 11:06
>  256k 2008/11/10 D:\cygwin-1.7\bin\cygicule38.dll - os=4.0 img=1.0 sys=4.0
>                  "cygicule38.dll" v0.0 ts=2008/11/10 11:01
>   70k 2008/11/10 D:\cygwin-1.7\bin\cygiculx38.dll - os=4.0 img=1.0 sys=4.0
>                  "cygiculx38.dll" v0.0 ts=2008/11/10 11:01
>  1066k 2008/11/10 D:\cygwin-1.7\bin\cygicuuc38.dll - os=4.0 img=1.0 sys=4.0
>                  "cygicuuc38.dll" v0.0 ts=2008/11/10 10:53
>  191k 2009/09/15 D:\cygwin-1.7\bin\cygidn-11.dll - os=4.0 img=1.0 sys=4.0
>                  "cygidn-11.dll" v0.0 ts=2009/9/15 11:41
>   22k 2001/12/13 D:\cygwin-1.7\bin\cygintl-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygintl-1.dll" v0.0 ts=2001/12/13 9:28
>   37k 2003/08/10 D:\cygwin-1.7\bin\cygintl-2.dll - os=4.0 img=1.0 sys=4.0
>                  "cygintl-2.dll" v0.0 ts=2003/8/10 22:50
>   31k 2005/11/20 D:\cygwin-1.7\bin\cygintl-3.dll - os=4.0 img=1.0 sys=4.0
>                  "cygintl-3.dll" v0.0 ts=2005/11/20 2:04
>   31k 2009/04/03 D:\cygwin-1.7\bin\cygintl-8.dll - os=4.0 img=1.0 sys=4.0
>                  "cygintl-8.dll" v0.0 ts=2009/4/3 2:15
>  246k 2008/04/02 D:\cygwin-1.7\bin\cygjasper-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygjasper-1.dll" v0.0 ts=2008/4/2 17:19
>   41k 2009/03/10 D:\cygwin-1.7\bin\cygjbig-2.dll - os=4.0 img=1.0 sys=4.0
>                  "cygjbig-2.dll" v0.0 ts=2009/3/10 3:10
>   48k 2003/08/10 D:\cygwin-1.7\bin\cygjbig1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygjbig1.dll" v0.0 ts=2003/8/11 0:58
>  125k 2009/08/08 D:\cygwin-1.7\bin\cygjpeg-62.dll - os=4.0 img=1.0 sys=4.0
>                  "cygjpeg-62.dll" v0.0 ts=2009/8/8 21:48
>  193k 2009/08/08 D:\cygwin-1.7\bin\cygjpeg-7.dll - os=4.0 img=1.0 sys=4.0
>                  "cygjpeg-7.dll" v0.0 ts=2009/8/8 20:39
>  119k 2002/02/09 D:\cygwin-1.7\bin\cygjpeg6b.dll - os=4.0 img=1.0 sys=4.0
>                  "cygjpeg6b.dll" v0.0 ts=2002/2/9 5:19
>   39k 2008/09/07 D:\cygwin-1.7\bin\cyglber-2-3-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cyglber-2-3-0.dll" v0.0 ts=2008/9/7 13:28
>  189k 2008/09/07 D:\cygwin-1.7\bin\cygldap-2-3-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygldap-2-3-0.dll" v0.0 ts=2008/9/7 13:29
>  201k 2008/09/07 D:\cygwin-1.7\bin\cygldap_r-2-3-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygldap_r-2-3-0.dll" v0.0 ts=2008/9/7 13:31
>    5k 2009/10/03 D:\cygwin-1.7\bin\cyglsa.dll - os=4.0 img=1.0 sys=4.0
>                  "cyglsa.dll" v0.0 ts=2009/10/3 13:34
>    9k 2009/10/03 D:\cygwin-1.7\bin\cyglsa64.dll - os=4.0 img=0.0 sys=5.2
>   27k 2009/07/13 D:\cygwin-1.7\bin\cygltdl-7.dll - os=4.0 img=1.0 sys=4.0
>                  "cygltdl-7.dll" v0.0 ts=2009/7/13 1:50
>  133k 2009/06/10 D:\cygwin-1.7\bin\cyglua-5.1.dll - os=4.0 img=1.0 sys=4.0
>                  "cyglua-5.1.dll" v0.0 ts=2009/6/10 18:29
>  123k 2009/08/30 D:\cygwin-1.7\bin\cyglzma-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cyglzma-1.dll" v0.0 ts=2009/8/30 23:35
>   12k 2009/03/15 D:\cygwin-1.7\bin\cyglzmadec-0.dll - os=4.0 img=1.0 sys=4.0
>                  "cyglzmadec-0.dll" v0.0 ts=2009/3/15 7:16
>   98k 2009/03/16 D:\cygwin-1.7\bin\cygmagic-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygmagic-1.dll" v0.0 ts=2009/3/16 17:32
>   21k 2009/03/01 D:\cygwin-1.7\bin\cygmenu-8.dll - os=4.0 img=1.0 sys=4.0
>                  "cygmenu-8.dll" v0.0 ts=2009/3/1 6:31
>   22k 2009/10/26 D:\cygwin-1.7\bin\cygmenu-9.dll - os=4.0 img=1.0 sys=4.0
>                  "cygmenu-9.dll" v0.0 ts=2009/10/26 23:01
>   29k 2003/08/09 D:\cygwin-1.7\bin\cygmenu7.dll - os=4.0 img=1.0 sys=4.0
>                  "cygmenu7.dll" v0.0 ts=2003/8/9 10:25
>   24k 2008/10/30 D:\cygwin-1.7\bin\cygminires.dll - os=4.0 img=1.2 sys=4.0
>                  "cygminires.dll" v0.0 ts=2008/10/31 0:53
>  211k 2009/06/06 D:\cygwin-1.7\bin\cygmp-3.dll - os=4.0 img=1.0 sys=4.0
>                  "cygmp-3.dll" v0.0 ts=2009/6/6 12:23
>  269k 2009/06/07 D:\cygwin-1.7\bin\cygmpfr-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygmpfr-1.dll" v0.0 ts=2009/6/7 22:10
>   75k 2009/07/08 D:\cygwin-1.7\bin\cygMrm-2.dll - os=4.0 img=1.0 sys=4.0
>                  "cygMrm-2.dll" v0.0 ts=2009/7/8 4:26
>   66k 2009/03/01 D:\cygwin-1.7\bin\cygncurses++-8.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygncurses++-8.dll" v0.0 ts=2009/3/1 6:39
>   61k 2009/10/26 D:\cygwin-1.7\bin\cygncurses++-9.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygncurses++-9.dll" v0.0 ts=2009/10/26 23:12
>  237k 2009/03/01 D:\cygwin-1.7\bin\cygncurses-8.dll - os=4.0 img=1.0 sys=4.0
>                  "cygncurses-8.dll" v0.0 ts=2009/3/1 6:28
>  195k 2009/10/26 D:\cygwin-1.7\bin\cygncurses-9.dll - os=4.0 img=1.0 sys=4.0
>                  "cygncurses-9.dll" v0.0 ts=2009/10/26 22:58
>  224k 2003/08/09 D:\cygwin-1.7\bin\cygncurses7.dll - os=4.0 img=1.0 sys=4.0
>                  "cygncurses7.dll" v0.0 ts=2003/8/9 10:24
>  115k 2009/09/30 D:\cygwin-1.7\bin\cygneon-27.dll - os=4.0 img=1.0 sys=4.0
>                  "cygneon-27.dll" v0.0 ts=2009/9/30 14:33
>  173k 2009/09/02 D:\cygwin-1.7\bin\cygnetpbm-10.dll - os=4.0 img=1.0 sys=4.0
>                  "cygnetpbm-10.dll" v0.0 ts=2009/9/2 4:33
>   11k 2009/03/01 D:\cygwin-1.7\bin\cygpanel-8.dll - os=4.0 img=1.0 sys=4.0
>                  "cygpanel-8.dll" v0.0 ts=2009/3/1 6:30
>   12k 2009/10/26 D:\cygwin-1.7\bin\cygpanel-9.dll - os=4.0 img=1.0 sys=4.0
>                  "cygpanel-9.dll" v0.0 ts=2009/10/26 23:00
>   19k 2003/08/09 D:\cygwin-1.7\bin\cygpanel7.dll - os=4.0 img=1.0 sys=4.0
>                  "cygpanel7.dll" v0.0 ts=2003/8/9 10:24
>  230k 2009/07/27 D:\cygwin-1.7\bin\cygpango-1.0-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygpango-1.0-0.dll" v0.0 ts=2009/7/27 5:42
>   34k 2009/07/27 D:\cygwin-1.7\bin\cygpangocairo-1.0-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygpangocairo-1.0-0.dll" v0.0 ts=2009/7/27 5:42
>  142k 2009/07/27 D:\cygwin-1.7\bin\cygpangoft2-1.0-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygpangoft2-1.0-0.dll" v0.0 ts=2009/7/27 5:42
>   37k 2009/07/27 D:\cygwin-1.7\bin\cygpangox-1.0-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygpangox-1.0-0.dll" v0.0 ts=2009/7/27 5:42
>   23k 2009/07/27 D:\cygwin-1.7\bin\cygpangoxft-1.0-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygpangoxft-1.0-0.dll" v0.0 ts=2009/7/27 5:42
>  190k 2009/04/17 D:\cygwin-1.7\bin\cygpcre-0.dll - os=4.0 img=1.0 sys=4.0
>                  "cygpcre-0.dll" v0.0 ts=2009/4/17 17:07
>    7k 2009/04/17 D:\cygwin-1.7\bin\cygpcreposix-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygpcreposix-0.dll" v0.0 ts=2009/4/17 17:07
>  1543k 2008/07/03 D:\cygwin-1.7\bin\cygperl5_10.dll - os=4.0 img=1.0 sys=4.0
>                  "cygperl5_10.dll" v0.0 ts=2008/6/30 17:06
>  354k 2009/10/14 D:\cygwin-1.7\bin\cygpixman-1-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygpixman-1-0.dll" v0.0 ts=2009/10/14 1:39
>  242k 2009/03/07 D:\cygwin-1.7\bin\cygpng12.dll - os=4.0 img=1.0 sys=4.0
>                  "cygpng12.dll" v0.0 ts=2009/3/7 22:38
>   22k 2002/06/09 D:\cygwin-1.7\bin\cygpopt-0.dll - os=4.0 img=1.0 sys=4.0
>                  "cygpopt-0.dll" v0.0 ts=2002/6/9 6:45
>  103k 2009/01/07 D:\cygwin-1.7\bin\cygpq.dll - os=4.0 img=1.0 sys=4.0
>                  "cygpq.dll" v0.0 ts=2009/1/7 16:46
>    4k 2007/12/18 D:\cygwin-1.7\bin\cygpspell-15.dll - os=4.0 img=1.0 sys=4.0
>                  "cygpspell-15.dll" v0.0 ts=2007/12/18 11:40
>  155k 2009/06/23 D:\cygwin-1.7\bin\cygreadline6.dll - os=4.0 img=1.0 sys=4.0
>                  "cygreadline6.dll" v0.0 ts=2009/6/23 13:20
>  162k 2009/07/06 D:\cygwin-1.7\bin\cygreadline7.dll - os=4.0 img=1.0 sys=4.0
>                  "cygreadline7.dll" v0.0 ts=2009/7/5 15:45
>  761k 2008/09/30 D:\cygwin-1.7\bin\cygruby18.dll - os=4.0 img=1.0 sys=4.0
>                  "cygruby18.dll" v0.0 ts=2008/9/30 14:10
>   78k 2004/10/13 D:\cygwin-1.7\bin\cygsasl2-2.dll - os=4.0 img=1.0 sys=4.0
>                  "cygsasl2-2.dll" v0.0 ts=2004/10/13 23:50
>   43k 2009/02/06 D:\cygwin-1.7\bin\cygserf-0-0.dll - os=4.0 img=1.0 sys=4.0
>                  "cygserf-0-0.dll" v0.0 ts=2009/2/6 17:04
>    7k 2009/07/22 D:\cygwin-1.7\bin\cygsigsegv-0.dll - os=4.0 img=1.0 sys=4.0
>                  "cygsigsegv-0.dll" v0.0 ts=2009/7/22 9:57
>    9k 2009/07/24 D:\cygwin-1.7\bin\cygsigsegv-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygsigsegv-1.dll" v0.0 ts=2009/7/24 21:04
>   27k 2009/09/03 D:\cygwin-1.7\bin\cygSM-6.dll - os=4.0 img=1.0 sys=4.0
>                  "cygSM-6.dll" v0.0 ts=2009/9/3 9:56
>  355k 2008/09/09 D:\cygwin-1.7\bin\cygsqlite3-0.dll - os=4.0 img=1.0 sys=4.0
>                  "cygsqlite3-0.dll" v0.0 ts=2008/9/9 19:20
>  125k 2009/10/07 D:\cygwin-1.7\bin\cygssh2-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygssh2-1.dll" v0.0 ts=2009/10/7 3:25
>  232k 2009/03/25 D:\cygwin-1.7\bin\cygssl-0.9.8.dll - os=4.0 img=1.0 sys=4.0
>                  "cygssl-0.9.8.dll" v0.0 ts=2009/3/25 17:45
>    8k 2009/09/29 D:\cygwin-1.7\bin\cygssp-0.dll - os=4.0 img=1.0 sys=4.0
>                  "cygssp-0.dll" v0.0 ts=2009/9/14 16:49
>  771k 2009/09/29 D:\cygwin-1.7\bin\cygstdc++-6.dll - os=4.0 img=1.0 sys=4.0
>                  "cygstdc++-6.dll" v0.0 ts=2009/9/14 17:19
>  234k 2009/10/26 D:\cygwin-1.7\bin\cygsvn_client-1-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygsvn_client-1-0.dll" v0.0 ts=2009/10/23 16:46
>   36k 2009/10/26 D:\cygwin-1.7\bin\cygsvn_delta-1-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygsvn_delta-1-0.dll" v0.0 ts=2009/10/23 16:43
>   39k 2009/10/26 D:\cygwin-1.7\bin\cygsvn_diff-1-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygsvn_diff-1-0.dll" v0.0 ts=2009/10/23 16:43
>   18k 2009/10/26 D:\cygwin-1.7\bin\cygsvn_fs-1-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygsvn_fs-1-0.dll" v0.0 ts=2009/10/23 16:44
>  144k 2009/10/26 D:\cygwin-1.7\bin\cygsvn_fs_base-1-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygsvn_fs_base-1-0.dll" v0.0 ts=2009/10/23 16:43
>  123k 2009/10/26 D:\cygwin-1.7\bin\cygsvn_fs_fs-1-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygsvn_fs_fs-1-0.dll" v0.0 ts=2009/10/23 16:43
>    7k 2009/10/26 D:\cygwin-1.7\bin\cygsvn_fs_util-1-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygsvn_fs_util-1-0.dll" v0.0 ts=2009/10/23 16:43
>   30k 2009/10/26 D:\cygwin-1.7\bin\cygsvn_ra-1-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygsvn_ra-1-0.dll" v0.0 ts=2009/10/23 16:46
>   23k 2009/10/26 D:\cygwin-1.7\bin\cygsvn_ra_local-1-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygsvn_ra_local-1-0.dll" v0.0 ts=2009/10/23 16:44
>  113k 2009/10/26 D:\cygwin-1.7\bin\cygsvn_ra_neon-1-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygsvn_ra_neon-1-0.dll" v0.0 ts=2009/10/23 16:43
>  114k 2009/10/26 D:\cygwin-1.7\bin\cygsvn_ra_serf-1-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygsvn_ra_serf-1-0.dll" v0.0 ts=2009/10/23 16:43
>   70k 2009/10/26 D:\cygwin-1.7\bin\cygsvn_ra_svn-1-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygsvn_ra_svn-1-0.dll" v0.0 ts=2009/10/23 16:43
>  138k 2009/10/26 D:\cygwin-1.7\bin\cygsvn_repos-1-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygsvn_repos-1-0.dll" v0.0 ts=2009/10/23 16:44
>  246k 2009/10/26 D:\cygwin-1.7\bin\cygsvn_subr-1-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygsvn_subr-1-0.dll" v0.0 ts=2009/10/23 16:43
>  240k 2009/10/26 D:\cygwin-1.7\bin\cygsvn_wc-1-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygsvn_wc-1-0.dll" v0.0 ts=2009/10/23 16:43
>  231k 2009/09/15 D:\cygwin-1.7\bin\cygt1-5.dll - os=4.0 img=1.0 sys=4.0
>                  "cygt1-5.dll" v0.0 ts=2009/9/15 10:59
>   46k 2009/10/26 D:\cygwin-1.7\bin\cygtic-9.dll - os=4.0 img=1.0 sys=4.0
>                  "cygtic-9.dll" v0.0 ts=2009/10/26 22:58
>  312k 2009/08/10 D:\cygwin-1.7\bin\cygtiff-5.dll - os=4.0 img=1.0 sys=4.0
>                  "cygtiff-5.dll" v0.0 ts=2009/8/10 23:04
>  281k 2003/02/24 D:\cygwin-1.7\bin\cygtiff3.dll - os=4.0 img=1.0 sys=4.0
>                  "cygtiff3.dll" v0.0 ts=2003/2/24 4:58
>  282k 2003/08/11 D:\cygwin-1.7\bin\cygtiff4.dll - os=4.0 img=1.0 sys=4.0
>                  "cygtiff4.dll" v0.0 ts=2003/8/11 3:32
>  282k 2009/08/10 D:\cygwin-1.7\bin\cygtiffxx-5.dll - os=4.0 img=1.0 sys=4.0
>                  "cygtiffxx-5.dll" v0.0 ts=2009/8/10 23:04
>   65k 2009/07/08 D:\cygwin-1.7\bin\cygUil-2.dll - os=4.0 img=1.0 sys=4.0
>                  "cygUil-2.dll" v0.0 ts=2009/7/8 4:26
>   27k 2006/12/06 D:\cygwin-1.7\bin\cygungif-4.dll - os=4.0 img=1.0 sys=4.0
>                  "cygungif-4.dll" v0.0 ts=2006/12/6 3:41
>   40k 2009/07/08 D:\cygwin-1.7\bin\cygusb0.dll - os=4.0 img=1.0 sys=4.0
>                  "cygusb0.dll" v0.0 ts=2009/7/8 9:35
>   24k 2009/03/29 D:\cygwin-1.7\bin\cygwrap-0.dll - os=4.0 img=1.0 sys=4.0
>                  "cygwrap-0.dll" v0.0 ts=2009/3/29 7:28
>  1038k 2009/10/25 D:\cygwin-1.7\bin\cygX11-6.dll - os=4.0 img=1.0 sys=4.0
>                  "cygX11-6.dll" v0.0 ts=2009/10/25 18:27
>    6k 2009/10/25 D:\cygwin-1.7\bin\cygX11-xcb-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygX11-xcb-1.dll" v0.0 ts=2009/10/25 18:27
>    9k 2009/09/03 D:\cygwin-1.7\bin\cygXau-6.dll - os=4.0 img=1.0 sys=4.0
>                  "cygXau-6.dll" v0.0 ts=2009/9/2 22:47
>  251k 2009/10/19 D:\cygwin-1.7\bin\cygXaw-6.dll - os=4.0 img=1.0 sys=4.0
>                  "cygXaw-6.dll" v0.0 ts=2009/10/18 22:55
>  352k 2009/10/19 D:\cygwin-1.7\bin\cygXaw-7.dll - os=4.0 img=1.0 sys=4.0
>                  "cygXaw-7.dll" v0.0 ts=2009/10/18 22:55
>  268k 2008/11/15 D:\cygwin-1.7\bin\cygXaw3d-7.dll - os=4.0 img=1.0 sys=4.0
>                  "cygXaw3d-7.dll" v0.0 ts=2008/11/13 8:37
>   74k 2009/09/21 D:\cygwin-1.7\bin\cygxcb-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygxcb-1.dll" v0.0 ts=2009/9/21 22:31
>   22k 2009/09/21 D:\cygwin-1.7\bin\cygxcb-render-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygxcb-render-0.dll" v0.0 ts=2009/9/21 22:32
>   11k 2009/09/03 D:\cygwin-1.7\bin\cygxcb-render-util-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygxcb-render-util-0.dll" v0.0 ts=2009/9/3 6:24
>    5k 2009/02/09 D:\cygwin-1.7\bin\cygxcb-xlib-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygxcb-xlib-0.dll" v0.0 ts=2009/2/9 4:06
>   10k 2009/10/14 D:\cygwin-1.7\bin\cygXcomposite-1.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygXcomposite-1.dll" v0.0 ts=2009/10/14 18:51
>   30k 2009/09/03 D:\cygwin-1.7\bin\cygXcursor-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygXcursor-1.dll" v0.0 ts=2009/9/2 22:47
>    9k 2009/10/14 D:\cygwin-1.7\bin\cygXdamage-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygXdamage-1.dll" v0.0 ts=2009/10/14 17:54
>   17k 2009/10/14 D:\cygwin-1.7\bin\cygXdmcp-6.dll - os=4.0 img=1.0 sys=4.0
>                  "cygXdmcp-6.dll" v0.0 ts=2009/10/13 23:31
>   51k 2009/10/22 D:\cygwin-1.7\bin\cygXext-6.dll - os=4.0 img=1.0 sys=4.0
>                  "cygXext-6.dll" v0.0 ts=2009/10/22 4:45
>   16k 2009/10/14 D:\cygwin-1.7\bin\cygXfixes-3.dll - os=4.0 img=1.0 sys=4.0
>                  "cygXfixes-3.dll" v0.0 ts=2009/10/14 17:48
>   66k 2009/10/15 D:\cygwin-1.7\bin\cygXft-2.dll - os=4.0 img=1.0 sys=4.0
>                  "cygXft-2.dll" v0.0 ts=2009/10/14 21:33
>   47k 2009/10/14 D:\cygwin-1.7\bin\cygXi-6.dll - os=4.0 img=1.0 sys=4.0
>                  "cygXi-6.dll" v0.0 ts=2009/10/14 6:19
>    8k 2009/10/14 D:\cygwin-1.7\bin\cygXinerama-1.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygXinerama-1.dll" v0.0 ts=2009/10/14 8:39
>  122k 2009/10/15 D:\cygwin-1.7\bin\cygxkbfile-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygxkbfile-1.dll" v0.0 ts=2009/10/14 6:57
>  1172k 2009/07/08 D:\cygwin-1.7\bin\cygXm-2.dll - os=4.0 img=1.0 sys=4.0
>                  "cygXm-2.dll" v0.0 ts=2009/7/8 4:26
>  1123k 2009/10/08 D:\cygwin-1.7\bin\cygxml2-2.dll - os=4.0 img=1.0 sys=4.0
>                  "cygxml2-2.dll" v0.0 ts=2009/10/7 3:49
>   75k 2009/10/14 D:\cygwin-1.7\bin\cygXmu-6.dll - os=4.0 img=1.0 sys=4.0
>                  "cygXmu-6.dll" v0.0 ts=2009/10/14 8:29
>   11k 2009/10/14 D:\cygwin-1.7\bin\cygXmuu-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygXmuu-1.dll" v0.0 ts=2009/10/14 8:29
>   53k 2009/10/14 D:\cygwin-1.7\bin\cygXpm-4.dll - os=4.0 img=1.0 sys=4.0
>                  "cygXpm-4.dll" v0.0 ts=2009/10/14 18:01
>   25k 2009/03/20 D:\cygwin-1.7\bin\cygXrandr-2.dll - os=4.0 img=1.0 sys=4.0
>                  "cygXrandr-2.dll" v0.0 ts=2009/3/13 8:05
>   30k 2009/10/14 D:\cygwin-1.7\bin\cygXrender-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygXrender-1.dll" v0.0 ts=2009/10/14 8:40
>  277k 2009/10/14 D:\cygwin-1.7\bin\cygXt-6.dll - os=4.0 img=1.0 sys=4.0
>                  "cygXt-6.dll" v0.0 ts=2009/10/14 4:02
>   64k 2009/03/02 D:\cygwin-1.7\bin\cygz.dll - os=4.0 img=1.0 sys=4.0
>                  "cygz.dll" v0.0 ts=2009/3/2 1:33
>  2410k 2009/10/03 D:\cygwin-1.7\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygwin1.dll" v0.0 ts=2009/10/3 13:33
>    Cygwin DLL version info:
>        DLL version: 1.7.0
>        DLL epoch: 19
>        DLL old termios: 5
>        DLL malloc env: 28
>        Cygwin conv: 181
>        API major: 0
>        API minor: 214
>        Shared data: 5
>        DLL identifier: cygwin1
>        Mount registry: 3
>        Cygwin registry name: Cygwin
>        Program options name: Program Options
>        Cygdrive default prefix:
>        Build date: Sat Oct 3 14:33:20 CEST 2009
>        Shared id: cygwin1S5
>
>  111k 2009/08/07 D:\cygwin-1.7\bin\cygapr-1-0.dll - os=4.0 img=1.0 sys=4.0
>                  "cygapr-1-0.dll" v0.0 ts=2009/8/7 20:58
>   87k 2009/08/07 D:\cygwin-1.7\bin\cygaprutil-1-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygaprutil-1-0.dll" v0.0 ts=2009/8/7 21:46
>  704k 2007/12/18 D:\cygwin-1.7\bin\cygaspell-15.dll - os=4.0 img=1.0 sys=4.0
>                  "cygaspell-15.dll" v0.0 ts=2007/12/18 11:39
>   88k 2009/03/24 D:\cygwin-1.7\bin\cygatk-1.0-0.dll - os=4.0 img=1.0 sys=4.0
>                  "cygatk-1.0-0.dll" v0.0 ts=2009/3/25 0:36
>  351k 2008/01/14 D:\cygwin-1.7\bin\cygboost_date_time-gcc-mt-1_33_1.dll -
> os=4.0 img=1.33 sys=4.0
>                  "cygboost_date_time-gcc-mt-1_33_1.dll" v0.0 ts=2008/1/14
> 8:36
>  120k 2008/01/14 D:\cygwin-1.7\bin\cygboost_filesystem-gcc-mt-1_33_1.dll -
> os=4.0 img=1.33 sys=4.0
>                  "cygboost_filesystem-gcc-mt-1_33_1.dll" v0.0 ts=2008/1/14
> 8:36
>   79k 2008/01/14 D:\cygwin-1.7\bin\cygboost_iostreams-gcc-mt-1_33_1.dll -
> os=4.0 img=1.33 sys=4.0
>                  "cygboost_iostreams-gcc-mt-1_33_1.dll" v0.0 ts=2008/1/14
> 8:37
>  526k 2008/01/14
> D:\cygwin-1.7\bin\cygboost_program_options-gcc-mt-1_33_1.dll - os=4.0
> img=1.33 sys=4.0
>                  "cygboost_program_options-gcc-mt-1_33_1.dll" v0.0
> ts=2008/1/14 8:38
>  564k 2008/01/14 D:\cygwin-1.7\bin\cygboost_python-gcc-mt-1_33_1.dll -
> os=4.0 img=1.33 sys=4.0
>                  "cygboost_python-gcc-mt-1_33_1.dll" v0.0 ts=2008/1/14 8:39
>  678k 2008/01/14 D:\cygwin-1.7\bin\cygboost_regex-gcc-mt-1_33_1.dll - os=4.0
> img=1.33 sys=4.0
>                  "cygboost_regex-gcc-mt-1_33_1.dll" v0.0 ts=2008/1/14 8:41
>  621k 2008/01/14 D:\cygwin-1.7\bin\cygboost_serialization-gcc-mt-1_33_1.dll
> - os=4.0 img=1.33 sys=4.0
>                  "cygboost_serialization-gcc-mt-1_33_1.dll" v0.0
> ts=2008/1/14 8:44
>  118k 2008/01/14 D:\cygwin-1.7\bin\cygboost_signals-gcc-mt-1_33_1.dll -
> os=4.0 img=1.33 sys=4.0
>                  "cygboost_signals-gcc-mt-1_33_1.dll" v0.0 ts=2008/1/14 8:44
>   91k 2008/01/14 D:\cygwin-1.7\bin\cygboost_thread-gcc-mt-1_33_1.dll -
> os=4.0 img=1.33 sys=4.0
>                  "cygboost_thread-gcc-mt-1_33_1.dll" v0.0 ts=2008/1/14 8:47
>   61k 2009/03/02 D:\cygwin-1.7\bin\cygbz2-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygbz2-1.dll" v0.0 ts=2009/3/2 3:11
>  456k 2009/06/25 D:\cygwin-1.7\bin\cygcairo-2.dll - os=4.0 img=1.0 sys=4.0
>                  "cygcairo-2.dll" v0.0 ts=2009/6/25 7:25
>    7k 2009/05/30 D:\cygwin-1.7\bin\cygcharset-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygcharset-1.dll" v0.0 ts=2009/5/30 20:05
>    7k 2003/10/19 D:\cygwin-1.7\bin\cygcrypt-0.dll - os=4.0 img=1.0 sys=4.0
>                  "cygcrypt-0.dll" v0.0 ts=2003/10/19 8:57
>  1074k 2009/03/25 D:\cygwin-1.7\bin\cygcrypto-0.9.8.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygcrypto-0.9.8.dll" v0.0 ts=2009/3/25 17:45
>  254k 2009/08/23 D:\cygwin-1.7\bin\cygcurl-4.dll - os=4.0 img=1.0 sys=4.0
>                  "cygcurl-4.dll" v0.0 ts=2009/8/23 6:25
>  703k 2007/12/17 D:\cygwin-1.7\bin\cygdb-4.2.dll - os=4.0 img=1.0 sys=4.0
>                  "cygdb-4.2.dll" v0.0 ts=2007/12/17 11:58
>  943k 2007/12/17 D:\cygwin-1.7\bin\cygdb-4.5.dll - os=4.0 img=1.0 sys=4.0
>                  "cygdb-4.5.dll" v0.0 ts=2007/12/17 13:12
>  1036k 2007/12/17 D:\cygwin-1.7\bin\cygdb_cxx-4.2.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygdb_cxx-4.2.dll" v0.0 ts=2007/12/17 11:58
>  1296k 2007/12/17 D:\cygwin-1.7\bin\cygdb_cxx-4.5.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygdb_cxx-4.5.dll" v0.0 ts=2007/12/17 13:12
>  118k 2007/04/06 D:\cygwin-1.7\bin\cygexpat-0.dll - os=4.0 img=1.0 sys=4.0
>                  "cygexpat-0.dll" v0.0 ts=2007/4/6 21:43
>  118k 2008/05/09 D:\cygwin-1.7\bin\cygexpat-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygexpat-1.dll" v0.0 ts=2008/5/9 5:03
>   28k 2009/03/22 D:\cygwin-1.7\bin\cygfam-0.dll - os=4.0 img=1.0 sys=4.0
>                  "cygfam-0.dll" v0.0 ts=2009/3/22 19:56
>  286k 2006/08/06 D:\cygwin-1.7\bin\cygfcgi++-0.dll - os=4.0 img=1.0 sys=4.0
>                  "cygfcgi++-0.dll" v0.0 ts=2006/8/6 21:09
>   30k 2006/08/06 D:\cygwin-1.7\bin\cygfcgi-0.dll - os=4.0 img=1.0 sys=4.0
>                  "cygfcgi-0.dll" v0.0 ts=2006/8/6 21:09
>   22k 2009/09/29 D:\cygwin-1.7\bin\cygffi-4.dll - os=4.0 img=1.0 sys=4.0
>                  "cygffi-4.dll" v0.0 ts=2009/9/14 16:50
>  784k 2009/07/28 D:\cygwin-1.7\bin\cygfftw3-3.dll - os=4.0 img=1.0 sys=4.0
>                  "cygfftw3-3.dll" v0.0 ts=2009/7/28 20:14
>  758k 2009/07/28 D:\cygwin-1.7\bin\cygfftw3f-3.dll - os=4.0 img=1.0 sys=4.0
>                  "cygfftw3f-3.dll" v0.0 ts=2009/7/28 20:05
>   19k 2009/07/28 D:\cygwin-1.7\bin\cygfftw3f_threads-3.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygfftw3f_threads-3.dll" v0.0 ts=2009/7/28 20:05
>   19k 2009/07/28 D:\cygwin-1.7\bin\cygfftw3_threads-3.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygfftw3_threads-3.dll" v0.0 ts=2009/7/28 20:14
>  174k 2009/09/25 D:\cygwin-1.7\bin\cygfontconfig-1.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygfontconfig-1.dll" v0.0 ts=2009/9/25 3:05
>   21k 2009/10/14 D:\cygwin-1.7\bin\cygfontenc-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygfontenc-1.dll" v0.0 ts=2009/10/14 2:04
>   40k 2009/03/01 D:\cygwin-1.7\bin\cygform-8.dll - os=4.0 img=1.0 sys=4.0
>                  "cygform-8.dll" v0.0 ts=2009/3/1 6:32
>   41k 2009/10/26 D:\cygwin-1.7\bin\cygform-9.dll - os=4.0 img=1.0 sys=4.0
>                  "cygform-9.dll" v0.0 ts=2009/10/26 23:02
>   48k 2003/08/09 D:\cygwin-1.7\bin\cygform7.dll - os=4.0 img=1.0 sys=4.0
>                  "cygform7.dll" v0.0 ts=2003/8/9 10:25
>  489k 2009/10/15 D:\cygwin-1.7\bin\cygfreetype-6.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygfreetype-6.dll" v0.0 ts=2009/10/15 2:22
>   44k 2009/09/29 D:\cygwin-1.7\bin\cyggcc_s-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cyggcc_s-1.dll" v0.0 ts=2009/9/14 16:42
>   41k 2008/09/12 D:\cygwin-1.7\bin\cyggcc_s.dll - os=4.0 img=1.0 sys=4.0
>                  "cyggcc_s.dll" v0.0 ts=2008/9/11 7:43
>   19k 2009/02/26 D:\cygwin-1.7\bin\cyggdbm-4.dll - os=4.0 img=1.0 sys=4.0
>                  "cyggdbm-4.dll" v0.0 ts=2009/2/26 7:58
>    8k 2009/02/26 D:\cygwin-1.7\bin\cyggdbm_compat-4.dll - os=4.0 img=1.0
> sys=4.0
>                  "cyggdbm_compat-4.dll" v0.0 ts=2009/2/26 7:58
>  193k 2009/03/23 D:\cygwin-1.7\bin\cyggdk-1-2-0.dll - os=4.0 img=1.0 sys=4.0
>                  "cyggdk-1-2-0.dll" v0.0 ts=2009/3/23 15:24
>  504k 2009/09/08 D:\cygwin-1.7\bin\cyggdk-x11-2.0-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cyggdk-x11-2.0-0.dll" v0.0 ts=2009/9/7 7:34
>   90k 2009/09/08 D:\cygwin-1.7\bin\cyggdk_pixbuf-2.0-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cyggdk_pixbuf-2.0-0.dll" v0.0 ts=2009/9/7 7:32
>  954k 2009/04/03 D:\cygwin-1.7\bin\cyggettextlib-0-17.dll - os=4.0 img=1.0
> sys=4.0
>                  "cyggettextlib-0-17.dll" v0.0 ts=2009/4/3 2:21
>  218k 2009/04/03 D:\cygwin-1.7\bin\cyggettextpo-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cyggettextpo-0.dll" v0.0 ts=2009/4/3 2:29
>  203k 2009/04/03 D:\cygwin-1.7\bin\cyggettextsrc-0-17.dll - os=4.0 img=1.0
> sys=4.0
>                  "cyggettextsrc-0-17.dll" v0.0 ts=2009/4/3 2:24
>  642k 2009/09/29 D:\cygwin-1.7\bin\cyggfortran-3.dll - os=4.0 img=1.0
> sys=4.0
>                  "cyggfortran-3.dll" v0.0 ts=2009/9/14 17:42
>   29k 2009/03/23 D:\cygwin-1.7\bin\cyggif-4.dll - os=4.0 img=1.0 sys=4.0
>                  "cyggif-4.dll" v0.0 ts=2009/3/23 19:55
>  367k 2009/09/07 D:\cygwin-1.7\bin\cyggio-2.0-0.dll - os=4.0 img=1.0 sys=4.0
>                  "cyggio-2.0-0.dll" v0.0 ts=2009/9/7 5:10
>  2311k 2009/10/16 D:\cygwin-1.7\bin\cygGL-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygGL-1.dll" v0.0 ts=2009/10/16 10:17
>  133k 2009/03/25 D:\cygwin-1.7\bin\cygglib-1-2-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygglib-1-2-0.dll" v0.0 ts=2009/3/23 15:12
>  678k 2009/09/07 D:\cygwin-1.7\bin\cygglib-2.0-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygglib-2.0-0.dll" v0.0 ts=2009/9/7 5:07
>  141k 2009/03/30 D:\cygwin-1.7\bin\cygglitz-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygglitz-1.dll" v0.0 ts=2009/3/30 17:22
>   21k 2009/03/30 D:\cygwin-1.7\bin\cygglitz-glx-1.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygglitz-glx-1.dll" v0.0 ts=2009/3/30 17:23
>  445k 2009/10/16 D:\cygwin-1.7\bin\cygGLU-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygGLU-1.dll" v0.0 ts=2009/10/16 10:17
>   12k 2009/03/25 D:\cygwin-1.7\bin\cyggmodule-1-2-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cyggmodule-1-2-0.dll" v0.0 ts=2009/3/23 15:12
>   13k 2009/09/07 D:\cygwin-1.7\bin\cyggmodule-2.0-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cyggmodule-2.0-0.dll" v0.0 ts=2009/9/7 5:08
>  315k 2009/06/06 D:\cygwin-1.7\bin\cyggmp-3.dll - os=4.0 img=1.0 sys=4.0
>                  "cyggmp-3.dll" v0.0 ts=2009/6/6 12:23
>  226k 2009/09/07 D:\cygwin-1.7\bin\cyggobject-2.0-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cyggobject-2.0-0.dll" v0.0 ts=2009/9/7 5:08
>   24k 2009/09/29 D:\cygwin-1.7\bin\cyggomp-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cyggomp-1.dll" v0.0 ts=2009/9/14 16:51
>  5491k 2008/11/27 D:\cygwin-1.7\bin\cyggs-8.dll - os=4.0 img=1.0 sys=4.0
>                  "cyggs-8.dll" v0.0 ts=2008/11/27 13:24
>  1640k 2009/09/20 D:\cygwin-1.7\bin\cyggsl-0.dll - os=4.0 img=1.0 sys=4.0
>                  "cyggsl-0.dll" v0.0 ts=2009/9/20 15:39
>  186k 2009/09/20 D:\cygwin-1.7\bin\cyggslcblas-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cyggslcblas-0.dll" v0.0 ts=2009/9/20 15:29
>    9k 2009/03/25 D:\cygwin-1.7\bin\cyggthread-1-2-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cyggthread-1-2-0.dll" v0.0 ts=2009/3/23 15:13
>   15k 2009/09/07 D:\cygwin-1.7\bin\cyggthread-2.0-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cyggthread-2.0-0.dll" v0.0 ts=2009/9/7 5:08
>  1258k 2009/03/23 D:\cygwin-1.7\bin\cyggtk-1-2-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cyggtk-1-2-0.dll" v0.0 ts=2009/3/23 15:29
>  3502k 2009/09/08 D:\cygwin-1.7\bin\cyggtk-x11-2.0-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cyggtk-x11-2.0-0.dll" v0.0 ts=2009/9/7 7:40
>   24k 2009/06/23 D:\cygwin-1.7\bin\cyghistory6.dll - os=4.0 img=1.0 sys=4.0
>                  "cyghistory6.dll" v0.0 ts=2009/6/23 13:20
>   25k 2009/07/06 D:\cygwin-1.7\bin\cyghistory7.dll - os=4.0 img=1.0 sys=4.0
>                  "cyghistory7.dll" v0.0 ts=2009/7/5 15:45
>   73k 2009/09/02 D:\cygwin-1.7\bin\cygICE-6.dll - os=4.0 img=1.0 sys=4.0
>                  "cygICE-6.dll" v0.0 ts=2009/9/2 22:39
>  270k 2009/05/07 D:\cygwin-1.7\bin\cygicons-0.dll - os=4.0 img=1.0 sys=4.0
>                  "cygicons-0.dll" v0.0 ts=2009/5/7 1:58
>  981k 2009/05/30 D:\cygwin-1.7\bin\cygiconv-2.dll - os=4.0 img=1.0 sys=4.0
>                  "cygiconv-2.dll" v0.0 ts=2009/5/30 20:05
> 10918k 2008/11/10 D:\cygwin-1.7\bin\cygicudata38.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygicudata38.dll" v0.0 ts=2008/11/10 11:06
>  1246k 2008/11/10 D:\cygwin-1.7\bin\cygicui18n38.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygicui18n38.dll" v0.0 ts=2008/11/10 10:59
>  243k 2008/11/10 D:\cygwin-1.7\bin\cygicuio38.dll - os=4.0 img=1.0 sys=4.0
>                  "cygicuio38.dll" v0.0 ts=2008/11/10 11:06
>  256k 2008/11/10 D:\cygwin-1.7\bin\cygicule38.dll - os=4.0 img=1.0 sys=4.0
>                  "cygicule38.dll" v0.0 ts=2008/11/10 11:01
>   70k 2008/11/10 D:\cygwin-1.7\bin\cygiculx38.dll - os=4.0 img=1.0 sys=4.0
>                  "cygiculx38.dll" v0.0 ts=2008/11/10 11:01
>  1066k 2008/11/10 D:\cygwin-1.7\bin\cygicuuc38.dll - os=4.0 img=1.0 sys=4.0
>                  "cygicuuc38.dll" v0.0 ts=2008/11/10 10:53
>  191k 2009/09/15 D:\cygwin-1.7\bin\cygidn-11.dll - os=4.0 img=1.0 sys=4.0
>                  "cygidn-11.dll" v0.0 ts=2009/9/15 11:41
>   22k 2001/12/13 D:\cygwin-1.7\bin\cygintl-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygintl-1.dll" v0.0 ts=2001/12/13 9:28
>   37k 2003/08/10 D:\cygwin-1.7\bin\cygintl-2.dll - os=4.0 img=1.0 sys=4.0
>                  "cygintl-2.dll" v0.0 ts=2003/8/10 22:50
>   31k 2005/11/20 D:\cygwin-1.7\bin\cygintl-3.dll - os=4.0 img=1.0 sys=4.0
>                  "cygintl-3.dll" v0.0 ts=2005/11/20 2:04
>   31k 2009/04/03 D:\cygwin-1.7\bin\cygintl-8.dll - os=4.0 img=1.0 sys=4.0
>                  "cygintl-8.dll" v0.0 ts=2009/4/3 2:15
>  246k 2008/04/02 D:\cygwin-1.7\bin\cygjasper-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygjasper-1.dll" v0.0 ts=2008/4/2 17:19
>   41k 2009/03/10 D:\cygwin-1.7\bin\cygjbig-2.dll - os=4.0 img=1.0 sys=4.0
>                  "cygjbig-2.dll" v0.0 ts=2009/3/10 3:10
>   48k 2003/08/10 D:\cygwin-1.7\bin\cygjbig1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygjbig1.dll" v0.0 ts=2003/8/11 0:58
>  125k 2009/08/08 D:\cygwin-1.7\bin\cygjpeg-62.dll - os=4.0 img=1.0 sys=4.0
>                  "cygjpeg-62.dll" v0.0 ts=2009/8/8 21:48
>  193k 2009/08/08 D:\cygwin-1.7\bin\cygjpeg-7.dll - os=4.0 img=1.0 sys=4.0
>                  "cygjpeg-7.dll" v0.0 ts=2009/8/8 20:39
>  119k 2002/02/09 D:\cygwin-1.7\bin\cygjpeg6b.dll - os=4.0 img=1.0 sys=4.0
>                  "cygjpeg6b.dll" v0.0 ts=2002/2/9 5:19
>   39k 2008/09/07 D:\cygwin-1.7\bin\cyglber-2-3-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cyglber-2-3-0.dll" v0.0 ts=2008/9/7 13:28
>  189k 2008/09/07 D:\cygwin-1.7\bin\cygldap-2-3-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygldap-2-3-0.dll" v0.0 ts=2008/9/7 13:29
>  201k 2008/09/07 D:\cygwin-1.7\bin\cygldap_r-2-3-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygldap_r-2-3-0.dll" v0.0 ts=2008/9/7 13:31
>    5k 2009/10/03 D:\cygwin-1.7\bin\cyglsa.dll - os=4.0 img=1.0 sys=4.0
>                  "cyglsa.dll" v0.0 ts=2009/10/3 13:34
>    9k 2009/10/03 D:\cygwin-1.7\bin\cyglsa64.dll - os=4.0 img=0.0 sys=5.2
>   27k 2009/07/13 D:\cygwin-1.7\bin\cygltdl-7.dll - os=4.0 img=1.0 sys=4.0
>                  "cygltdl-7.dll" v0.0 ts=2009/7/13 1:50
>  133k 2009/06/10 D:\cygwin-1.7\bin\cyglua-5.1.dll - os=4.0 img=1.0 sys=4.0
>                  "cyglua-5.1.dll" v0.0 ts=2009/6/10 18:29
>  123k 2009/08/30 D:\cygwin-1.7\bin\cyglzma-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cyglzma-1.dll" v0.0 ts=2009/8/30 23:35
>   12k 2009/03/15 D:\cygwin-1.7\bin\cyglzmadec-0.dll - os=4.0 img=1.0 sys=4.0
>                  "cyglzmadec-0.dll" v0.0 ts=2009/3/15 7:16
>   98k 2009/03/16 D:\cygwin-1.7\bin\cygmagic-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygmagic-1.dll" v0.0 ts=2009/3/16 17:32
>   21k 2009/03/01 D:\cygwin-1.7\bin\cygmenu-8.dll - os=4.0 img=1.0 sys=4.0
>                  "cygmenu-8.dll" v0.0 ts=2009/3/1 6:31
>   22k 2009/10/26 D:\cygwin-1.7\bin\cygmenu-9.dll - os=4.0 img=1.0 sys=4.0
>                  "cygmenu-9.dll" v0.0 ts=2009/10/26 23:01
>   29k 2003/08/09 D:\cygwin-1.7\bin\cygmenu7.dll - os=4.0 img=1.0 sys=4.0
>                  "cygmenu7.dll" v0.0 ts=2003/8/9 10:25
>   24k 2008/10/30 D:\cygwin-1.7\bin\cygminires.dll - os=4.0 img=1.2 sys=4.0
>                  "cygminires.dll" v0.0 ts=2008/10/31 0:53
>  211k 2009/06/06 D:\cygwin-1.7\bin\cygmp-3.dll - os=4.0 img=1.0 sys=4.0
>                  "cygmp-3.dll" v0.0 ts=2009/6/6 12:23
>  269k 2009/06/07 D:\cygwin-1.7\bin\cygmpfr-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygmpfr-1.dll" v0.0 ts=2009/6/7 22:10
>   75k 2009/07/08 D:\cygwin-1.7\bin\cygMrm-2.dll - os=4.0 img=1.0 sys=4.0
>                  "cygMrm-2.dll" v0.0 ts=2009/7/8 4:26
>   66k 2009/03/01 D:\cygwin-1.7\bin\cygncurses++-8.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygncurses++-8.dll" v0.0 ts=2009/3/1 6:39
>   61k 2009/10/26 D:\cygwin-1.7\bin\cygncurses++-9.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygncurses++-9.dll" v0.0 ts=2009/10/26 23:12
>  237k 2009/03/01 D:\cygwin-1.7\bin\cygncurses-8.dll - os=4.0 img=1.0 sys=4.0
>                  "cygncurses-8.dll" v0.0 ts=2009/3/1 6:28
>  195k 2009/10/26 D:\cygwin-1.7\bin\cygncurses-9.dll - os=4.0 img=1.0 sys=4.0
>                  "cygncurses-9.dll" v0.0 ts=2009/10/26 22:58
>  224k 2003/08/09 D:\cygwin-1.7\bin\cygncurses7.dll - os=4.0 img=1.0 sys=4.0
>                  "cygncurses7.dll" v0.0 ts=2003/8/9 10:24
>  115k 2009/09/30 D:\cygwin-1.7\bin\cygneon-27.dll - os=4.0 img=1.0 sys=4.0
>                  "cygneon-27.dll" v0.0 ts=2009/9/30 14:33
>  173k 2009/09/02 D:\cygwin-1.7\bin\cygnetpbm-10.dll - os=4.0 img=1.0 sys=4.0
>                  "cygnetpbm-10.dll" v0.0 ts=2009/9/2 4:33
>   11k 2009/03/01 D:\cygwin-1.7\bin\cygpanel-8.dll - os=4.0 img=1.0 sys=4.0
>                  "cygpanel-8.dll" v0.0 ts=2009/3/1 6:30
>   12k 2009/10/26 D:\cygwin-1.7\bin\cygpanel-9.dll - os=4.0 img=1.0 sys=4.0
>                  "cygpanel-9.dll" v0.0 ts=2009/10/26 23:00
>   19k 2003/08/09 D:\cygwin-1.7\bin\cygpanel7.dll - os=4.0 img=1.0 sys=4.0
>                  "cygpanel7.dll" v0.0 ts=2003/8/9 10:24
>  230k 2009/07/27 D:\cygwin-1.7\bin\cygpango-1.0-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygpango-1.0-0.dll" v0.0 ts=2009/7/27 5:42
>   34k 2009/07/27 D:\cygwin-1.7\bin\cygpangocairo-1.0-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygpangocairo-1.0-0.dll" v0.0 ts=2009/7/27 5:42
>  142k 2009/07/27 D:\cygwin-1.7\bin\cygpangoft2-1.0-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygpangoft2-1.0-0.dll" v0.0 ts=2009/7/27 5:42
>   37k 2009/07/27 D:\cygwin-1.7\bin\cygpangox-1.0-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygpangox-1.0-0.dll" v0.0 ts=2009/7/27 5:42
>   23k 2009/07/27 D:\cygwin-1.7\bin\cygpangoxft-1.0-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygpangoxft-1.0-0.dll" v0.0 ts=2009/7/27 5:42
>  190k 2009/04/17 D:\cygwin-1.7\bin\cygpcre-0.dll - os=4.0 img=1.0 sys=4.0
>                  "cygpcre-0.dll" v0.0 ts=2009/4/17 17:07
>    7k 2009/04/17 D:\cygwin-1.7\bin\cygpcreposix-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygpcreposix-0.dll" v0.0 ts=2009/4/17 17:07
>  1543k 2008/07/03 D:\cygwin-1.7\bin\cygperl5_10.dll - os=4.0 img=1.0 sys=4.0
>                  "cygperl5_10.dll" v0.0 ts=2008/6/30 17:06
>  354k 2009/10/14 D:\cygwin-1.7\bin\cygpixman-1-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygpixman-1-0.dll" v0.0 ts=2009/10/14 1:39
>  242k 2009/03/07 D:\cygwin-1.7\bin\cygpng12.dll - os=4.0 img=1.0 sys=4.0
>                  "cygpng12.dll" v0.0 ts=2009/3/7 22:38
>   22k 2002/06/09 D:\cygwin-1.7\bin\cygpopt-0.dll - os=4.0 img=1.0 sys=4.0
>                  "cygpopt-0.dll" v0.0 ts=2002/6/9 6:45
>  103k 2009/01/07 D:\cygwin-1.7\bin\cygpq.dll - os=4.0 img=1.0 sys=4.0
>                  "cygpq.dll" v0.0 ts=2009/1/7 16:46
>    4k 2007/12/18 D:\cygwin-1.7\bin\cygpspell-15.dll - os=4.0 img=1.0 sys=4.0
>                  "cygpspell-15.dll" v0.0 ts=2007/12/18 11:40
>  155k 2009/06/23 D:\cygwin-1.7\bin\cygreadline6.dll - os=4.0 img=1.0 sys=4.0
>                  "cygreadline6.dll" v0.0 ts=2009/6/23 13:20
>  162k 2009/07/06 D:\cygwin-1.7\bin\cygreadline7.dll - os=4.0 img=1.0 sys=4.0
>                  "cygreadline7.dll" v0.0 ts=2009/7/5 15:45
>  761k 2008/09/30 D:\cygwin-1.7\bin\cygruby18.dll - os=4.0 img=1.0 sys=4.0
>                  "cygruby18.dll" v0.0 ts=2008/9/30 14:10
>   78k 2004/10/13 D:\cygwin-1.7\bin\cygsasl2-2.dll - os=4.0 img=1.0 sys=4.0
>                  "cygsasl2-2.dll" v0.0 ts=2004/10/13 23:50
>   43k 2009/02/06 D:\cygwin-1.7\bin\cygserf-0-0.dll - os=4.0 img=1.0 sys=4.0
>                  "cygserf-0-0.dll" v0.0 ts=2009/2/6 17:04
>    7k 2009/07/22 D:\cygwin-1.7\bin\cygsigsegv-0.dll - os=4.0 img=1.0 sys=4.0
>                  "cygsigsegv-0.dll" v0.0 ts=2009/7/22 9:57
>    9k 2009/07/24 D:\cygwin-1.7\bin\cygsigsegv-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygsigsegv-1.dll" v0.0 ts=2009/7/24 21:04
>   27k 2009/09/03 D:\cygwin-1.7\bin\cygSM-6.dll - os=4.0 img=1.0 sys=4.0
>                  "cygSM-6.dll" v0.0 ts=2009/9/3 9:56
>  355k 2008/09/09 D:\cygwin-1.7\bin\cygsqlite3-0.dll - os=4.0 img=1.0 sys=4.0
>                  "cygsqlite3-0.dll" v0.0 ts=2008/9/9 19:20
>  125k 2009/10/07 D:\cygwin-1.7\bin\cygssh2-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygssh2-1.dll" v0.0 ts=2009/10/7 3:25
>  232k 2009/03/25 D:\cygwin-1.7\bin\cygssl-0.9.8.dll - os=4.0 img=1.0 sys=4.0
>                  "cygssl-0.9.8.dll" v0.0 ts=2009/3/25 17:45
>    8k 2009/09/29 D:\cygwin-1.7\bin\cygssp-0.dll - os=4.0 img=1.0 sys=4.0
>                  "cygssp-0.dll" v0.0 ts=2009/9/14 16:49
>  771k 2009/09/29 D:\cygwin-1.7\bin\cygstdc++-6.dll - os=4.0 img=1.0 sys=4.0
>                  "cygstdc++-6.dll" v0.0 ts=2009/9/14 17:19
>  234k 2009/10/26 D:\cygwin-1.7\bin\cygsvn_client-1-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygsvn_client-1-0.dll" v0.0 ts=2009/10/23 16:46
>   36k 2009/10/26 D:\cygwin-1.7\bin\cygsvn_delta-1-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygsvn_delta-1-0.dll" v0.0 ts=2009/10/23 16:43
>   39k 2009/10/26 D:\cygwin-1.7\bin\cygsvn_diff-1-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygsvn_diff-1-0.dll" v0.0 ts=2009/10/23 16:43
>   18k 2009/10/26 D:\cygwin-1.7\bin\cygsvn_fs-1-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygsvn_fs-1-0.dll" v0.0 ts=2009/10/23 16:44
>  144k 2009/10/26 D:\cygwin-1.7\bin\cygsvn_fs_base-1-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygsvn_fs_base-1-0.dll" v0.0 ts=2009/10/23 16:43
>  123k 2009/10/26 D:\cygwin-1.7\bin\cygsvn_fs_fs-1-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygsvn_fs_fs-1-0.dll" v0.0 ts=2009/10/23 16:43
>    7k 2009/10/26 D:\cygwin-1.7\bin\cygsvn_fs_util-1-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygsvn_fs_util-1-0.dll" v0.0 ts=2009/10/23 16:43
>   30k 2009/10/26 D:\cygwin-1.7\bin\cygsvn_ra-1-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygsvn_ra-1-0.dll" v0.0 ts=2009/10/23 16:46
>   23k 2009/10/26 D:\cygwin-1.7\bin\cygsvn_ra_local-1-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygsvn_ra_local-1-0.dll" v0.0 ts=2009/10/23 16:44
>  113k 2009/10/26 D:\cygwin-1.7\bin\cygsvn_ra_neon-1-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygsvn_ra_neon-1-0.dll" v0.0 ts=2009/10/23 16:43
>  114k 2009/10/26 D:\cygwin-1.7\bin\cygsvn_ra_serf-1-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygsvn_ra_serf-1-0.dll" v0.0 ts=2009/10/23 16:43
>   70k 2009/10/26 D:\cygwin-1.7\bin\cygsvn_ra_svn-1-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygsvn_ra_svn-1-0.dll" v0.0 ts=2009/10/23 16:43
>  138k 2009/10/26 D:\cygwin-1.7\bin\cygsvn_repos-1-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygsvn_repos-1-0.dll" v0.0 ts=2009/10/23 16:44
>  246k 2009/10/26 D:\cygwin-1.7\bin\cygsvn_subr-1-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygsvn_subr-1-0.dll" v0.0 ts=2009/10/23 16:43
>  240k 2009/10/26 D:\cygwin-1.7\bin\cygsvn_wc-1-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygsvn_wc-1-0.dll" v0.0 ts=2009/10/23 16:43
>  231k 2009/09/15 D:\cygwin-1.7\bin\cygt1-5.dll - os=4.0 img=1.0 sys=4.0
>                  "cygt1-5.dll" v0.0 ts=2009/9/15 10:59
>   46k 2009/10/26 D:\cygwin-1.7\bin\cygtic-9.dll - os=4.0 img=1.0 sys=4.0
>                  "cygtic-9.dll" v0.0 ts=2009/10/26 22:58
>  312k 2009/08/10 D:\cygwin-1.7\bin\cygtiff-5.dll - os=4.0 img=1.0 sys=4.0
>                  "cygtiff-5.dll" v0.0 ts=2009/8/10 23:04
>  281k 2003/02/24 D:\cygwin-1.7\bin\cygtiff3.dll - os=4.0 img=1.0 sys=4.0
>                  "cygtiff3.dll" v0.0 ts=2003/2/24 4:58
>  282k 2003/08/11 D:\cygwin-1.7\bin\cygtiff4.dll - os=4.0 img=1.0 sys=4.0
>                  "cygtiff4.dll" v0.0 ts=2003/8/11 3:32
>  282k 2009/08/10 D:\cygwin-1.7\bin\cygtiffxx-5.dll - os=4.0 img=1.0 sys=4.0
>                  "cygtiffxx-5.dll" v0.0 ts=2009/8/10 23:04
>   65k 2009/07/08 D:\cygwin-1.7\bin\cygUil-2.dll - os=4.0 img=1.0 sys=4.0
>                  "cygUil-2.dll" v0.0 ts=2009/7/8 4:26
>   27k 2006/12/06 D:\cygwin-1.7\bin\cygungif-4.dll - os=4.0 img=1.0 sys=4.0
>                  "cygungif-4.dll" v0.0 ts=2006/12/6 3:41
>   40k 2009/07/08 D:\cygwin-1.7\bin\cygusb0.dll - os=4.0 img=1.0 sys=4.0
>                  "cygusb0.dll" v0.0 ts=2009/7/8 9:35
>   24k 2009/03/29 D:\cygwin-1.7\bin\cygwrap-0.dll - os=4.0 img=1.0 sys=4.0
>                  "cygwrap-0.dll" v0.0 ts=2009/3/29 7:28
>  1038k 2009/10/25 D:\cygwin-1.7\bin\cygX11-6.dll - os=4.0 img=1.0 sys=4.0
>                  "cygX11-6.dll" v0.0 ts=2009/10/25 18:27
>    6k 2009/10/25 D:\cygwin-1.7\bin\cygX11-xcb-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygX11-xcb-1.dll" v0.0 ts=2009/10/25 18:27
>    9k 2009/09/03 D:\cygwin-1.7\bin\cygXau-6.dll - os=4.0 img=1.0 sys=4.0
>                  "cygXau-6.dll" v0.0 ts=2009/9/2 22:47
>  251k 2009/10/19 D:\cygwin-1.7\bin\cygXaw-6.dll - os=4.0 img=1.0 sys=4.0
>                  "cygXaw-6.dll" v0.0 ts=2009/10/18 22:55
>  352k 2009/10/19 D:\cygwin-1.7\bin\cygXaw-7.dll - os=4.0 img=1.0 sys=4.0
>                  "cygXaw-7.dll" v0.0 ts=2009/10/18 22:55
>  268k 2008/11/15 D:\cygwin-1.7\bin\cygXaw3d-7.dll - os=4.0 img=1.0 sys=4.0
>                  "cygXaw3d-7.dll" v0.0 ts=2008/11/13 8:37
>   74k 2009/09/21 D:\cygwin-1.7\bin\cygxcb-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygxcb-1.dll" v0.0 ts=2009/9/21 22:31
>   22k 2009/09/21 D:\cygwin-1.7\bin\cygxcb-render-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygxcb-render-0.dll" v0.0 ts=2009/9/21 22:32
>   11k 2009/09/03 D:\cygwin-1.7\bin\cygxcb-render-util-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygxcb-render-util-0.dll" v0.0 ts=2009/9/3 6:24
>    5k 2009/02/09 D:\cygwin-1.7\bin\cygxcb-xlib-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygxcb-xlib-0.dll" v0.0 ts=2009/2/9 4:06
>   10k 2009/10/14 D:\cygwin-1.7\bin\cygXcomposite-1.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygXcomposite-1.dll" v0.0 ts=2009/10/14 18:51
>   30k 2009/09/03 D:\cygwin-1.7\bin\cygXcursor-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygXcursor-1.dll" v0.0 ts=2009/9/2 22:47
>    9k 2009/10/14 D:\cygwin-1.7\bin\cygXdamage-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygXdamage-1.dll" v0.0 ts=2009/10/14 17:54
>   17k 2009/10/14 D:\cygwin-1.7\bin\cygXdmcp-6.dll - os=4.0 img=1.0 sys=4.0
>                  "cygXdmcp-6.dll" v0.0 ts=2009/10/13 23:31
>   51k 2009/10/22 D:\cygwin-1.7\bin\cygXext-6.dll - os=4.0 img=1.0 sys=4.0
>                  "cygXext-6.dll" v0.0 ts=2009/10/22 4:45
>   16k 2009/10/14 D:\cygwin-1.7\bin\cygXfixes-3.dll - os=4.0 img=1.0 sys=4.0
>                  "cygXfixes-3.dll" v0.0 ts=2009/10/14 17:48
>   66k 2009/10/15 D:\cygwin-1.7\bin\cygXft-2.dll - os=4.0 img=1.0 sys=4.0
>                  "cygXft-2.dll" v0.0 ts=2009/10/14 21:33
>   47k 2009/10/14 D:\cygwin-1.7\bin\cygXi-6.dll - os=4.0 img=1.0 sys=4.0
>                  "cygXi-6.dll" v0.0 ts=2009/10/14 6:19
>    8k 2009/10/14 D:\cygwin-1.7\bin\cygXinerama-1.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygXinerama-1.dll" v0.0 ts=2009/10/14 8:39
>  122k 2009/10/15 D:\cygwin-1.7\bin\cygxkbfile-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygxkbfile-1.dll" v0.0 ts=2009/10/14 6:57
>  1172k 2009/07/08 D:\cygwin-1.7\bin\cygXm-2.dll - os=4.0 img=1.0 sys=4.0
>                  "cygXm-2.dll" v0.0 ts=2009/7/8 4:26
>  1123k 2009/10/08 D:\cygwin-1.7\bin\cygxml2-2.dll - os=4.0 img=1.0 sys=4.0
>                  "cygxml2-2.dll" v0.0 ts=2009/10/7 3:49
>   75k 2009/10/14 D:\cygwin-1.7\bin\cygXmu-6.dll - os=4.0 img=1.0 sys=4.0
>                  "cygXmu-6.dll" v0.0 ts=2009/10/14 8:29
>   11k 2009/10/14 D:\cygwin-1.7\bin\cygXmuu-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygXmuu-1.dll" v0.0 ts=2009/10/14 8:29
>   53k 2009/10/14 D:\cygwin-1.7\bin\cygXpm-4.dll - os=4.0 img=1.0 sys=4.0
>                  "cygXpm-4.dll" v0.0 ts=2009/10/14 18:01
>   25k 2009/03/20 D:\cygwin-1.7\bin\cygXrandr-2.dll - os=4.0 img=1.0 sys=4.0
>                  "cygXrandr-2.dll" v0.0 ts=2009/3/13 8:05
>   30k 2009/10/14 D:\cygwin-1.7\bin\cygXrender-1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygXrender-1.dll" v0.0 ts=2009/10/14 8:40
>  277k 2009/10/14 D:\cygwin-1.7\bin\cygXt-6.dll - os=4.0 img=1.0 sys=4.0
>                  "cygXt-6.dll" v0.0 ts=2009/10/14 4:02
>   64k 2009/03/02 D:\cygwin-1.7\bin\cygz.dll - os=4.0 img=1.0 sys=4.0
>                  "cygz.dll" v0.0 ts=2009/3/2 1:33
>  2410k 2009/10/03 D:\cygwin-1.7\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0
>                  "cygwin1.dll" v0.0 ts=2009/10/3 13:33
>    Cygwin DLL version info:
>        DLL version: 1.7.0
>        DLL epoch: 19
>        DLL old termios: 5
>        DLL malloc env: 28
>        Cygwin conv: 181
>        API major: 0
>        API minor: 214
>        Shared data: 5
>        DLL identifier: cygwin1
>        Mount registry: 3
>        Cygwin registry name: Cygwin
>        Program options name: Program Options
>        Cygdrive default prefix:
>        Build date: Sat Oct 3 14:33:20 CEST 2009
>        Shared id: cygwin1S5
>
>  393k 2009/10/25 D:\cygwin-1.7\lib\lapack\cygblas-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cygblas-0.dll" v0.0 ts=2009/10/24 14:54
>  4053k 2009/10/25 D:\cygwin-1.7\lib\lapack\cyglapack-0.dll - os=4.0 img=1.0
> sys=4.0
>                  "cyglapack-0.dll" v0.0 ts=2009/10/24 23:11
>
> Service             : cygserver
> Display name        : CYGWIN cygserver
> Current State       : Running
> Controls Accepted   : Stop
> Command             : /usr/sbin/cygserver
> stdin path          : /dev/null
> stdout path         : /var/log/cygserver.log
> stderr path         : /var/log/cygserver.log
> Process Type        : Own Process
> Startup             : Automatic
> Account             : LocalSystem
>
> Service             : sshd
> Display name        : CYGWIN sshd
> Current State       : Running
> Controls Accepted   : Stop
> Command             : /usr/sbin/sshd -D
> stdin path          : /dev/null
> stdout path         : /var/log/sshd.log
> stderr path         : /var/log/sshd.log
> Process Type        : Own Process
> Startup             : Automatic
> Dependencies        : tcpip
> Account             : LocalSystem
>
>
> Cygwin Package Information
> Last downloaded files to: D:\downloads\cygwin-1.7
> Last downloaded files from: ftp://mirror.cs.vt.edu/pub/cygwin/cygwin/
>
> Package                        Version
> _update-info-dir               00833-1
> alternatives                   1.3.30c-10
> aspell                         0.60.5-1
> aspell-en                      6.0.0-1
> atool                          0.37.0-1
> autoconf                       7-10
> autoconf2.1                    2.13-10
> autoconf2.5                    2.64-10
> automake                       4-10
> automake1.10                   1.10.2-10
> automake1.11                   1.11-10
> automake1.4                    1.4p6-10
> automake1.5                    1.5-10
> automake1.6                    1.6.3-11
> automake1.7                    1.7.9-10
> automake1.8                    1.8.5-10
> automake1.9                    1.9.6-10
> base-cygwin                    2.0-1
> base-files                     3.8-4
> base-passwd                    3.1-1
> bash                           3.2.49-23
> bash-completion                1.0-1
> bc                             1.06-2
> binutils                       2.19.51-1
> bison                          2.3-1
> boost                          1.33.1-4
> boost-devel                    1.33.1-4
> bzip2                          1.0.5-10
> clisp                          2.48-2
> cocom                          0.995-1
> compositeproto                 0.4.1-1
> coreutils                      7.0-2
> crypt                          1.1-1
> csih                           0.9.1-1
> cvs                            1.12.13-10
> cygport                        0.9.9-1
> cygrunsrv                      1.34-1
> cygutils                       1.4.0-1
> cygwin                         1.7.0-62
> cygwin-doc                     1.5-1
> damageproto                    1.2.0-1
> dash                           0.5.5.1-2
> diffstat                       1.50-1
> diffutils                      2.8.7-1
> doxygen                        1.5.5-1
> e2fsprogs                      1.35-3
> ed                             1.0-1
> editrights                     1.01-2
> emacs                          23.1-10
> emacs-el                       23.1-10
> emacs-X11                      23.1-10
> expat                          2.0.1-1
> ffcall                         1.10-1
> fftw3                          3.2.2-1
> file                           5.00-3
> findutils                      4.5.4-1
> fixesproto                     4.1.1-1
> flex                           2.5.35-1
> font-adobe-dpi75               1.0.1-1
> font-adobe-utopia-dpi75        1.0.2-1
> font-adobe-utopia-type1        1.0.2-1
> font-alias                     1.0.2-1
> font-bh-dpi75                  1.0.1-1
> font-bh-lucidatypewriter-dpi75 1.0.1-1
> font-bh-ttf                    1.0.1-1
> font-bh-type1                  1.0.1-1
> font-bitstream-dpi75           1.0.1-1
> font-bitstream-speedo          1.0.1-1
> font-bitstream-type1           1.0.1-1
> font-bitstream-vera-ttf        1.10-1
> font-cursor-misc               1.0.1-1
> font-encodings                 1.0.3-1
> font-misc-misc                 1.1.0-1
> font-util                      1.1.1-1
> font-xfree86-type1             1.0.2-1
> fontconfig                     2.7.3-1
> fontsproto                     2.1.0-1
> fonttosfnt                     1.0.4-1
> gamin                          0.1.10-10
> gawk                           3.1.7-1
> gcc-core                       3.4.4-999
> gcc-g++                        3.4.4-999
> gcc-mingw-core                 20050522-1
> gcc-mingw-g++                  20050522-1
> gcc4                           4.3.4-1
> gcc4-core                      4.3.4-1
> gcc4-g++                       4.3.4-1
> gcc4-runtime                   4.3.2-1
> gdb                            6.8-2
> gettext                        0.17-11
> gettext-devel                  0.17-11
> ghostscript                    8.63-2
> ghostscript-fonts-other        6.0-1
> ghostscript-fonts-std          8.11-1
> giflib                         4.1.6-10
> glproto                        1.4.10-1
> gnome-icon-theme               2.26.0-1
> gnupg                          1.4.9-2
> grep                           2.5.3-1
> groff                          1.19.2-2
> gsl                            1.13-2
> gsl-devel                      1.13-2
> gsl-doc                        1.13-2
> gtk2.0-engines                 2.18.4-1
> gv                             3.6.5-1
> gzip                           1.3.12-2
> hicolor-icon-theme             0.11-1
> icu                            3.8-5
> imake                          1.0.2-2
> inetutils                      1.5-6
> inputproto                     2.0-1
> ipc-utils                      1.0-1
> jbigkit                        2.0-10
> kbproto                        1.0.4-1
> less                           429-1
> lesstif                        0.95.2-1
> lftp                           3.7.15-1
> libapr1                        1.3.8-2
> libaprutil1                    1.3.9-2
> libaspell15                    0.60.5-1
> libatk1.0-devel                1.26.0-1
> libatk1.0_0                    1.26.0-1
> libboost                       1.33.1-4
> libbz2-devel                   1.0.5-10
> libbz2_1                       1.0.5-10
> libcairo-devel                 1.8.8-1
> libcairo2                      1.8.8-1
> libcharset1                    1.13-10
> libcurl4                       7.19.6-1
> libdb4.2                       4.2.52.5-2
> libdb4.5                       4.5.20.2-2
> libdb4.5-devel                 4.5.20.2-2
> libexpat0                      1.95.8-2
> libexpat1                      2.0.1-1
> libexpat1-devel                2.0.1-1
> libfam0                        0.1.10-10
> libfcgi-devel                  2.4.0-2
> libfcgi0                       2.4.0-2
> libffi4                        4.3.4-1
> libfftw3-devel                 3.2.2-1
> libfftw3_3                     3.2.2-1
> libfontconfig-devel            2.7.3-1
> libfontconfig1                 2.7.3-1
> libfontenc-devel               1.0.5-1
> libfontenc1                    1.0.5-1
> libfreetype-devel              2.3.11-1
> libfreetype6                   2.3.11-1
> libgcc1                        4.3.4-1
> libgdbm-devel                  1.8.3-20
> libgdbm4                       1.8.3-20
> libgdk_pixbuf2.0-devel         2.16.6-1
> libgdk_pixbuf2.0_0             2.16.6-1
> libgettextpo0                  0.17-11
> libgfortran3                   4.3.4-1
> libgif-devel                   4.1.6-10
> libgif4                        4.1.6-10
> libGL-devel                    7.5.2-1
> libGL1                         7.5.2-1
> libglib1.2-devel               1.2.10-10
> libglib1.2_0                   1.2.10-10
> libglib2.0-devel               2.20.5-1
> libglib2.0_0                   2.20.5-1
> libglitz-devel                 0.5.6-10
> libglitz1                      0.5.6-10
> libGLU-devel                   7.5.2-1
> libGLU1                        7.5.2-1
> libgmp3                        4.3.1-3
> libgomp1                       4.3.4-1
> libgs-devel                    8.63-2
> libgs8                         8.63-2
> libgtk1.2-devel                1.2.10-10
> libgtk1.2_0                    1.2.10-10
> libgtk2.0-devel                2.16.6-1
> libgtk2.0_0                    2.16.6-1
> libICE-devel                   1.0.6-1
> libICE6                        1.0.6-1
> libiconv                       1.13-10
> libiconv2                      1.13-10
> libicu38                       3.8-5
> libidn11                       1.15-10
> libintl1                       0.10.40-1
> libintl2                       0.12.1-3
> libintl3                       0.14.5-1
> libintl8                       0.17-11
> libjasper-devel                1.900.1-1
> libjasper1                     1.900.1-1
> libjbig-devel                  2.0-10
> libjbig1                       1.5-3
> libjbig2                       2.0-10
> libjpeg-devel                  7-10
> libjpeg62                      6b-21
> libjpeg6b                      6b-8
> libjpeg7                       7-10
> liblapack-devel                3.2.1-1
> liblapack0                     3.2.1-1
> libltdl7                       2.2.7a-14
> liblzma1                       4.999.9beta-10
> liblzmadec-devel               4.32.7-10
> liblzmadec0                    4.32.7-10
> libmpfr1                       2.4.1-4
> libncurses-devel               5.7-15
> libncurses7                    5.3-4
> libncurses8                    5.5-10
> libncurses9                    5.7-15
> libneon27                      0.29.0-1
> libnetpbm10                    10.47.2-1
> libopenldap2_3_0               2.3.43-1
> libpango1.0-devel              1.24.5-1
> libpango1.0_0                  1.24.5-1
> libpcre-devel                  7.9-1
> libpcre0                       7.9-1
> libpixman1-devel               0.16.2-1
> libpixman1_0                   0.16.2-1
> libpng12                       1.2.35-10
> libpng12-devel                 1.2.35-10
> libpopt0                       1.6.4-4
> libpq-devel                    8.2.11-1
> libpq5                         8.2.11-1
> libpthread-stubs               0.2-1
> libreadline6                   5.2.14-12
> libreadline7                   6.0.3-2
> libsasl2                       2.1.19-3
> libserf0_0                     0.3.0-2
> libsigsegv                     2.6+-1
> libsigsegv0                    2.6-1
> libsigsegv1                    2.6+-1
> libSM-devel                    1.1.1-1
> libSM6                         1.1.1-1
> libsqlite3_0                   3.6.2-1
> libssh2_1                      1.2.1-1
> libssp0                        4.3.4-1
> libstdc++6                     4.3.4-1
> libstdc++6-devel               4.3.4-1
> libtiff-devel                  3.8.2-11
> libtiff3                       3.6.0-2
> libtiff4                       3.6.0-5
> libtiff5                       3.8.2-11
> libtool                        2.2.7a-14
> libungif-devel                 4.1.4-2
> libungif4                      4.1.4-2
> libusb-win32                   0.1.12.2-1
> libwrap0                       7.6-20
> libX11-devel                   1.3.2-1
> libX11-xcb1                    1.3.2-1
> libX11_6                       1.3.2-1
> libXau-devel                   1.0.5-1
> libXau6                        1.0.5-1
> libXaw-devel                   1.0.7-1
> libXaw3d-devel                 1.5D-8
> libXaw3d7                      1.5D-8
> libXaw6                        1.0.7-1
> libXaw7                        1.0.7-1
> libxcb-devel                   1.4-2
> libxcb-render-devel            1.4-2
> libxcb-render-util-devel       0.3.6-1
> libxcb-render-util0            0.3.6-1
> libxcb-render0                 1.4-2
> libxcb-xlib-devel              1.1-3
> libxcb-xlib0                   1.1-3
> libxcb1                        1.4-2
> libXcomposite-devel            0.4.1-1
> libXcomposite1                 0.4.1-1
> libXcursor-devel               1.1.10-1
> libXcursor1                    1.1.10-1
> libXdamage-devel               1.1.2-1
> libXdamage1                    1.1.2-1
> libXdmcp-devel                 1.0.3-1
> libXdmcp6                      1.0.3-1
> libXext-devel                  1.1.1-1
> libXext6                       1.1.1-1
> libXfixes-devel                4.0.4-1
> libXfixes3                     4.0.4-1
> libXft-devel                   2.1.14-1
> libXft2                        2.1.14-1
> libXi-devel                    1.3-1
> libXi6                         1.3-1
> libXinerama-devel              1.1-1
> libXinerama1                   1.1-1
> libxkbfile1                    1.0.6-1
> libXm-devel                    0.95.2-1
> libXm2                         0.95.2-1
> libxml2                        2.7.4-1
> libxml2-devel                  2.7.4-1
> libXmu-devel                   1.0.5-1
> libXmu6                        1.0.5-1
> libXmuu1                       1.0.5-1
> libXpm-devel                   3.5.8-1
> libXpm4                        3.5.8-1
> libXrandr-devel                1.3.0-10
> libXrandr2                     1.3.0-10
> libXrender-devel               0.9.5-1
> libXrender1                    0.9.5-1
> libXt-devel                    1.0.7-1
> libXt6                         1.0.7-1
> lndir                          1.0.1-2
> login                          1.10-10
> lua                            5.1.4-11
> luit                           1.0.4-2
> m4                             1.4.13-2
> make                           3.81-2
> makedepend                     1.0.2-1
> man                            1.6e-1
> mingw-runtime                  3.16-1
> minires                        1.02-1
> mintty                         0.5.2-1
> mkfontdir                      1.0.5-1
> mkfontscale                    1.0.7-1
> ncurses                        5.7-15
> netpbm                         10.47.2-1
> opengl                         1.1.0-10
> openssh                        5.2p1-4
> openssl                        0.9.8k-2
> openssl-devel                  0.9.8k-2
> patch                          2.5.8-9
> pcre                           7.9-1
> perl                           5.10.0-5
> perl-Tk                        804.028-1
> ping                           1.0-1
> pkg-config                     0.23b-10
> printproto                     1.0.4-1
> python                         2.5.2-1
> randrproto                     1.3.1-1
> rcs                            5.7-4
> readline                       6.0.3-2
> rebase                         3.0.1-1
> renderproto                    0.11-1
> rgb                            1.0.3-1
> rsync                          3.0.6-1
> ruby                           1.8.7-p72-2
> run                            1.1.12-10
> run2                           0.3.0-1
> rxvt                           20050409-21
> sed                            4.1.5-2
> shared-mime-info               0.70-1
> subversion                     1.6.6-2
> sunrpc                         4.0-3
> t1lib5                         5.1.2-10
> tar                            1.22-1
> tcltk                          20080420-1
> termcap                        20050421-1
> terminfo                       5.7_20090228-10
> terminfo0                      5.5_20061104-10
> texinfo                        4.13-3
> tic0                           5.5-10
> time                           1.7-2
> transfig                       3.2.5-1
> tzcode                         2009k-1
> unison2.27                     2.27.157-1
> unzip                          6.0-10
> util-linux                     2.14.1-1
> w32api                         3.13-1
> wget                           1.11.4-4
> which                          2.20-2
> wtf                            0.0.4-7
> xauth                          1.0.4-1
> xcursor-themes                 1.0.2-1
> xemacs-emacs-common            21.4.22-1
> xextproto                      7.1.1-1
> xfig                           3.2.4-7
> xfig-lib                       3.2.4-7
> xineramaproto                  1.2-1
> xinit                          1.1.1-6
> xkbcomp                        1.1.1-1
> xkeyboard-config               1.7-1
> xlsfonts                       1.0.2-1
> xmodmap                        1.0.4-1
> xorg-cf-files                  1.0.3-1
> xorg-server                    1.7.1-1
> xorg-util-macros               1.3.0-1
> xpdf                           3.02-1
> xproto                         7.0.16-1
> xrdb                           1.0.6-1
> xterm                          250-1
> xtrans                         1.2.5-1
> xz                             4.999.9beta-10
> zip                            3.0-11
> zlib                           1.2.3-10
> zlib-devel                     1.2.3-10
> zlib0                          1.2.3-10
> Use -h to see help about each section
>
> Welcome to the XWin X Server
> Vendor: The Cygwin/X Project
> Release: 1.7.1.0 (10701000)
> Build Date: 2009-10-25
>
> Contact: cygwin-***@cygwin.com
>
> XWin was started with the following command line:
>
> XWin -multiwindow -clipboard -silent-dup-error -emulate3buttons
>
> ddxProcessArgument - Initializing default screens
> winInitializeDefaultScreens - w 1280 h 1024
> winInitializeDefaultScreens - Returning
> 2009-11-03 08:50:44 winValidateArgs - g_iNumScreens: 1
> iMaxConsecutiveScreen: 1
> 2009-11-03 08:50:44 (II) xorg.conf is not supported
> 2009-11-03 08:50:44 (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html
> for more information
> 2009-11-03 08:50:44 winPrefsLoadPreferences: /home/kbrown/.XWinrc
> 2009-11-03 08:50:44 LoadPreferences: Done parsing the configuration file...
> 2009-11-03 08:50:44 winGetDisplay: DISPLAY=:0.0
> 2009-11-03 08:50:44 winDetectSupportedEngines - Windows NT/2000/XP
> 2009-11-03 08:50:44 winDetectSupportedEngines - DirectDraw installed
> 2009-11-03 08:50:44 winDetectSupportedEngines - DirectDraw4 installed
> 2009-11-03 08:50:44 winDetectSupportedEngines - Returning, supported engines
> 00000007
> 2009-11-03 08:50:44 winSetEngine - Multi Window or Rootless => ShadowGDI
> 2009-11-03 08:50:44 winAdjustVideoModeShadowGDI - Using Windows display
> depth of 32 bits per pixel
> 2009-11-03 08:50:44 winAllocateFBShadowGDI - Creating DIB with width: 1280
> height: 1024 depth: 32
> 2009-11-03 08:50:44 winFinishScreenInitFB - Masks: 00ff0000 0000ff00
> 000000ff
> 2009-11-03 08:50:44 winInitVisualsShadowGDI - Masks 00ff0000 0000ff00
> 000000ff BPRGB 8 d 24 bpp 32
> 2009-11-03 08:50:44 null screen fn ReparentWindow
> 2009-11-03 08:50:44 null screen fn RestackWindow
> 2009-11-03 08:50:44 InitQueue - Calling pthread_mutex_init
> 2009-11-03 08:50:44 InitQueue - pthread_mutex_init returned
> 2009-11-03 08:50:44 InitQueue - Calling pthread_cond_init
> 2009-11-03 08:50:44 InitQueue - pthread_cond_init returned
> 2009-11-03 08:50:44 winInitMultiWindowWM - Hello
> 2009-11-03 08:50:44 winInitMultiWindowWM - Calling pthread_mutex_lock ()
> 2009-11-03 08:50:44 Screen 0 added at XINERAMA coordinate (0,0).
> 2009-11-03 08:50:44 winMultiWindowXMsgProc - Hello
> 2009-11-03 08:50:44 winMultiWindowXMsgProc - Calling pthread_mutex_lock ()
> 2009-11-03 08:50:44 (II) AIGLX: Loaded and initialized
> /usr/lib/dri/swrast_dri.so
> 2009-11-03 08:50:44 (II) GLX: Initialized DRISWRAST GL provider for screen 0
> 2009-11-03 08:50:44 [dix] Could not init font path element
> /usr/share/fonts/OTF/, removing from list!
> 2009-11-03 08:50:47 winPointerWarpCursor - Discarding first warp: 640 512
> 2009-11-03 08:50:47 (--) 5 mouse buttons found
> 2009-11-03 08:50:47 (--) Setting autorepeat to delay=500, rate=31
> 2009-11-03 08:50:47 (--) winConfigKeyboard - Layout: "00000409" (00000409)
> 2009-11-03 08:50:47 (--) Using preset keyboard for "English (USA)" (409),
> type "4"
> 2009-11-03 08:50:47 Rules = "base" Model = "pc105" Layout = "us" Variant =
> "none" Options = "none"
> 2009-11-03 08:50:47 winInitMultiWindowWM - pthread_mutex_lock () returned.
> 2009-11-03 08:50:47 winInitMultiWindowWM - pthread_mutex_unlock () returned.
> 2009-11-03 08:50:47 winGetDisplay: DISPLAY=:0.0
> 2009-11-03 08:50:47 winInitMultiWindowWM - DISPLAY=:0.0
> 2009-11-03 08:50:47 winMultiWindowXMsgProc - pthread_mutex_lock () returned.
> 2009-11-03 08:50:47 winMultiWindowXMsgProc - pthread_mutex_unlock ()
> returned.
> 2009-11-03 08:50:48 winProcEstablishConnection - Hello
> 2009-11-03 08:50:48 winInitClipboard ()
> 2009-11-03 08:50:48 winClipboardProc - Hello
> 2009-11-03 08:50:48 DetectUnicodeSupport - Windows NT/2000/XP
> 2009-11-03 08:50:48 winProcEstablishConnection - winInitClipboard returned.
> 2009-11-03 08:50:48 winGetDisplay: DISPLAY=:0.0
> 2009-11-03 08:50:48 winMultiWindowXMsgProc - DISPLAY=:0.0
> 2009-11-03 08:50:48 winGetDisplay: DISPLAY=:0.0
> 2009-11-03 08:50:48 winClipboardProc - DISPLAY=:0.0
> 2009-11-03 08:50:48 winInitMultiWindowWM - XOpenDisplay () returned and
> successfully opened the display.
> 2009-11-03 08:50:48 winMultiWindowXMsgProc - XOpenDisplay () returned and
> successfully opened the display.
> 2009-11-03 08:50:48 winClipboardProc - XOpenDisplay () returned and
> successfully opened the display.
>
>
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Problem reports:       http://cygwin.com/problems.html
> Documentation:         http://x.cygwin.com/docs/
> FAQ:                   http://x.cygwin.com/docs/faq/
>

--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
Linda Walsh
2009-11-03 19:12:36 UTC
Permalink
Florent Fievez wrote:
> I've exactly the same issue, so if you find a solution, please post it ! ;-)
> 2009/11/3 Ken Brown <***@cornell.edu> wrote::
>> "'run xterm' fails to pen a window":
>> I don't know if this is a problem with run, or xterm, or
>> something else.
>> ...
>> Obviously I have no good reason to want to start an xterm via 'run xterm' in
>> an xterm window, but this issue is causing problems in a script I'm writing.
>> [Briefly, I have a desktop shortcut with target '\path\to\run.exe bash -c
>> foo.sh'. The script foo.sh calls xterm, which starts with no visible
>> window, exactly as above.]
---

I have two responses, 1, mostly to Florent Fieves, the other to both
Florent, and Ken Brown who wrote that he also has the problem

1) to Florent Fievee, (you don't need to answer if you have no good
reason, but if you do, I'm curious as to your reasoning) --

Why did you copy Ken's complete note as into your response, when you
simply has to say "me too"?


2) to both Florent and Ken?

In addition to Gery Herbozo Jimenez's response and question to you,
( "Have you tried just starting the XWin server first and the the
xterm? it looks like the X server doesn't recognize that line
command." ),

a) Have you tried starting 'xterm' without 'run' ?

b) I see you have started 'Xwin'. Do either of you know what display
'XWin' started itself on?

If you specified no value, it probably created the display ":0.0".

If you then open a 'client' program that needs to attach to your
Xwin display, "you" need to ensure that the new client knows what
"X display" your client connects to (usually, ":0.0"). A well
behaved X client won't make assumptions about what display to use.

If you were running entirely under *nix, any X clients you opened
afterwards would use the the display passed in the Environment via
'DISPLAY'. However, both of you appear to be starting Xwin with
no preset value of 'DISPLAY' AND passing >>NO<< (of
DISPLAY) to the 'X client' program, 'xterm', in order to tell it
what 'X display' to use.


You both appear to be doing the same thing. You both start an Xserver
in background (which is normal and what I do as well). You then appear
to be starting a client ('xterm'), in a separate "session" (an empty
Xsession, with no display). In order for an X client to display to
an Xserver, it needs to know what display to open it's output window
on.

Suggestions:
1) Don't use the cygwin command 'run.exe' unless you are
calling Windows programs.

2) Explicitly tell xterm what display to use. Set the value of
the environment var 'DISPLAY' before you all xterm.

Ex. Using the Windows 'Run' command (from the start menu, using the
builtin Windows 'Run' option on the start menu):

<Your cygwin path>\bin\bash.exe -c 'DISPLAY=:0 xterm'

for cygwin path='C:\cygwin':

C:\cygwin\bin\bash.exe -c 'DISPLAY=:0 xterm'
or
C:\cygwin\bash\bash.exe -c 'xterm -display :0'

for cygwin path= 'C:\': (my value)

C:\bin\bash.exe -c 'DISPLAY=:0 xterm'

or

C:\bash\bash.exe -c 'xterm -display :0'


The above two commands work on WinXP and Vista under the 1.5.x series
of Cygwin.

Linda


--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
Florent Fievez
2009-11-04 08:54:48 UTC
Permalink
Hi,

2009/11/3 Linda Walsh <***@tlinx.org>:
> 1) to Florent Fievee, (you don't need to answer if you have no good
>  reason, but if you do, I'm curious as to your reasoning) --   Why did you
> copy Ken's complete note as into your response, when you
>  simply has to say "me too"?

I simply clicked on "reply" button of my webmail. I will not do it again ;-)

> 2) to both Florent and Ken?
>
>  In addition to Gery Herbozo Jimenez's response and question to you,
>  ( "Have you tried just starting the XWin server first and the the
>  xterm? it looks like the X server doesn't recognize that line
>  command." ),
>  a) Have you tried starting 'xterm' without 'run' ?

Yes, it works without problem but a cmd window remain and that is
annoying. To explain exactly my situation, I have a Windows cmd script
which try to launch a bash script.

------- rxvtwin.cmd ------
@echo on

SET DISPLAY=127.0.0.1:0.0

if defined CYGWIN_ROOT goto :OK
set CYGWIN_ROOT=%~dp0
:OK

SET RUN=%CYGWIN_ROOT%\bin\run -p /usr/bin

SET PATH=%CYGWIN_ROOT%\bin;%PATH%


%RUN% %CYGWIN_ROOT%\bin\bash /usr/local/bin/rxvtwin.sh %*
-------------------------------

I call it in windows shortcut with a "***@host" as parameter and it
launch a rxvt terminal with a ssh session to the host and background
color depending on host.
If instead of "%RUN% %CYGWIN_ROOT%\bin\bash /usr/local/bin/rxvtwin.sh
%*" I launch "%CYGWIN_ROOT%\bin\bash /usr/local/bin/rxvtwin.sh %*", it
works.
So it seems to be really run which has an issue.



>  b) I see you have started 'Xwin'.  Do either of you know what display
>     'XWin' started itself on?         If you specified no value, it probably
> created the display ":0.0".

Yes my server is running on display 0.0 and I specify it in DISPLAY
environment variable.
 (I specified it in both bash and cmd script since I don't know if
environment is inherited by bash process when I run it)


>   <Your cygwin path>\bin\bash.exe -c 'DISPLAY=:0 xterm'
>
>   for cygwin path='C:\cygwin':
>
>      C:\cygwin\bin\bash.exe -c 'DISPLAY=:0 xterm'
>        or
>      C:\cygwin\bash\bash.exe -c 'xterm -display :0'
>   for cygwin path= 'C:\':     (my value)
>
>      C:\bin\bash.exe -c 'DISPLAY=:0 xterm'
>                or
>
>     C:\bash\bash.exe -c 'xterm -display :0'
>
> The above two commands work on WinXP and Vista under the 1.5.x series
> of Cygwin.

It don't work as I expected since what I have explained before.
But I have a little track : My office has given me a new computer and
with the old I had no problem with the same scripts, the difference
between the two is that the old one was Windows XP 32bits and the new
one is Windows XP 64 bits.
I tried first with cygwin 1.5 and I installed also cygwin 1.7 (I have
the same problem in both installation).


Best Regards,

Florent Fievez

--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
Linda Walsh
2009-11-04 20:14:38 UTC
Permalink
Florent Fievez wrote:
> 2009/11/3 Linda Walsh <me'***@me'dom>:
^^^^^^^^^^^^^^^ -- another no no**(see bottom)
>> [curious] Why did you copy [the previous,] complete note
>> into your response, when [all you said was] "me too"?
>
> I simply clicked on "reply" button of my webmail. I will not do it
> again ;-)
---

The point was not whether you hit reply, but whether or not you chose to
edit down the part you included to some minimal subset of the message so as
not to fill the rest of anyone's screen with unnecessary characters.

Some people (call them group A) use text-only readers that display the
whole message from top to bottom that scrolls your response off the screen
if you fill your message with a copy of a long included response. As a
result, they have to redisplay your message with paging enabled, just to see
a 1-liner that is placed at the top of the message (call that Style-A).

Other people (call them group B) using Graphical-readers(GUI's) to read
email only see the first page of a long email, so when someone includes the
whole message and puts a 1-liner at the end (call that style B), have to
manually scroll through a bunch of text they've already read in previous
posts, just to see a one liner.

Note: Style-A is sometimes called 'top-posting', and Style-B is sometimes
called 'bottom-posting'.

When someone is using a GUI, and reads a 'Style-B' message, they have to
slowly scroll through your message, either using the mouse or using some
page-down type character. That can be a tedious and error-prone process

In both cases it requires more work to read your message which was simply
a "me too" message that didn't require inclusion of the entire previous
message. So some people get 'irritated' at having to scroll up or page
through repeated text just to get to a "me too" response.

This is even more of a problem for people who have disabilities -- blind
people might have problems reading through tons of repeated text just to get
to important stuff, so its important for you to pare down the extraneous
parts to make it easier in any event. People with motion disabilities
(including people with RSI type problem (Carpal tunnel, Ulnar 'tunnel', or
spinal problems) may have problems with the extra motions required to read
your text.

So, in generally, it's just a good idea to trim down included text to
some minimal context that is needed to make your message "make sense" --
which is, nearly always, something that is both, considerably less than the
full message, but will also fit on 1 screen, with your message, of those in
group-A and in group-B -- thus making both happy, though, I believe
"Style-A" (AKA top-posing), as you did, would best serve those using
screen-readers -- which work with GUI's but not usually text-style windows.

Note -- you didn't do anything *wrong* -- I'm just letting you know the
problems that other people have raised about posting styles in the past, so
you can be aware, and be conscious about your posting style. We certainly
don't want any *unconscious postings*! :-) (been there, done that, got no
T-shirt -- just negative karma points).

Hopefully I won't get flamed for this, but I'm cross-posting this to the
cygwin main list, as well, where this issue comes up on some periodic basis,
with the hope that my suggestions will be considered: "Style-A" (AKA
top-posting) is easier on people with disabilities, but excessively quoting
old text such that the "new content" is scrolled off a screen is also
annoying and wasteful. For those in Group-B, if they are trying to be
thorough and make sure you had no further comments interspersed with the
content below, they'll still be forced to page through pages of repeated
text).

I'll respond to the rest of your note separately on the appropriate list.

Linda

** -- it's also considered a no-no, to include people's actual email
address when responding: use their name instead or at least heavily
obfuscate their email addr, since these emails are archived on publicly
searchable websites and spammers skim these archives to look for email
addresses to send spam to. I can vouch for getting a considerable amount
of spam sent my list-dedicated email accounts.


--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
Linda Walsh
2009-11-05 02:57:08 UTC
Permalink
Florent Fievez wrote:
>> 2) to both Florent and Ken?
>>
>> In addition to Gery Herbozo Jimenez's response and question to you,
>> ( "Have you tried just starting the XWin server first and the the
>> xterm? it looks like the X server doesn't recognize that line
>> command." ),
>> a) Have you tried starting 'xterm' without 'run' ?
>
> Yes, it works without problem but a cmd window remain and that is
> annoying.
---
Maybe you can close the cmd window after it starts...

Yeah, still a pain...

> To explain exactly my situation, I have a Windows cmd script
> which try to launch a bash script.
---
I'm not a windows.cmd language expert, but....

> SET DISPLAY=127.0.0.1:0.0
---
I don't know if it would make a difference, but I use
DISPLAY=":0" (I only have 1 display, so the extra ".0" should
be superfluous). But also ":0" should connect via a local socket
instead of using IP. Do you have any firewall products that could
be blocking traffic to or from 127.0.0.x?


> if defined CYGWIN_ROOT goto :OK
> set CYGWIN_ROOT=%~dp0
----
Not sure what ~dp0 is supposed to do. ??


> :OK
>
> SET RUN=%CYGWIN_ROOT%\bin\run -p /usr/bin
>
> SET PATH=%CYGWIN_ROOT%\bin;%PATH%
>
>
> %RUN% %CYGWIN_ROOT%\bin\bash /usr/local/bin/rxvtwin.sh %*
---

Is is possible to change that last line to:
%RUN% %CYGWIN_ROOT%\bin\bash -c "DISPLAY=:0 /usr/local/bin/rxvtwin.sh %* "
---that's all 1 line---

What does rxvtwin have in it?

Any reason not just to run it?

It looks like you are running the X server and the rxvt on the same
machine. You might want to look at 'minTTY'. It's a replacement
for the cmd.exe standard window that you can resize and set transparency
on -- i.e. it has more options, I think than rxvt.

It might be more what you want?

run %
> -------------------------------
>
> I call it in windows shortcut with a "***@host" as parameter and it
> launch a rxvt terminal with a ssh session to the host and background
> color depending on host.
> If instead of "%RUN% %CYGWIN_ROOT%\bin\bash /usr/local/bin/rxvtwin.sh
> %*" I launch "%CYGWIN_ROOT%\bin\bash /usr/local/bin/rxvtwin.sh %*", it
> works.
> So it seems to be really run which has an issue.
---
If it works locally but not under 'run', maybe you might try reporting
it on the main list -- as it doesn't seem to be strictly an X problem,
but some there might go "eewww, X" ... that belongs in cygwin-x! But
a bug in run is a bug in run... I have a feeling that
your DISPLAY variable isn't getting passed properly to your shellscript.

Another possibility -- get a non-X version of rvxt. I don't know if there is one in the main package base or not...I connected up to a french site with binaries other than the standard ones -- I might have pulled it down there -- has a neat 'server-client' version of rxvt as well --
launch 1 serer, an then each client takes about 200K/client.


>> Do either of you know what display 'XWin' started itself on?

> Yes my server is running on display 0.0 and I specify it in DISPLAY
> environment variable.
> (I specified it in both bash and cmd script since I don't know if
> environment is inherited by bash process when I run it)
----
does your logfile in /var/log/Xwin...(something) also confirm
that it opened the 0.0 display?

I'm not sure your rvxt script is getting DISPLAY -- maybe you
could echo DISPLAY out to a file? i.e. inside rxvt.sh -- put in an
"echo $DISPLAY>/tmp/my_rxvt.out" (or some place where you can store it
temporarily)...see if it stores the value you think it is storing.

Maybe try putting DISPLAY=":0" in the script?



>> for cygwin path='C:\cygwin':
>> C:\cygwin\bin\bash.exe -c 'DISPLAY=:0 xterm'
>> or C:\cygwin\bash\bash.exe -c 'xterm -display :0'
>> for cygwin path= 'C:\': (my value)
>> C:\bin\bash.exe -c 'DISPLAY=:0 xterm'
>> or C:\bash\bash.exe -c 'xterm -display :0'
>
>> The above two commands work on WinXP and Vista using cygwin1.5

>
> It don't work as I expected since what I have explained before.
---
I thought you said it DID work? Oh...the above also
is assuming your PATH variable has already included /usr/bin under
your cygwin dir.


Hopefully, something will help...:-)



--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
Florent Fievez
2009-11-05 08:47:04 UTC
Permalink
Hello,

First thanks for taking time to answer me, it now works but I don't
understand very well why ...
However that's not a problem, it's just my mind which like to know ...

2009/11/5 Linda Walsh <***@tlinx.org>:
>>
>> Yes, it works without problem but a cmd window remain and that is
>> annoying.
>
> ---
>        Maybe you can close the cmd window after it starts...
>
>        Yeah, still a pain...

No it kills subprocesses, so if I close that window, rxvt will close.


>        I'm not a windows.cmd language expert, but....
>
>> SET DISPLAY=127.0.0.1:0.0
>
> ---
>        I don't know if it would make a difference, but I use
> DISPLAY=":0"  (I only have 1 display, so the extra ".0" should
> be superfluous).  But also ":0" should connect via a local socket
> instead of using IP.  Do you have any firewall products that could
> be blocking traffic to or from 127.0.0.x?

For the firewall, it's completely disabled on my computer and I can
export display from other host to my computer without any problems.
With DISPLAY=:0 (in both bash and cmd script, *it works*), so thank
you but I'm not understanding the source of my problem.


>
>
>> if defined CYGWIN_ROOT goto :OK
>> set CYGWIN_ROOT=%~dp0
>
> ----
>        Not sure what ~dp0 is supposed to do.  ??
>

~dp0 return the path of current script, it's like you do a :
myDir=`dirname $0`
pushd $myDir
CYGWIN_ROOT=`pwd`
popd


Best regards,

--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
Florent Fievez
2009-11-05 09:45:13 UTC
Permalink
2009/11/5 Florent Fievez <***@fievel.be>:
> Hello,
>
> First thanks for taking time to answer me, it now works but I don't
> understand very well why ...
> However that's not a problem, it's just my mind which like to know ...

Ok, well I understand. When I run with "DISPLAY=:0", it doesn't
recognize my X server and start rxvt locally. If I kill the X server,
it also work ...
But It's not a problem since I can do what I want in this mode.

Best regards,

--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
jean-luc malet
2009-11-05 14:17:30 UTC
Permalink
Hi!
I have the same kind of issue but with gvim....
however it does work with xterm....

xterm.bat :
c:\cygwin\bin\run -p /usr/X11R6/bin xterm

gvim.bat :
c:\cygwin\bin\run -p /bin gvim

1rst is working... second is launching gvim (ps -a show the process)
but gvim don't open the window....

in all case DISPLAY is correctly set, launching c:\cygwin\bin\gvim in
a cmd.com is working fine, launching the .bat in the same cmd.com
don't print anything but process is started...

any idea?
thanks
JLM

On Thu, Nov 5, 2009 at 10:45 AM, Florent Fievez <***@fievel.be> wrote:
> 2009/11/5 Florent Fievez <***@fievel.be>:
>> Hello,
>>
>> First thanks for taking time to answer me, it now works but I don't
>> understand very well why ...
>> However that's not a problem, it's just my mind which like to know ...
>
> Ok, well I understand. When I run with "DISPLAY=:0", it doesn't
> recognize my X server and start rxvt locally. If I kill the X server,
> it also work ...
> But It's not a problem since I can do what I want in this mode.
>
> Best regards,
>
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Problem reports:       http://cygwin.com/problems.html
> Documentation:         http://x.cygwin.com/docs/
> FAQ:                   http://x.cygwin.com/docs/faq/
>
>



--
KISS! (Keep It Simple, Stupid!)
(garde le simple, imbécile!)
"mais qu'est-ce que tu m'as pondu comme usine à gaz? fait des choses
simples et qui marchent, espèce d'imbécile!"
-----------------------------
"Si vous pensez que vous êtes trop petit pour changer quoique ce soit,
essayez donc de dormir avec un moustique dans votre chambre." Betty
Reese
http://www.grainesdechangement.com/citations.htm

--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
Linda Walsh
2009-11-05 20:06:10 UTC
Permalink
This post might be inappropriate. Click to display it.
jean-luc malet
2009-11-06 17:46:52 UTC
Permalink
thanks for the reply,
for some reason I would like to continue using the cygwin one...
this .bat was working some time ago, until I update cygwin....

1) when I launch cygwin's gvim from a dos cmd shell it run as expected
2) when I launch "c:\Cygwin\bin\run gvim" in the same dos cmd shell it
spawn a process gvim (ps -a show it) attached to con but nothing is
displayed on screen

-> this isn't a pb of DISPLAY else 1) wouldn't have worked and
cygwin's gvim wouldn't have displayed

thanks and regards
JLM

On Thu, Nov 5, 2009 at 9:06 PM, Linda Walsh <***@tlinx.org> wrote:
> I would suggest you run the native version of 'gvim' instead
> of the cygwin 'gvim' unless you know you need something that
> the 'X' version provides.
>
> You can download the native gvim from the vim website.
>
> The native version can use the SAME config files as the cygwin
> version (i.e. it works equally well with LF line endings as
> it does CRLF line endings).
>
> It handles "/" or "\" as path separators.  I believe.
>
> BUT, one caveat, I have my Cygwin installed in C:\ not
> C:\cygwin, and my drive prefix is "/" not 'cygdrive/'  This
> means all my dos paths and cygwin paths are *equal*. So
> from any directory, if I type in 'vi xxx', I get the cygwin
> based 'vi' editor, but if I want a gui, I can type in 'gvim xxx'
> and I will get the native-windows based gui.
>
> Just make sure you add /prog/vim/ to your path (or wherever you
> install vim programs).  It's faster and doesn't need a running
> xserver.
> I do use the X-version of gvim, but only when editing a file
> on a remote machine.
>
> That said, the process of getting the 'X' version of gvim
> is straightforward.
>
> Start from debugging the launching of it in 'cmd.exe' -- that's like calling
> it from 'run'. which is similar to how
> explorer will run it.
>
> Also, if you use ":0" for your output, be sure to
> put it in quotes.  DISPLAY=:0 isn't safe unless it
> is quotes : DISPLAY=":0"   DISPLAY=":0" will go through
> a unix socket to talk to your Xserver.  In 'xhost', it shows
> up as "LOCAL:", whereas internet addresses show up as
> INET:localhost"  (entry for localhost:0).
>
>
>
> jean-luc malet wrote:
>>
>> Hi!
>> I have the same kind of issue but with gvim....
>> however it does work with xterm....
>
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Problem reports:       http://cygwin.com/problems.html
> Documentation:         http://x.cygwin.com/docs/
> FAQ:                   http://x.cygwin.com/docs/faq/
>
>



--
KISS! (Keep It Simple, Stupid!)
(garde le simple, imbécile!)
"mais qu'est-ce que tu m'as pondu comme usine à gaz? fait des choses
simples et qui marchent, espèce d'imbécile!"
-----------------------------
"Si vous pensez que vous êtes trop petit pour changer quoique ce soit,
essayez donc de dormir avec un moustique dans votre chambre." Betty
Reese
http://www.grainesdechangement.com/citations.htm

--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
Linda Walsh
2009-11-10 06:03:30 UTC
Permalink
jean-luc malet wrote:
> thanks for the reply,
> for some reason I would like to continue using the cygwin one...
> this .bat was working some time ago, until I update cygwin....
>
> 1) when I launch cygwin's gvim from a dos cmd shell it run as expected
> 2) when I launch "c:\Cygwin\bin\run gvim" in the same dos cmd shell it
> spawn a process gvim (ps -a show it) attached to con but nothing is
> displayed on screen
>
> -> this isn't a pb of DISPLAY else 1) wouldn't have worked and
> cygwin's gvim wouldn't have displayed
----
That may not, exactly, be the case.

I was under the impression that starting something using the
'run' command is starting outside of your normal "Cygwin" session (and not
attached to a Shell window). Depending on how you set your DISPLAY variable,
this could easily mean that the 'gvim' you start via "run" doesn't have
DISPLAY set properly.

I.e. if you set DISPLAY in your cygwin environment via the
startup commands in BASH, OR if you start "X", which spawns an Xterm, that
already has DISPLAY, "preset" for you, (by "X", before it spawns Xterm), then
by using "run", you are starting 'gvim' outside of the "environment" where
you normally have DISPLAY set to a valid value.

The only way DISPLAY would be set correctly for gvim when run
using 'run', is if you be sure that it's set by the 'run' command,
OR if you have it set in your Windows System or User Environment variables
when you log on (settable in Computer Properties(shortcut=WIN-BREAK on keyboard),
then Advanced->Environment Variables. There you can set display for your
userid, or system wide under the User variables.

So do you know that DISPLAY is set correctly for gvim when invoked
by "run"?

A test you could do is « run bash.exe -c "printenv>/tmp/my_envvars.txt" »
That will dump out all the env vars you think you are setting to a file that you
can look at after running it -- then you can make sure DISPLAY is set the way
you want it.

BTW, regarding Vim versions:
I use the X-version of Gvim when i'm logged into my linux machines, but I
use the Win version locally on my desktop (or the 'cygwin-vim' version when I'm
working in a command window and just want to do quick edits). So I jump between
all three version somewhat interchangeably. The Win version has a nicety that
you can set the horizontal scaling of a font separately from the vertical scaling,
and use 'half' sizes like "Lucida_Console:h10.5" -- which is different than
Lucida_Console:10, or 11. But the X-version of Gvim has better Foreign character
display capabilities which can confused the Windows version. So depends on what I'm
editing I suppose, as well.

Hope the DISPLAY stuff helps.

-linda

--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
jean-luc malet
2009-11-16 16:04:32 UTC
Permalink
thanks for the reply
I tested doing
c:\Cygwin\bin\run.exe sh -c "env|grep DISP > /cygdrive/c/log"
I get the expected value : DISPLAY=:0.0
C:\cygwin\bin\run.exe -p /usr/bin sh -c "gvim > /cygdrive/c/log 2>&1"
do diplay waring in the log.... but does make the window appears
in fact it seems that because gvim do output some error string it is
stopped by run.exe....

so as said in next reply
C:\cygwin\bin\run.exe -p /usr/bin sh -c "gvim >/dev/null 2>&1" is a workaround

thanks
JLM





On Tue, Nov 10, 2009 at 7:03 AM, Linda Walsh <***@tlinx.org> wrote:
> jean-luc malet wrote:
>>
>> thanks for the reply,
>> for some reason I would like to continue using the cygwin one...
>> this .bat was working some time ago, until I update cygwin....
>>
>> 1) when I launch cygwin's gvim from a dos cmd shell it run as expected
>> 2) when I launch "c:\Cygwin\bin\run gvim" in the same dos cmd shell it
>> spawn a process gvim (ps -a show it) attached to con but nothing is
>> displayed on screen
>>
>> -> this isn't a pb of DISPLAY else 1) wouldn't have worked and
>> cygwin's gvim wouldn't have displayed
>
> ----
>        That may not, exactly, be the case.
>
>        I was under the impression that starting something using the
> 'run' command is starting outside of your normal "Cygwin" session (and not
> attached to a Shell window).  Depending on how you set your DISPLAY
> variable,
> this could easily mean that the 'gvim' you start via "run" doesn't have
> DISPLAY set properly.
>
>        I.e. if you set DISPLAY in your cygwin environment via the startup
> commands in BASH, OR if you start "X", which spawns an Xterm, that
> already has DISPLAY, "preset" for you, (by "X", before it spawns Xterm),
> then
> by using "run", you are starting 'gvim' outside of the "environment" where
> you normally have DISPLAY set to a valid value.
>
>        The only way DISPLAY would be set correctly for gvim when run
> using 'run', is if you be sure that it's set by the 'run' command, OR if you
> have it set in your Windows System or User Environment variables
> when you log on (settable in Computer Properties(shortcut=WIN-BREAK on
> keyboard),
> then Advanced->Environment Variables.  There you can set display for your
> userid, or system wide under the User variables.
>
>        So do you know that DISPLAY is set correctly for gvim when invoked
> by "run"?
>        A test you could do is « run bash.exe -c
> "printenv>/tmp/my_envvars.txt" »
> That will dump out all the env vars you think you are setting to a file that
> you
> can look at after running it -- then you can make sure DISPLAY is set the
> way
> you want it.
>
>        BTW, regarding Vim versions:
>        I use the X-version of Gvim when i'm logged into my linux machines,
> but I
> use the Win version locally on my desktop (or the 'cygwin-vim' version when
> I'm
> working in a command window and just want to do quick edits).  So I jump
> between
> all three version somewhat interchangeably.  The Win version has a nicety
> that
> you can set the horizontal scaling of a font separately from the vertical
> scaling,
> and use 'half' sizes like "Lucida_Console:h10.5" -- which is different than
> Lucida_Console:10, or 11.  But the X-version of Gvim has better Foreign
> character
> display capabilities which can confused the Windows version.  So depends on
> what I'm
> editing I suppose, as well.
>
>        Hope the DISPLAY stuff helps.
>
> -linda
>



--
KISS! (Keep It Simple, Stupid!)
(garde le simple, imbécile!)
"mais qu'est-ce que tu m'as pondu comme usine à gaz? fait des choses
simples et qui marchent, espèce d'imbécile!"
-----------------------------
"Si vous pensez que vous êtes trop petit pour changer quoique ce soit,
essayez donc de dormir avec un moustique dans votre chambre." Betty
Reese
http://www.grainesdechangement.com/citations.htm

--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
jean-luc malet
2009-11-16 17:03:25 UTC
Permalink
the workaround isn't sufficient....
installing the font don't help
setting the LANG=C don't help
but in gvim.bat
C:\cygwin\bin\run.exe -p /usr/bin sh -c "gvim '%*'>/dev/null 2>&1"
don't work all the time

1)if I run it in a cmd.com : gvim.bat c:\some\path\to.file it's working
2)if I do open with in explorer, this don't work, after investigation
it appears that %* in this case is replaced by "c:\some\path\to.file"
ie
C:\cygwin\bin\run.exe -p /usr/bin sh -c "gvim
'"c:\some\path\to.file"'>/dev/null 2>&1"
(note that there is double quote inside single quote) removing the
single quote cause the \ to be escaped and then gvim try to open
c:omeatho.file.....

please can someone give a fix to run.exe so that the process is run
with stdout and stderr redirected to /dev/null?
thanks
JLM


On Mon, Nov 16, 2009 at 5:04 PM, jean-luc malet <***@gmail.com> wrote:
> thanks for the reply
> I tested doing
> c:\Cygwin\bin\run.exe sh -c "env|grep DISP > /cygdrive/c/log"
> I get the expected value : DISPLAY=:0.0
> C:\cygwin\bin\run.exe -p /usr/bin sh -c "gvim > /cygdrive/c/log 2>&1"
> do diplay waring in the log.... but does make the window appears
> in fact  it seems that because gvim do output some error string it is
> stopped by run.exe....
>
> so as said in next reply
> C:\cygwin\bin\run.exe -p /usr/bin sh -c "gvim >/dev/null 2>&1" is a workaround
>
> thanks
> JLM
>
>
>
>
>
> On Tue, Nov 10, 2009 at 7:03 AM, Linda Walsh <***@tlinx.org> wrote:
>> jean-luc malet wrote:
>>>
>>> thanks for the reply,
>>> for some reason I would like to continue using the cygwin one...
>>> this .bat was working some time ago, until I update cygwin....
>>>
>>> 1) when I launch cygwin's gvim from a dos cmd shell it run as expected
>>> 2) when I launch "c:\Cygwin\bin\run gvim" in the same dos cmd shell it
>>> spawn a process gvim (ps -a show it) attached to con but nothing is
>>> displayed on screen
>>>
>>> -> this isn't a pb of DISPLAY else 1) wouldn't have worked and
>>> cygwin's gvim wouldn't have displayed
>>
>> ----
>>        That may not, exactly, be the case.
>>
>>        I was under the impression that starting something using the
>> 'run' command is starting outside of your normal "Cygwin" session (and not
>> attached to a Shell window).  Depending on how you set your DISPLAY
>> variable,
>> this could easily mean that the 'gvim' you start via "run" doesn't have
>> DISPLAY set properly.
>>
>>        I.e. if you set DISPLAY in your cygwin environment via the startup
>> commands in BASH, OR if you start "X", which spawns an Xterm, that
>> already has DISPLAY, "preset" for you, (by "X", before it spawns Xterm),
>> then
>> by using "run", you are starting 'gvim' outside of the "environment" where
>> you normally have DISPLAY set to a valid value.
>>
>>        The only way DISPLAY would be set correctly for gvim when run
>> using 'run', is if you be sure that it's set by the 'run' command, OR if you
>> have it set in your Windows System or User Environment variables
>> when you log on (settable in Computer Properties(shortcut=WIN-BREAK on
>> keyboard),
>> then Advanced->Environment Variables.  There you can set display for your
>> userid, or system wide under the User variables.
>>
>>        So do you know that DISPLAY is set correctly for gvim when invoked
>> by "run"?
>>        A test you could do is « run bash.exe -c
>> "printenv>/tmp/my_envvars.txt" »
>> That will dump out all the env vars you think you are setting to a file that
>> you
>> can look at after running it -- then you can make sure DISPLAY is set the
>> way
>> you want it.
>>
>>        BTW, regarding Vim versions:
>>        I use the X-version of Gvim when i'm logged into my linux machines,
>> but I
>> use the Win version locally on my desktop (or the 'cygwin-vim' version when
>> I'm
>> working in a command window and just want to do quick edits).  So I jump
>> between
>> all three version somewhat interchangeably.  The Win version has a nicety
>> that
>> you can set the horizontal scaling of a font separately from the vertical
>> scaling,
>> and use 'half' sizes like "Lucida_Console:h10.5" -- which is different than
>> Lucida_Console:10, or 11.  But the X-version of Gvim has better Foreign
>> character
>> display capabilities which can confused the Windows version.  So depends on
>> what I'm
>> editing I suppose, as well.
>>
>>        Hope the DISPLAY stuff helps.
>>
>> -linda
>>
>
>
>
> --
> KISS! (Keep It Simple, Stupid!)
> (garde le simple, imbécile!)
> "mais qu'est-ce que tu m'as pondu comme usine à gaz? fait des choses
> simples et qui marchent, espèce d'imbécile!"
> -----------------------------
> "Si vous pensez que vous êtes trop petit pour changer quoique ce soit,
> essayez donc de dormir avec un moustique dans votre chambre." Betty
> Reese
> http://www.grainesdechangement.com/citations.htm
>



--
KISS! (Keep It Simple, Stupid!)
(garde le simple, imbécile!)
"mais qu'est-ce que tu m'as pondu comme usine à gaz? fait des choses
simples et qui marchent, espèce d'imbécile!"
-----------------------------
"Si vous pensez que vous êtes trop petit pour changer quoique ce soit,
essayez donc de dormir avec un moustique dans votre chambre." Betty
Reese
http://www.grainesdechangement.com/citations.htm

--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
Mike Ayers
2009-11-06 18:40:00 UTC
Permalink
> From: cygwin-xfree-***@cygwin.com [mailto:cygwin-xfree-
> ***@cygwin.com] On Behalf Of jean-luc malet
> Sent: Thursday, November 05, 2009 6:18 AM

> gvim.bat :
> c:\cygwin\bin\run -p /bin gvim

Try:

c:\cygwin\bin\run -p /bin:/usr/X11R6/bin gvim


HT
jean-luc malet
2009-11-09 10:50:07 UTC
Permalink
no more result... gvim process is still started, appears in ps -a, but
nothing is displayed on screen, replacing gvim by xterm still work
with this solution...
thanks and regards
JLM

On Fri, Nov 6, 2009 at 7:40 PM, Mike Ayers <***@tvworks.com> wrote:
>> From: cygwin-xfree-***@cygwin.com [mailto:cygwin-xfree-
>> ***@cygwin.com] On Behalf Of jean-luc malet
>> Sent: Thursday, November 05, 2009 6:18 AM
>
>> gvim.bat :
>> c:\cygwin\bin\run -p /bin gvim
>
>        Try:
>
> c:\cygwin\bin\run -p /bin:/usr/X11R6/bin gvim
>
>
>        HTH,
>
> Mike
>
>



--
KISS! (Keep It Simple, Stupid!)
(garde le simple, imbécile!)
"mais qu'est-ce que tu m'as pondu comme usine à gaz? fait des choses
simples et qui marchent, espèce d'imbécile!"
-----------------------------
"Si vous pensez que vous êtes trop petit pour changer quoique ce soit,
essayez donc de dormir avec un moustique dans votre chambre." Betty
Reese
http://www.grainesdechangement.com/citations.htm

--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
Mike Ayers
2009-11-10 23:44:10 UTC
Permalink
> From: cygwin-xfree-***@cygwin.com [mailto:cygwin-xfree-
> ***@cygwin.com] On Behalf Of jean-luc malet
> Sent: Monday, November 09, 2009 2:50 AM

> no more result... gvim process is still started, appears in ps -a, but
> nothing is displayed on screen, replacing gvim by xterm still work
> with this solution...

To find out why this is, run gvim from an xterm:

[SNIP]
m-ayers-lap> gvim

(gvim:1748): Pango-WARNING **: Error loading GSUB table 0x6EAD

(gvim:1748): Pango-WARNING **: Error loading GPOS table 0x6EAD

(gvim:1748): Pango-WARNING **: Error loading GSUB table 0x6EAD

(gvim:1748): Pango-WARNING **: Error loading GPOS table 0x6EAD
m-ayers-lap>
(gvim:1092): Pango-WARNING **: Error loading GPOS table 0x6EAD
[/SNIP]

Apparently, run.exe is not providing stdout/stderr to dump to. The workaround:

[SNIP]
C:\mike>C:\cygwin\bin\run.exe -p /usr/bin sh -c "gvim >/dev/null 2>&1"
C:\mike>
[/SNIP]
Lothar Brendel
2009-11-11 00:52:04 UTC
Permalink
Mike Ayers wrote:

[...]

> Apparently, run.exe is not providing stdout/stderr to dump to.

Is that by chance due to the fact that run.exe is compiled with -mwindows,
i.e. as GUI?
And am I the only one for whom this has further consequences?

E.g. in a Windows command prompt or a non-X11 cygwin-console, the command
run sleep -wait 5
does *not* wait for the sleep to terminate. Moreover
run false -wait
does *not* set %errorlevel% to 1.

Ciao
Lothar


--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
Mike Ayers
2009-11-11 01:37:03 UTC
Permalink
> From: cygwin-xfree-***@cygwin.com [mailto:cygwin-xfree-
> ***@cygwin.com] On Behalf Of Lothar Brendel
> Sent: Tuesday, November 10, 2009 4:52 PM

> E.g. in a Windows command prompt or a non-X11 cygwin-console, the
> command
> run sleep -wait 5
> does *not* wait for the sleep to terminate. Moreover
> run false -wait
> does *not* set %errorlevel% to 1.

Why are you using run for these?

[SNIP]
C:\mike>C:\cygwin\bin\sh.exe -c false

C:\mike>echo %ERRORLEVEL%
1

C:\mike>
[/SNIP]

[SNIP]
C:\mike>C:\cygwin\bin\sh.exe -c "PATH=/usr/bin sleep 5"

C:\mike>
[/SNIP]

Sleep occurred.

On Windows there must be a console for programs that use console, which means a console window. To not have a console window, a program must be compiled as a GUI app, which means no console available. To get nifty cygwin features like windowless consoles, you must fully enter the cygwin environment. There is no
Lothar Brendel
2009-11-11 07:34:16 UTC
Permalink
Mike Ayers wrote:
>> From: cygwin-xfree-***@cygwin.com [mailto:cygwin-xfree-
>> ***@cygwin.com] On Behalf Of Lothar Brendel
>> Sent: Tuesday, November 10, 2009 4:52 PM
>
>> E.g. in a Windows command prompt or a non-X11 cygwin-console, the
>> command
>> run sleep -wait 5
>> does *not* wait for the sleep to terminate. Moreover
>> run false -wait
>> does *not* set %errorlevel% to 1.
>
> Why are you using run for these?

I normally don't. It was what I boiled down the non-functioning line
%RUN% checkX -wait -d %DISPLAY% -t 12
in startxwin.bat (from xinit-1.1.1-6.tar.bz2) to.

Like that, the "-wait" has no effect and a non-running X-server isn't
reflected in %errorlevel%, either.

And (of course) I can confirm the correct behaviour when using sh.exe
instead of run.exe. Which brings us to the question of using run.exe in
startxwin.bat. I don't see the point of hoping for a windowless console
there, since a BAT-script always opens a window anyway (even when starting
with "@echo off" and outputting nothing).

Hence, wouldn't be sh.exe instead of run.exe the right thing for
startxwin.bat?

Asks
Lothar


--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
Jon TURNEY
2009-11-12 20:17:07 UTC
Permalink
On 10/11/2009 23:44, Mike Ayers wrote:
>> On Behalf Of jean-luc malet
>> Sent: Monday, November 09, 2009 2:50 AM
>
>> no more result... gvim process is still started, appears in ps -a, but
>> nothing is displayed on screen, replacing gvim by xterm still work
>> with this solution...
>
> To find out why this is, run gvim from an xterm:
>
> [SNIP]
> m-ayers-lap> gvim
>
> (gvim:1748): Pango-WARNING **: Error loading GSUB table 0x6EAD
>
> (gvim:1748): Pango-WARNING **: Error loading GPOS table 0x6EAD
>
> (gvim:1748): Pango-WARNING **: Error loading GSUB table 0x6EAD
>
> (gvim:1748): Pango-WARNING **: Error loading GPOS table 0x6EAD
> m-ayers-lap>
> (gvim:1092): Pango-WARNING **: Error loading GPOS table 0x6EAD
> [/SNIP]
>
> Apparently, run.exe is not providing stdout/stderr to dump to. The workaround:
>
> [SNIP]
> C:\mike>C:\cygwin\bin\run.exe -p /usr/bin sh -c "gvim>/dev/null 2>&1"
> C:\mike>
> [/SNIP]

Wait, are you saying that the process that run starts is blocked if it tries
to output anything?

Also, the suggestions that this has something to do with DISPLAY not being set
correctly seem a little unlikely. If gvim or any other X application isn't
able to determine which display to use, it should exit with an error, not hang
around....


--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
Mike Ayers
2009-11-12 20:33:42 UTC
Permalink
> From: cygwin-xfree-***@cygwin.com [mailto:cygwin-xfree-
> ***@cygwin.com] On Behalf Of Jon TURNEY

> Wait, are you saying that the process that run starts is blocked if it
> tries
> to output anything?

That is what I am experiencing.

> Also, the suggestions that this has something to do with DISPLAY not
> being set
> correctly seem a little unlikely. If gvim or any other X application
> isn't
> able to determine which display to use, it should exit with an error,
> not hang
> around....

I agree. I think DISPLAY is a red herring. Not having the display set can cause programs which exit without output, not hang around.


HTH,

Mike
Ken Brown
2009-11-13 03:14:17 UTC
Permalink
On 11/12/2009 3:17 PM, Jon TURNEY wrote:
> On 10/11/2009 23:44, Mike Ayers wrote:
>>> On Behalf Of jean-luc malet
>>> Sent: Monday, November 09, 2009 2:50 AM
>>
>>> no more result... gvim process is still started, appears in ps -a, but
>>> nothing is displayed on screen, replacing gvim by xterm still work
>>> with this solution...
>>
>> To find out why this is, run gvim from an xterm:
>>
>> [SNIP]
>> m-ayers-lap> gvim
>>
>> (gvim:1748): Pango-WARNING **: Error loading GSUB table 0x6EAD
>>
>> (gvim:1748): Pango-WARNING **: Error loading GPOS table 0x6EAD
>>
>> (gvim:1748): Pango-WARNING **: Error loading GSUB table 0x6EAD
>>
>> (gvim:1748): Pango-WARNING **: Error loading GPOS table 0x6EAD
>> m-ayers-lap>
>> (gvim:1092): Pango-WARNING **: Error loading GPOS table 0x6EAD
>> [/SNIP]
>>
>> Apparently, run.exe is not providing stdout/stderr to dump to.
>> The workaround:
>>
>> [SNIP]
>> C:\mike>C:\cygwin\bin\run.exe -p /usr/bin sh -c "gvim>/dev/null 2>&1"
>> C:\mike>
>> [/SNIP]
>
> Wait, are you saying that the process that run starts is blocked if it
> tries to output anything?

Ah, so this explains my xterm problem that started this thread. When I
start xterm from a shell, I always get the message

Warning: Missing charsets in String to FontSet conversion

When I start xterm via run, this message apparently has nowhere to go
and the xterm process is blocked. Mike's workaround (with 'gvim'
replaced by 'xterm') solves the problem, as he said. Is this a bug in run?

It would also be nice to get rid of that xterm warning. Setting LANG=C
gets rid of it, so it seems to be another locale issue.

Ken

--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
Ken Brown
2009-11-13 14:59:59 UTC
Permalink
On 11/12/2009 10:14 PM, Ken Brown wrote:
> Ah, so this explains my xterm problem that started this thread. When I
> start xterm from a shell, I always get the message
>
> Warning: Missing charsets in String to FontSet conversion
>
[...]
> It would also be nice to get rid of that xterm warning. Setting LANG=C
> gets rid of it, so it seems to be another locale issue.

Never mind. I found the answer in a different thread:

http://cygwin.com/ml/cygwin-xfree/2009-11/msg00085.html

The workaround is to install the font-isas-misc, font-jis-misc, and
font-daewoo-misc packages.

Ken

--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
Jon TURNEY
2009-11-20 15:25:21 UTC
Permalink
On 13/11/2009 03:14, Ken Brown wrote:
> On 11/12/2009 3:17 PM, Jon TURNEY wrote:
>> On 10/11/2009 23:44, Mike Ayers wrote:]
>>>
>>> Apparently, run.exe is not providing stdout/stderr to dump to. The
>>> workaround:
>>>
>>> [SNIP]
>>> C:\mike>C:\cygwin\bin\run.exe -p /usr/bin sh -c "gvim>/dev/null 2>&1"
>>> C:\mike>
>>> [/SNIP]
>>
>> Wait, are you saying that the process that run starts is blocked if it
>> tries to output anything?
>
> Ah, so this explains my xterm problem that started this thread. When I
> start xterm from a shell, I always get the message
>
> Warning: Missing charsets in String to FontSet conversion
>
> When I start xterm via run, this message apparently has nowhere to go
> and the xterm process is blocked. Mike's workaround (with 'gvim'
> replaced by 'xterm') solves the problem, as he said. Is this a bug in run?

It does kind of look like some problem with run, but not a universal one, 'run
xterm' has been working as expected for me, even when it has to output something.

Experimenting a bit, this seems to be related to having CYWIN=tty set in the
windows environment. If I remove that, I can reproduce the problem you see.

I really don't understand the invisible console stuff well enough to attempt a
fix, though...

--
Jon TURNEY
Volunteer Cygwin/X X Server maintainer

--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
jean-luc malet
2009-11-27 15:22:54 UTC
Permalink
On Fri, Nov 20, 2009 at 4:25 PM, Jon TURNEY <***@dronecode.org.uk> wrote:
> On 13/11/2009 03:14, Ken Brown wrote:
>>
>> On 11/12/2009 3:17 PM, Jon TURNEY wrote:
>>>
>>> On 10/11/2009 23:44, Mike Ayers wrote:]
>>>>
>>>> Apparently, run.exe is not providing stdout/stderr to dump to. The
>>>> workaround:
>>>>
>>>> [SNIP]
>>>> C:\mike>C:\cygwin\bin\run.exe -p /usr/bin sh -c "gvim>/dev/null 2>&1"
>>>> C:\mike>
>>>> [/SNIP]
>>>
>>> Wait, are you saying that the process that run starts is blocked if it
>>> tries to output anything?
>>
>> Ah, so this explains my xterm problem that started this thread. When I
>> start xterm from a shell, I always get the message
>>
>> Warning: Missing charsets in String to FontSet conversion
>>
>> When I start xterm via run, this message apparently has nowhere to go
>> and the xterm process is blocked. Mike's workaround (with 'gvim'
>> replaced by 'xterm') solves the problem, as he said. Is this a bug in run?
>
> It does kind of look like some problem with run, but not a universal one,
> 'run xterm' has been working as expected for me, even when it has to output
> something.
>
> Experimenting a bit, this seems to be related to having CYWIN=tty set in the
> windows environment.  If I remove that, I can reproduce the problem you see.
>
> I really don't understand the invisible console stuff well enough to attempt
> a fix, though...
>


Ok thanks, yes CYGWIN=tty does fix the issue!
many many thanks!
JLM



--
KISS! (Keep It Simple, Stupid!)
(garde le simple, imbécile!)
"mais qu'est-ce que tu m'as pondu comme usine à gaz? fait des choses
simples et qui marchent, espèce d'imbécile!"
-----------------------------
"Si vous pensez que vous êtes trop petit pour changer quoique ce soit,
essayez donc de dormir avec un moustique dans votre chambre." Betty
Reese
http://www.grainesdechangement.com/citations.htm

--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
Gery Herbozo Jimenez
2009-11-03 19:33:01 UTC
Permalink
<***@tlinx.org>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0



Hi Linda=2C
=20
Thanks for your answer and explanation. I just press the Xserver icon and t=
hen the xterm (most of the time) appears. If not=2C I press the xterm icon.=
Simple like that. I don't write "run" or something like that in anycase.
=20
Hope this helps=2C
=20
Cheers=2C=20
Gery

=20
> Date: Tue=2C 3 Nov 2009 11:12:36 -0800
> From: ***@tlinx.org
> To: ***@fievel.be
> CC: cygwin-***@cygwin.com=3B ***@hotmail.com
> Subject: Re: 'run xterm' fails to open a window
>=20
> Florent Fievez wrote:
>> I've exactly the same issue=2C so if you find a solution=2C please post =
it ! =3B-)=20
>> 2009/11/3 Ken Brown <***@cornell.edu> wrote::
>>> "'run xterm' fails to pen a window":
>>> I don't know if this is a problem with run=2C or xterm=2C or=20
>>> something else.=20
>>> ...
>>> Obviously I have no good reason to want to start an xterm via 'run xter=
m' in
>>> an xterm window=2C but this issue is causing problems in a script I'm w=
riting.
>>> [Briefly=2C I have a desktop shortcut with target '\path\to\run.exe bas=
h -c
>>> foo.sh'. The script foo.sh calls xterm=2C which starts with no visible
>>> window=2C exactly as above.]
> ---
>=20
> I have two responses=2C 1=2C mostly to Florent Fieves=2C the other to bot=
h
> Florent=2C and Ken Brown who wrote that he also has the problem=20
>=20
> 1) to Florent Fievee=2C (you don't need to answer if you have no good
> reason=2C but if you do=2C I'm curious as to your reasoning) --=20
>=20
> Why did you copy Ken's complete note as into your response=2C when you
> simply has to say "me too"?
>=20
>=20
> 2) to both Florent and Ken?
>=20
> In addition to Gery Herbozo Jimenez's response and question to you=2C
> ( "Have you tried just starting the XWin server first and the the
> xterm? it looks like the X server doesn't recognize that line
> command." )=2C=20
>=20
> a) Have you tried starting 'xterm' without 'run' ?=20
>=20
> b) I see you have started 'Xwin'. Do either of you know what display
> 'XWin' started itself on?=20
>=20
> If you specified no value=2C it probably created the display ":0.0".
>=20
> If you then open a 'client' program that needs to attach to your
> Xwin display=2C "you" need to ensure that the new client knows what
> "X display" your client connects to (usually=2C ":0.0"). A well
> behaved X client won't make assumptions about what display to use.
>=20
> If you were running entirely under *nix=2C any X clients you opened
> afterwards would use the the display passed in the Environment via
> 'DISPLAY'. However=2C both of you appear to be starting Xwin with
> no preset value of 'DISPLAY' AND passing>>NO<< (of=20
> DISPLAY) to the 'X client' program=2C 'xterm'=2C in order to tell it
> what 'X display' to use.
>=20
>=20
> You both appear to be doing the same thing. You both start an Xserver
> in background (which is normal and what I do as well). You then appear
> to be starting a client ('xterm')=2C in a separate "session" (an empty
> Xsession=2C with no display). In order for an X client to display to=20
> an Xserver=2C it needs to know what display to open it's output window
> on.
>=20
> Suggestions:=20
> 1) Don't use the cygwin command 'run.exe' unless you are
> calling Windows programs.=20
>=20
> 2) Explicitly tell xterm what display to use. Set the value of
> the environment var 'DISPLAY' before you all xterm.
>=20
> Ex. Using the Windows 'Run' command (from the start menu=2C using the
> builtin Windows 'Run' option on the start menu):
>=20
> <Your cygwin path>\bin\bash.exe -c 'DISPLAY=3D:0 xterm'
>=20
> for cygwin path=3D'C:\cygwin':
>=20
> C:\cygwin\bin\bash.exe -c 'DISPLAY=3D:0 xterm'
> or
> C:\cygwin\bash\bash.exe -c 'xterm -display :0'=20
>=20
> for cygwin path=3D 'C:\': (my value)
>=20
> C:\bin\bash.exe -c 'DISPLAY=3D:0 xterm'
>=20
> or
>=20
> C:\bash\bash.exe -c 'xterm -display :0'=20
>=20
>=20
> The above two commands work on WinXP and Vista under the 1.5.x series
> of Cygwin.=20
>=20
> Linda
> =20
_________________________________________________________________
Deja que Sietes te ense=F1e todo los secretos de Windows
http://www.sietesunpueblodeexpertos.com/=

--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
Linda Walsh
2009-11-03 23:45:51 UTC
Permalink
Gery Herbozo Jimenez wrote:
> Thanks for your answer and explanation. I just press the Xserver icon and
> t hen the xterm (most of the time) appears. If not, I press the xterm
> icon. Simple like that. I don't write "run" or something like that in
> anycase.
---
Oddly enough, I find the menu items less reliable (by grouping):

Under cygwin:
- MinTTY, rxvt-unicode-xS, rxvt-unicode-xC: work
- rxvt-x, rxvt-native (*pseudo* work: come up w/poopy doublewide-font)

Under cygwin/cygwin-X
- oclock works, but not xclock.
- rxvt works (perversely, w/double-wide chars)
- none of the rest work

Under cygwin/cygwin-X/Toys:
- glxgears, xeyes, xlogo, ico --- all work
- xgc doesn't work from menu (but does from Bash).

Under cygwin/cygwin-x/tools:
- only xev and xrefresh work
- idle gives a path-not-found message (may not be installed)
- the rest give no output, but start a process (that sits in
background until I kill it).

Under cygwin-xgames, texteroids brings up a window, then immediately
exits. From bash, I see the error message:

| %% DPS Client Library Warning:
| Auto-launching DPS NX agent.
| %% DPS Client Library Warning:
| FAILED to auto-launch:
| dpsnx.agent
|
| texteroids: DPS is not available.
| You need an X server with the DPS extension, or a DPS NX agent.

> Hope this helps.

In some way. It lets me know that my reasoning for doing
workarounds, that I implemented years ago, were done for good
reason. The default menu items don't work reliably in some
environments (like mine).

It is interesting to check out things I didn't even know I had
installed! :-)

I don't regard any of the above that don't work as 'bugs', as I
don't know what some of them are *supposed* to do, and it could easily be
I have something interfering in my path. I'd have to go through each menu
item in its properties and figure out why they didn't work before I'd call
them a bug -- some may be left over menu items that didn't get deleted
"properly' when an app was moved or uninstalled.

I see at least a few, in my setup, that still reference
/usr/X11R6/bin for executables, when their executable is now under
/usr/bin (though some executables are under my /usr/X11R6/bin -- maybe
alien binaries; again, I'd only report something as a bug if I was
pretty sure it wasn't unique to my setup; I do too many non-standard
things; :-) ).

I don't know how the shortcut got left around, so I certainly
wouldn't report it as "bug" or problem to the cygwin list.


Another potential source of problem I found today, while playing
around.

I had the setting of LANG set to incorrect value 'en_US.utf8', but it
should be 'en_US.utf-8' for some applications that 'care'. :-)

Same could could for CTYPE or some of the LC prefixed vars -- if they are
set incorrectly it might prevent one of the X utils opening properly when
called by run.

To set those values, you need to alter them in 'System properties',
Advanced -> "Environment Variables". I have LANG in my "System variables"
section, but DISPLAY, I made a 'User' variable. I see LANG being SYSTEM
wide. I see DISPLAY as only being valid with my login as it's only
when I login that the Xserver is started (I autostart it via a shortcut
in my Programs->Startup Menu group).

Linda Yakinalotski
:-)




--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
Continue reading on narkive:
Loading...