Color problems XDCMP to 16 and 24bit (probably endianness)

Harold Hunt huntharo@msu.edu
Thu Apr 12 08:27:00 GMT 2001


Oh, great to hear it :)

Harold

> -----Original Message-----
> From: verhaegs@imec.be [ mailto:verhaegs@imec.be]On Behalf Of Staf
> Verhaegen
> Sent: Thursday, April 12, 2001 10:53 AM
> To: Harold Hunt
> Subject: Re: Color problems XDCMP to 16 and 24bit (probably 
> endianness)
> 
> 
> Staf Verhaegen wrote:
> > 
> > This craches for me, probably due to my old NT version ?
> > I've tried with -engine 1, -engine 2, -engine 4.
> > All crash with exception STATUS_ACCESS_VIOLATION. The last 
> line before
> > handle_exceptions displayed is:
> > InitInput()
> > When doing with -fullscreen. The same error as above with -engine 1.
> > With -engine 2 and -engine 4 I get 
> STATUS_INTEGER_DIVIDE_BY_ZERO with the last
> > line displayed before that:
> > winInitVisualsShadowDD() - Returning
> > 
> > Is this caused by my old DirectX version ?
> > Why did it work with the XWin.exe (fullscreen only) version 
> on the ftp server
> > ?
> 
> Please ignore. I tried it with 8bit but 16bit works, like you 
> mentioned on the
> page.
> 24bit crashes, 32bit works.
> Also excuse me for sending this to you.
> Otherwise good work !
> 
> greets,
> Staf.
> 
> +----------------------------------------+--------------------
> ---------+
> |Staf Verhaegen (staf.verhaegen@imec.be) |ADRESS: IMEC vzw. - 
> ASP/LITHO|
> |tel: 016/ 281 783                       |        Kapeldreef 
> 75        |
> |fax: 016/ 281 214                       |        3001 Leuven 
> (Belgium)|
> +----------------------------------------+--------------------
> ---------+
>  For every tool there are at least 2 uses: the one it was designed for
>                  and the other for which it wasn't.



More information about the Cygwin-xfree mailing list