Hi All,
I am trying to make several entries in SLB :
- one for OS4 final
- one for OS4 update4
- one for linux

pb is how to get OS4 final and OS4 update4.
both partitions are bootable with same boot priority but only os4 final appears in the SLB (I guess it is because it is the first partition on the HD).
I modified the kicklayout to add the lines from my update4 and redirect calls to my update4 partition (ex:"EXEC sd0:Kickstart/loader" instead of "EXEC Kickstart/loader") but that is not valid.

so how to have and boot from mixed version of AmigaOS 4.0 ?

@lionstorm

The 'safe' way I do this is to change the boot priority and re-boot.

I am not sure what files are loaded, up to displaying the boot options, but
when I tried booting into update#4 using the early startup menu I ended up with a big problem.
The early startup menu is only avaiable once kickstart is loaded, So it booted from the partition with the highest boot priority, and then tried to load workbench from the partition I had selected.

A recipe for disaster, which meant unmatched kickstart/workbench combinations.

The above probably doesn't help, but is what I do.

_________________
Peter Swallow.
A1XEG3-800 [IBM 750FX PowerPC], running OS4.1FE, using ac97 onboard sound.

"There are 10 types of people in the world: those who understand binary, and those who don't."

@lionstorm

Copy the Update4 Kickstart files to your OS4final partition, put them inside an Update4 directory.

There's an option for setting the default boot partition that Kickstart will use - check the docs on the CD and set it to your Update4 partition.

Chris

_________________
"Miracles we do at once, the impossible takes a little longer" - AJS on Hyperion
Avatar is Tabitha by Eric W Schwartz

@lionstorm

Sorry, I've just had a look at my OS4Final install.
have you looked in the documentation folder on the install cd.

The following is extracted from the kickstart/bootmenu.doc

Quote:

Predefining the default boot device in the KickLayout file ---------------------------------------------------------- This feature requires slb 1.16+ and Loader V51.10+ on an AmigaOne or BootLoader 51.14+ on a classic machine. You should not try to use it without those requirements, this may result in a non-booting or unstable system! If you want some other device than that with the highest boot priority to be the default boot device for a given KickLayout file, add an entry like MODULE Kickstart/BootDevice to the KickLayout file (caution, the name is case sensitive) and create a text file with that name that contains the device name (not the volume name) of the preferred boot device, e.g. this command Echo >Kickstart/BootDevice "DH1" executed in the shell will do it.

I hope that is more helpful.

_________________
Peter Swallow.
A1XEG3-800 [IBM 750FX PowerPC], running OS4.1FE, using ac97 onboard sound.

"There are 10 types of people in the world: those who understand binary, and those who don't."

@ Swoop :

changing boot priorities is also the (only) way I am following !

@ Chris
I totally forgot the doc !
It is not very clear to me what to do.
I added and entry at the end of the kicklayout like this :
MODULE Kickstart/BootDevice "Sd0"
Sd0 being my update4 partition name.

cold boot and slb tells me it could not find the MODULE (which is true : there is no BootDevice module in /kickstart)

I updated the SLB from v2 1.12 to 1.16, dont know about the "Loader V51.10+" and where it is (not in C: or L:)

EDIT : found the loader in kickstart

Last edited by lionstorm on 31-Dec-2006 at 12:06 PM.

@lionstorm

Quote:

lionstorm wrote: It is not very clear to me what to do. I added and entry at the end of the kicklayout like this : MODULE Kickstart/BootDevice "Sd0" Sd0 being my update4 partition name.

No, no, that's not what you do

Create a text file containing the text "SD0" and having the name BootDevice, and put that file in your Kickstart directory. This can e.g. be done from a shell by typing:

echo "SD0" > SYS:Kickstart/BootDevice

MODULE Kickstart/BootDevice

@nbache

ok here is what I did :
1) create a subdir called update4 and copied over my files from update4 kickstart drawer

2) modify the kicklayout of os4final by adding a new configuration name and copying all lines from my update4 kicklayout and changed all path to kickstart/update4/, add MODULE kickstart/update4/bootdevice line.
so it presents like this :

; Configuration name
LABEL Update4
; Exec name
EXEC Kickstart/loader
MODULE Kickstart/update4/BootDevice
;
; PPC native modules
;
MODULE Kickstart/update4/kernel
MODULE Kickstart/update4/FastFileSystem
MODULE Kickstart/update4/SmartFilesystem
MODULE Kickstart/update4/a1ide.device.kmod
MODULE Kickstart/update4/battclock.resource.kmod
etc...

3) create a file named bootdevice in kickstart/update4/ that contains the device name (case sensitive) bearing my update4 partition (in this case Sd0)


Does it work ? Well not fully : I see my update4 entry in SLB, it loads the kernel and modules and it stops ! I have a black screen.

Maybe I am missing something !

@lionstorm

I also haven't been able to get the BootDevice thing to work.

I can get it to load the old Update4 kernel modules, and I can use the Early Startup screen to select the update 4 partition. But it doesn't automatically use that partition if I give it in my Kickstart_old/BootDevice file and add an entry to Kicklayout.

@lionstorm

> Maybe I am missing something !

Yes, you didnt read the *complete* instructions which I already wrote
on this website in some other thread.

What you missed is that only the OS4final version of bootmenu.kmod supports
the new BootDevice feature, thats why I suggested in the other thread to
overwrite the Update4 versions of Loader and bootmenu.kmod in the
Kickstart/Update4/ subdirectory with the OS4final versions.

@dangerman

> I can get it to load the old Update4 kernel modules, and I can use the
> Early Startup screen to select the update 4 partition.
> But it doesn't automatically use that partition if I give it in my
> Kickstart_old/BootDevice file and add an entry to Kicklayout.

What you missed is that only the OS4final version of bootmenu.kmod supports
the new BootDevice feature, thats why I suggested in the other thread to
overwrite the Update4 versions of Loader and bootmenu.kmod in the
Kickstart_old/ subdirectory with the OS4final versions.

@TetiSoft

sorry but I cant follow all the threads

so I did what you said and now I am getting gurus in a loop whenever I select update4 in the SLB

error 30038035
task 0x018BCBC8

EDIT : got it working the other way around : update4 as high priority and having subdir containing bootdevice and os4final modules, copied loader and bootmenu.kmod from os4final to update4 and modified update4 kicklayout to add a new configuration called os4final (and where modules are directed to kickstart/os4final/ drawer).

the only thing is that after each (soft) reboot I get a guru, but the boot process continues after pressing RMB !

Thanks for your patience !

Last edited by lionstorm on 03-Jan-2007 at 10:09 PM.