public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: "Greg Jewell" <gjewell@cnnxn.com>
To: <cygwin-xfree@cygwin.com>
Subject: RE: fatal IO error 104 on start
Date: Wed, 07 Jan 2004 02:21:00 -0000	[thread overview]
Message-ID: <741C3B0BAF7B1F4F8FCC50AC4766CBF0248AF5@phoenix.ossconnexn.com> (raw)

Hi again,

I just read this explanation you gave to Jim.  I'm sure that you are correct about this, but the machine that I just installed Cygwin on had no previous installation of it.  I did install to my D drive, but there should have been nothing in the registry at that point.


Greg


-----Original Message-----
From: Harold L Hunt II [mailto:huntharo@msu.edu]
Sent: Tuesday, January 06, 2004 6:28 PM
To: cygwin-xfree@cygwin.com
Subject: Re: fatal IO error 104 on start


Jim,

Jim Scheef wrote:
> Harold,
> 
> I had this same problem. Your suggestions resolved the font problem. The
> first umount returned no messages, the second gave a "file not found" error.
> Does this problem indicate trouble in the setup scripts? 
> 
> Best of all, I can type into xterm for the first time in months.
> 
> Is there someplace I can find more about the problems caused by installing
> Microsoft Services for UNIX along with Cygwin Xfree86?
> 
> Thanks,
> Jim
> MSU '68

Well, since you are an MSU grad, I will answer your questions :)  I'm 
about to be a two time grad in May.  Wish me luck...

There is not really a "problem" with the setup scripts, so much as there 
is a problem with installing Cygwin/X to a drive other than your C 
drive, removing that drive from the computer without uninstalling 
Cygwin/X, then trying to install Cygwin/X to your C drive.  In that case 
a mount is left in your registry that points to your D drive, setup.exe 
tries to unpack the files on the D drive, but fails because it cannot 
find that drive anymore.  We would need a "preinstall" script that iced 
the mounts, then recreated them... but setup.exe does not support such a 
script (I don't believe it does).  Keep in mind that this is just and 
example; there are a plethora of reasons that you might end up in a 
similar situation.

Yes, there is more info about Services for UNIX:

http://xfree86.cygwin.com/docs/faq/cygwin-xfree-faq.html#microsoft-services-for-unix

Have fun with Cygwin/X,

Harold


             reply	other threads:[~2004-01-07  2:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-07  2:21 Greg Jewell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-01-07  2:18 Greg Jewell
2004-01-06  0:24 Greg Jewell
2004-01-06  0:42 ` Harold L Hunt II
2004-01-06 22:39   ` Jim Scheef
2004-01-07  1:28     ` Harold L Hunt II
2004-01-05 20:52 Greg Jewell
2004-01-05 20:57 ` Harold L Hunt II

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=741C3B0BAF7B1F4F8FCC50AC4766CBF0248AF5@phoenix.ossconnexn.com \
    --to=gjewell@cnnxn.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).