Custom Kickstart Rom

[watsonfmly]

Good day.

I tried following mfilos guide to create a custom Kickstart:
http://www.mfilos.com/2010/12/guide-create-and-burn-custom-kickstart.html

I didn't get very far.

I installed all of the software as required on my real Amiga 2000, when I run RomSplit it fails:
Unsupported ROM (Unidentified ROM)

My Setup:
Amiga 2000
Kickstart Real 3.1 from AmigaKit (version 40.63)
OS 3.9 with BB1, BB2 and ClassicWB installed.


Things I have tried:
I dumped the ROM to an image using my eprom burner, and tried using that in WinUAE. It fails with "HALT1" in the status bar.
I ran WinUAE (same install as my A2000), with the AmigaForever 3.1 ROM, and it works fine.

Does anyone have any idea why I can't dump my real ROM?

Thanks.

 

[roy_bates]

i dont think you need to split the rom on a 2000 its one kickstart?


what was you doing whan you was reading the rom into the pc etc?

what settings was you using for the rom? 27c400?

 

[watsonfmly]

Romsplit lets you dump the rom, and split out the modules. It comes out as one rom.

When dumping the rom, i was simply clicking grab rom. It fails immediately.

When reading the physical rom into my pc, i had the reader set for 27c400. After reading the rom, i could look at it on the data tab, and it looked like a kickstart.

I will perform more tests later today.

Thanks.

 

[mfilos]

First of all...
Dumping a real ROM from your burner gives you a ByteSwapped ROM which simply doesn't work under WinUAE or with using RomSplit.
You need to ByteSwap the ROM once you grab it, and then save it to be able to use it.

Apart from that, running RomSplit in a Genuine 3.1 ROM should not give you a single error.

 

[watsonfmly]

Sorry I didn't get back to this very fast. I have a lot of irons in the fire.

I am re-trying to do the custom OS3.9 ROM again....
These questions are for mfilos (since I am following your instructions).

1. On an A2000, which exec_45.20 should I use (A2000 was not listed. There was A1200-A500,A3000,A4000,CD32 and unknown).

2. Which bootmenu should I use? I have a 68040 card. The only choices were 68020, A500 and CD32.

3. I can only deal with a 512K ROM (Amiga 2000 - one chip). Putting in all the files in your list (adding intuition.library and workbench.library) didn't fit.
What can I drop (if anything)?

4. Since I am doing a 512K ROM, do I need the 1MB_ROM file?

5. You had system:devs/scsi.device. I want to make sure i have the proper one. When using WinUAE, I can't find the file. When using my A2000, will it be the right one?

6. When loading all of the original files to the REMUS program, I only have 492 bytes free. Will it be possible for me to create a custom ROM in such a small chip?

7. Finally, I tried to find this information, can the Amiga 2000 support a larger ROM?

I really appreciate any help you can offer.

Thank you!

 

[mfilos]

1. You use exec_45.20(A1200-A500)

2. There is no problem as either will work just fine. As you have an accelerator, I'd suggest the bootmenu_44.7(68020).

3. Since you're using OS3.9, you can easily put out Workbench.library and if you need even more space Icon.library as well. Don't forget of course to copy them to LIBS accordingly though before rebooting!

4. Of course not

5. I had /Devs/scsi.device because at the time there I had putted an updated version (not in the BB2 update). BB2's scsi.device is 43.43. There are other versions greater than BB2's like 43.45 (patched by Toni & Piru), 43.47 (patched by Cosmos), 44.2 (patched by Doobrey) which you can use instead.

6. Certainly because some newer modules have less size than the originals (as optimized) and also you can leave outside the Workbench.library and Icon.library that can save you lots of space.

7. Yes, it can support a larger ROM with a little mod (getting one signal from Garry). Will try and find out the mod and will report back.

Good luck and have fun

 

[demolition]

I guess it depends on which HDD controller he is using whether he will need scsi.device at all? Does A2000 have a controller using scsi.device?

 

[watsonfmly]

@mfilos
Thank you so much! I am understanding this more and more.

Your tutorial ia awesome!

@demolition

I have a Buddha IDE card thar uses scsi.device.

I'll work on this later (it is 4am here).


Thank you again!!!!!!!!!!!!!!!

 

[FOL]

You dont need to add buddha modules as they are in the buddha rom on boot.
So that will save space if you were thinking about putting them in there.

 

[watsonfmly]

I was able to build the rom, and boot it with winuae.

Yay



Then i tried to burn it (byte swapped of course)

My writer stopped at 0x002000.

Sigh.

It turns out that my new programmer has a problem.

I can write byte filled images (all aa, or whatever), but not my (or any other) image.

Sigh.

I have opened a case with the manufacturer.

It is a GQ-4x by the way.

Have a good day.

 

[ancalimon]

We will be writing roms for our Amigas with a couple of friends once we put everything in order.

For my A4000T, do you think I should go for a Zorro based flashable rom card instead of replacing the original roms? I guess rom size on A4000T is limited to 2x256 and larger ones can not be used?

I really need to especially update scsi.device since it can't boot from ide hdds at the moment unless I load a patched one from floppy.

Also do you known if there are any updated rom parts that would cause problems with AmigaOS 3.1?