Amiga.org
Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: ottomobiehl on August 11, 2003, 02:41:06 AM
-
I was just reading the step by step boot up process of a PC (intel) and found it facinating but was wondering about the boot up sequence of an Amiga, well a classic one. I am interested in comparing the two.
Could some one enlighten me to the process of booting an Amiga or point me to a link (or previous thread on the subject.) If so I would be indebted.
Thanks in advance.
-
WB1.3 boot (Provided by The Amiga Exchange BBS)
(I don't know the accuracy of it)
1. Clear all chips of old data.
2. Disable DMA and interrupts during the test.
3. Clear the screen.
4. Check the hardware(CPU).
5. Change the screen color.
6. Do a checksum test on all ROMS.
7. Change the screen color.
8. Begin system startup.
9. Check RAM at $C0000, and move SYSBASE to it.
10. Test all Chip RAM
11. Change the screen color.
12. Check that software is coming in without problems.
13. Change the screen color.
14. Setup Chip RAM to receive data.
15. Link the libraries.
16. Check for additional memory, and link it.
17. Turn the DMA and interrupts back on.
18. Start a default task.
19. Check for a 68010, 68020, and 68881.
20. Check to see if there is an exception (processor error).
21. If there is an exception, reset the system. ;-)
-
Lo wrote:
WB1.3 boot (Provided by The Amiga Exchange BBS)
(I don't know the accuracy of it)
1. Clear all chips of old data.
2. Disable DMA and interrupts during the test.
3. Clear the screen.
4. Check the hardware(CPU).
5. Change the screen color.
6. Do a checksum test on all ROMS.
7. Change the screen color.
8. Begin system startup.
9. Check RAM at $C0000, and move SYSBASE to it.
10. Test all Chip RAM
11. Change the screen color.
12. Check that software is coming in without problems.
13. Change the screen color.
14. Setup Chip RAM to receive data.
15. Link the libraries.
16. Check for additional memory, and link it.
17. Turn the DMA and interrupts back on.
18. Start a default task.
19. Check for a 68010, 68020, and 68881.
20. Check to see if there is an exception (processor error).
21. If there is an exception, reset the system. ;-)
Thank you very much!!!!! :-)
-
Hey....by any chance do you know the LED blink counts when the screen turns to an error color?
Just curious...
-
os4 runs on classic amigas right? :-o
-
@DIABLO_NEGRO
AOS4 doesn't run anywhere yet, they have not fully assembled it. The demo shown only 2 weeks ago was only 50% complete.
When released, it will run only on Amiga 4000's running DCE's Cyberstorm PowerPC cards.
-
The error codes (screen colours and caps lock light) are here (http://finebyme.natch.org/amigaboot.html) (but it doesn't mention magenta, curiously). There are probably more detailed places elsewhere on the net.
-
When released, it will run only on Amiga 4000's running DCE's Cyberstorm PowerPC cards.
Semi-classic Amiga. :-) Or is that Semi-carnally. :-D :python:
-
When released, it will run only on Amiga 4000's running DCE's Cyberstorm PowerPC cards.
... and the AmigaOne of course ...
-
mikeymike wrote:
When released, it will run only on Amiga 4000's running DCE's Cyberstorm PowerPC cards.
... and the AmigaOne of course ...
Eventually.... And hoprfully my BlizzardPPC!!!
-
DUHHH... lol .... I thought it was farther along than 50% ... well thats cool
-
by downix on 2003/8/11 19:08:23
@DIABLO_NEGRO
AOS4 doesn't run anywhere yet, they have not fully assembled it. The demo shown only 2 weeks ago was only 50% complete.
When released, it will run only on Amiga 4000's running DCE's Cyberstorm PowerPC cards.
CSPPC Phase5 also? or only DCE ones?
Ciao
-
DIABLO_NEGRO wrote:
DUHHH... lol .... I thought it was farther along than 50% ... well thats cool
Depends which 50% you mean, though.
I think Ben Hermans (project leader) said about 50% of the work of porting modules from m68k to PPC (it's already in C, the rewrite from assembly has been done) was done this summer, the only thing that's missing then is the last 50% of those modules and finalizing everything.
This isn't the same as 50% finished, because it's only the last step. 50% finished to me means it would take another 2 years, but we're talking another month or so.
Downix will stop at nothing to make it look like Hyperion hasn't even started on it, don't listen _too much_ on him. Or at least take every side of every argument with a bit of salt...
-
Depends which 50% you mean, though.
Maybe the Statical Mechanics part of my Degree, was wrong... but 50% is aproximatly half... and it is always half of the whole...
So I guess when he says 50% isn't completed... I guess he means that Half of the Operating system has not been completed... I could be wrong... :-/