Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: TheBilgeRat on May 02, 2011, 09:11:07 PM
-
May seem silly, but it sure beats me hitting Ctrl A A over and over till I have them committed to memory :D
I did a BB1 and BB2 install (os 3.5) and it dorked up some stuff (non-executeable bits and so forth), but with this new CF card and the PFS3 they are like a subliminal message! Are they hanging about somewhere to be accessed? Or should I get out a digi cam and snap a quick pick?
-
What Boot Messages !!! you seeing things now... ;)
-
Are they hanging about somewhere to be accessed?
You can redirect them to the serial port and watch them, old school with a VT102 like I used to :), or with Term/JRComm/etc on another Amiga, and even capture them to a file.
-
May seem silly, but it sure beats me hitting Ctrl A A over and over till I have them committed to memory :D
I did a BB1 and BB2 install (os 3.5) and it dorked up some stuff (non-executeable bits and so forth), but with this new CF card and the PFS3 they are like a subliminal message! Are they hanging about somewhere to be accessed? Or should I get out a digi cam and snap a quick pick?
As a temporary debugging measure, you can comment out the 'EndCLI >NIL:' line at the end of the startup-sequence, and for additional info you could even add 'set echo on' at the beginning.
-
May seem silly, but it sure beats me hitting Ctrl A A over and over till I have them committed to memory :D
I did a BB1 and BB2 install (os 3.5) and it dorked up some stuff (non-executeable bits and so forth), but with this new CF card and the PFS3 they are like a subliminal message! Are they hanging about somewhere to be accessed? Or should I get out a digi cam and snap a quick pick?
You mean the initial CLI window opens with some error messages in it, but closes so fast that you cannot read them?
Put this at the end of startup-sequence:
LoadWB
ask Continue ; <== insert this line
EndCLI
Then the window stays open until you press enter and you have enough time to read the messages.
-
You mean the initial CLI window opens with some error messages in it, but closes so fast that you cannot read them?
Put this at the end of startup-sequence:
LoadWB
ask Continue ; <== insert this line
EndCLI
Then the window stays open until you press enter and you have enough time to read the messages.
Awesome! Thanks, Thomas!