Kickstart 3.1 Rom
Kickstart 3.1 ROM chip for the Amiga 500 / Amiga 500+ / Amiga 1500 and Amiga 2000. Update your Amiga with a Kickstart 3.1 ROM chip. Supplied with installation. Amiga workbench 1.3 (kickstart 3.1) booting with disk sound. Search results for amiga kickstart rom 1 3 download from Search.com. Do you have questions about amiga kickstart rom 1 3 download? I have yet to examine and compare.
The is a short video on how to load the correct kickstart 3.1 ROM on the MCC-216. You basically want to use the kickstart 3.1 ROM made as the ROM upgrade for the the Amiga 2000, Amiga 500, or Amiga 600. This version of the ROM is slightly different from the one released for the Amiga CD32, Amiga 1200, and Amiga 4000. It comes down to the fact the one set of these ROM's is for the 68000 or higher and the other you must use 68020 or higher to boot the ROM. The current core for the MCC-216 has a 68000 in the core design so it is flashed into the FPGA with the Amiga chipset. The MCC-216 is set up to run Amiga 500 games and the original Amiga chipset due the fact the majority of Amiga games are for this setup.
When dealing with workbench related tasks, kickstart 3.1 is a vast improvement over 1.3, If hardfile access is added in the future, running kickstart 3.1 including adding a selection on the main MCC menu makes sense at that point. 'music by audionautix.com'.
Legal Notice: In order to use the following guide, it's really important for you to own legally an Original Amiga OS 3.9 Installation, along with a legal Kickstart 3.1. Ok lets start.
To be able to run Remus and make the Custom ROMS the requirements are the following: Hardware: - Amiga OS3.0 and above. At least 1MB of free RAM Software: - (everyone has it anyway) -The MUI libraries bellow. (although optional) - (used by Arexx scripts) - (used by Arexx scripts) - (for Anti-Virus usage) Or you can get ALL the above in the following archive that I putted on my Dropbox Once we install everything. We need to run the program ROMsplit in order for us to extract the modules from our Kickstart 3.1 ROM and from our BB2 ROM update (DEVS: AmigaOS ROM Update).
So we either click 'Grab ROM' for ROMsplit getting the contents from our Kickstart 3.1 ROM. We search from our Partitions to find a legal 3.1 ROM in file for contents to appear. (1st pic has 3.9 Update while 2nd pic has the 3.1 Kickstart).
Lets get a bit familiar with the interface a bit. Left side below toolbar are the contents that we're gonna put on our future ROM 2.
Right side below toolbar are the folders/files from which we're gonna choose what to put into the left list. In this screenshot for example I have in the right side a folder in which I have the following folders: - 40.68(A1200) - This is an extract of my A1200's 3.1 Kickstart ROM - 44.57ROMUpdate(3.9bb2) - This is an extract from 'AmigaOS ROM Update) - BlizKick - This is a copy of DEVS: Modules that were installed with BlizKick In next step, we're creating a new Normal Kickstart by pressing the button 'New' in toolbar, and we insert the info from the following screenshot. As an example, I'm attaching the order of my files based on folder name. IMPORTANT: YOU NEED to insert 'Exec' first and then '1MBROM' module or else the Kickstart won't work at all! As you will realize, we putted all the Modules of Kickstart 3.1 (with the same order as it existed on the Kickstart itself) but we changed some modules with the new ones from the extracted BB2 3.9 Update. That way we have a nice new Custom 3.9 Kickstart missing though Workbench.library and Intuition.library.
No worries, we left them to save space, and we're gonna put them in the extended Kickstart (Hell yeah! 1MB ROM ftw) in a while. Now, we're gonna click the button 'Compile' in toolbar that will make the Kickstart under RAM:3.9normal.rom (if you kept the same name as the screenshot under 'Settings' tab like mine) (It's a good idea to save the template of your Normal Kickstart for future use like 'MyCustomKickstart39Normal.rpf') Time for the extended Kickstart ROM now. We're clicking on 'New' in toolbar and we insert the info from the following screenshot. As an example, I'm attaching the order of my files based on folder name. IMPORTANT: YOU NEED to insert ROMHeader and DummyCDstrap (only if you use an BPPC or CSPPC accelerator) first, or else the Kickstart won't work at all!. Others/RomHeader/romheader.
Others/DummyCDstrap/DummyCDstrap (This is optional module for BPPC and CSPPC accelerators). System:Libs/workbench.library. DH0: Devs/morelibspacemodule (This is AfA OS Morelibspace Module to avoid declaring it in Startup-Sequence!). DH0: Devs/Modules/BPPCFix (This is BPPCFix Module to avoid declaring it in Startup-Sequence!). The last step asks us if Remus should perform a ByteSwap operation for the ROM. Our choice will be based on the following: - If you wanna burn the image to a Real Kickstart Image: then choose YES, since we won't need to byteswap it in the EPROM Programmer application - since Amiga requires ByteSwapping procedure for its ROMS). If you wanna use the image to kick it via MapROM (like for example on ACA6x0/ACA12xx accelerators via ACATune utility): then choose NO, since ACATune and general MapROM applications use normal (non-ByteSwapped) images.
In that case. Your ROM image is ready to be used so you can kick it right away by using the following line in you Startup-Sequence (according you have an ACA6x0/ACA12xx with ACATune utility installed). You can comment them also if you included them in the Custom 3.9 ROM. That's all folks.
Kickstart Rom 3.1 Image File
I hope this guide will be useful to someone else but me. P.S. I'm attaching an example of my Custom Kickstart Remus files (renamed to.txt). You just need to alter the location of the folders if you wanna try them out. EDIT: Since I was tinkering with creating a Custom Kickstart 3.9 for an Amiga A4000D I found and solved the following problems: Problem: A4000 doesn't support 512KB ROMS which can be a problem for custom 1MB ROMS Solution: Create your custom rom as a 512KB as my guide says but you exclude the 1MBROM module (if you use the 3.1 exec, or 3.9 exec).
Kickstart 3.1 Rom
We'll leave outside though Workbench.library which is rather big and can't be left out (can be put in hard drive's LIBS: folder with no problem). You'd should include the module in your ROM as well as it's a module that tells the system that the Workbench.library exists in SYS:Libs Problem: Since we're not making an 1MB ROM (we'll only make Normal ROM without Extended), we can't actually use Doobrey's awesome Make1MBROM Arexx script (since it combines normal/extended, and splits and byteswaps according to your need). Using utilities like most guys suggest in forums (WinHex) is cool, but it was certainly uncool for me to register WinHex (45 euro) just to dissect the 512KB ROM file to even/odd files. Solution: After checking Doobrey's script, I managed to realise that you only need to use his tool SplitRROMImage that exists in 'Tools' folder under Remus installation folder. The declaration of the command is fairly simple: SplitROMImage SWAP (SWAP is optional and it only ByteSwaps your files for using it under your Eprom Burner) In my example: SplitROMIMage kick39a4000.rom SWAP.created 2 files:. kick39a4000.rom.hi (256kb). kick39a4000.rom.lo (256kb) Now you can get these files and burn them to your programer (in 256KB EPROMS).
Download Kickstart Rom 3.1
Note: If you want to write your custom Kickstart to 512KB EPROMS (like 27C400) you'd need to double the HI and LO images (since they are 256KB in size) before burning them or else the Kickstart won't work. To double these images, the easiest way is to use the DOS Command Prompt like this: C: copy kick39a4000.rom.hi /B+kick39a4000.rom.hi /B kick39a4000512.rom.hi /B C: copy kick39a4000.rom.lo /B+kick39a4000.rom.lo /B kick39a4000512.rom.lo /B That way you created 2 new files ( kick39a4000512.rom.hi and kick39a4000512.rom.lo ) which now you can burn to the 27C400 EPROMS just fine:).