@McTrinsic
I'm finally in a position to get my 2nd Kickstart ROM in a workable situation on the Phoenix. Funny: no matter where I look online for this process I can't seem to locate single step-by-step guide on setting up multiple Kickstarts.
There are plenty of places that talk about adding the Kickstart ROM chips or switchers, but nobody (that I've been able to locate) explains how to set up the
drives. Even the old manuals I've read only talk about the hardware; they never explain the hard drive setup, which I find completely baffling. I don't have a ton of stuff for OS 2.0, but I do have some programs I really want to run and just can't on 1.3, unfortunately.
Naturally once I figure out the hard drive side of things I'm going to have to create an article here and make it a Sticky.
In any case, my Kickstarts are all set and ready to go. Here's my current setup:
1.3 is my boot KS.
I have 2 (current) HDD partitions: DH0 (System) and DH1 (Programs)
DH0 (50MB) has Workbench 1.3 installed on it.
DH1 (200MB) has programs I've moved over (Terminals, a few other odds and ends - nothing critical). It was going to be where I installed most everything.
I have 2.04 as my secondary KS.
Here's what I was going to try and do. Please correct me if I'm wrong.
Step 1: Partition
I was going to re-partition DH1 into 2 drives.
So I'd have 3 drives.
DH0: (1.3 Workbench) (50MB)
DH1: (Programs) (190 MB)
DH2: (2.0 Workbench) (10MB)
Step 2: Install Workbench 2.0
I would install 2.04 onto DH2:
I assume I have to boot the Phoenix using the KS 2.0, with the Install WB 2.04 disk in FDD, and go through an install from FDD - and manually tell it to install to DH2: (I've not done that before, so that'll be my first challenge).
This next step is where I find things to be a bit confusing... assuming I've got the previous steps correct
Step 3: Modify Old and Create New Startup Sequence
I know this has to do with boot sequences (I think?) but when I flip the switch to KS 2.0, it will hit my main system's Startup-Sequence. You've shared yours, which I really appreciate. I would take your code (where applicable) and insert it ... where? At the top of the Startup Sequence?
Also, once it hits that statement about which WB to load, won't I technically have two startup sequences now? One "main" one on 1.3, which determines what to hit (and loading the newly named SS which used to be my "real" SS, right?).
I think I have it right in my head, but it sounds strange.
1) Load your custom SS, which is really just a SS chooser. Then it will either hit my original (which has a new name) or the one over on DH2:.
Does that make sense?
My "Chooser" startup-sequence will look something like this:
Code: Select all
; startup-sequence "WB-Chooser" (20-Mar-2018)
c:version >nil: exec.library 37
; Kick 2.0+
if not warn
;echo "ROM 2.x"
assign sys: DH2:
skip boot
endif
; Default
execute s:startup-13 ; THIS LOADS MY OLD (Current) STARTUP SEQUENCE - WITH EVERYTHING IN IT, BUT FILE RE-NAMED
lab boot
assign c: sys:c
assign s: sys:s
assign libs: sys:libs
assign devs: sys:devs
assign fonts: sys:fonts
assign l: sys:l
execute s:startup-sequence ; THIS IS MY *NEW* STARTUP SEQUENCE, WITH JUST *THIS* CODE (ABOVE) IN IT, RIGHT?
And do I need all of those assigns? I'm wondering if I can eliminate those or if they're needed for this process? I mean, they aren't bad per se, just trying to remove variables in case something goes wrong.
Thanks for any clarifications you might remember. Your code is 9 years-old, so I wouldn't blame you if you have trouble remembering.