Logging Startup and Userstartup-sequence

[XDelusion]

I know this has been asked before, but I can not find the post, nor do I recall the solution, but I think Piru answered it.

What I want to know, is if there is a way to log my startup-sequence and my userstartup-sequence.

This way if there are any errors on boot up that I'm not seeing, I can go back and see them.

[Thomas]

You can log into the console window if you add set echo on to the beginning of startup-sequence and you can prevent the console window from closing if you remove the endcli command from the end. Or insert ask "press enter" before endcli.

The latter alone will already allow you to read error messages. Both in combination will also show you which command output the message. To stop the log flow you can press any key and continue by deleting the key you entered.

[XDelusion]

Thank you much sir, that is a good idea, though I am wondering if it is possible to output the log to a txt file on the hard drive?

[Matt_H]

What I like to do in situations like this is boot without startup-sequence, set echo on, as Thomas described, then execute s:startup-sequence. If you append >dh0:logfile it will save the buffer to disk. I don't know if you'll be able to see it on screen while it's executing - there's probably a way, but I'm not sure of the command syntax.

There's also an interactive mode - set interactive on, maybe? It'll ask you to confirm executing each line of the script.

[Piru]

What I like to do in situations like this is boot without startup-sequence, set echo on, as Thomas described, then execute s:startup-sequence. If you append >dh0:logfile it will save the buffer to disk.

Hmm, are you sure? I was under the impression that each command handles redirection by their own.

There's also an interactive mode - set interactive on, maybe? It'll ask you to confirm executing each line of the script.

I'm fairly sure that there's no such thing.

[Matt_H]

Hmm, are you sure? I was under the impression that each command handles redirection by their own.

Nope, I'm not sure

I'm fairly sure that there's no such thing.

That may not be the right command, but I've done it in the past, somehow. Maybe it was a command line argument for 'execute'?

[Piru]

That may not be the right command, but I've done it in the past, somehow. Maybe it was a command line argument for 'execute'?

Nope. I've reimplemented AmigaOS shell, resident commands, execute and many of the C command for MorphOS and I'm fairly sure I would remember if there was such a feature anywhere in AmigaOS.

[Matt_H]

@ Piru

It's possible I'm imagining things. I'll check my manuals and let you know if I come up with anything.

[Matt_H]

A quick update: set interactive on is the right command, but the feature was only introduced with 3.9 or one of its updates. I confirmed that it's not in 3.1 and Piru confirmed that it's not in 3.5.

So you'll need to have the 3.9 ROM modules kicked in at cold boot (Deneb/Algor FlashROM, custom Kickstart) to use this method.