From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30253 invoked by alias); 7 Jan 2004 01:28:26 -0000 Mailing-List: contact cygwin-xfree-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-xfree-owner@cygwin.com Mail-Followup-To: cygwin-xfree@cygwin.com Reply-To: cygwin-xfree@cygwin.com Received: (qmail 30245 invoked from network); 7 Jan 2004 01:28:25 -0000 Received: from unknown (HELO sys22.mail.msu.edu) (35.9.75.122) by sources.redhat.com with SMTP; 7 Jan 2004 01:28:25 -0000 Received: from [207.179.68.222] (helo=msu.edu) by sys22.mail.msu.edu with asmtp (Exim 4.24 #37) (TLSv1:AES256-SHA:256) id 1Ae2Uj-0003g9-5v for cygwin-xfree@cygwin.com; Tue, 06 Jan 2004 20:28:25 -0500 Message-ID: <3FFB60BA.9010701@msu.edu> Date: Wed, 07 Jan 2004 01:28:00 -0000 From: Harold L Hunt II User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031208 MIME-Version: 1.0 To: cygwin-xfree@cygwin.com Subject: Re: fatal IO error 104 on start References: <20040106223947.29051.qmail@web41511.mail.yahoo.com> In-Reply-To: <20040106223947.29051.qmail@web41511.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus: None found by Clam AV X-SW-Source: 2004-01/txt/msg00122.txt.bz2 List-Id: 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