Broadblues finally got it through my head what I needed to do to get my backup 4.1.6 listed in the early bootup menu. So I chopped into the dhx partition that was taking up all the spare space on my first hard disk (it shouldn't have been there anyway!), and set up about 2.7GB of it as dh41, SFS\02, and copied the 4.1.6 backup on the second hard drive into it.

Then I did a hard reboot and chose Amiga Menu when the selecter came up, sure now that I would have two choices, OS4FE and OS4.1.6 (by whatever name).

Surprise! Up came, after the OS4FE choice at "1",

2. AmigaOS4.1_Update_6 (Volume dh41)
3. AmigaOS4.1_Update_5-Debug (Volume dh41)

This raises the question, "Huh? What in the world?" Like, how could I have those two OSes in the same partition, and where did 5-Debug come from? And why is it running DOpus5 as WB replacement, which I didn't set up until I had been running update 6 exclusively.

Anyway, that's what I am using, and it works very nicely. It runs PageStream 5.0.5.8 Pro beautifully (can't do that on FE yet), and the fake Amiga keys work as they should; they didn't work while the OS was on the wrong disk.

@kilaueabart

If you load Kickstart/Kicklayout in a text reader, you will see 2 configuration settings. What you're seeing is the 'label' for each one. The first is normal boot (default), the 2nd is for debug testing. Each bootable system partition can have as many bootable configurations as you want. Default boot will be green, you can override by selecting a different number, hit the space bar to pause.

_________________
Hate tends to make you look stupid...

@kilaueabart

Quote:

Surprise! Up came, after the OS4FE choice at "1", 2. AmigaOS4.1_Update_6 (Volume dh41) 3. AmigaOS4.1_Update_5-Debug (Volume dh41) This raises the question, "Huh? What in the world?" Like, how could I have those two OSes in the same partition, and where did 5-Debug come from?

The volume name in the parentheses after an entry is the volume where a Kicklayout file was found which contained that entry as a label.

So you will probably find, if you look in DH41:Kickstart/, that there is a KickLayout file which contains configurations with those two labels. That does not mean that the systems themselves are on that drive, it depends on whether you have a BootDevice file pointing elsewhere in one or both of the configurations.

Best regards,

Niels

@nbache

Sho nuff, what I have in Kicklayout is

; Configuration name
LABEL AmigaOS4.1_Update_6
; Exec name
EXEC Kickstart/loader.of
;
; PPC native modules
;
MODULE Kickstart/kernel

and a list of files (MODULES), followed by

; Configuration name
LABEL AmigaOS4.1_Update_5-Debug
; Exec name
EXEC Kickstart/loader.of
;
; PPC native modules
;
MODULE Kickstart/kernel.debug

and exactly the same list.

Would it be OK to edit the second half out?

@kilaueabart

Quote:

Would it be OK to edit the second half out?

You can, but be safer to leave it in place. Make one mistake in the first config & your system may not boot again, the second config would allow you to boot & correct the problem.

_________________
Hate tends to make you look stupid...

@kilaueabart

A better idea might be to rename it AmigaOS4.1_Update_6-Debug and keep it, after making sure that the two module lists are in fact exactly the same apart from the debug kernel replacing the normal one.

If you want to play it safe, use NotePad to copy out the two lists to two separate, temporary files in RAM:, then run SYS:Utilities/FileCompare on them and inspect any differences.

Then you have a normal and a debug version of Update 6 to choose from.

(Do remember that you should take great care to avoid making any more empty lines, or remove any existing ones, in your Kicklayout file; it will fail to boot if you mess that up.)

Best regards,

Niels

@nbache

Good idea for use of FileCompare and nice plug.

@nbache

Aha! A couple subtle differences I was too senile to notice.

To compare, I copied with no name change -- left Kicklayout as is. Besides the different name lines, there were just these two:

MODULE Kickstart/kernel vs. MODULE Kickstart/kernel.debug
MODULE Kickstart/RadeonHD.chip vs. MODULE Kickstart/RadeonHD.chip.debug

Would you believe I have never heard of Kickstart debug before, and have no idea what the difference is supposed to be?

Meanwhile, I have detected no difference so far between running the 4.1.6 and the 4.1.5 .debug.