Click Here
home features news forums classifieds faqs links search
6071 members 
Amiga Q&A /  Free for All /  Emulation /  Gaming / (Latest Posts)



Lost Password?

Don't have an account yet?
Register now!

Your support is needed and is appreciated as is primarily dependent upon the support of its users.

Main sections
OS4 Zone
IRC Network
AmigaWorld Radio
Top Members
Amiga Dealers
About Us
Terms of Service

IRC Channel
Ports: 1024,5555, 6665-6669
SSL port: 6697
Channel: #Amigaworld
Channel Policy and Guidelines

Who's Online
13 crawler(s) on-line.
 29 guest(s) on-line.
 2 member(s) on-line.

 kolla,  zipper

You are an anonymous user.
Register Now!
 zipper:  19 secs ago
 kolla:  21 secs ago
 billt:  5 mins ago
 NutsAboutAmiga:  25 mins ago
 matthey:  27 mins ago
 Beajar:  59 mins ago
 Karlos:  1 hr 6 mins ago
 Kronos:  1 hr 31 mins ago
 Frank:  1 hr 50 mins ago
 Rob:  2 hrs 25 mins ago


Main »» Tutorials

OS4.x multiboot at UBoot time  Popular
(Read 13493 times)
Multiboot into different iterations of OS4.x.

a: For this tutorial we assume that the bootvolume with the highest bootpriority contains OS 4.1 and for sake of simplicity it is assumed that the volume name is "OS_4.1:". My system has, but yours may have it named differently.

b: We want to be able to choose a different version of the OS at UBoot time. In this 'tutorial' we assume that we want to be able to have OS 4.0 Final + update as a second option. Again for the sake of simplicity we assume that that iteration resides on volume "OS_4.0_F1:". Again, my system has, but yours may have it named differently.

c: Further, we assume that currently we have booted into OS 4.1.


To achieve our goal, we take these steps:
1 : In "OS_4.1:Kickstart" make a directory with the name of "OS_4.0_F1".

2 : Find out the Exec designation of volume "OS_4.0_F1:" by means of "Information..." (RAmiga + I).

3 : Open up a texteditor (NotePad) and type the outcome of the previous step here. (Something like DH3 or DH7. Note the absence of the colon (:)!)

4 : Save this text as "OS_4.1:Kickstart/OS_4.0_F1/BootDevice"

5 : Close the texteditor

6 : Copy ALL files (and only files) from "OS_4.0_F1:Kickstart" to "OS_4.1:Kickstart"

7 : Load "OS_4.0_F1:Kickstart/KickLayout" into a texteditor

8 : Replace the string "Kickstart/" by "Kickstart/OS_4.0_F1/"

9 : Locate this line:
EXEC Kickstart/OS_4.0_F1/loader

10: Right after that line insert this line:
MODULE Kickstart/OS_4.0_F1/BootDevice


11: Copy this text into the buffer by selecting it all and using (RAmiga + C)

12: Close the texteditor, but DO NOT SAVE THIS FILE!

13: Load "OS_4.1:Kickstart/KickLayout" into a texteditor

14: Set the cursor at the end of this file

15: Now use (RAmiga + V) and paste the contents of the buffer to the end of the file

16: Save the modified file "OS_4.1:Kickstart/KickLayout" back to disk

17: Close the texteditor

18: Now cold reboot and experience the joy of being able to choose from two options to boot from


An excerpt of my "OS_4.1:Kickstart/KickLayout" looks like this:
(Beware: it multiboots into three iterations of the OS!)

; $VER: Kicklayout_AmigaOne 53.1 (16.7.2006)
; Kernel configuration for the AmigaOne
; This file describes how the "Kickstart" image should look like,
; i.e. it describes which modules should be pre-loaded and available
; at boot time.
; Format:
; ~~~~~~
; The file lists one or more configurations.
; Each configuration starts with the LABEL keyword, followed by the
; name of the configuration. The name can be used to specify the
; configuration in the bootloader tool (see Documentation/kernel/
; bootloader.txt). Note that empty lines end one configuration and
; start the next, which means that you must be careful not to leave
; an empty line anywhere unless you are defining multiple configurations.
; Each configuration must have exactly one line with the EXEC keyword.
; This specifies the filename of the main kernel to use. This kernel is
; the absolute minimum required to boot. It contains, among other things,
; exec.library.
; The following lines define additional modules to be loaded into the
; kickstart image. Each of these lines starts with the MODULE keyword
; followed by the filename of the module.
; Configuration name
LABEL AmigaOS4.1
; Exec name
EXEC Kickstart/loader
; PPC native modules
MODULE Kickstart/kernel
MODULE Kickstart/FastFileSystem
MODULE Kickstart/SmartFilesystem
MODULE Kickstart/JXFileSystem
;MODULE Kickstart/a1floppy.device.kmod
MODULE Kickstart/a1ide.device.kmod
MODULE Kickstart/battclock.resource.kmod
MODULE Kickstart/uhci.usbhcd
MODULE Kickstart/hub.usbfd
;MODULE Kickstart/bootmouse.usbfd
;MODULE Kickstart/bootkeyboard.usbfd
MODULE Kickstart/massstorage.usbfd
MODULE Kickstart/ohci.usbhcd

; Configuration name
LABEL AmigaOS4.0_F1
; Exec name
EXEC Kickstart/OS_4.0_F1/loader
MODULE Kickstart/OS_4.0_F1/BootDevice
; PPC native modules
MODULE Kickstart/OS_4.0_F1/kernel
MODULE Kickstart/OS_4.0_F1/FastFileSystem
MODULE Kickstart/OS_4.0_F1/SmartFilesystem
;MODULE Kickstart/OS_4.0_F1/a1floppy.device.kmod
MODULE Kickstart/OS_4.0_F1/a1ide.device.kmod
MODULE Kickstart/OS_4.0_F1/battclock.resource.kmod
MODULE Kickstart/OS_4.0_F1/uhci.usbhcd
MODULE Kickstart/OS_4.0_F1/hub.usbfd
;MODULE Kickstart/OS_4.0_F1/bootmouse.usbfd
;MODULE Kickstart/OS_4.0_F1/bootkeyboard.usbfd

LABEL AmigaOS4.0_F
; Exec name
EXEC Kickstart/OS_4.0_F/loader
MODULE Kickstart/OS_4.0_F/BootDevice
; PPC native modules
MODULE Kickstart/OS_4.0_F/kernel
MODULE Kickstart/OS_4.0_F/FastFileSystem
MODULE Kickstart/OS_4.0_F/SmartFilesystem
;MODULE Kickstart/OS_4.0_F/a1floppy.device.kmod
MODULE Kickstart/OS_4.0_F/a1ide.device.kmod
MODULE Kickstart/OS_4.0_F/battclock.resource.kmod
MODULE Kickstart/OS_4.0_F/uhci.usbhcd
MODULE Kickstart/OS_4.0_F/hub.usbfd
;MODULE Kickstart/OS_4.0_F/bootmouse.usbfd
;MODULE Kickstart/OS_4.0_F/bootkeyboard.usbfd

- OldFart
[ home ][ about us ][ privacy ] [ forums ][ classifieds ] [ links ][ news archive ] [ link to us ][ user account ]
Copyright (C) 2000 - 2019 was originally founded by David Doyle