public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Linda Walsh <cygwin@tlinx.org>
To: cygwin-xfree@cygwin.com
Subject: Re: X on win 7
Date: Wed, 20 Jul 2011 05:16:00 -0000	[thread overview]
Message-ID: <4E266378.40301@tlinx.org> (raw)
In-Reply-To: <alpine.GSO.2.00.1107071023050.9606@mango.cc.columbia.edu>

Daniel Bienstock wrote:

> Hello,
> 
> I have a new Dell Dimension M6600 with Windows 7 SP 1.  I have disabled 
> the Windows firewall and added rules to allow programs in cygwin and 
> cygwin\bin to run.
> 
> I am using cygwin 1.7.9  (I also use older cygwins on many 32-bit 
> Windows machines).
> 
> On this machine, X runs badly: often very slowly, and frequently with 
> crashes as well.  A couple of times I was forced to reboot the machine 
> -- Windows appeared unresponsive.
> 
> I did try rebaseall, but did not help (in fact had to reinstall cygwin).
> 
> I have seen some posts on this topic, but no definitive workaround.

---
	This may be entire unhelpful, but is mentioned as a
datapoint only,
I have X on Win7 working with
cygwin 1.4.2-1
and
xorg-server 1.8.0-1
xorg-server-dmx 1.8.0-.1

(and lots of other packages from that era

I tried upgrading to latest, and nothing worked.
No bash, No X, -- rebase died didn't solve anything
..
I reverted as didn't have the time to track down all the
problems of such a large update.

I'd like to try updating packages 1-by-1, but that's not
easily supported through setup (it selects all, and there's
no way to unselect the 100+ updates except by repetitious mouse
clicks (keyboard accel's didn't function).

My wrists warned me to quit.

Dunno wazzup w/newer versions as I'm sure many use them
with no difficulties, BUT, the version I have now works
with what I currently have installed (BLODA, though I don't
think  I have anything that falls into that category, given it's
"precise definition", it's hard to tell from day-to-day).

So things keep changing in both Win7, and cygwin, (and my server,
that I upgraded to a changed samba(3.6) hasn't done me any
favors in tracking down all my little nuisances....

Note, it's generally the cyg-support way to blame things on the
user or tell them they can use the source and fix it themselves.

Tried that 3 times, insufficiently documented and/or included
too many assumptions about user's environment for me to replicate.
(Doesn't mean I won't try again some day, but fixing my samba server
handing out Domain GUID's is higher prio -- as is writing my script
to create auto-snap-shots of my home-dir on linux with LSM and rsynch
that are mounted w/samba so as to show up as "previous versions" of
changed files....

(and of course, those tasks are always getting interrupted as well...
nested so damn deep, I've my overflow counter has wrapped.


--
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/


      parent reply	other threads:[~2011-07-20  5:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-07 15:32 Daniel Bienstock
2011-07-07 16:10 ` Larry Hall (Cygwin-X)
2011-07-20  5:16 ` Linda Walsh [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E266378.40301@tlinx.org \
    --to=cygwin@tlinx.org \
    --cc=cygwin-xfree@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).