This is the mail archive of the
cygwin-xfree
mailing list for the Cygwin XFree86 project.
RE: cygwin-x xterm not compatible with windows 7?
- From: "Mike Ayers" <mike_ayers at tvworks dot com>
- To: <cygwin-xfree at cygwin dot com>
- Date: Thu, 3 Dec 2009 14:22:23 -0800
- Subject: RE: cygwin-x xterm not compatible with windows 7?
- References: <4AEAEEAB.2030009@cornell.edu> <4B06CE7D.6060709@cwilson.fastmail.fm> <DC10C91353D145DE868EA645D34FACF9@MultiOcke> <4B0A8AC5.9080305@cwilson.fastmail.fm> <EABCFA5150B14960B856418FF34758D3@MultiOcke> <4B0B4728.40300@cwilson.fastmail.fm> <6BA35940945A4A9D87019C6253F94814@MultiOcke> <4B0D2EB3.6020102@cwilson.fastmail.fm> <DD64BEC938054D459976F9311F71E290@MultiOcke> <4B0E9679.5050108@cornell.edu> <270AA78168E41541833C52448F4F34AD1D16D2C4@VHAISHMSGJ2.vha.med.va.gov> <CBDD77CD57ED4827A8A30DFA1DFBC285@MultiOcke> <270AA78168E41541833C52448F4F34AD1D16D545@VHAISHMSGJ2.vha.med.va.gov> <3 4FC5A3DFA88402C87957FC903ED71A2@MultiOcke> <270AA78168E41541833C52448F4F34AD1D16D5E4@VHAISHMSGJ2.vha.med.va.gov > <64D542799A7246F4A7712FD0F65274D7@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B13A0@VHAISHMSGJ2.vha.med.va.gov> < 3A87660989894F8C82CE373AC8C8382F@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B1C41@VHAISHMSGJ2.vha.med.va.gov> <005001ca72b2$c4bebc60$4401a8c0@BANDIT> <016701ca746 2$1de95b50$4401a8c0@BANDIT>
- Reply-to: cygwin-xfree at cygwin dot com
> From: cygwin-xfree-owner@cygwin.com [mailto:cygwin-xfree-
> owner@cygwin.com] On Behalf Of wgweis@sbcglobal.net
> Sent: Thursday, December 03, 2009 1:47 PM
> I sent this post earlier this week and have not received any
> replies.
> If this is the wrong place to post this,
> please let me know where I should.
This is the right place, but it's possible none of us with time to spare has run on Windows 7 64 bit yet.
> I just bought a new PC with windows 7 64 bit, build number 7600,
> version 6.1.
> I downloaded a fresh install of cygwin and cannot get cygwin-x xterm
> running. Cygwin version is 1.7.0(0.218/5/3)
>
> I tried running the cygwin-x XWin Server shortcut command line from a
> cmd
> window to get the error output:
>
> C:\cygwin\bin\run.exe /usr/bin/startxwin.bat
>
> and see this:
>
> "/usr/bin/xterm Xt error: Can't open display: 127.0.0.1:0.0"
>
> this seems to be coming from this command in the batch file:
> :\Users\princess>C:\cygwin\bin\\..\bin\run -p /usr/bin xterm -e
> /usr/bin/bash -
>
> usr/bin/xterm Xt error: Can't open display: 127.0.0.1:0.0
...implying that the server didn't start. Did you run as administrator?
> I
> checked to see if there
> was more than one cygwin1.dll in response to earlier posts about this
> error
> and there is only one.
>
> I tried turning off the windows firewall. That helps in other ways,
> because
> other cygwin network
> utilities, such as nslookup were blocked until I did that.
>
> I tried changing the display from 127.0.0.1 to the IP address of the
> machine.
I believe the X server listens on 0.0.0.0, so that shouldn't make a difference.
> Basically, I have a fresh machine with windows 7 and a fresh install of
> cygwin and I can't get
> xterm to work. Anyone have any ideas? Or is this just a windows 7
> thing,
> and I'll have to give
> up on cygwin-x for a while?
>
> BTW, other shortcuts in the cygwin-x start folder work, such as bitmap
> and
> xcalc, just not the
> Xwin server and xterm.
How can xcalc work if the server doesn't start?!
Please send your /var/log/XWin0.log and cygcheck.out (cygcheck -s -v -r >cygcheck.out) as attachments in the hope that they will inspire.
Thanks,
Mike