This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
RE: startxwin.bat fails
- Subject: RE: startxwin.bat fails
- From: Suhaib Siddiqi <ssiddiqi at inspirepharm dot com>
- Date: Fri, 25 May 2001 15:11:34 -0400
- Cc: "'cygx'" <cygwin-xfree at cygwin dot com>
One of the use emailed me private a Thank note. I do not remember who was he
He changed Windows display to 16 bit and started
Xwin with 16 bps. It wroks for him.
Suhaib
> -----Original Message-----
> From: Harold Hunt [mailto:huntharo@msu.edu]
> Sent: Friday, May 25, 2001 2:53 PM
> To: Pierre A. Humblet; Richard_Larrabee@amsinc.com
> Cc: cygx
> Subject: RE: startxwin.bat fails
>
>
> > Wouldn't it be more practical to have xwin output
> > an information message when the display depth cannot
> > be handled, rather than having to answer incessantly
> > the same question?
>
> I had thought about the same thing, just haven't had time to
> get to it yet.
> :)
>
> I was going to write such a patch a couple days ago but then
> the FAQ stuff took center stage.
>
> However, I see something interesting about this user's error message:
> > > winInitVisualsShadowDD () - Masks: 00000000 00000000
> 00000000 bpRGB:
> > > 0
>
> Normally I know that a user is running Windows at 8 bits per
> pixel because the bpRGB field gets set to 8 when we query
> DirectDraw for the current display mode. However, this
> user's bpRGB is 0, which I haven't seen before. Perhaps there
> is something else going on with this particular user's problem...
>
> Harold
>