Re: Problem on windows 2000 machine

["Robert Collins" <robert dot collins at itdomain dot com dot au>]

Windows 2000 no service pack. I've download sp1 and will try that tomorrow.

Rob


----- Original Message -----
From: "Suhaib Siddiqi" <ssiddiqi@inspirepharm.com>
To: "Robert Collins" <robert.collins@itdomain.com.au>;
<cygwin-xfree@sources.redhat.com>
Sent: Wednesday, September 13, 2000 9:31 PM
Subject: RE: Problem on windows 2000 machine


>
> Rob,
> Is this Windows2000 or NT 4.0?
>
> XF86 has some problems on Linux machines with i80 cards.
> I do not think we would have same issues on Windows,
> but you never know
>
> Suhaib
>
> > -----Original Message-----
> > From: cygwin-xfree-owner@sources.redhat.com
> > [mailto:cygwin-xfree-owner@sources.redhat.com]On Behalf Of Robert
> > Collins
> > Sent: Tuesday, September 12, 2000 10:42 PM
> > To: Suhaib Siddiqi; cygwin-xfree@sources.redhat.com
> > Subject: RE: Problem on windows 2000 machine
> >
> >
> > Well I got the current intel 810 drivers (v4.1) and installed them - but
> > it still doesn't work. The error looks the same to me - fatil IO error
> > 104. Interestingly the driver reports DirectX 5.00.2180.1 under the
> > version tab!? Anyway what should I tell intel to log a fault on this?
> >
> > Has anyone else got this working on an intel 810 based system?
> >
> > Rob
> >
> > > -----Original Message-----
> > > From: Suhaib Siddiqi [mailto:ssiddiqi@inspirepharm.com]
> > > Sent: Tuesday, 12 September 2000 9:41 PM
> > > To: cygwin-xfree@sources.redhat.com
> > > Subject: RE: Problem on windows 2000 machine
> > >
> > >
> > >
> > >
> > > > I took the step to day of loading X on my work machine. Cygwin is
> > > > already running happily, CVS w/SSH working properly etc etc.
> > > >
> > > > I get the following on the console after running startx (from within
> > > > bash)
> > > > ===
> > > > bash-2.04$ startx
> > > >
> > > > _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
> > > > pwin->width = 00000500
> > > > pwin->height = 00000400
> > > > pwin->paddedWidth = 00000a00
> > > > pwin->bitsPerPixel = 00000010
> > > > calling winAllocateFramebufferMemory
> > > > XIO:  fatal IO error 104 (Connection reset by peer) on X
> > > server ":0.0"
> > > >       after 0 requests (0 known processed) with 0 events remaining.
> > > > ====
> > > >
> > >
> > > That is because I1810 video cards drivers do not fully support
> > > DirectX.  Did you check Intel URL for an updated driver.
> > > Intel is usually VERY VERY lousey in providing PATCHES and
> > > new drivers.
> > > Their tech support is one of the LOUSIEST I have ever seen in
> > > the world.
> > > I had their C++/F compilers, reported bugs to them. It took
> > > them six month
> > > to confirm the bugs, and no fixes yet, almost 11 months are gone.
> > >
> > > Suhaib
> > >
> > >
> > > > There is an accompanying GUI error (error.png).
> > > >
> > > > The graphics card is a Intel810 w/4Mb memory. (Running at 1024/768
> > > > 16-bit.)
> > > > Windows 2000 pro.
> > > >
> > > > Sequence of events:
> > > > untarred into /
> > > > added /usr/X11R6 to my cgywin path.
> > > > started new bash
> > > > ran startx - got error couldn't find ./xinit
> > > > edit startx - changed last line from ./xinit .... to xinit ....
> > > >
> > > > Any suggestions?
> > > >
> > > > Rob
> > > >
> > >
>