RE: fatal IO error 104 on start

RE: fatal IO error 104 on start

[Greg Jewell]

Harold,

Your suggestions fixed the problem -- thank you very much!

Just a few notes:
The second umount command gave me a "File or directory not found" error.
I never installed the Cyrillic fonts, so I didn't "reinstall" that package.

Other than that, I did everything exactly as you asked.


Thanks again!

Greg Jewell


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


Follow these steps:

1) Open Cygwin bash shell.

2) In bash shell, run the following two commands:

umount /usr/X11R6/lib/X11/fonts
umount -u /usr/X11R6/lib/X11/fonts

3) Rerun Cygwin's setup.exe, select 'Reinstall' for any of the following 
packages that were already installed:

XFree86-f100
XFree86-fcyr
XFree86-fenc
XFree86-fnts
XFree86-fscl

4) Launch Cygwin/X again and test that the font problems have gone away.

5) Report your results here along with any deviations you had to make 
from these instructions.

Harold

Greg Jewell wrote:

> Thanks for the tip.  Looking at the log file, it appears that this is the pertinent error message:
> 
> Fatal server error:
> could not open default font 'fixed'
> winDeinitClipboard - Noting shutdown in progress
> winDeinitMultiWindowWM - Noting shutdown in progress
> 
> Any ideas?  I installed the default XFree86 packages.
> 
> 
> Greg
> 
> 
> 
> 
>>-----Original Message-----
>>From: Harold L Hunt II [mailto:huntharo@msu.edu]
>>Sent: Monday, January 05, 2004 13:58
>>To: cygwin-xfree@cygwin.com
>>Subject: Re: fatal IO error 104 on start
>>
>>
>>Greg,
>>
>>Look at /tmp/XWin.log.
>>
>>Harold
>>
>>Greg Jewell wrote:
>>
>>
>>>Hi All,
>>>
>>>I just installed cygwin on my work machine, but am unable to 
>>
>>start the X server.  Each time I try (using startx), I receive 
>>the following error:
>>
>>>XIO:  fatal IO error 104 (Connection reset by perr) on X 
>>
>>server ":0.0"
>>
>>>        after 0 requests (0 known processed) with 0 events remaining.
>>>
>>>I searched the archives and saw that others were having the 
>>
>>same problem at the end of November/beginning of December, but 
>>no solution was offered.
>>
>>>I downloaded the packages from a couple of different sources 
>>
>>this morning, but none of them produced different results.  
>>Other than the few times that I've installed the software this 
>>morning, cygwin had not been on this machine previously.  
>>(It's a new box.)
>>
>>>Does anybody know how to resolve this?
>>>
>>>
>>>Thanks,
>>>Greg Jewell
>>>
>>>
>>
> 

RE: fatal IO error 104 on start

[Greg Jewell]

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

Re: fatal IO error 104 on start

[Harold L Hunt II]

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

Re: fatal IO error 104 on start

[Jim Scheef]

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

--- Harold L Hunt II <huntharo@msu.edu> wrote:
> Follow these steps:
> 
> 1) Open Cygwin bash shell.
> 
> 2) In bash shell, run the following two commands:
> 
> umount /usr/X11R6/lib/X11/fonts
> umount -u /usr/X11R6/lib/X11/fonts
> 
> 3) Rerun Cygwin's setup.exe, select 'Reinstall' for any of the following 
> packages that were already installed:
> 
> XFree86-f100
> XFree86-fcyr
> XFree86-fenc
> XFree86-fnts
> XFree86-fscl
> 
> 4) Launch Cygwin/X again and test that the font problems have gone away.
> 
> 5) Report your results here along with any deviations you had to make 
> from these instructions.
> 
> Harold
> 
> Greg Jewell wrote:
> 
> > Thanks for the tip.  Looking at the log file, it appears that this is the
> pertinent error message:
> > 
> > Fatal server error:
> > could not open default font 'fixed'
> > winDeinitClipboard - Noting shutdown in progress
> > winDeinitMultiWindowWM - Noting shutdown in progress
> > 
> > Any ideas?  I installed the default XFree86 packages.
> > 
> > 
> > Greg
> > 
> > 
> > 
> > 
> >>-----Original Message-----
> >>From: Harold L Hunt II [mailto:huntharo@msu.edu]
> >>Sent: Monday, January 05, 2004 13:58
> >>To: cygwin-xfree@cygwin.com
> >>Subject: Re: fatal IO error 104 on start
> >>
> >>
> >>Greg,
> >>
> >>Look at /tmp/XWin.log.
> >>
> >>Harold
> >>
> >>Greg Jewell wrote:
> >>
> >>
> >>>Hi All,
> >>>
> >>>I just installed cygwin on my work machine, but am unable to 
> >>
> >>start the X server.  Each time I try (using startx), I receive 
> >>the following error:
> >>
> >>>XIO:  fatal IO error 104 (Connection reset by perr) on X 
> >>
> >>server ":0.0"
> >>
> >>>        after 0 requests (0 known processed) with 0 events remaining.
> >>>
> >>>I searched the archives and saw that others were having the 
> >>
> >>same problem at the end of November/beginning of December, but 
> >>no solution was offered.
> >>
> >>>I downloaded the packages from a couple of different sources 
> >>
> >>this morning, but none of them produced different results.  
> >>Other than the few times that I've installed the software this 
> >>morning, cygwin had not been on this machine previously.  
> >>(It's a new box.)
> >>
> >>>Does anybody know how to resolve this?
> >>>
> >>>
> >>>Thanks,
> >>>Greg Jewell
> >>>
> >>>
> >>
> > 


__________________________________
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus

Re: fatal IO error 104 on start

[Harold L Hunt II]

Follow these steps:

1) Open Cygwin bash shell.

2) In bash shell, run the following two commands:

umount /usr/X11R6/lib/X11/fonts
umount -u /usr/X11R6/lib/X11/fonts

3) Rerun Cygwin's setup.exe, select 'Reinstall' for any of the following 
packages that were already installed:

XFree86-f100
XFree86-fcyr
XFree86-fenc
XFree86-fnts
XFree86-fscl

4) Launch Cygwin/X again and test that the font problems have gone away.

5) Report your results here along with any deviations you had to make 
from these instructions.

Harold

Greg Jewell wrote:

> Thanks for the tip.  Looking at the log file, it appears that this is the pertinent error message:
> 
> Fatal server error:
> could not open default font 'fixed'
> winDeinitClipboard - Noting shutdown in progress
> winDeinitMultiWindowWM - Noting shutdown in progress
> 
> Any ideas?  I installed the default XFree86 packages.
> 
> 
> Greg
> 
> 
> 
> 
>>-----Original Message-----
>>From: Harold L Hunt II [mailto:huntharo@msu.edu]
>>Sent: Monday, January 05, 2004 13:58
>>To: cygwin-xfree@cygwin.com
>>Subject: Re: fatal IO error 104 on start
>>
>>
>>Greg,
>>
>>Look at /tmp/XWin.log.
>>
>>Harold
>>
>>Greg Jewell wrote:
>>
>>
>>>Hi All,
>>>
>>>I just installed cygwin on my work machine, but am unable to 
>>
>>start the X server.  Each time I try (using startx), I receive 
>>the following error:
>>
>>>XIO:  fatal IO error 104 (Connection reset by perr) on X 
>>
>>server ":0.0"
>>
>>>        after 0 requests (0 known processed) with 0 events remaining.
>>>
>>>I searched the archives and saw that others were having the 
>>
>>same problem at the end of November/beginning of December, but 
>>no solution was offered.
>>
>>>I downloaded the packages from a couple of different sources 
>>
>>this morning, but none of them produced different results.  
>>Other than the few times that I've installed the software this 
>>morning, cygwin had not been on this machine previously.  
>>(It's a new box.)
>>
>>>Does anybody know how to resolve this?
>>>
>>>
>>>Thanks,
>>>Greg Jewell
>>>
>>>
>>
> 

RE: fatal IO error 104 on start

[Greg Jewell]

Thanks for the tip.  Looking at the log file, it appears that this is the pertinent error message:

Fatal server error:
could not open default font 'fixed'
winDeinitClipboard - Noting shutdown in progress
winDeinitMultiWindowWM - Noting shutdown in progress

Any ideas?  I installed the default XFree86 packages.


Greg



>-----Original Message-----
>From: Harold L Hunt II [mailto:huntharo@msu.edu]
>Sent: Monday, January 05, 2004 13:58
>To: cygwin-xfree@cygwin.com
>Subject: Re: fatal IO error 104 on start
>
>
>Greg,
>
>Look at /tmp/XWin.log.
>
>Harold
>
>Greg Jewell wrote:
>
>> Hi All,
>> 
>> I just installed cygwin on my work machine, but am unable to 
>start the X server.  Each time I try (using startx), I receive 
>the following error:
>> 
>> XIO:  fatal IO error 104 (Connection reset by perr) on X 
>server ":0.0"
>>         after 0 requests (0 known processed) with 0 events remaining.
>> 
>> I searched the archives and saw that others were having the 
>same problem at the end of November/beginning of December, but 
>no solution was offered.
>> 
>> I downloaded the packages from a couple of different sources 
>this morning, but none of them produced different results.  
>Other than the few times that I've installed the software this 
>morning, cygwin had not been on this machine previously.  
>(It's a new box.)
>> 
>> Does anybody know how to resolve this?
>> 
>> 
>> Thanks,
>> Greg Jewell
>> 
>> 
>

Re: fatal IO error 104 on start

[Harold L Hunt II]

Greg,

Look at /tmp/XWin.log.

Harold

Greg Jewell wrote:

> Hi All,
> 
> I just installed cygwin on my work machine, but am unable to start the X server.  Each time I try (using startx), I receive the following error:
> 
> XIO:  fatal IO error 104 (Connection reset by perr) on X server ":0.0"
>         after 0 requests (0 known processed) with 0 events remaining.
> 
> I searched the archives and saw that others were having the same problem at the end of November/beginning of December, but no solution was offered.
> 
> I downloaded the packages from a couple of different sources this morning, but none of them produced different results.  Other than the few times that I've installed the software this morning, cygwin had not been on this machine previously.  (It's a new box.)
> 
> Does anybody know how to resolve this?
> 
> 
> Thanks,
> Greg Jewell
> 
> 

fatal IO error 104 on start

[Greg Jewell]

Hi All,

I just installed cygwin on my work machine, but am unable to start the X server.  Each time I try (using startx), I receive the following error:

XIO:  fatal IO error 104 (Connection reset by perr) on X server ":0.0"
        after 0 requests (0 known processed) with 0 events remaining.

I searched the archives and saw that others were having the same problem at the end of November/beginning of December, but no solution was offered.

I downloaded the packages from a couple of different sources this morning, but none of them produced different results.  Other than the few times that I've installed the software this morning, cygwin had not been on this machine previously.  (It's a new box.)

Does anybody know how to resolve this?


Thanks,
Greg Jewell