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:[EMAIL PROTECTED] Sent: Tuesday, January 06, 2004 6:28 PM To: [EMAIL PROTECTED] 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
