Creating a custom kickstart

[Glen M]

I'm going to create a custom kickstart to include EHIDE.DEVICE as required for the TF1230 to work properly.

Before I say anything further I am fully aware that I can buy 3.2.1 with this already added to it, I do not want to do that.

The plan here is to add the device driver to 3.1. I can use REMUS to modify the contents of the kickstart rom file but is it just as simple as drop device driver in there and it sorts itself out or is there code to modify to tell the Amiga theres a new driver in there too.

While I'm at it I'll update the scsi.device but is there anything else that worth updating or adding that won't break compatibility with the original 3.1 kickstart?

[Jope]

compactflash.device is romable as well, perhaps that could be a useful rom filler

[alexh]

The problem you will encounter is that it is already very full.

You can do what the A4000 Kickstart 3.1 ROM does and remove workbench.library and put it in LIBS: on the HDD if you need ROM space. (I think the same goes for icon.library but I've no experience with that)

You can go for a bigger Kickstart ROM (up from 512Kbytes) but going above a 512Kbyte ROM has issues with older accelerators MapROM function.

[lesta_smsc]

How does 3.2.1 add this? What has been removed? Why not just mimick it exactly?

[alexh]

Originally Posted by lesta_smsc

How does 3.2.1 add this? What has been removed? Why not just mimick it exactly?

They removed (at least) workbench.library and icons.library

[lesta_smsc]

Originally Posted by alexh

They removed (at least) workbench.library and icons.library

Is the exact list of what is included available or is this closed source?

[alexh]

Originally Posted by lesta_smsc

Is the exact list of what is included

No. To find out you would have to install RomSplit plus the various libraries it needs.

Open Kickstart 3.1 and make a list.

Open Kickstart 3.2.1 and make a list.

Compare lists.

[lesta_smsc]

Originally Posted by alexh

No. To find out you would have to install RomSplit plus the various libraries it needs.

Open Kickstart 3.1 and make a list.

Open Kickstart 3.2.1 and make a list.

Compare lists.

Is this against any rules. If not maybe could do a sticky thread with the ROMS I have if it helps others.

And others can share their own set ups (not sharing the ROM itself) and size/free space so it helps people get the most of custom roms.

[supaduper]

I did a step by step guide on how to add ehide.device to a 3.1 rom, it is some where on here

But a guy over on A1K made a OS 3.2.1 patcher, where you just need a genuine 3.2.1 rom , either from your hardware using say `Transrom` or getting it from `Amiga Forever` if you have the genuine disk.

Then run it through the patcher and it will spit out two Hi and Lo files that you just then byteswap and can burn to eproms

a link below

https://mega.nz/file/Np5HlZZZ#WjcdHi...xpQOuIRSOFxCGA


Link to my step by step guide Howto using Remus

http://eab.abime.net/showthread.php?...36#post1532936

[Glen M]

Originally Posted by supaduper

I did a step by step guide on how to add ehide.device to a 3.1 rom, it is some where on here

But a guy over on A1K made a OS 3.2.1 patcher, where you just need a genuine 3.2.1 rom , either from your hardware using say `Transrom` or getting it from `Amiga Forever` if you have the genuine disk.

Then run it through the patcher and it will spit out two Hi and Lo files that you just then byteswap and can burn to eproms

a link below

https://mega.nz/file/Np5HlZZZ#WjcdHi...xpQOuIRSOFxCGA


Link to my step by step guide Howto using Remus

http://eab.abime.net/showthread.php?...36#post1532936

This is fantastic, thanks it'll make my life a lot easier. Bit of a shame there isn't room for the driver along with workbench library but it is what it is.

[Jope]

Originally Posted by lesta_smsc

Is the exact list of what is included available or is this closed source?

I don't see why you couldn't get to look at the list.

https://drive.google.com/file/d/1xFu...ew?usp=sharing

[Daedalus]

Given that you're using an A1200, why not opt for 1MB ROMs instead (which the A1200 already supports), that way you can include everything you need... Yes, older accelerators only cover 512kB for MapROM, but you're using a TF card which doesn't itself have a physical MapROM feature so you'll be softkicking to do that anyway so the ROM size doesn't matter.

[Jope]

Originally Posted by lesta_smsc

Is this against any rules. If not maybe could do a sticky thread with the ROMS I have if it helps others.

And others can share their own set ups (not sharing the ROM itself) and size/free space so it helps people get the most of custom roms.

Are you sure this is really useful?

The amount of space in 3.1 and older is not very large. You would have to go for a 1MB ROM in most nontrivial cases (ie. only replacing scsi.device).

[Glen M]

Originally Posted by Daedalus

Given that you're using an A1200, why not opt for 1MB ROMs instead (which the A1200 already supports), that way you can include everything you need... Yes, older accelerators only cover 512kB for MapROM, but you're using a TF card which doesn't itself have a physical MapROM feature so you'll be softkicking to do that anyway so the ROM size doesn't matter.

Interesting thought.

Just for my information and so I understand this properly... The 1200s high and low roms combined are 512KB so therefore must 256kB each. The eproms I have here are 27C400s 512x8 so with the 2 of them is that the 1MB I need?

ROMs sizing is something that I swear I cannot get into my head, it always confuses me.

[supaduper]

Originally Posted by Glen M

Interesting thought.

Just for my information and so I understand this properly... The 1200s high and low roms combined are 512KB so therefore must 256kB each. The eproms I have here are 27C400s 512x8 so with the 2 of them is that the 1MB I need?

ROMs sizing is something that I swear I cannot get into my head, it always confuses me.

if you are going to use Remus I explain about the `Conacatenation`(doubling up) of the 256k files to 512k in my Howto so look at that for the exact explaination and how to do it using Eprom Hexxer, look at Steps 8, 9, 10 ..its easy fella

If using the 3.2.1 patcher do not worry that will spit out two 512k roms anyway

[Jope]

Originally Posted by Glen M

Just for my information and so I understand this properly... The 1200s high and low roms combined are 512KB so therefore must 256kB each. The eproms I have here are 27C400s 512x8 so with the 2 of them is that the 1MB I need?

Yes, this is true. When burning a normal sized 512k ROM to a pair of 27c400s, you are essentially splitting the 512k ROM first into two 256k pieces, then doubling each 256k piece so that they fill the chips.

In a 1MB ROM situation you would only split your created image and then burn to 27c400s without any doubling.

[Glen M]

I'm working with 3.1 here, I don't own 3.2.

What eprom chips do I need to write 1MB roms?

EDIT: just noticed its already answered.

[Jope]

Originally Posted by Glen M

What eprom chips do I need to write 1MB roms?

Two 27c400 chips. The version of the OS is irrelevant here, 1MB of data is 1MB of data.

[alexh]

Going to 1MB Kickstart ROM is not rocket science but IIRC is not as simple as just adding more files in Remus until you reach 1MB.

You must use the correct ROM modules and an exec that supports 1MB ROM e.g. CD32

[Glen M]

From what I gather the everything you need to build it is included within REMUS. Could be wrong, usually am. I'll have a play later and see how I get on.