SPEED DEMONS FORUM ARCHIVE OOT 2000 SOFTWARE

(A1000) - 4 Blinks then a 5 second pause - This is normal and part of its boot sequence, but can also indicate a bad Kickstart disk. (A2000) A Dim LED with no blinks can indicate a Buster issue. 74S51 (U9I) & 74F74 (U8I) damaged from expansion port. (A1000) - Fast steady power LED blink dark screen. White - CPU failure or Denise/Lisa issue. Often means a CIA error if not booting.īlack / Stripes - CPU or ROM error (try pressing down on the chips during power off) Bad Capacitors, or a bad expansion card can often cause this, as can any other type of untrappable error.Ĭyan - Rev 0.x Kickstarts - Kickstart Error.īlack - No CPU detected, or unspecified ROM error.

SPEED DEMONS FORUM ARCHIVE OOT 2000 SOFTWARE

Yellow - The computer found an error before the error trapping software (the guru) was running. Green- There is an error in the Chip RAM or general Ram error.īlue - An error was found in the custom chips Denise, Paula or Agnus. Red - There is an error in the Kickstart ROM(s) Kickstart - The initialization tests were all passed White - The software is being executed and seems OK If it stops at light grey it can mean a CIA error, or ROM corruption.

The 68000 is running and the ROM registers are readable. The Shell running the Startup-Sequence is closed.ĭark Grey - The initial hardware tested OK. The contents of the SYS:WBStartup drawer are run.ĩ. The Workbench is loaded by the LoadWB command.Ĩ. Additional assigns can be made and other programs can be executed here.ħ. The User-Startup is designed for user-customization of the system. A line in the Startup-Sequence causes the User-Startup to be executed. It also runs other small programs to prepare the Workbench.Ħ. The Startup-Sequence prepares the system for use by running SetPatch?, activating assignments for Devs:, Libs, etc. An AmigaDOS bootblock assigns SYS: to the active device and executes SYS:S/Startup-Sequence, a script.ĥ. (Some games use a custom bootblock which activates a nonstandard bootup – usually to decrunch compressed game data).Ĥ. If no bootable device is found, the Kickstart screen appears.ģ. With no disk in the drive, the system moves on to the device with the next highest priority. Finds the device with the highest boot priority. These drives may fail to boot on other controllers.Ģ. Some early controllers are not RDB compliant and require a custom preparation of an attached drive. This can be the onboard SCSI or IDE controllers, or a peripheral device with its own boot ROM. Checks available boot devices for a valid RDB. After this, the ROM GURU trap handler will display errors as codes on the screen.ġ. The Kickstart Image is Displayed showing that the rom has been installed to memory, is running, and everything so far has reported OK. If there is an Exception (processor error), or issue reported, the system will reboot.Ģ1b. Check to see if there are additional CPUs on the system, accelerators or a maths coprocessor.Ģ1a. Chance screen colour to Yellow if there is an error with external cards/devices.ġ9. Check for additional memory in these devices and link it to the computer.ġ6b. Link the ROM libraries so the machine can identify connected devices and peripherals.ġ6. Change colour to White if the software test is OK, stays Light Grey if faulty, or Blue if Custom Chip error.ġ5. Check to see if the ROM software is coming in OK and being executed.ġ3. Change screen colour to Green if RAM is faulty, or change to Light Grey if RAM is OK.ġ2. Check the Ram at $C0000, and move SYS_BASE there.ġ1. Change screen to Red if ROMs are faulty, or change to Dark Gray if ROMs are OK.ĩ. Change the screen to Black, screen stays Black (or with red Stripes) if CPU fault.ħ. Check the Hardware to make sure the 68000 is working.ĥ. Disable DMA and interrupts during the test.Ĥ. Do let me know if this info is correct or wrong!Ģ. Here is some info I gathered from around the web concerning your Amigas boot sequence, and the error codes which your computer will provide to help pinpoint damage and issues.

Speed demons forum archive oot 2000