Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!cwjcc!hal!nic.MR.NET!tank!mimsy!dftsrv!ames!pasteur!ucbvax!kepler.Berkeley.EDU!me128-aw
From: me128-aw@kepler.Berkeley.EDU (me128 student)
Newsgroups: comp.sys.amiga
Subject: Re: Ami crashes, RAD:
Message-ID: <27066@ucbvax.BERKELEY.EDU>
Date: 8 Dec 88 08:23:10 GMT
References: <10207@watdragon.waterloo.edu> <27024@ucbvax.BERKELEY.EDU> <2450@antique.UUCP>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: me128-aw@kepler.Berkeley.EDU (me128 student)
Organization: University of California, Berkeley
Lines: 38

In article <2450@antique.UUCP> vax135!cjp (Charles Poirier) writes:
>
>This is a long-standing bug in the system.  The bug causes crashes when
>you have more than one Interlaced screen plus a Non-interlaced screen
>simultaneously, and try to flip among them.  Occasionally it fails to
>crash, but don't bet on it.  It's safe to drag screens down by mousing
>the title bar.  Sometimes this lets you get to a place from which you
>can kill one or more screens so that remaining screens can be flipped
>safely.
>
Thanks for the Help.
A few questions:

I have found that the it will NOT crash if the non-interlaced screen is
opened before the second interlaced screen (wb is the first).  I guess 
this makes sense if the non-interlaced screen is trashing some interlaced
bit somewhere when it's opened.  

1) Once it did this while I was playing a beta-version of a new game.
   The game did non open or flip screens, but was just bringing up a 
   requestor in it's interlaced screen.  When it did, the screen flashed
   to non-interlace (BOOM!).  How could this occur?

2) Why hasn't anybody written a patch to fix this?  It seems to me that
   this SERIOUSLY undermines the multitasking nature of the Amiga.  Shouldn't
   it be possible to write a little program which monitors the screen
   ordering and does some magic which the Guru is thinking of dropping
   by?

3) Could anything make this occur more frequently?  I have had an identical
   system configuration for quite some time now, and have had relatively
   few crashes until recently.  As I recall, I have had interlaced and
   non-interlaced screens together often with no problems in the past.

4) Is the interlacing a function of having separate odd and even source
   bitmaps, or just the way the screen is drawn.  In other words, if I
   use SetLace or something like it on the non-interlaced screen, will that
   prevent a crash?