schwager@m.cs.uiuc.edu (08/05/90)
Now that my A500 gave me a major scare the other day, I'd like to know:
What does it mean when it boots up to a green screen, and the red led
flashes twice in succession, followed by a pause (continuously)?
This has been covered before, I know... but, in my infinite wisdom, I
saw fit to simply ignore it... cuz my computer worked, why would I need
that info? :-) Now that my machine is acting up, I promise
to save and print out this information so I can refer to it forever and
ever. Amen.
-Mike Schwager |"We must never permit the voice of
INTERNET:schwager@cs.uiuc.edu | humanity within us to be silenced.
UUCP:{uunet|convex|pur-ee}!uiucdcs!schwager| It is man's sympathy with all
BITNET:schwager%cs.uiuc.edu@uiucvmd | creatures that first makes him
University of Illinois, Dept. of Comp. Sci.| truly a man." -Albert Schweitzerdonb@bushido.uucp (Donald Burnett) (08/05/90)
Realizing netbandwidth etc.. Have you tried checking the seating of the Agnus chip? Have your dealer do it if it's under warranty, or you dont feel comfortable with it..
schwager@m.cs.uiuc.edu (08/06/90)
> /* Written 10:31 am Aug 5, 1990 by donb@bushido.uucp in m.cs.uiuc.edu:comp.sys.amiga.tech */ > Realizing netbandwidth etc.. Have you tried checking the seating > of the Agnus chip? Have your dealer do it if it's under warranty, > or you dont feel comfortable with it.. Yup... I pushed everything back in. Didn't work... but then, all the sudden, the machine started working again. Actually, what I'd like is a list of what all the colors and flashing LED combinations mean. Anybody have such a beast? -Mike Schwager |"We must never permit the voice of INTERNET:schwager@cs.uiuc.edu | humanity within us to be silenced. UUCP:{uunet|convex|pur-ee}!uiucdcs!schwager| It is man's sympathy with all BITNET:schwager%cs.uiuc.edu@uiucvmd | creatures that first makes him University of Illinois, Dept. of Comp. Sci.| truly a man." -Albert Schweitzer
plav@cup.portal.com (Rick M Plavnicky) (08/09/90)
On 8/5/90 schwager@m.cs.uiuc.edu wrote: >Actually, what I'd like is a list of what all the colors and flashing LED >combinations mean. Anybody have such a beast? I've kept this around for quite a while. It used to appear in the ``monthly intro'' postings. Appologies, this is old stuff and I was considering mailing it, but I haven't seen it lately so it may be of general interest. ---------- cut here ------------ Message-ID: #2463.pnet02.amiga/usenet 2061 chars. (19 more) From: daveh@cbmvax.UUCP (Dave Haynie) Newsgroups: comp.sys.amiga Subject: Re: Screen changes to green during reboot Date: 16 Jul 87 16:09:37 GMT Organization: Commodore Technology, West Chester, PA [Dave speaks about the colors of boot screens...] Actually, green is meaningful in the right context. On initial powerup, the first meaningful color displayed is dark grey, which indicates the system has passed the "hardware test". The 68000 is running, and some hardware registers are seen. Next is the light grey screen, the "software test", where the system software is starting to come up. Finally, the "white" screen comes up indicating that the machine is just about ready to ask for a disk; everything has checked out OK. Failures come up as colors. Green indicates a CHIP RAM failure of some kind. Red indicates a ROM/WCS failure. Blue indicates a custom chip failure. And yellow indicates that a 68000 exception trap has occurred before the normal OS trap handler (the GURU code) has been installed. When a failure is detected, the OS will often retry, so you can see cycling from failure to test, at least for the right kind of failures. -- Dave Haynie Commodore-Amiga Usenet: {ihnp4|caip|rutgers}!cbmvax!daveh "The A2000 Guy" PLINK : D-DAVE H BIX : hazy "Catch a wave and you're sittin' on top of the world" -Beach Boys A M I G A ' S I N I T I A L I Z A T I O N C O L O R S Dark gray Ok Hardware Light gray Ok Software Red Bad ROM Checksum Green Bad RAM Blue Bad Custom Chips Yellow Exception /Gateways/Usenet/comp/sys/amiga.tech/Rebooting 6880.3.1462.3 Re: Rebooting 5/31/89 14:09 page%swap@Sun.COM (Bob Page) Lines 1 to 26 of 37 (70%) u586182058ea@deneb.ucdavis.edu Frank Kuan wrote: >What does the Amiga do when you reboot? This should be in the 'most asked questions' posting, along with "what does color X mean on startup?" - Clear Chips (screen turns blue on custom chip failure) - Disable DMA and Interrupts - Clear the Screen - Check the Hardware - Pass or fail the Hardware to the Screen (dark grey if OK) - Checksum the WCS (OS does not checksum the ROM) - Pass or fail the WCS to the Screen (displays "Insert Kickstart" screen) - System setup - Check the for RAM at $C00000 - Move SYS_BASE to $C00000 if it exists - RAM Test - Pass or fail the RAM to the Screen (green if bad) - Check the Software - Pass or fail the Software to the Screen (light grey if OK) - Set up the RAM - Link the Libraries - Find External RAM and link it to the list - Set up Interrupts and DMA - Start default Task - Check for 68010, 68020, and 68881 - Check for an Exception (screen yellow if found and GURU handler not set up) - System Reset >Is it possible to change a vector somewhere and have the Amiga >run your code instead of the reboot sequence? Yes. This is one of those Amiga Secrets, most people don't discuss it because (presumably) it encourages crackers to write viruses and other nasty stuff. ..bob The Keyboard has it's own processor, RAM and ROM. A selftest is peformed on power-up in the following sequence. 1. Performs checksum on ROM's 2. Checks 64 bytes of RAM. 3. The timer is tested. 4. Performs handshake with computer and gives results of selftest. If the keyboard does not pass the test it will notify you that it is not working properly. This information is indicated with the blinking of the CAPS-LOCK light. One Blink: Keyboard ROM check failed. Two Blinks: Keyboard RAM checked failed. Three Blinks: Watchdog timer failed Four Blinks: A short between two row lines or special control keys. --------- cut here --------- /* Rick Plavnicky ...!sun!cup.portal.com!plav -or- plav@cup.portal.com */