Dual Booting 1.3 and 3.1

[DiskChris]

I'm trying to dual-boot my KS 1.3 A2000 with 3.1 using mkick, and I have both OS's installed on different partitions. I want it to automatically detect which Kickstart is running and load the appropriate workbench (using movesys and vercheck). So I made the 1.3 partition bootable, and modified the startup sequence:

Code: [Select]

Vercheck 34
If WARN
echo "Booting 3.1"
movesys cd WB1.3:
execute WB1.3:s/startup
EndCli

Else

echo "Booting 1.3"
movesys cd WB3.1:
execute WB3.1:s/startup-sequence
EndCli

where startup is workbench 1.3s original startup-sequence. It work's but when loading 3.1, with a 3.1 KS, it still *looks* like 1.3! Everything's blue orange, and yet root has changed, since sys: points to the 3.1 partition, so it does actually seem to be running 3.1 and not 1.3...

[Calimeiro]

I do not use any of those programs, but still might help you.

"If .. Else .. " blocks, like all If conditions, should be closed by Endif.

You probably need only one check, no .. else .. condition, because if "warn" fails the script will jump to Endif and continues normal execution.

I'll make following assumptions:

WB 1.3 is default.
It loads from first bootable partition with high priority (DH0).

WB 3.1 is exception.
It boots from (non-bootable)partition with lower priority (DH1).

Put following code on top of dh0:s/startup-sequence
-------------------------
vercheck 40>
if warn
    movesys dh1:
    execute s:startup-sequence
endif

...... ()

If Kick_3.1 is not selected current startup loads WB_1.3.

EndCLI is not needed as it is executed at end of each startup-sequence.

Execute does not run a script asynchronous. CLI or current script waits for end of execution.

Hope this works