Path: utzoo!mnetor!uunet!husc6!cmcl2!beta!hc!ames!pasteur!zooey.Berkeley.EDU!c162-br
From: c162-br@zooey.Berkeley.EDU (Warner Young)
Newsgroups: comp.sys.atari.st
Subject: Re: Setcolor() crash
Message-ID: <2498@pasteur.Berkeley.Edu>
Date: 18 Apr 88 18:32:39 GMT
References: <11830005@hpldola.HP.COM>
Sender: news@pasteur.Berkeley.Edu
Reply-To: c162-br@zooey.Berkeley.EDU.UUCP (Warner Young)
Organization: University of California, Berkeley
Lines: 23
Keywords: setcolor crash bug
Summary: really stupendous crash!


	One time as I was writing a program, I happened to have a bit of
code that was something like:
	i = ~Setcolor(0, -1);
	Setcolor(0, i);

The astute readers will have already noticed that I forgot to mask 'i'
with 0x777 first.  Well, I found out what happens if you try to do
a Setcolor() with a value over 0x777.  The ST crashes, gives you a blank
screen with bombs all the way across, and reset only gives you the same
screen.

	Now, I'm wondering why this is.  It seems to me that it wouldn't
have been very hard to add a little bit of checking in the Xbios routine
to set colors.  And even if no checking is done, why would the ST crash
so badly?  Does anyone happen to know what causes this problem?  (Yes,
I know I should just mask with 0x777, but I'm curious.)

\        /arner	- Writer of the dreaded Safety Seal Reviews
 \  /   /	- Owner of the vaporware group Safety Seal Software
  \/ \_/oung
       |	- Disclaimer: standard, reusable kind. 
     \_|