Welcome, Guest. Please login or register.

Author Topic: WB 1.3 Startup-Sequence issue - boot CLI not closing w/ app load  (Read 7448 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Pat the Cat

EDIT: The other person isn't using RUN EXECUTE, just EXECUTE...

startii won't finish until LoadWB has ended (Workbench has been closed). Don't bother waiting, just endcli after you've executed startupii.

An alternative to mclk is to use the AVAIL command somewhere to print available memory.

EDIT EDIT;

RUN  MCLK >nil:

Different from

RUN >NIL: MCLK

The program you are trying to run has to be immediately after the RUN. On 1.3 anyway.

Am baffled why you are using the >NIL: Isn't the whole point that you want to see the output printed rather than suppressed?
« Last Edit: March 30, 2021, 01:05:02 AM by Pat the Cat »
"To recurse is human. To iterate, divine."

A1200, Vanilla, Surf Squirrel, SD Card, KS 3.0/3.z, PCMCIA dev
A500, Vanilla, A570, Rev 5, KS 1.2/1.3 Testbench system
Rasp Pi, UAE4ARM, 3D laser scanner, experimental, hoping for AmigaOS4Arm, based on Watterott Fabscan Pi
 

Offline Pat the Cat

Re: WB 1.3 Startup-Sequence issue - boot CLI not closing w/ app load
« Reply #1 on: March 30, 2021, 03:49:32 AM »
<scratches head>

Well... you definitely need an endcli at the end of startupii. After the Break command. I wouldn't bother with the Break there an failat in  startup-sequence. Or the Wait. I guess the Wait does help you read any messages though,.

You have a DELAY option on the LoadWB after the 5 minute timer in your startup-sequence, if a sub process hasn't ended, that might cause it?

I always just use LoadWB without any options.

It's a good idea to click on the "Window to back" icons to see if Workbench has actually loaded behind the opening Amiga Dos screen.

And it's a very good idea to leave out the >NIL: flags to dump the output on commands when debugging a startup sequence. It might be printing an error code, which can help you find causes to problems.
« Last Edit: March 30, 2021, 04:31:50 AM by Pat the Cat »
"To recurse is human. To iterate, divine."

A1200, Vanilla, Surf Squirrel, SD Card, KS 3.0/3.z, PCMCIA dev
A500, Vanilla, A570, Rev 5, KS 1.2/1.3 Testbench system
Rasp Pi, UAE4ARM, 3D laser scanner, experimental, hoping for AmigaOS4Arm, based on Watterott Fabscan Pi
 

Offline Pat the Cat

Re: WB 1.3 Startup-Sequence issue - boot CLI not closing w/ app load
« Reply #2 on: March 31, 2021, 05:18:31 AM »
Two differences between your startup-sequence and "the other guys" - first, they are running rexxmast, which means they're likely running Workbench 2 or higher.

The other thing I noticed was that they run popcli before they try to run mclk. May or may not be how they get around the old mclk not liking detaching when it is run from a cli, as opposed to clicked on from an icon. (Which is what alu is supposed to do).

It would appear you are both using the old version of mclk... although I wonder why they are exactly? When there's mclk32 for more recent Kickstarts.

If alu doesn't help getting mclk running, perhaps WBRun can.

https://aminet.net/package/util/cli/WBRun
« Last Edit: March 31, 2021, 05:32:29 AM by Pat the Cat »
"To recurse is human. To iterate, divine."

A1200, Vanilla, Surf Squirrel, SD Card, KS 3.0/3.z, PCMCIA dev
A500, Vanilla, A570, Rev 5, KS 1.2/1.3 Testbench system
Rasp Pi, UAE4ARM, 3D laser scanner, experimental, hoping for AmigaOS4Arm, based on Watterott Fabscan Pi