Installing WB 3.1.4 with MapROM (3.0 ROMs on board)

bitter · 30 October 2018, 02:07

Quick question (I hope). I've ordered some new ROMs, but while I'm waiting, my Amiga 1200 has 3.0 ROMs and I would like to install 3.1.4. I have ACA1221ec, which has MapROM functionality.

How can I install it? I was thinking of:

1. Create a temporary bootable partition with 3.1 install
2. Use MapROM on it to softkick 3.1.4 KS into RAM
3. Install 3.1.4 into proper partition
4. Move the MapROM command onto the new partition

Will this work, or will 3.1.4 complain on reboot before system has a chance to softkick KS 3.1.4??

oscillik · 30 October 2018, 02:29

If you have an ACA card that can use mapROM, you may have wasted money buying ROMs — You can just use the mapROM facility to kick.

I did it by making a boot floppy, like how AmigaBill describes in his YouTube video here [ Show youtube player ]

Time stamp 21m36s

Once booted up, install 3.1.4, then copy the files over to the HD install and edit your Startup-Sequence to match.

bitter · 30 October 2018, 03:41

Quote:

Originally Posted by oscillik

If you have an ACA card that can use mapROM, you may have wasted money buying ROMs — You can just use the mapROM facility to kick.

I did it by making a boot floppy, like how AmigaBill describes in his YouTube video here [ Show youtube player ]

Time stamp 21m36s

Once booted up, install 3.1.4, then copy the files over to the HD install and edit your Startup-Sequence to match.

Thanks! I was making it way too complicated...

bitter · 30 October 2018, 22:13

Posting for others as I've learned my lesson the hard way - enabling long file names on boot partition is a sure way to require 3.1.4 ROMs prior to being able to use MapROM, as my 3.0 and my Cloanto 3.x ROMs both complain that DH0 is not a valid disk.

For now I'm just booting and doing MapROM from floppy, then warm booting into 3.1.4, until my physical ROMs come...

kolla · 30 October 2018, 23:18

Just make a tiny boot partition (for example with device-name BOOT:), using "regular old" FFS, put maprom, the 3.1.4 kickstart and bootctrl there and make a startup-sequence with...

Code:

BootControl INSTALL QUIET BOOTDEV=DH0 HIDDEN=BOOT
MapROM kickstart3.1.4

The bootcontrol will then hide the boot-partition and set DH0 as default boot partition from there on (until you enter early-startup, or power-off the system).

http://aminet.net/package/util/boot/bootctrl

thomas · 31 October 2018, 08:40

Quote:

Originally Posted by bitter

my 3.0 and my Cloanto 3.x ROMs both complain that DH0 is not a valid disk.

You have to load FastFileSystem with DosType 0x444f5307 into the Add/Update list of HDToolbox. That's all. It's the same method as with all third-party file systems.

There is no need for a physical 3.1.4 ROM or an invisible boot partition or even a boot floppy.

kolla · 31 October 2018, 08:52

That makes a whole lot more sense.

bitter · 31 October 2018, 11:21

Quote:

Originally Posted by thomas

You have to load FastFileSystem with DosType 0x444f5307 into the Add/Update list of HDToolbox. That's all. It's the same method as with all third-party file systems.

There is no need for a physical 3.1.4 ROM or an invisible boot partition or even a boot floppy.

Thanks Thomas, I've got a lot to learn, AmigaOS isn't a little C64 ...

daxb · 31 October 2018, 14:43

You can also put the new FFS into RDB. I don't know if the new FFS exist as file (module). If yes, loading it resident should also work.

30 October 2018, 02:07	#1
bitter Registered User Join Date: Oct 2018 Location: Fort Mill, SC, US Posts: 83	Installing WB 3.1.4 with MapROM (3.0 ROMs on board) Quick question (I hope). I've ordered some new ROMs, but while I'm waiting, my Amiga 1200 has 3.0 ROMs and I would like to install 3.1.4. I have ACA1221ec, which has MapROM functionality. How can I install it? I was thinking of: 1. Create a temporary bootable partition with 3.1 install 2. Use MapROM on it to softkick 3.1.4 KS into RAM 3. Install 3.1.4 into proper partition 4. Move the MapROM command onto the new partition Will this work, or will 3.1.4 complain on reboot before system has a chance to softkick KS 3.1.4??

30 October 2018, 23:18	#5
kolla Banned Join Date: Nov 2007 Location: Trondheim, Norway Posts: 1,893	Just make a tiny boot partition (for example with device-name BOOT:), using "regular old" FFS, put maprom, the 3.1.4 kickstart and bootctrl there and make a startup-sequence with... Code: BootControl INSTALL QUIET BOOTDEV=DH0 HIDDEN=BOOT MapROM kickstart3.1.4 The bootcontrol will then hide the boot-partition and set DH0 as default boot partition from there on (until you enter early-startup, or power-off the system). http://aminet.net/package/util/boot/bootctrl

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Split/join ROMs (kickstart ROMs)	NLS	support.Other	7	09 September 2018 23:54
Need help with installing KS3.1 ROMs in Amiga 3000D	salocinx	support.Hardware	8	06 September 2016 00:32
Wanted pinouts of 3000T roms and 3000 roms	Vars191	support.Hardware	1	20 November 2008 10:38
Installing A1200 ROMs - which is which?	alphonsus	support.Hardware	15	09 July 2008 17:45
WHDLoad and Maprom	fortytwo	project.WHDLoad	4	02 June 2007 21:50

30 October 2018, 02:29	#2
oscillik Registered User Join Date: Aug 2018 Location: UK Posts: 50	If you have an ACA card that can use mapROM, you may have wasted money buying ROMs — You can just use the mapROM facility to kick. I did it by making a boot floppy, like how AmigaBill describes in his YouTube video here [ Show youtube player ] Time stamp 21m36s Once booted up, install 3.1.4, then copy the files over to the HD install and edit your Startup-Sequence to match.

30 October 2018, 22:13	#4
bitter Registered User Join Date: Oct 2018 Location: Fort Mill, SC, US Posts: 83	Posting for others as I've learned my lesson the hard way - enabling long file names on boot partition is a sure way to require 3.1.4 ROMs prior to being able to use MapROM, as my 3.0 and my Cloanto 3.x ROMs both complain that DH0 is not a valid disk. For now I'm just booting and doing MapROM from floppy, then warm booting into 3.1.4, until my physical ROMs come...

31 October 2018, 08:52	#7
kolla Banned Join Date: Nov 2007 Location: Trondheim, Norway Posts: 1,893	That makes a whole lot more sense.

31 October 2018, 14:43	#9
daxb Registered User Join Date: Oct 2009 Location: Germany Posts: 3,303	You can also put the new FFS into RDB. I don't know if the new FFS exist as file (module). If yes, loading it resident should also work.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)