Welcome, Guest. Please login or register.

Author Topic: Awkward OS4.1 Classic boot procedure  (Read 1846 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline JurassicCamper

  • Hero Member
  • *****
  • Join Date: May 2002
  • Posts: 635
    • Show all replies
Re: Awkward OS4.1 Classic boot procedure
« on: February 04, 2013, 01:11:45 PM »
You dont need IDEFIX software to use a 4 Way addaptor suchas the idefix express with OS4.1 All you need in your Kicklayout is :-

scsi.device.kmod
scsi.device_ppc.kmod (Required for Memory Paging)
ATAPIismajik (Required for 4 way activation)

I notice you are using blizkick (ages since i used 3.x) means your maprom jumper is closed, OS4.1 requires maprom to be open. (NO MAPROM)

If you are using a medaitor check the state of your wait jumper it needs to be closed for OS4.1

Simplest way to set it up is :-

Add 68K smartfilesystem 1.279 Qualifier 53465300 to the RDB
 
For Dual Boot Without scripts

DH0 - First 1 GB of the disk
SFS/00
512 Blocks
Buffers 600
Bootable BootPri 0
Install OS4.1 from the CD. CDROM-Drive needs to be primary slave.

Create a textfile in sys:kickstart called bootdevice
the contents being DH0

remove the semicolon from the line in your sys:kickstart/Kicklayout-A1200 file

;MODULE Kickstart/BootDevice

HD0 - Second 1 GB of the disk
Same as above
BootPri 1
Put your 3.9 Install here

By default it will boot into 3.9. To boot 4.1 enter the ESS and boot from dh0: the kernel will load, reset and the bootdevice line will tell it to boot workbench from DH0 overriding the higer bootpri of hd0:

Once you have that working then reintroduce your scripts.
« Last Edit: February 04, 2013, 01:16:04 PM by JurassicCamper »
A1200T PPC 330Mhz in a Custom Modified Fractal Design R3 Case
 

Offline JurassicCamper

  • Hero Member
  • *****
  • Join Date: May 2002
  • Posts: 635
    • Show all replies
Re: Awkward OS4.1 Classic boot procedure
« Reply #1 on: February 05, 2013, 07:58:12 PM »
Remove SFS 1.290 from the RDB its PPC, replace it with 1.279 68K version from the Install CD or the internet.
PPC Filesystems are loaded as part of the kickstart not from the RDB
You might as well replace fastfilesystem with V52.6 from the CD too whilst your at it.

to set your bootdevice do the following

Echo >hd2:Kickstart/BootDevice "hd2"

all you need in your script is

;booting OS4.1
assign sys: hd2:
assign c: sys:c
cd sys:
c:bootloader filename hd2:kickstart/kicklayout-a1200 VERBOSE

You can remove VERBOSE part later

to debug this if this

Attach a nullmodem cable between your A1200 and a terminal package on another computer

Change bootloader to

BootLoader COMMANDLINE="debuglevel=3 serial baudrate=38400"

change the kernel line in the kicklayout-a1200 file from

MODULE Kickstart/kernel

to

MODULE Kickstart/kernel.debug

hope this helps.

p.s.

You can also put semicolons in front of a lot of items in the kicklayout file too like the usb, gfxcardones that arnt needed and remove usbctrl start from the startup-sequence
A1200T PPC 330Mhz in a Custom Modified Fractal Design R3 Case