Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!bagate!cbmvax!daveh
From: daveh@cbmvax.commodore.com (Dave Haynie)
Newsgroups: comp.sys.amiga.hardware
Subject: Re: Hardrives and the A3000
Message-ID: <20092@cbmvax.commodore.com>
Date: 25 Mar 91 19:08:49 GMT
References: <17727@crdgw1.crd.ge.com> <1991Mar20.220547.4677@en.ecn.purdue.edu> <20023@cbmvax.commodore.com> <1991Mar22.064048.12805@en.ecn.purdue.edu>
Reply-To: daveh@cbmvax.commodore.com (Dave Haynie)
Organization: Commodore, West Chester, PA
Lines: 26

In article <1991Mar22.064048.12805@en.ecn.purdue.edu> wwarner@en.ecn.purdue.edu (William A Warner) writes:

>Has anyone figured out yet why the 3000 flashes a yellow screen at you 
>instead of automaticly rebooting after a crash?  This didn't start occuring
>until I added more RAM.  Dave, is this occuring on any of your "maxed-out"
>3000's????   

No, I never ran into yellow flashes.  I used to get a nice, deep blue for a
sec on my A3000 prototypes when powering up, under 1.3 ROMs.  I haven't
noticed any color flashes so far under 2.0x and SuperKickStart.  Though I
haven't been using a system with 16MB in it much (when I set up a 52MB system,
it was with loaner DRAM).  There's always a chance, when you add more of 
something, that the computer takes just a tad longer to figure out your total,
and lets you see something you wouldn't ordinarily see (and perhaps the OS 
people themselves missed?).  The only normal reason for a yellow screen is a
processor exception that happens before alerts are possible, though I have 
never run into a situation where that flashes for a second, it's generally the
equivalent of a GURU or System Error, it stays yellow. 

>Art Warner


-- 
Dave Haynie Commodore-Amiga (Amiga 3000) "The Crew That Never Rests"
   {uunet|pyramid|rutgers}!cbmvax!daveh      PLINK: hazy     BIX: hazy
	"What works for me might work for you"	-Jimmy Buffett