public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Brian Ford <ford@vss.fsi.com>
To: cygwin-xfree@cygwin.com
Subject: Re: xfree and windows XP home version
Date: Fri, 30 Jan 2004 16:42:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.58.0401301023450.11773@eos> (raw)
In-Reply-To: <4019B89D.5030200@mchsi.com>
On Thu, 29 Jan 2004, Robert Tramel wrote:
> I down loaded the Cygwin/X package to a machine running windows XP home
> edition.
> Howver the X windows never fire up properly, i..e., they don't do
> anyting at all are freeze imediately depending on which startup option I
> try. Is this a limitation of XP home or am I missing something?
>
AFAIK, there are no known issues with XP home. As such, I suggest you do
the following three things so we can help you better.
1.) Please visit http://cygwin.com/problems.html and review the problem
reporting guide lines. Specifically, review the part about *attaching
uncompressed* cygcheck output. That will allow us to see all the relevent
versions of your software, and if they are properly installed.
2.) Please give more detail about exactly how you do both "start options".
Then, we have the information necessary to try and reproduce your problem,
or see if you are starting Xwin incorrectly.
3.) Please describe in more detail what "freeze imediately" and "don't do
anything at all" means ie. what did you expect to happen, and what did
happen.
Thanks.
--
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax: 314-551-8444
next prev parent reply other threads:[~2004-01-30 16:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-30 2:05 Robert Tramel
2004-01-30 16:42 ` Brian Ford [this message]
2004-01-31 23:47 Robert Tramel
2004-02-02 20:32 ` Brian Ford
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=Pine.GSO.4.58.0401301023450.11773@eos \
--to=ford@vss.fsi.com \
--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).