PDA

View Full Version : Guide: How to burn a Custom Kickstart 3.9 (incl. 1MB ROM)



Pages : [1] 2

mfilos
12th December 2010, 23:24
My fellow Amibayers...
As I said in a previous post (http://www.amibay.com/showpost.php?p=125564&postcount=65) and since I succesfuly managed to burn a custom 3.9 Kickstart including BB2 ROM Update + AfA OS plus some other goodies, I decided to make a step-by-step HOW-TO including not only screenshots from Doobrey's Remus software, but even from EPROM Burner's software (Willem in my case).
(Zetr0, merlinkv, stachu100 there you go :))

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:
- MUI 3.8 (http://aminet.net/util/libs/mui38usr.lha) (everyone has it anyway)

- Remus 1.0 (rc23) + ROMsplit 1.0 (rc15) (http://www.doobreynet.co.uk/files/remus/Remus_rc23.lha)
- Remus 1.0 (rc35 - update 27/07/2010) (http://www.doobreynet.co.uk/files/remus/Remus_rc35.lha)
- Remus 1.0 (rc36 - update 04/08/2011) (http://dl.dropbox.com/u/939939/Remus_rc36.lha)

- BlizKick 1.24 (http://aminet.net/util/boot/BlizKick.lha)

- The MUI libraries bellow
* Nlist.mcc (http://sourceforge.net/projects/nlist-classes/)
* BetterString.mcc (http://sourceforge.net/projects/bstring-mcc/)
* ToolBar.mcc (http://sourceforge.net/projects/toolbar-mcc/)
* TheBar.mcc (http://sourceforge.net/projects/thebar/)
* PopupMenu.library (http://aminet.net/package/util/libs/pmuser)
* UrlText.mcc (http://alfie.altervista.org/downloads/MCC_Urltext.lha) (although optional)
- rxasl.library (http://alfie.altervista.org/downloads/rxasl.lha) (used by Arexx scripts)
- rmh.library (http://alfie.altervista.org/downloads/rmh.lha) (used by Arexx scripts)
- xvs.library (http://aminet.net/util/virus/xvslibrary.lha) (for Anti-Virus usage)
Or you can get ALL the above in the following archive that I putted on my Dropbox here (http://dl.dropbox.com/u/939939/Remus_Required_Files.lha)

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 or... 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)

http://img641.imageshack.us/img641/5959/screen1mo.th.jpg (http://img641.imageshack.us/i/screen1mo.jpg/) http://img522.imageshack.us/img522/91/screen2wy.th.jpg (http://img522.imageshack.us/i/screen2wy.jpg/)

Once we have the contents loaded we click "Select All" for all contents to be selected and then we click "Extract file(s)".
Note: A folder will be created under DEVS: Modules/<Auto_Name_Depending_On_Kickstart_Version>


Next, we'll be running "Remus" which is the program which will help us make an image of our future custom Kickstart.

http://img46.imageshack.us/img46/8595/screen3zo.th.jpg (http://img46.imageshack.us/i/screen3zo.jpg/)

Lets get a bit familiar with the interface a bit...
1. 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.57_ROMUpdate(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:

http://img151.imageshack.us/img151/3955/screen4l.th.jpg (http://img151.imageshack.us/i/screen4l.jpg/)

Now, we only need to add the required files from our folders to the left side list.

http://img213.imageshack.us/img213/6718/screen5d.th.jpg (http://img213.imageshack.us/i/screen5d.jpg/)

As an example, I'm attaching the order of my files based on folder name.

IMPORTANT: YOU NEED to insert "Exec" first and then "1MB_ROM" module or else the Kickstart won't work at all!

--> Modules/44.57_ROMUpdate(3.9bb2)/exec_45.20(A1200-A500)
--> Others/Blizkick/1MB_ROM
--> Modules/40.68(A1200)/audio.device_37.10
--> Modules/40.68(A1200)/battclock.resource_39.3
--> Modules/40.68(A1200)/battmem.resource_39.2
--> Modules/44.57_ROMUpdate(3.9bb2)/bootmenu_44.7(68020)
--> Modules/40.68(A1200)/card.resource_40.4
--> Modules/40.68(A1200)/carddisk.resource_40.1
--> Modules/40.68(A1200)/cia.resource_39.1
--> Modules/40.68(A1200)/con-handler_40.2
--> Modules/44.57_ROMUpdate(3.9bb2)/console.device_44.8
--> Modules/40.68(A1200)/disk.resource_37.2
--> Modules/40.68(A1200)/dos.library_40.3
--> Modules/40.68(A1200)/expansion_40.2(A1200)
--> Modules/44.57_ROMUpdate(3.9bb2)/filesystem.resource_45.10
--> Modules/44.57_ROMUpdate(3.9bb2)/filesystem_45.13
--> Modules/40.68(A1200)/gadtools.library_40.4
--> Modules/40.68(A1200)/graphics.lib_40.24(AGA)
--> Modules/40.68(A1200)/icon.library_40.1
--> Modules/40.68(A1200)/input_40.1
--> Modules/40.68(A1200)/keymap.library_40.4
--> Modules/40.68(A1200)/layers.library_40.1
--> LIBS:mathffp.library (These are my regged HSMathLibs that I included)
--> LIBS:mathieeesingbas.library (These are my regged HSMathLibs that I included)
--> Modules/40.68(A1200)/misc.resource_37.1
--> Modules/40.68(A1200)/potgo.resource_37.4
--> Modules/44.57_ROMUpdate(3.9bb2)/ram-handler_44.24_NoBss
--> Modules/40.68(A1200)/ramdrive_39.35
--> Modules/40.68(A1200)/ramlib_40.2
--> Modules/40.68(A1200)/romboot_40.1
--> System: Devs/scsi.device
--> Modules/44.57_ROMUpdate(3.9bb2)/shell_45.7
--> Modules/40.68(A1200)/timer.device_39.4
--> Modules/40.68(A1200)/trackdisk.device_40.1
--> Modules/40.68(A1200)/utility.library_40.1(020)
--> Modules/40.68(A1200)/wbtask_39.1


Okey dokey...
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 "MyCustomKickstart39_Normal.rpf")


Time for the extended Kickstart ROM now. We're clicking on "New" in toolbar and we insert the info from the following screenshot:

http://img5.imageshack.us/img5/9767/screen6g.th.jpg (http://img5.imageshack.us/i/screen6g.jpg/)

As we did before we need to add the required remaining files from our folders on the right to the right side modules.

http://img526.imageshack.us/img526/2128/screen7h.th.jpg (http://img526.imageshack.us/i/screen7h.jpg/)

As an example, I'm attaching the order of my files based on folder name.

IMPORTANT: YOU NEED to insert ROMHeader and DummyCDstrap first or else the Kickstart won't work at all!

--> Others/RomHeader/romheader
--> Others/DummyCDstrap/DummyCDstrap
--> Modules/40.68(A1200)/intuition.library_40.85
--> System:Libs/workbench.library
--> DH0: Devs/morelibspace_module (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!)

Cool! That was it :thumbsup:
Now we only need to click "Compile" in the toolbar for the file to be created under RAM:3.9extended.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 Extended Kickstart for future use like "MyCustomKickstart39_Extended.rpf")

Now we have both the Normal+Extended ROMS under RAM:

http://img593.imageshack.us/img593/1483/screen8z.th.jpg (http://img593.imageshack.us/i/screen8z.jpg/)


You can now easily check if you newly created Custom 3.9 Kickstart are working under WinUAE by inserting the ROMS in the corresponding area :)

http://img560.imageshack.us/img560/338/winuae1.th.jpg (http://img560.imageshack.us/i/winuae1.jpg/) http://img815.imageshack.us/img815/4172/winuae2.th.jpg (http://img815.imageshack.us/i/winuae2.jpg/)


Cool isn't it? :bowdown:

If you wanted this Custom Kickstart for your WinUAE environment then your work is done so congratulations and cya later :)

If you want this Custom Kickstart for your Classic Amiga... there's work to be done! Fear NOT though!... LETS GO!


We were back at the point where we had the 2xROMS in RAM Disk. From Remus now, we click the button "ARexx" and then on the submenu entry "1MB_ROM.rx". By pressing this option a window will appear asking our Amiga Model.

http://img163.imageshack.us/img163/453/screen9e.th.jpg (http://img163.imageshack.us/i/screen9e.jpg/)

That is done just for Remus to split the ROM into 2 pieces (for A1200/A4000 etc) or into 1 piece (for A500/600/2000 etc).
Note: If you make custom kickstart for using under MapROM environments (like ACA630/ACA630 via ACATune utility) better choose A500/600/2000 to only get 1xOutput file instead of 2x that A1200/A4000 choice will

Next steps are selecting the Normal ROM image, the Extended ROM image and last but not least... The location+name where the "To-Burn-Image(s)" will be put...

http://img46.imageshack.us/img46/5154/screen10w.th.jpg (http://img46.imageshack.us/i/screen10w.jpg/) http://img140.imageshack.us/img140/4170/screen11d.th.jpg (http://img140.imageshack.us/i/screen11d.jpg/) http://img213.imageshack.us/img213/6091/screen12s.th.jpg (http://img213.imageshack.us/i/screen12s.jpg/)


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 ACA630/ACA1230 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 ACA603/ACA1230 with ACATune utility installed):


C:ACATune -maprom <path & name of the kick file> <rest options> >NIL:
for example:
C:ACATune -maprom Devs:kick39_mfilos.rom -cache on -burst on >NIL:
http://img213.imageshack.us/img213/8873/screen13m.th.jpg (http://img213.imageshack.us/i/screen13m.jpg/)


If we done everything as intended... We must have 2x Files (since we choose A1200)

http://img27.imageshack.us/img27/5769/screen14nk.th.jpg (http://img27.imageshack.us/i/screen14nk.jpg/)

A you'll see on the screenshot the files that Remus created based on the filename that I gave was:
- mfilos_Custom_39.rom_LO.bin
- mfilos_Custom_39.rom_HI.bin


Bye bye Amiga... Time to use our trusted old PC where we have an El'Cheapo Parallel Willem Programmer.

http://img252.imageshack.us/img252/2798/screen15a.th.jpg (http://img252.imageshack.us/i/screen15a.jpg/) http://img560.imageshack.us/img560/4895/screen16.th.jpg (http://img560.imageshack.us/i/screen16.jpg/)


I won't go as deep as How to Install/Setup the Willem... But we need to choose to burn EPROM of type (at least in my example 27C400)

http://img502.imageshack.us/img502/8488/screen17h.th.jpg (http://img502.imageshack.us/i/screen17h.jpg/)


Next step is to "Load" one of our files (for example the 3.9_LO.bin)

http://img440.imageshack.us/img440/4637/screen18y.th.jpg (http://img440.imageshack.us/i/screen18y.jpg/)


Yey! That was it. File is loaded succesfully so now it's time for us to BURN it by clicking the designated button in the toolbar!

http://img213.imageshack.us/img213/660/screen19f.th.jpg (http://img213.imageshack.us/i/screen19f.jpg/)

Important: Make sure you're burning an erased by UV EPROM


Next step is to load the next file (for example the 3.9_HI.bin)

http://img69.imageshack.us/img69/8580/screen20i.th.jpg (http://img69.imageshack.us/i/screen20i.jpg/)

And repeat the procedure of Burning it.


--- VOILA! That's it dudes! :thumbsup::thumbsup::thumbsup: ---

Ok for testing your Kickstarts now make sure that...

For A1200
- You insert the EPROM burned from LO file into the U6B Kickstart socket (top)
- You insert the EPROM burned from HI file into the U6A Kickstart socket (bottom)

For A3000 - thx to drbrain for the clarification
- You insert the EPROM burned from LO file into the U181 Kickstart socket (top)
- You insert the EPROM burned from HI file into the U180 Kickstart socket (bottom)

For A4000 - thx to drbrain for the clarification
- You insert the EPROM burned from LO file into the U176 Kickstart socket (bottom)
- You insert the EPROM burned from HI file into the U175 Kickstart socket (top)


Time to change some stuff:
- Move the file in DEVS: "AmigaOS ROM Update" to another folder, or Rename it to something else.
- Comment the line you have for SetPatch and insert the following SetPatch declaration instead:
C:SetPatch NOROMUPDATE QUIET

If you had other declarations like me for example:
- C:BPPCFix install >NIL:
or
- C:Morelibspace
you can comment them also if you included them in the Custom 3.9 ROM.


That's all folks. 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.
1. Kickstart 3.9 A1200 Normal ROM Image] (http://dl.dropbox.com/u/939939/Guides/39normal.rpf.txt)
2. Kickstart 3.9 A1200 Extended ROM Image] (http://dl.dropbox.com/u/939939/Guides/39extended.rpf.txt)

-----------------------------------------------------------

EDIT:
P.S.2. 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 1MB_ROM module (if you use the 3.1 exec, or 3.9 exec since Cosmos Exec doesnt' need it anyway).
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 WBFind (http://wt.exotica.org.uk/files/test/WT31.lzx) 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 Make_1MB_ROM 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 <your_512kb_rom_name> SWAP
(SWAP is optional and it only ByteSwaps your files for using it under your Eprom Burner)

In my example: SplitROMIMage kick39_a4000.rom SWAP
...created 2 files:
- kick39_a4000.rom.hi (256kb)
- kick39_a4000.rom.lo (256kb)

Now you can get these files and burn them to your programer (in 256KB EPROMS).

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 kick39_a4000.rom.hi /B+kick39_a4000.rom.hi /B kick39_a4000_512.rom.hi /B
C:\> copy kick39_a4000.rom.lo /B+kick39_a4000.rom.lo /B kick39_a4000_512.rom.lo /B


That way you created 2 new files (kick39_a4000_512.rom.hi and kick39_a4000_512.rom.lo) which now you can burn to the 27C400 EPROMS just fine :)


Disclaimer: I haven't burned this ROMS myself to use them on a real A4000 but others did (http://www.amibay.com/showpost.php?p=268465&postcount=170) and it works just fine :)

stachu100
12th December 2010, 23:29
Not read till end yet, but BIG BIG Thank You my Friend!!! :bowdown::bowdown::bowdown:
This is my next task in "to do" list.:)

mfilos
12th December 2010, 23:36
No problem Stanis my friend. I love helping out :)
This guide took a lot of TIME... I hope peepz like it.

r0jaws
12th December 2010, 23:37
Awesome, I know a chap with an EPROM burner. I may have to butter him up with some choccy hob nobs. :D

fatbob_gb
12th December 2010, 23:40
Excellent timing - I have only just got some eproms delivered from Hong Kong

jvdbossc
12th December 2010, 23:44
I do not have the right equipment/skills, but was wondering how it was done anyhow, so it is in my bookmarks. Thanks a lot this is great info :thumbsup: I am sure this is usefull for a lot of people!

mfilos
12th December 2010, 23:48
@jvdbossc
You don't need to have the gear mate.
You can make the .bin files from Remus and then buy EPROMs from eBay asking the seller to burn the images that you will send him :)
I done it in the past. He will ask you if you want ByteSwapping (that you won't if you follow the guide) and you're set to go.

StrontiumDog
13th December 2010, 02:43
I brought my 3.9 ROM's from one of the traders here - less hassle and oh so cheap if you don't have a EPROM burner :D

Zetr0
13th December 2010, 02:59
@Marios

Fantastic post my friend, its certainly worth the sticky!!!

I have some bits you can add that will improve your 3.9 ROM (like reducing the IDE wait to 9 seconds instead of 30 - should you not have an IDE device attached) - its a simple blizkick module but a damn effective one =D


@r0jaws

Awesome, I know a chap with an EPROM burner. I may have to butter him up with some choccy hob nobs. :D

yes.... chocy hobnobs (http://www.littleshamrocks.com/image-files/hob-nobs-combo.gif)..... the alternate currency in the united kingdom =D

I will need to do some hackery as my Power supply for my programmer is dead.... its dead dave.... its all dead... it struggles to give even 1.2 Amps on the +12.... (we needs the 2 amps for proper programming =D)

rkauer
13th December 2010, 04:36
Zetr0, my good friend, how about just deriving the +12V from inside the pc to the programmer?

I'm pretty sure the pc will have a bit more than 2A available on the +12V rail...

mfilos
13th December 2010, 07:09
@blankstare
Yes I know mate. I had the same 3.9 Kickstart myself before I got a programmer :)
The difference is that the ready to use Kicks... don't have the modules I need (like AfA OS or my HSMathLibs etc), plus is more generic for all Amigas. My Kick is only 1200 usable lol.

@Zetr0
Thanks for the good works my friend.
I believe you mean SpeedIDE? I never tried it tbh, but it might certainly worth the test! Thanks.
I tried for fun the NoClick module as well to get rid of AntiClick but it said something about required another version of TrackDisk.device... So I thought to leave it as it it without it :)

keropi
13th December 2010, 07:44
...and I thought your woman just beat you sensless because you spent too much time in retro stuff... I guess I was wrong :lol:
nice guide M!!!!

rkauer
13th December 2010, 20:17
My friend, the only drawback on 3.9 ROM is most of the modules goes to chip RAM if you don't autoconfig the FAST RAM prior to start to load they.

salaxi54
13th December 2010, 21:04
Most interesting Mario! :thumbsup: I'm sure that plenty of users (of various Ami-forums) will find this helpfull. :)

Phipscube
13th December 2010, 21:25
Fantastic work Marios, very well written guide too. I was going to buy some pre configured 3.9 Roms, but I have access to a programmer and think I will give making my own a shot, its much more fun :) thanks again mate, stellar stuff! :thumbsup:

Amigafanboi
15th January 2011, 21:00
Just going to have a go at this...wish me luck!

Amigafanboi
15th January 2011, 23:28
Worked perfectly for me, thanks for a great guide. :thumbsup:

mfilos
16th January 2011, 00:32
I'm glad it worked for ya mate! It's really easy if you try it 1-2 times :)
I'm making custom kickstarts from time to time to check them via MapROM of ACA630/ACA1230 and they work so quick and fine.

BTW, I noticed that some extra BlizKick modules like SpeedyIDE, BBlank or NoClick despite they can be putted on the extended ROM image, they compile process fails until you removed them. If you insert them into the Standard ROM image, then the compile executes just fine, and the ROMS works perfectly!

EDIT:
Also added some extra info regarding making custom kickstarts for using them under ACA630/ACA1230 via MapROM feature of ACATune utility.

czarek
18th January 2011, 12:06
Mate is it also possible to get rid of PrepareEmul? I was thinking how does it work in 3.9 BB2 which no longer needs external program to run ShapeShifter.
It would be awesome to have it all in ROM and start system without restarting it in between, especially that Blizzard 2060 is copying whole ROM to RAM on startup anyways.

mfilos
18th January 2011, 14:22
BlizKick has an PrepareEmul module that can be loaded into a Custom Kickstart (AFAIK), unless it conflicts with something from the BB2+ patches.
Also, Piru's Exec44, patches the Memory in that way that PrepareEmul is not needed anymore.

I haven't checked both methods but will gief them a try @ some point since I plan to use Mac emulation in both my machines.

Foul
15th February 2011, 20:58
@blankstare
I tried for fun the NoClick module as well to get rid of AntiClick but it said something about required another version of TrackDisk.device... So I thought to leave it as it it without it :)

seems to be working with this : http://aminet.net/package/disk/misc/floppy43

edit : not working :\

edit2: noway to delete entire post ? :blink:

mfilos
23rd February 2011, 23:34
Btw...
Cosmos new Exec.library including lotsa other stuff, includes a new trackdisk.device for no clicking (bye bye AntiClickers) along with exec.library for non having to use PrepareEmul for ShapeShifter usage :)

That will make El'Steavo happy :)

mfilos
25th February 2011, 10:01
Hey guys,

I thought of sharing some knowledge from last night cause some might find it useful.

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 1MB_ROM module (if you use the 3.1 exec, or 3.9 exec since Cosmos Exec doesnt' need it anyway).
We'll leave outside though Icon.library and Workbench.library which are big and can't be left out (can be put in hard drive's LIBS: folder with no problem). That leave us all the space we need for extra modules and patches!!!

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 Make_1MB_ROM 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 <your_512kb_rom_name> SWAP
(SWAP is optional and it only ByteSwaps your files for using it under your Eprom Burner)

In my example: SplitROMIMage kick39_a4000.rom SWAP
...created 2 files:
- kick39_a4000.rom.hi (256kb)
- kick39_a4000.rom.lo (256kb)

Now you can get these files and burn them to your programer.

Disclaimer: I haven't burned this ROMS myself to use them on a real A4000 since I don't have any but theoretically it must be ok.

Justin
25th February 2011, 10:34
brilliant stuff, thanks for the share dude:thumbsup:

rkauer
26th February 2011, 02:14
Here comes another sticky thread to the forum. Well done, Marios!:thumbsup:

mfilos
18th March 2011, 15:36
Since I use for long time a custom kickstart 3.9 on my beloved A600 with ACA630 (kicked via MapROM) I thought of sharing my info and modules with you in case you wanna try that yourself.

The kickstart contains all the normal modules from Kickstart 3.1 (A500/600/2000) but with the following extra:


- Exec 45.24 (instead of 40.10) --> OS3.9 BB4
- BootMenu 44.7 68020 (instead of 40.5) --> OS3.9 BB2
- Card.resource 40.5 (instead of 40.4) --> OS3.9 BB4
- Console.device 44.10 (instead of 40.2) --> OS3.9 BB3
- Datatypes.library 44.48 (instead of 44.47) --> OS3.9 BB4
- Filesystem.resource 45.10 (instead of 40.1) --> OS3.9 BB2
- FastFilesystem 45.16 (instead of 40.1) --> OS3.9 BB4
- Graphics.library 42.8b11-02 (instead of 40.24) --> OS3.9 BB4
- Icon.library 46.4.191 (instead of 40.1) --> OS3.9 BB4
- Misc.resource 37.2 (instead of 37.1) --> OS3.9 BB4
- RAM Handler 44.24 (instead of 39.4) --> OS3.9 BB3
- Ramlib 40.3 (instead of 40.2) --> OS3.9 BB4
- Romheader 45.21 (instead of BlizKick module) --> OS3.9 BB4
- SCSI.device 43.46b4 (instead of 40.5) --> OS3.9 BB4
- Shell 45.27 (instead of 40.2) --> OS3.9 BB3
- Trackdisk.device 40.2 (instead of 40.1) --> OS3.9 BB4
- Workbench.library 45.131 (instead of 40.5) --> OS3.9 BB3
- BBlank --> For Blank Borders
- HRTModule --> Action Replay clone
using ACA's NMI header
The only change comparing to the initial Guide procedure is the fact that you don't need the 1MB_ROM module (on the normal ROM) since Cosmos's new exec.library doesn't require it. Also you need to replace the old Romheader (on the extended ROM) with the new Romheader from Cosmos's exec.library archive and also remove the DummyCDstrap module since it's only needed for BlizzardPPC and CyberStormPPC.
HRTModule is a really cool module that is in fact HRTMon romable! Using ACA630's NMI header (if you have the module loaded on the kickstart) with a switch, you can have the HRTMon (like Action Replay) anytime!!! If it's in ROM you can even call it in Early Startup Menu :ninja:
Ofc it's a matter of choice if you need it or not.

To help you even more, I'm attaching the Normal+Extended Remus files to check them out (don't forget to remove the .txt extension from them if you decide to load them to Remus). Ofc they won't work out of the box since the paths of my own files may be different from your own. Just open them with an Editor though to understand the order and how I load the files into Remus :)

Once you finish with the Final ROM file according to the guide:
Rename the following files from your libraries folder for new ones to be loaded on boot:
- Datatypes.library
- Icon.library
- Workbench.library

Note: For BBlank to work you can't have other Border Blanking applications run at the same time!!!


Enjoy :thumbsup:

Cosmos
18th March 2011, 17:20
DummyCDstrap is NEEDED ONLY for BlizzardPPC and CyberStormPPC


@mfilos

You can completly remove ROMUpdate 44.57

mfilos
18th March 2011, 18:02
Cosmos my friend, thanks for the clarifications :) Will edit.

Phipscube
31st March 2011, 00:37
I've managed to roll my own 3.9 ROMS now with the help of this purely awesome guide of yours Marios, thanks for all your advice and help over PM too, Cheers mate! :)

Gulliver
31st March 2011, 04:02
If anyone is looking for a specific alternative rom module list, just surf to:

http://lilliput.amiga-projects.net/ROM_modules.htm

mfilos
31st March 2011, 07:11
@Phipscube
Cheers mate. I'm glad I could help ya out. Making it on your own seriously rox :D

@Gulliver
Nice that you shared the link here as well mate. I have it on my Bookmarks for some time now!
Thank you for your hard work Gulliver my friend. \o/

Phipscube
31st March 2011, 21:26
It does mate, its a great feeling seeing it boot up :)

@Gulliver, I've seen that link too, its Custom ROM heaven :D problem for me is I have not much clue just yet what can mix with what. I'm trying to figure out if I can make my ROMS even more awesome, but i'm not so knowledgeable with all the modules and how they work with each other. But anyway its a great page for anyone wanting to make a really up to date set of ROMS :)

Cosmos
2nd April 2011, 02:55
@mfilos

You can remove the con handler and install this version of KingCON : http://aminet.net/package/util/shell/KingCON_404

mfilos
2nd April 2011, 07:12
@Cosmos
Thanks a lot for your constant advices my friend! If you think that there are other useful modules to replace some old 3.1 ones, let me know! \o/

The new Custom 1MB Kickstart ROM for A600s has all the 3.1 Modules plus the following:


- Exec 45.24 (instead of 40.10) --> OS3.9 BB4
- BootMenu 44.7 68020 (instead of 40.5) --> OS3.9 BB2
- Card.resource 40.5 (instead of 40.4) --> OS3.9 BB4
- Console.device 44.10 (instead of 40.2) --> OS3.9 BB3
- Datatypes.library 44.48 (instead of 44.47) --> OS3.9 BB4
- Filesystem.resource 45.10 (instead of 40.1) --> OS3.9 BB2
- FastFilesystem 45.16 (instead of 40.1) --> OS3.9 BB4
- Graphics.library 42.8b11-02 (instead of 40.24) --> OS3.9 BB4
- KingCON-handler 40.4 (instead of Con-Handler 40.2) --> Cosmos
- Icon.library 46.4.196 (instead of 40.1) --> PeterK
- Misc.resource 37.2 (instead of 37.1) --> OS3.9 BB4
- RAM Handler 44.24 (instead of 39.4) --> OS3.9 BB3
- Ramlib 40.3 (instead of 40.2) --> OS3.9 BB4
- Romheader 45.21 (instead of BlizKick module) --> OS3.9 BB4
- SCSI.device 43.46b4 (instead of 40.5) --> OS3.9 BB4
- Shell 45.27 (instead of 40.2) --> OS3.9 BB3
- Trackdisk.device 40.2 (instead of 40.1) --> OS3.9 BB4
- Workbench.library 45.131 (instead of 40.5) --> OS3.9 BB3
- BBlank --> For Blank Borders
- HRTModule (2.30) --> HRTmon using
ACA's NMI header

while the Custom 512KB Kickstart ROM for A4000s has all the 3.1 Modules plus the following:


- Exec 45.24 (instead of 40.10) --> OS3.9 BB4
- BootMenu 44.7 68020 (instead of 40.5) --> OS3.9 BB2
- Console.device 44.10 (instead of 40.2) --> OS3.9 BB3
- Datatypes.library 44.48 (instead of 44.47) --> OS3.9 BB4
- Filesystem.resource 45.10 (instead of 40.1) --> OS3.9 BB2
- FastFilesystem 45.16 (instead of 40.1) --> OS3.9 BB4
- Icon.library 46.4.196 (instead of 40.1) --> PeterK
- Misc.resource 37.2 (instead of 37.1) --> OS3.9 BB4
- RAM Handler 44.24 (instead of 39.4) --> OS3.9 BB3
- Ramlib 40.3 (instead of 40.2) --> OS3.9 BB4
- SCSI.device 44.2 (instead of 40.5) --> OS3.9 BB3
- Shell 45.27 (instead of 40.2) --> OS3.9 BB3
- Trackdisk.device 40.2 (instead of 40.1) --> OS3.9 BB4

Sorry but no room left for Cosmos Graphics.Library and KingCON-Handler
(you either leave them out or load them via LoadModule on boot)
Enjoy...

rkauer
3rd April 2011, 05:05
Does this custom A600 are intended for 030 or plain 68000 machines?

Or both?

Calgor
3rd April 2011, 08:58
@mfilos

Great instructions mate. Stellar job. Sorry I did not get back to you ages ago on the 3.9 ROM but looks like you figured it out for yourself!

Only thing missing is Poseidon on bootup - any reason you did not include that? Was it due to PsdStackLoader file needing to be changed when USB configuration changes?

The modules needed for that are in my now old instructions for building the rom (using info gleaned from the poseidon docs and amiga board threads), but I never built a rom with them in it to test:

http://eab.abime.net/showthread.php?t=45260

I had deliberately kept the instructions vague and did not include instructions for burning of the ROM in fear of reprisals as it was newer at that time but now it seems times have changed. :)

Cosmos
3rd April 2011, 09:08
@rkauer

All libraries are 000+

Only KingCON 40.4, icon.library 46.4.196 and workbench.library 45.131 are 020+

mfilos
3rd April 2011, 11:15
@Rkauer
Rogerio my friend this specific ROM is intended for 020+ Α600's since as Cosmos said, modules like:
- KingCON-Handler,
- Icon.library,
- Workbench.library and
- BootMenu (020)
... are versions inserted for 020+ Amigas.

Just for info, about the BootMenu, there is also the simple 68k if you extract the "AmigaOS ROM Update" file (it has BootMenu versions for almost all Amiga Models). Btw, simple 68k BootMenu from BB2 doesn't have the Button "Expansion Board Diagnostic" as the other version have (dunno why). So you can either put the 68k instead or the 3.1 BootMenu (as I did on the past).

@Calgor
My friend, if it wasn't you starting this thread, I would have never managed to make such a job! Indeed instructions were minimal so it was really painful to me to figure out how to do it without much help.
That's why I decided to write this guide in order to help others in the future :)
The reason I haven't inserted Poseidon yet, is only one... WHDLoad.
Tbh I haven't tried it yet, and I will really soon (maybe later today) since the only thing you need are the required classes, device, library and PSDStackLoader.

For example you only need to put:
- subwayusb.device (or device that you have for USB)
- hub.class
- massstorage.class
- poseidon.library
- PSDStackLoader (this must be the one you're using now and works)

NOTE: if you want to change anything in Poseidon like new classes or re-arranging based on usb hub etc... You need to save the settings and remake the ROM with the new PSDStackLoader.

If you want even Fat32 support to be able to boot from Windows Sticks you should also include FAT95 from L:
If you want more stuff like USB Mouse, Keyboard, you also need HID.class and the keyboard/mouse classes as well (many KB's in ROM usage though).

My only fear is that with Poseidon in the ROM, you'll have issues with WHDLoad since all know that it has issues with WHDLoad once activated.
(Although Merlinkmkv on this thread (http://www.amibay.com/showthread.php?t=14610) found a way that WHDLoad works just fine even with Poseidon installed when RTGMaster libraries are installed).
Amiga is full of potential and weird machine. You can never say you know enough of this... I guess this is a reason we only love it :)
Thanks again for your support my friend. :thumbsup:

Calgor
3rd April 2011, 14:15
@mfilos

Don't you also need the input.device from the poseidon package? As per the EAB thread, you can use romsplit "input patch" to split 3.9BB2 input.device into input.device and gameport.device, and then replace that smaller input.device with the Poseidon input.device, leaving the gameport.device on its own. Don't know what the poseidon input.device does compared with the os3.9 one.

Have no idea about rtgmaster, I looked at the list of files in the package on aminet and didn't understand how rtgmaster.library would affect anything. Guess I would need to try it to see exactly what it does. I would have put the usb stack start/stop in the whdload scripts so it is performed automatically (as suggested in another EAB thread), as whdload seems to be the only app I have read that suffers.

btw: someone had told me I did not need (or was it should not?) to put the BootMenu in the ROM image.... but again don't know the differences of not putting it in (I did include the BB2 version in my ROM) You say in your posts that different versions of bootmenu can result in different buttons in early startup. So maybe that is the effect.

mfilos
4th April 2011, 00:48
Calgor my friend you need the input.device if you wanna try USB mouse or keyboard from the Early Startup Menu.
Indeed Remus's Romsplit patches the input.device but i never used it :)

You can see my A600 booting from USB in the following link. Told you I will try it tonight!
http://www.youtube.com/watch?v=8gtDZUm46ks

Cheers

Phipscube
5th April 2011, 09:31
OMG AWESOME! I want this in my A1200 ROMZZZ :) I know i've asked this before, but is it DEFINATELY not possible to include Delfina files in some way so its initialised from ROM at boot?

mfilos
5th April 2011, 12:44
Well... the way I see it is definitely possible (at least theoretically) since Delfina drivers insist from delfina.library and delfinampeg.device that I think both can be inserted into the EPROM.
The only issue is that they are both together 120KB which is a lot, but definitely can be put if you leave Workbench.library under Libs: and not in the Eprom :)

Only one way to find out! (Nice idea btw, and I'm gonna try it for sure since I don't like making external mixer if I can use Delfina's passthrough on boot! :O)

Phipscube
5th April 2011, 21:44
@Marios, Awesome! But Bah about the size, I guess there is only so much that can go in 1MB. Yeah, the reason would be to try and avoid the need for a hardware mixer and allow Native audio to pass thru the Delfina at cold boot. Once you are back on the A1200 it will be interesting to see what you find out here :) Its maybe too late for me as I ended up making the mixer now, but would be fun to know if its possible! And if it is, then you da man that can! :)

FOL
6th April 2011, 12:57
@Marios, Awesome! But Bah about the size, I guess there is only so much that can go in 1MB. Yeah, the reason would be to try and avoid the need for a hardware mixer and allow Native audio to pass thru the Delfina at cold boot. Once you are back on the A1200 it will be interesting to see what you find out here :) Its maybe too late for me as I ended up making the mixer now, but would be fun to know if its possible! And if it is, then you da man that can! :)

Be nice if remus could compress the modules, bit like lucerferin can on the deneb.

Phipscube
6th April 2011, 12:59
Thinking more about practicallity of having to Burn EPROMS often when changing things (undo Amiga, physically extract ROMS and place into burner etc).... It would be Awesome if someone (Individual Computers?) made a ROM adapter that could be plugged into the ROM socket/s and have onboard EEPROMS that could be controlled from the actual amiga and be reflashed from the desktop using some software. :cool:

mfilos
6th April 2011, 16:11
Thinking more about practicallity of having to Burn EPROMS often when changing things (undo Amiga, physically extract ROMS and place into burner etc).... It would be Awesome if someone (Individual Computers?) made a ROM adapter that could be plugged into the ROM socket/s and have onboard EEPROMS that could be controlled from the actual amiga and be reflashed from the desktop using some software. :cool:
This is exactly what me and Gulliver said so many times in the past!
This is called ROMflash (http://www.terminal-entry.de/amiga/romflash.html , http://www.a1k.org/forum/showthread.php?t=13078) and was already build including the tool, but never saw the lights of day (at least as production run, AFAIK).

There is also a ready DIY mod, including the software in Aminet here:
http://aminet.net/package/docs/hard/DC-KF500

I just wish I had your knowledge and skills to make it. As I see it, it shouldn't be too hard to make.

Phipscube
6th April 2011, 20:47
@FOL, yeah that would be really nice!

@Marios, OMG! How did I miss that!? I smell another breadboard prooooojeeeect! :D But a REAL shame about that ROMflash project, it looks very nice, I wonder what happened? Have you or Gulliver or anyone else tried contacting the creator to see whats what?

mfilos
6th April 2011, 20:53
There was also a homebrew project by Doobrey (http://www.doobreynet.co.uk/flash.html) that worked just fine but he never released any schematic AFAIK.

Btw I indeed tried contacting the creator of ROMFlash some months ago but I didn't even get a reply :(
If you make a test board, I'll gladly pick one of yours for sure...

rkauer
6th April 2011, 21:39
Redskull is an awesome guy, but very hard to reach contact of any sorts (PM, e-mail, etc).

Phipscube
7th April 2011, 14:24
I've been reading around a bit and yeah, it seems like this ROMFlash is finished, just too expensive to produce without enough orders!!

But seems like there wasn't a real push to do this?......

Have you guys at Amigakit tried any contact? FOL? do you guys think its a feasable device to get out there? I flippin' do! :D

I also read that its possible to address upto 2.5MB for custom ROMS (2MB definatley safe anyway) that would also make a real big difference in getting all those extra modules in.

I Was also thinking about putting IDEFix in the ROM too so that one could boot from CD/DVD! And even adding a little boot screen :) I need 2MB! :D

Later today i'll check out that Aminet project, i've not had chance to look properly yet (been playing too much DJ Hero!).

heALer
8th April 2011, 22:51
Time to change some stuff:
- Move the file in DEVS: "AmigaOS ROM Update" to another folder, or Rename it to something else.
- Comment the line you have for SetPatch and insert the following SetPatch declaration instead:
C:SetPatch NOROMUPDATE QUIET


I 'm using aca 1230 with the line
C:AcaTune -maprom Devs:custom.rom ..... for example and I have
done a 1Mb rom, not planning to burn them to a rom, just softkick, should I add NOROMUPDATE to startup-sequence? And then rename "AmigaOS Rom Update" to something else?
I tried first without doing that and I got a "Recoverable Alert. Press Left Mouse Button to Continue. error: 0100 0003", when I added NOROMUPDATE and renamed the file the message dissappeared and workbench loads up fine.
I just want to make sure that everything is ok :roll:
(http://www.google.se/search?hl=sv&biw=1467&bih=745&sa=X&ei=_XSfTYS9McjFswaWkpyMAg&ved=0CCAQvwUoAQ&q=disappeared&spell=1)

mfilos
9th April 2011, 00:29
Just for you to understand better...

The file "AmigaOS ROM Update" as you'll see on my guide contains the following modules inside it:
- bootmenu 44.7 (with different versions for 68020, A500, CD32)
- console.device 44.8
- exec 45.20 (with different versions for A1200-A500, A3000, A4000, CD32, unknown)
- filesystem.resource 45.10
- filesystem 45.137
- NCRscsi.device 43.43 (A4000T)
- ram-handler 44.23 (and also 44.24 patched via RomSplit)
- ROMUpdate 44.57
- scsi.device 43.43 (with different versions for A600, A1200, A3000, A4000)
- shell 45.7

So everytime you use the SetPatch without the NOROMUPDATE option, SetPatch uses this file to load these modules into memory.
By using the NOROMUPDATE command you tell SetPatch to ignore the file from Devs:
The step to just rename the file is optional but I thought of doing it as well just for safety (since it's like it never existed).

The errors you have, appear because the SetPatch command tries to load in memory... the modules from the "AmigaOS ROM Update" file BUT memory already has the updated files already (since you made a custom ROM with those) so it just CAN'T!

That's all :)
Everything's ok with the NOROMUPDATE option but make sure you have included all the necessary modules in the Custom ROM file of yours.

Cheers

lurbi
9th April 2011, 03:01
If you want even Fat32 support to be able to boot from Windows Sticks you should also include FAT95 from L:


Would it also be possible to include additionally compactflash.device and boot from CF card in PCMCIA slot?

mfilos
9th April 2011, 08:42
Theoretically yes. I never tried it but I will soon :)

lurbi
17th April 2011, 00:26
Theoretically yes. I never tried it but I will soon :)

I have just read in the remus.guide that:
"FAT95 filesystem disappears from exec's resident list."
whatever that means ;)

So I have to either use boot95 utility from the fat95 archive or
or use FFS.
Would it be possible to make 2 partitions on the CF card in the PCMCIA reader?
one fat for PC file exchange, and one FFS where a modified kick.rom could boot from?

BTW. I get the message from romsplit:
"unsupported ROM (Genuine 40.68 A1200 ROM)"
I thought the 3.1 amiga 1200 rom IS supported ... or did I do something wrong?
I installed the MUI components, started romsplit, and got this message.

PS: They are also writing the KingCon is NOT ROMsafe.
Have seen it been mentioned here, but as Amiga newbie I do not really know what it is.

mfilos
17th April 2011, 01:55
Would it be possible to make 2 partitions on the CF card in the PCMCIA reader?
one fat for PC file exchange, and one FFS where a modified kick.rom could boot from?
You can easily make 2 partitions on the CF Card as you said. 1 with FFS for booting Amiga and 1 for Filesharing.
If (and I say if cause I never tried it) compactflash.device in ROM works as theoretically would... that would be possible indeed.




BTW. I get the message from romsplit:
"unsupported ROM (Genuine 40.68 A1200 ROM)"
I thought the 3.1 amiga 1200 rom IS supported ... or did I do something wrong?
I installed the MUI components, started romsplit, and got this message.
Not all Amiga ROMS can be processed by Remus. Especially the ones that are Custom! :)
Even many TOSEC ROMS can't be read. Just try with a different ROM (! or b) or try a grab from your original 3.1 Kickstart.




PS: They are also writing the KingCon is NOT ROMsafe.
Have seen it been mentioned here, but as Amiga newbie I do not really know what it is.
Dunno what version of KingCon is not ROM safe as you say, but Cosmos KingCON-Handler is perfectly ROMable and I have it for some weeks now with no issue at all.

lurbi
17th April 2011, 10:35
You can easily make 2 partitions on the CF Card as you said. 1 with FFS for booting Amiga and 1 for Filesharing.
If (and I say if cause I never tried it) compactflash.device in ROM works as theoretically would... that would be possible indeed.

Thanx for your support!
I am very curious if compactflash.device plays nicely in ROM.

I have sent you a PM with the file I have been using.
The strange thing is that I get the same message for kick 3.1 that I grab from ROM.

lurbi
17th April 2011, 20:14
Theoretically yes. I never tried it but I will soon :)

So it seems not to work for either of us.
I have added compactflash.device but see no change in the early bootup menu.
Well - it is not that important ;)

thanx for trying mflios!

mfilos
17th April 2011, 20:33
Yep installation of CompactFlash.device and pccard.library didn't seem to make any difference. CF still doesn't show on startup.
Oh well, no probz anywayz. We got many shiz to boot from :)

At least you learned how to make custom ROMS! That is indeed awesome stuff mate \o/
I'm glad I could help

FOL
25th April 2011, 13:33
I've been reading around a bit and yeah, it seems like this ROMFlash is finished, just too expensive to produce without enough orders!!

But seems like there wasn't a real push to do this?......

Have you guys at Amigakit tried any contact? FOL? do you guys think its a feasable device to get out there? I flippin' do! :D

I also read that its possible to address upto 2.5MB for custom ROMS (2MB definatley safe anyway) that would also make a real big difference in getting all those extra modules in.

I Was also thinking about putting IDEFix in the ROM too so that one could boot from CD/DVD! And even adding a little boot screen :) I need 2MB! :D

Later today i'll check out that Aminet project, i've not had chance to look properly yet (been playing too much DJ Hero!).

I do see it as a feasable project.
However it may be more hastle than its worth. Due to the possible legal implecations. Amiga Inc. would proberly go after the manufacturers of such a device.
This is why previous projects of this type have been scrapped.

Phipscube
25th April 2011, 21:14
@FOL, What if the unit is sold blank? With a bold printed disclaimer stating that Legal ROM images should be used etc etc (to cover the legal side of things). Then its up to the buyer to rip their own legal ROM using Remus and combine the newer modules as we have done. This way is fine, no harm done as far as I can see. I know its possible that some folks *might* use it with an illegal copy of a ROM, but for the price one would have to pay for these flashROM units they'd be a bit cheap to do that. It seem such a shame to have a device all made and ready to go that sat on the starting blocks :(

@Marios, I looked at the KS-500 mate and it seems very easy to build, but as it is, it will only work with the 16Bit machines with one ROM socket. The author says in his docs that it could quite easily be adapted to work with A1200 though, so will look further into it...

mfilos
25th April 2011, 23:10
@FOL
Tbh, this device doesn't do anything illegal. It's just gives you the opportunity to make custom ROMS and load them at will! Anyone having a legal kickstart can do modified ROMS of himself and play.
Loading illegal ROMS is exactly the same as downloading illegal ROMS using them under UAE so I don't see any difference there.
As Phipscube said, you can easily mark blank ROMS with a disclaimer that you need to provide valid kickstart ROM grabbed from your own Amigas with utilities like Remus or Transrom.

@Phipscube
Ye KS-500 seems really easy (I personally don't have the skill though to build it though) but even for A500/600/2000 it's godly since many MapROM features only work for ACA and some rare accelerators. Having that device can gief you the possibility to mount Custom Kicks in any Amiga and in whatever configuration!!!
Modifying it to work on SplitROM images isn't so difficult but requires a bit of more logic and some modification on the Flash ROM utility (dunno which programmer can help here).

FOL
26th April 2011, 01:37
@FOL
Tbh, this device doesn't do anything illegal. It's just gives you the opportunity to make custom ROMS and load them at will! Anyone having a legal kickstart can do modified ROMS of himself and play.
Loading illegal ROMS is exactly the same as downloading illegal ROMS using them under UAE so I don't see any difference there.
As Phipscube said, you can easily mark blank ROMS with a disclaimer that you need to provide valid kickstart ROM grabbed from your own Amigas with utilities like Remus or Transrom.

@Phipscube
Ye KS-500 seems really easy (I personally don't have the skill though to build it though) but even for A500/600/2000 it's godly since many MapROM features only work for ACA and some rare accelerators. Having that device can gief you the possibility to mount Custom Kicks in any Amiga and in whatever configuration!!!
Modifying it to work on SplitROM images isn't so difficult but requires a bit of more logic and some modification on the Flash ROM utility (dunno which programmer can help here).

He also pointed out the other major issue. People selling them with KS's already on them.
People would start selling 3.9 ROMS and then a whole can of worms is opened.

Zetr0
26th April 2011, 02:29
@FOL / Phips / Marios

My friends, there is only two practical ways of doing it -


1. Provided blank with PC/USB flash programing software

The product can then be updated by the target system.... incase of ISP failure the owner can re-flash them from USB via a PC or another Amiga equipped with USB.


A more expensive, yet inclusive approach -

2. A Physical 2x 42PIN KICKROM plug in's

The unit can be shipped kick-rom empty or with the latests official kickroms and hence programmed at source.

From here the user can program the flash-ram on the target machine by dropping in their original ROM's - booting up and then programming the Flash from the target machine (or via a PC USB)

The adapter has jumpers to select boot from KICKROM or FLASH

Phipscube
26th April 2011, 09:42
@Marios, it would indeed be awesome for the 16bitters too, I agree, so maybe the first thing to do is build it as it is and see if it works in a 16 bit machine, then go on from there.

@FOL, I can see that as the main problem too..... What about cutting an exclusive deal to Amigakit.com? ;) You guys would sell them properly :thumbsup:


@FOL / Phips / Marios

My friends, there is only two practical ways of doing it -


1. Provided blank with PC/USB flash programing software

The product can then be updated by the target system.... incase of ISP failure the owner can re-flash them from USB via a PC or another Amiga equipped with USB.


A more expensive, yet inclusive approach -

2. A Physical 2x 42PIN KICKROM plug in's

The unit can be shipped kick-rom empty or with the latests official kickroms and hence programmed at source.

From here the user can program the flash-ram on the target machine by dropping in their original ROM's - booting up and then programming the Flash from the target machine (or via a PC USB)

The adapter has jumpers to select boot from KICKROM or FLASH

Great points Zeets! I like number 2 the best. Its similar to how KS-500 works. The thing I like is that you can switch to original ROMS for compatibility if needed (And if the flash gets screwed up). Maybe this is the way to go as you HAVE to own physical ROMS before this will work.

cosmicfrog
26th April 2011, 13:18
Just plz do it

all this talk of z company suing you over Y IP has yet to be proved

Its not that I would like an easy way to update my KS roms its almost becoming essential if i want to keep up with this years software for my beloved amigas

salaxi54
8th May 2011, 18:51
Would it be too much to ask for a list of appropriate types of EPROMs for each Amiga model?
eg.
A500 --- 27C400
A600 --- xxxxxx
etc..

By the way, does anyone know if there's any difference between the A4000 (desktop) and A4000T Kickstart original Roms? Meaning, are they interchangeable?
Thanks!

J.T.Kirk
8th May 2011, 18:57
For what I know you can use A4000T 3.1 ROMS in A4000D if you're using AmigaOS 3.5 or higher.

mfilos
8th May 2011, 22:36
@Salaxi
Bill my friend, 27C400 is an 512KB Eprom with 40pins. It's compatible with every Amiga afaik (only tested it myself in A500/A600/A1200).
Since it's 512KB it can be used just fine with any Amiga and any Kickstart image and also can be used for 1MB ROM for A1200 due to Split ROMS and 2x512KB.
A4000 (not sure if only Desktop or either Tower version) can use only up to 512KB ROM images. Since they use 2xKickstart Eproms you can write 2x256KB Eproms (Split ROMS) for A4000 custom or not.

27C800 has 1MB space and has 42pins. (Can be used for 1MB Custom ROMS or 2x512KB ROMS switchable using Pin1).

If you need further info my friend, drop me a PM to help ya out with more technical data :D

salaxi54
8th May 2011, 22:50
@mfilos: Helpfull as always! Thanks man :)

rkauer
9th May 2011, 03:09
Just use 120ns or faster parts for your custom ROM and all will be fine.

150ns and slower parts will not work correctly (may work on the A3000 with the mobo jumpers set on 200ns).

jvdbossc
15th May 2011, 11:32
Is this and the right rom chip and uv eraser all I need?

http://cgi.ebay.com/Willem-Universal-EPROM-Programmer-27C256-27c512-C03-/190458353824?pt=LH_DefaultDomain_2&hash=item2c5833d8a0

:roll::roll:
btw: I have legal 3.1 rom for every amiga.

mfilos
15th May 2011, 12:07
This is just the Willem Programmer.

Seeing from this auction, you also need the option:
7. 27Cxxxx ( EPROM 16bit ,1-4Mbit ) Adapter ( DIP40)---us8$
To be able to burn 27C400 40pin 512KB Kickstarts
OR
8. 27Cxxxx ( EPROM 16bit ,4-32Mbit ) Adapter ( DIP42)---us10$
To be able to burn 27C800 42pin 1MB Kickstarts OR EVEN 27C400 40pin 512KB Kickstarts (by leaving the first row Pin1-Pin42 opened - This is what I have as well)

By getting this, you can program any chip that is erased!!!
To be able to erase Eprom chips as well, you need an UV eraser that you can easily find on eBay and it's pretty El'Cheapo

jvdbossc
15th May 2011, 12:45
Thanks mate:thumbsup: I ordered the willem and adapters, will look for UV erasor and some chips then.

I hope I figure it out.:roll: I'll format a pc and put xp on waiting for this.:roll: Or is there an Amiga burning tool as well?

The chip types sound real unfamiliar to me. Do you know what rom type to fetch for C64 kernal rom etc??

Is the Willem also usefull as rom extractor? ;) Like fetch a custom kernal rom for C64 etc??

:bowdown:

johnim
27th May 2011, 20:23
hi all can this be done using winuae once the rom has been grabbed off real miggy without any adverse affects?

as i have been using it on my miggy with a cf card and it is giving me read errors?

is it best to install 3.9 with all 4 bbs or just the bb2?

how does it get the 3.9 system screen as mine still says 3.1?

sorry if any thing as already been asked before

john

Justin
27th May 2011, 20:28
hiya johnnypoos,
i used winuae to test the custom roms before putting them in a real miggy, i did have bb 1 and 2 installed but that was all.

also a HUGE thanks to mfilos for being a complete star!! thank you my friend:thumbsup:

johnim
27th May 2011, 20:37
cheers juv

and yes thankyou mfilos for this guide it is really helpfull




hello im in a bit of a muddle i have done the first part of this guide to make 39.rom and extended but i have left out

--> LIBS:mathffp.library (These are my regged HSMathLibs that I included)
--> LIBS:mathieeesingbas.library (These are my regged HSMathLibs that I included)

from normal rom do i need them?

and

--> DH0: Devs/morelibspace_module (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!)

as i do not use

in winuae i can get the boot disk screen fine with 3.9 rom but when i add a hardrive with 3.9 and bb4 or floppy 3.1 it just keeps rebooting and dont load or any gurus

and have used the origional scsi.device and the bb4 scsi.device also 43.43scsi.device just to check

what could this be? sorry my bad it was the extended rom address i had it set as normal rom working now

thanks john

mfilos
27th May 2011, 23:12
I'm glad you like it guys and most of all... that you understood what is custom burnage all about :D
Tbh, after some fiddling around and burning a couple of Eproms, everything will be a lot clearer and appetite for more custom making will be certain lol.

Cheers

protek
28th May 2011, 08:45
Great guide! Thank you, mfilos, for putting this up!

A couple of questions:
Is it so that you can use the 1 MB ROMs in A1200 but for A4000 you have to have 512 kB ROMs?

Could you use flash ROMs instead of EPROMs? At least for the STe you could use the 29F010 instead of the 27C010.

mfilos
28th May 2011, 08:54
protek mate you are correct. You can use up to 1MB Eproms for A600/A1200 (A500/A2000 with a slight modification) but for A4000 you can use up to 512KB due to chipset limitation.

I don't know at all about Flash ROMS instead of EPROMs cause I never used them.

johnim
28th May 2011, 09:36
hi the roms i made in other post in wuae work fine with os3.9 but with others i get a ramlib error what libs or what would need 2 be copied 2 make this work with other installs eg cwb thanks

mfilos
28th May 2011, 10:31
You need to be more specific to be able to help ya out :)
- What modules did you include on your Custom ROM?
- What versions of ClassicWB are you trying to run?

johnim
28th May 2011, 13:01
hi mfilos

- What modules did you include on your Custom ROM? i did the guide exactly except what is in post 77

scsi.device is 43.46b4
workbench.lib is 45.131



- What versions of ClassicWB are you trying to run?p96 and 3.9

thankyou

protek
28th May 2011, 13:24
protek mate you are correct. You can use up to 1MB Eproms for A600/A1200 (A500/A2000 with a slight modification) but for A4000 you can use up to 512KB due to chipset limitation.

I don't know at all about Flash ROMS instead of EPROMs cause I never used them.

Thanks for that!

At least the Willem HW and software has support for Flash ROMS. There is also the benefit of not needing the external PSU for the Willem as you can feed it from the USB. Flash ROMs are also easier and quicker to erase.

mfilos
28th May 2011, 14:43
@johnim
My friend I never had experience with ClassicWB P96 since it's a special version for WinUAE. I seriously doubt that it can work out of the Box in a real Amiga without modifications (Steve can gief a little feedback here since he has done such a task himself AFAIK). The following advise stand for this as well though.

ClassicWB 3.9 should work just fine BUT you need to change the SetPatch line in S-S to:

C:Setpatch NOROMUPDATES QUIETalong with renaming the file "AmigaOS ROM Update" under DEVS: to something else.

Since your kickstart already has the newer files... it will conflict with OS3.9's BB2 update, and ClassicWB 3.9 already has BB2 installed!

johnim
28th May 2011, 16:22
thanks mfilos

i have found the problem is was the scsi device i changed it too 43.43 and it now works more playing if coming tho

alexh
31st May 2011, 18:43
Is there an easy way to extract the "AmigaOS ROM Update" file from the BB2 installer?

FYI In your great guide, you forgot to mention that you need the following library :

http://aminet.net/package/util/libs/pmuser

mfilos
31st May 2011, 20:02
@Alexh
The "AmigaOS ROM Update" file can be easily extracted using ROMsplit program in the Remus package (the one you use to grab the real ROM image as well).
As for the PopupMenu.library, I realized as well 2 days ago that it was needed when I installed Remus from scratch in a new installation. Apparently when I wrote the guide, I had this library already in my Amiga alas it wasn't needed and since it wasn't ever required in Doobrey's instructions (along with other files that needed as well) I missed it :)
I updated the guide adding this library as well on the list and on my Dropbox link with all the included Libraries. Cheers Alexh

alexh
31st May 2011, 21:20
@Alexh
The "AmigaOS ROM Update" file can be easily extracted using ROMsplit program in the Remus package (the one you use to grab the real ROM image as well).
I think we have our wires crossed. I know that ROMSplit will accept the file "AmigaOS ROM Update" and is able to extract the individual ROM update files.

BUT: How do you get that file from the BB2 installer? http://os.amigaworld.de/index.php?lang=en&page=12

I don't really want to go through the AmigaOS3.9 + BB1 + BB2 installation process just to get that file.

[Edit: Some kind soul sent it to me, so the solution is not urgent, but I think it is still of use to anyone else attempting this]

mfilos
1st June 2011, 00:30
BUT: How do you get that file from the BB2 installer? http://os.amigaworld.de/index.php?lang=en&page=12

I don't really want to go through the AmigaOS3.9 + BB1 + BB2 installation process just to get that file.

Ok now I understood what you meant :)
Well the only way for you to get that file without installing OS3.9 plus BB1+BB2 is this:

- Unarchive the "BoingBag39-2.lha" and inside the main folder there is a file called "AmigaOS-Update". This is actually a zip file, so if you put a .zip extension you can open it and see the contents. The file you want exists as always under Devs: BUT the whole archive is password protected (BB1 as well but with different passwords).
If you want the passes, I think there are references around... but I can provide some info as well... :whistle::ninja: :shhh:

alexh
1st June 2011, 01:07
there is a file called "AmigaOS-Update". This is actually a zip file, so if you put a .zip extension you can open it and see the contents.
Thanks. I had tried adding .LHA :)

FYI for those reading and wanting to do the same as myself the passwords for unarchiving are :

BB1 93ABDF11
BB2 3FB6986B-B0AD6339-4FF3254B

alexh
1st June 2011, 18:34
I'm getting closer to my goal of making a working A4000d Kickstart 3.9.

Your guide is a great help, but one or two steps seem to be missing?

1) Creating FastFileSystem v45.16

The guide currently uses FastFileSystem 45.10 from BB2 but ideally it could do with an explanation on how to patch to the latest 45.16

You need this :

http://aminet.net/package/util/misc/FFS4516p

And the tool Spatch

http://aminet.net/package/util/misc/patchgui

Details on how you actually patch are in the README in FFS4516p.

2) Creating scsi.device

I think this guide assumes that you are running Remus under AmigaOS3.9 BB2 which has already has the BB2 AmigaOS ROM Update applied? It uses SYSTEM:scsi.device?? Which I think would be 43.43?

I think an explanation of how to start with the appropriate scsi.device 43.43 for your Amiga (extracted from the 44.57 AmigaOS ROM Update in OS3.9 BB2) you then have to apply the v43.45 patch from Aminet

http://aminet.net/package/driver/media/SCSI4345p

Details on how to patch are in the README in the archive.

Then (A600/A1200 users) can use the additional v43.46b4 patch from Cosmos

http://eab.abime.net/showpost.php?p=739545&postcount=58

Misser
1st June 2011, 20:59
@mfilos Great guide, i've done some custom 4x and even 16x kernels for the C64, but somehow I can't think of a way (just return to that nice amiga thing since a week so call me a newbie)to use this besides that it's doable which is enough for the little freak inside me to try it out. Will keep you posted on results.

@protek
Flash roms should work just make sure you get the right voltage part. I used to use 27c256 eproms for my 4 times C64 kernel mods (way back in 1987 or so), but switched to 29f010 flash for my 16x kernel mods. Much easier to erase and program not to mention to find, every odd pc has one :)

Just replace the 27cxxx part for 29fxxx and google.

mfilos
1st June 2011, 21:02
Yeah you're right Alexh,
This Guide was made just to give people the knowledge on how to make a custom 3.9 BB2 Kickstart ROM.
There are SO many modules available in order to make a more advanced kickstart (like the ones I'm using on my A600 and some A4000 I made for testing purposes.

Just for info the A600 Kickstart I'm using on my A600 has the following modules:


- Exec 45.24 (instead of 40.10) --> OS3.9 BB4
- BootMenu 44.7 68020 (instead of 40.5) --> OS3.9 BB2
- Card.resource 40.5 (instead of 40.4) --> OS3.9 BB4
- Console.device 44.10 (instead of 40.2) --> OS3.9 BB3
- Datatypes.library 44.48 (instead of 44.47) --> OS3.9 BB4
- Filesystem.resource 45.10 (instead of 40.1) --> OS3.9 BB2
- FastFilesystem 45.16 (instead of 40.1) --> OS3.9 BB4
- Graphics.library 42.8b11 (instead of 40.24) --> Cosmos
- KingCON-handler 40.4 (instead of Con-Handler 40.2) --> Cosmos
- Icon.library 46.4.211 (instead of 40.1) --> OS3.9 BB4
- RAM Handler 44.24 (instead of 39.4) --> OS3.9 BB3
- Ramlib 40.3 (instead of 40.2) --> OS3.9 BB4
- Romheader 45.21 (instead of BlizKick module) --> OS3.9 BB4
- SCSI.device 43.46b4 (instead of 40.5) --> OS3.9 BB4
- Shell 45.27 (instead of 40.2) --> OS3.9 BB3
- Trackdisk.device 40.2 (instead of 40.1) --> OS3.9 BB4
- Workbench.library 45.131 (instead of 40.5) --> OS3.9 BB3
- BBlank --> For Blank Borders
- HRTModule (2.30) --> HRTmon using ACA's NMI header

Leaving ~200KB free (or ~400KB free if you leave out the Workbench.library)

While the A4000 Kickstart I made has the following modules:


- Exec 45.24 (instead of 40.10) --> OS3.9 BB4
- BootMenu 44.7 68020 (instead of 40.5) --> OS3.9 BB2
- Console.device 44.10 (instead of 40.2) --> OS3.9 BB3
- Datatypes.library 44.48 (instead of 44.47) --> OS3.9 BB4
- Filesystem.resource 45.10 (instead of 40.1) --> OS3.9 BB2
- FastFilesystem 45.16 (instead of 40.1) --> OS3.9 BB4
- Icon.library 46.4.211 (instead of 40.1) --> OS3.9 BB4
- RAM Handler 44.24 (instead of 39.4) --> OS3.9 BB3
- Ramlib 40.3 (instead of 40.2) --> OS3.9 BB4
- SCSI.device 44.2 (instead of 40.5) --> OS3.9 BB3
- Shell 45.27 (instead of 40.2) --> OS3.9 BB3
- Trackdisk.device 40.2 (instead of 40.1) --> OS3.9 BB4

Leaving a free space on ROM of 8.864bytes LOL :D :D :D

Also you can have Workbench.library 45.131 from BB3 installed into LIBS: since it doesn't need to be on the ROM leaving us the required space.
Sadly... Cosmos Graphics.library doesn't fit so only method is to LoadModule it along with any other modules you would like :)

merlinkv
25th August 2011, 09:04
Hi to all,

As I said in other thread I'm completely noob programming EPROM's. :oops:

I bought the TOP3000 USB programmer and some EPROM chips (not received).

My question is... If I programmed one chip...Is not erasable with the software of the programmer? I need one UV eraser?

Thanks

---------- Post added at 07:04 ---------- Previous post was at 05:51 ----------


Hi to all,

As I said in other thread I'm completely noob programming EPROM's. :oops:

I bought the TOP3000 USB programmer and some EPROM chips (not received).

My question is... If I programmed one chip...Is not erasable with the software of the programmer? I need one UV eraser?

Thanks


Self answered.

Reading more... UV eraser is needed! So, I bought one five minutes a go.... :)

johnim
8th September 2011, 20:01
hi all will the m27c4001-1of1 work with the a1200

thanks john

piacc64
8th September 2011, 22:01
i have a hardital tqm, the board work only with 3.0 because in the 3.1 the allocation of ram is different, i can create a 3.9 whit allocation for ram like 3.0?

thanks in advance

Carlo

esc
9th September 2011, 02:54
I've read this post at least 100 times now :) Great tutorial.

I tried it out in UAE and everything works great!

Now, I'm VERY new to this whole idea, so allow me to ask some stupid questions. First, I should say that I'd like to put custom 3.9 roms in my a4000 that has been towered with a Mediator kit.

Is there any way to speed up booting? I have my cf drive as device 1 master, cdrom as device 2 master, both working with a fast ata mkv. Booting takes forever, though, and I have an IDE terminator on the mobo...so I am wondering if copying something over to a ks rom will speed things up?

Also, is it possible to load any of my mediator stuff from the custom kickstart?

Thanks! I have spider II, fast ethernet, tv, soundblaster, voodoo 3...and that fastata. I really appreciate it. Also, a cocolino, but that should be fine I think.

mfilos
9th September 2011, 07:18
hi all will the m27c4001-1of1 work with the a1200

thanks john
Nope it won't work.
M27C4001 is an 8bit 32pin Eprom
You can check some diagrams here: http://www.datasheetcatalog.com/datasheets_pdf/M/2/7/C/M27C4001.shtml

@esc
A4000 has 512KB of ROM space so it's not very easy to buff it with extra stuff. Sure you can put the 3.9 BB2 updates plus some nice stuff from BB3 and BB4 but that's it.
It's good that you have an IDE terminator since you use your FastATA. AFAIK there is no modules that just speed the system up.
There are many things you can check though like:
- Max Transfer mask on formated partition
- Startup-Sequence/User-Startup/WBStartup declarations and things that load on startup
- Putting HSMathLibs and OxyPatcher/CyberPatcher, Quick ROM etc. You can read a wonderful guide here: http://www.youngmonkey.ca/nose/articles/NewTekniques_9902/ImprovingPerformance/

Sure thing though is that after RTG Amiga slows down on boot significally (after installing P96 or CGX). After you put AfAOS you have a bit of extra burden. So in general extra stuff bring some extra booting time.

johnim
9th September 2011, 08:20
thanks for that mate i never noticed the pin amount :oops:

merlinkv
20th September 2011, 22:03
@mfilos

Hi my friend. :)

It's possible to flash the Deneb and put inside the updated KS's to sustitute the real chips & AmigaOS ROM Updates?.......

mfilos
20th September 2011, 22:41
No. Deneb's flash AFAIK only gets ROM Modules and not complete Kickstarts.
I might be wrong but I never seen that documented.

Why would you want that though?
Putting ROM modules in Deneb is piece of cake and so much transparent as procedure! Make a little patience, and soon I'll have the Deneb flash guide ready :)

hikey
28th September 2011, 19:43
You can add complete kickstart images using the Algorkick module, but only with maprom supported accelerators. It's all documented in the Luciferin flash tool manual. :)

mfilos
28th September 2011, 19:57
Yes you can, but as you said it's only for Phase 5 accelerators with MapRom feature and for ONLY 512KB ROMS.

Deneb/Algor/Romulus only stores the kickstart image and kicks it to the Phase 5 accelerator (same as Blizkick does).

merlinkv
25th October 2011, 14:53
Hi Marios,

I want to program some 27C800 EPROM's for my A600 (x1) and A1200 ( x2? ).

My question is..... I need to program with the pins 1 & 42 without contact with the programmer? And when I install in the CPU socket.... these pins needs to be out?

Ah! :Doh: One more question... After installing BB4 the command "version DH0:/devs/scsi.device" shows 44.2 !!! :blink: This is correct?

Thanks


This is just the Willem Programmer.

Seeing from this auction, you also need the option:
7. 27Cxxxx ( EPROM 16bit ,1-4Mbit ) Adapter ( DIP40)---us8$
To be able to burn 27C400 40pin 512KB Kickstarts
OR
8. 27Cxxxx ( EPROM 16bit ,4-32Mbit ) Adapter ( DIP42)---us10$
To be able to burn 27C800 42pin 1MB Kickstarts OR EVEN 27C400 40pin 512KB Kickstarts (by leaving the first row Pin1-Pin42 opened - This is what I have as well)

By getting this, you can program any chip that is erased!!!
To be able to erase Eprom chips as well, you need an UV eraser that you can easily find on eBay and it's pretty El'Cheapo

stachu100
15th December 2011, 12:53
Hi Marios my friend!

Many thanks for this tutorial! :-)
I was able to create custom 3.9 ROM for A1200 and what is more interesting - everything worked from first attempt! :-)
It means that tutorial is written just perfectly. :thumbsup:
I've created universal ROM - working on 020 CPU and above.
Proof:

https://picasaweb.google.com/110121921198567459630/A1200KS39
http://youtu.be/4SK_u5qB-n8
http://youtu.be/TbHo73qC214
http://youtu.be/JnpSLwwMLYk

Many thanks once again!

merlinkv
15th December 2011, 13:41
Hi again,

Maybe I don't understnad well, sorry :oops: but.......

To program 27C800 in one 42 pin adapter....

- I need to burn in the programmerr with pins 1 & 42 out?

- To install in the mobo's ROM socket pins 1 & 42 needs to be out?

Anyone can answer me please? ... :bowdown: :bowdown: :bowdown:

mfilos
15th December 2011, 14:03
@stachu100
Stanislaw my friend thanks for your good words. I'm really glad you got right from the first attempt! Your vids are pure win as always :)

@merlinkv
Pablo mate I'm really sorry but I missed your last post :(
Don't worry I'll make up to you right now though :)
- To burn a 42pin Eprom in an 42pin socket you don't leave any Pins empty (leaving pin1+pin42 empty are only left open when burning 27C400 40pin EPROM).
- To install in the mobo's socket, you don't need to leave any Pin out... EXCEPT IF you have a Dual kickstart burned in the ROM and only then... you leave Pin1 outside to feed it to a switch.

Cosmos
15th December 2011, 16:57
Hi Marios my friend!

Many thanks for this tutorial! :-)
I was able to create custom 3.9 ROM for A1200 and what is more interesting - everything worked from first attempt! :-)
It means that tutorial is written just perfectly. :thumbsup:
I've created universal ROM - working on 020 CPU and above.
Proof:

https://picasaweb.google.com/110121921198567459630/A1200KS39
http://youtu.be/4SK_u5qB-n8
http://youtu.be/TbHo73qC214
http://youtu.be/JnpSLwwMLYk

Many thanks once again!

Any thanks for the coders ?? :unsure:

stachu100
15th December 2011, 18:17
Any thanks for the coders ?? :unsure:
Biggest thanks for coders of course! :thumbsup:
And a lot of Polish vodka. :D :drinkin:

Cosmos
15th December 2011, 18:42
...was a colossal work for coders, you cannot imagine...

merlinkv
16th December 2011, 13:38
@merlinkv
Pablo mate I'm really sorry but I missed your last post :-(
Don't worry I'll make up to you right now though :smile:
- To burn a 42pin Eprom in an 42pin socket you don't leave any Pins empty (leaving pin1+pin42 empty are only left open when burning 27C400 40pin EPROM).
- To install in the mobo's socket, you don't need to leave any Pin out... EXCEPT IF you have a Dual kickstart burned in the ROM and only then... you leave Pin1 outside to feed it to a switch.

Hi Marios,

Thanks a lot for the answer my friend. :bowdown:

Time to start burning 1MB ROMs :thumbsup:

My Best Wishes as allways.

Pablo

---------- Post added at 12:38 ---------- Previous post was at 12:31 ----------


Any thanks for the coders ?? :unsure:

@Cosmos

Hi mate :)

Your skills and jobs in hw/soft are impressive. Also, your blog is a great "Amiga's Book of Reference".

Thanks a lot for share your work :thumbsup:

merlinkv
27th December 2011, 00:06
Hi to all,

I'm not sure if it's a good idea to write this post here because is not about burning 3.9 ROM's..... So, if I need to open a new Thread, please tell me.

I started today a little job with my A600 (a way to free a bit my mind in this hard days) and I want to explain:

I'm using one KS switch with 1.3 & 3.1 ROM's and I upgraded the 3.1 as follows:

A600 3.1 40.63 Updated (512KB - 27C400 at 100ns)

exec_40.10 (A500-A600-A2000)
audio.device_37.10
battclock.resource_39.3
battmem.resource_39.2
bootmenu_40.5
cia.resource_39.1
con-handler_40.2
console.device_44.8
disk.resource_37.2
dos.library_40.3
expansion_40.2 (A500-A600-A2000)
filesystem.resource_40.1
filesystem_40.1
gadtools.library_40.4
graphics.library_40.24 (OCS-ECS)
icon.library_40.1
input_40.1
intuition.library_40.85
keymap.library_40.4
layers.library_40.1
mathffp.library_40.1
mathieeesingbas.lib_40.4
misc.resource_37.2
potgo.resource_37.4
ramdrive_39.35
ram-handler_44.24
ramlib_40.3
romboot_40.1
scsi.device_44.2 (A600)
shell_40.2
timer.device_39.4
trackdisk.device_40.2
utility.library_40.1 (68000)
wbtask_39.1
workbench.library_40.5
BBlank
NoClick

888 bytes free

-------------------

Out of this ROM:

card.resource_40.4
carddisk.resource_40.1

......These are only for PCMCIA cards? (I don't use PCMCIA)

The resulting ROM is working great with WB 1.3 & 3.1 but, of course, I'm not a coder or ROM expert. Maybe anyone have a better project? Any help will be appreciated.

Thanks

mfilos
27th December 2011, 10:48
Your post is welcome here Pablo my friend.
I'd suggest a few things though... :P

First, you don't need NoClick module since you putted the new Trackdisk.device by Cosmos that eliminates the clicking noise alas a few bytes more left :)

One major thing you can leave out is Workbench.library that will give you enough space to put other modules instead. Workbench.library only needs to be in LIBS folder and it will work just fine (as it works for A4000T kicks).

Also the new Misc.resource has some issues to some users so better avoid it (it was removed from BB3/BB4 as well).

I'd go with the newer Filesystem.resource 45.10 (from BB2) and FastFilesystem 45.16 (from BB4) just for better FFS support.

Also... since you use Doobrey's 44.2 SCSI.device, you might have some issues if you're using PFS3 but if you're using SFS or FFS you're just fine :)

merlinkv
27th December 2011, 11:43
Hi Marios,

Thanks for the info my friend, really appreciated. :thumbsup:

I will try your suggestions this evening/night. :)

Also I want to try again with KS 1.3 & patched scsi.device... I want/need to boot WB 1.3 from my CF card using KS 1.3..... :p

Thanks again for this great Thread :bowdown:

Pablo

mfilos
27th December 2011, 14:21
Kickstart 1.3+patched scsi.device works just fine in A600 as I tried it :)

Check your PM btw

merlinkv
28th December 2011, 08:07
Hi Marios,

Thanks a lot my friend.

No way.. I'm thinking is a compatibility issue with my Mikronik KS switcher

http://www.bboah.com/display_photos/3waykick_1_sm.jpg

It has sockets for three ROMs:

1 socket for KS 1.x single chip (now with 1.3)
2 socket for KS 2.x single chip (now with 3.1)
3 & 4 sockets for KS 3.x double chip (now empty)

In socket 1 only works unmodified 1.3 ROMs :shrug:

In socket 2 original or slightly modified KS 3.1 are working great, but big upgrades are not allowed :shrug:

I will try this evening/night with one upgraded KS 3.9 (1MB) splitted in two 27C400s in the sockets 3 & 4.....

Thanks again & Best wishes

Pablo


Kickstart 1.3+patched scsi.device works just fine in A600 as I tried it :)

Check your PM btw

drbrain
6th January 2012, 11:51
First of all I want to say thanks for an awesome guide!!! :bowdown: :thumbsup:

I'm about to burn my first very kickstart ROM for my A4000.
As I understand it only supports 512KB kickstarts so I can't use the "Make_1MB_ROM" script.

I found this in the thread. Has anyone tried that and confirmed that it works?
And where do I place the HI/LO on the motherboard?
Which one goes into U175 / U176 ?
And what could happen if I place them worng? Will it simply just not work or could there be some damage to motherboard/ROMs?



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 Make_1MB_ROM 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 <your_512kb_rom_name> SWAP
(SWAP is optional and it only ByteSwaps your files for using it under your Eprom Burner)

In my example: SplitROMIMage kick39_a4000.rom SWAP
...created 2 files:
- kick39_a4000.rom.hi (256kb)
- kick39_a4000.rom.lo (256kb)

Now you can get these files and burn them to your programer.

mfilos
6th January 2012, 12:04
SplitROMIMage works like a charm man.
I can't see a reason why this method won't work as I tested it in every configuration but A4000 (soz but it's really painful to dismantle my A4000's drive bracket just to change the ROMS lol)

In A1200 the LO image goes to the top socket and the HI image goes to the lower socket.
Can't recall what is the numbering in A1200 but I guess it's similar. You won't hurt anything if you put it in reverse order. It just won't boot :)

SpeedGeek
6th January 2012, 17:17
I never used the Arexx script for building 512K or 1MB ROM's for my A3000. I just used SplitROMimage or Make1MbROM from the Remus tools directory. Swapping an even for odd ROM won't cause any damage but wrong polarity installation or ignoring 42 pin sockets could cause serious problems...

P.S. To save some space in your ROM's you can eliminate the OSROMUpdate modules.

merlinkv
10th January 2012, 08:28
Hi to all,

Maybe is a good idea to publish here a list of compatible EPROMs for 512 & 1MB ROMs?

Like....

512KB ROMs

AMD - AM27C400
.........

1MB ROMs

..............


My best wishes as allways

BlindGerMan
10th January 2012, 08:40
Cool stuff!

Does such a Kickstart 3.9 work in my good old A2k Rev 6.2, too? If yes, can anybody burn me such ROM?

Storm
11th January 2012, 12:00
Hmmm all very interesting! Since I don't have the equipment to do this but do own original 3.1 and 3.9 OS am I able to pay someone for parts and time to make a set of ROM chips for my A4000D with up to BB4 updates?

mfilos
11th January 2012, 12:13
Sorry BlindGerMan and Storm mates but it's the wrong thread to ask for burned EPROMS.
I only showed the way to do it.

There were discussions in the past about whether we'd help by providing such a service with fellow Amibayers but due to copyright shiz of these kickstarts etc, we can't make such a task.
Apart from that, every system is unique (based on it's hardware) so just making custom kickstarts especially with BB3/BB4 stuff is almost unique per machine.

Because of that but mostly because I have very limited time tbh, I'm not offering such a service. I also didn't have the equipment or knowledge of doing such a task in the past, but I got an Cheapo programmer for 20$ and after a lot of patience and tries, I managed to understand how these EPROMS work. I only offered my knowledge to the community cause back then, there weren't such thorough guides to help me out.

I suggest you either do the same, or make your own EPROMS based on my guide (files only), test them on a clone environment (your Amiga on WinUAE) and then order new blank EPROMS but burned with the ROM files that you provided from an IC company (eBay or Not). I can provide the name of the company that I buy blank EPROMS if you like but nothing more :)

merlinkv
11th January 2012, 12:19
Sorry BlindGerMan and Storm mates but it's the wrong thread to ask for burned EPROMS.
I only showed the way to do it.

There were discussions in the past about whether we'd help by providing such a service with fellow Amibayers but due to copyright shiz of these kickstarts etc, we can't make such a task.
Apart from that, every system is unique (based on it's hardware) so just making custom kickstarts especially with BB3/BB4 stuff is almost unique per machine.

Because of that but mostly because I have very limited time tbh, I'm not offering such a service. I also didn't have the equipment or knowledge of doing such a task in the past, but I got an Cheapo programmer for 20$ and after a lot of patience and tries, I managed to understand how these EPROMS work. I only offered my knowledge to the community cause back then, there weren't such thorough guides to help me out.

I suggest you either do the same, or make your own EPROMS based on my guide (files only), test them on a clone environment (your Amiga on WinUAE) and then order new blank EPROMS but burned with the ROM files that you provided from an IC company (eBay or Not). I can provide the name of the company that I buy blank EPROMS if you like but nothing more :)

100% agreed :thumbsup:

stachu100
11th January 2012, 12:20
Hmmm all very interesting! Since I don't have the equipment to do this but do own original 3.1 and 3.9 OS am I able to pay someone for parts and time to make a set of ROM chips for my A4000D with up to BB4 updates?

There are some users that cna do this for you (including myself).
The biggest problem is that there is no such thing like KS3.9 BB1+2+3+4.
All custom ROMs are done individually to meet specific needs. Something you might find usefull is total crap (or incopatible) for other used with slightly different setup.
In short: You must "prepare" your own ROM and just give the files to person with programmer + two EPROMs just to burn them and test if Amiga will boot with them.
Nothing more.

Storm
11th January 2012, 12:34
No worries.... another project to add to the list :coffee:
Done the recapping, next is the 2 GALs and then it will be the custom ROMs :bounceBoingBall:

jvdbossc
11th January 2012, 15:33
I am going to put my A4000 back together, I was hoping to fit it with rom 3.9 BBQ4 wich is exactly I have made, but how do I split it? :o Romsplit refuses to, and it's not the Arex script?

http://img59.imageshack.us/img59/9386/romspliterror.jpg (http://imageshack.us/photo/my-images/59/romspliterror.jpg/)

Uploaded with ImageShack.us (http://imageshack.us)

mfilos
11th January 2012, 15:37
Someone didn't make his homework LOL :D:D:D

ROMsplit only gets the contents of a REAL EPROM into modules or the contents of an KICKSTART image into modules. It doesn't split an ROM. This is only made by SplitRomImage command in Tools directory of Remus.
ROMsplit also, doesn't recognize custom ROMS but only official ones.



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 1MB_ROM module (if you use the 3.1 exec, or 3.9 exec since Cosmos Exec doesnt' need it anyway).
We'll leave outside though Icon.library and Workbench.library which are big and can't be left out (can be put in hard drive's LIBS: folder with no problem). That leave us all the space we need for extra modules and patches!!!

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 Make_1MB_ROM 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 <your_512kb_rom_name> SWAP
(SWAP is optional and it only ByteSwaps your files for using it under your Eprom Burner)

In my example: SplitROMIMage kick39_a4000.rom SWAP
...created 2 files:
- kick39_a4000.rom.hi (256kb)
- kick39_a4000.rom.lo (256kb)

jvdbossc
11th January 2012, 15:45
:):)

I should have clicked a few pages futher. I thought only thanks and positve comments where there..

Thanks:thumbsup:

mfilos
11th January 2012, 15:54
Yeah you're right man. I should edit and paste them on the first page as I did on my Blog entry : http://mfilos.blogspot.com/p/guides.html

jvdbossc
11th January 2012, 16:32
I am trying to adept the script, do you know wich args machinetype takes? I am close, but my scripts writes 512K files because wrong argument.

jvdbossc
11th January 2012, 19:07
Ok I took the base of the 1MB script and adopted it for to use the other tool the 1MB rom split uses different tool. This one uses splitromimage in tools. It gives a dialog to ask the file to split and then overwrites hi and lo files or writes hi and lo files.

If errorcode is 0 it returns this to the remus window. If anyting is wrong it says so.

Best I could do, I do not know Aarexx to be honest.

http://img696.imageshack.us/img696/7470/naamloosub.png (http://imageshack.us/photo/my-images/696/naamloosub.png/)

Uploaded with ImageShack.us (http://imageshack.us)

mfilos
11th January 2012, 19:32
My friend read carefully what I wrote...



In my example: SplitROMIMage kick39_a4000.rom SWAP
...created 2 files:
- kick39_a4000.rom.hi (256kb)
- kick39_a4000.rom.lo (256kb)

You just supply a 512KB Image via compile (since A4000 CAN'T use 1MB ROM) so the SplitRomImage tool gets your 512KB image and splits it into 2x256KB ROMS for you to write in a programmer into 2x256KB EPROMS and then put into Amiga.

Unless I don't understand what you want to do :)

jvdbossc
11th January 2012, 19:38
I just wrote a script to do what you are saying, so it can be selected from the Aarex window and you can stay in remus so I automated what you where saying.

To make things more easy and straightforward like the 1MB script that served as an example for the code.


My friend read carefully what I wrote...



In my example: SplitROMIMage kick39_a4000.rom SWAP
...created 2 files:
- kick39_a4000.rom.hi (256kb)
- kick39_a4000.rom.lo (256kb)
You just supply a 512KB Image via compile (since A4000 CAN'T use 1MB ROM) so the SplitRomImage tool gets your 512KB image and splits it into 2x256KB ROMS for you to write in a programmer into 2x256KB EPROMS and then put into Amiga.

Unless I don't understand what you want to do :)

mfilos
11th January 2012, 19:40
Ah!!!!!
Yeah I thought of making one myself as well but haven't messed with it yet :)

jvdbossc
11th January 2012, 19:41
Would be a waste of time now, PM me email then I'll forward it to you, so you can test it.

---------- Post added at 19:41 ---------- Previous post was at 19:41 ----------

It took me 6 hours, without any knowledge of arexx

MadAngus
14th January 2012, 04:53
Great post thank you :thumbsup: and the programmers. :bowdown:

Tickle me neurons. All this talk of EPROMS and Willem programmers jogged the old memory. I was sure I had bought one to flash some BIOS chips years ago, and so I went rummaging around my stacks of boxes and look what I found an Enhanced Willem Programmer. :D

A little more rummaging on my file archive and I found the schematics for the 40/42 pin 16Bit Adapter. Thought someone might be interested in them, so I've attached them. The schematics and layout are in MS Word doc format. If you open them up in OpenOffice writer you can right click on the images and save the graphics to disk.

I couldn't help myself, so went and done some more digging on the Wayback machine and found that all the Willem adapter schematics are still there. Here's the link (http://web.archive.org/web/20041103094325/http://www.willem.org/) (on the left menu select "more downloads"). Last update was Nov 2007. Just had to download them all. I'm a file junkie. Oh, and here's another related Wayback link to the mpu51 site (http://web.archive.org/web/20040813044913/http://mpu51.lunarpages.com/eprom/eprom.html#adapter-MCS-48).

And now that you've got me interested, I'm going to have to add this to my todo list. :thumbsup:

[Edit]
I should have also pointed out the schematics for the Willem programmer v4.5 pcb are also there.

mfilos
14th January 2012, 09:47
Hehe I'm glad you like the guide mate. These wayback pages are nice finds mate.
I'm sure Zetr0 will love these schematics (as he a schema junkie lol).

merlinkv
14th January 2012, 20:06
Hi to all :)

Maybe an stupid & noob question but I just received a couple of new EPROMS :

Toshiba TC574200D-120

These are compatibles to burn Amiga 512KB ROMs?

Thanks in advance :bowdown: :bowdown:

mfilos
14th January 2012, 23:16
These are perfectly compatible my friend. In fact they are the best EPROMS that I've used and never had any issue with them.

I also have them on 120ns as well :D

merlinkv
14th January 2012, 23:44
Hi Marios my friend.

Great news!!! Time to more experiments :D

All the best


These are perfectly compatible my friend. In fact they are the best EPROMS that I've used and never had any issue with them.

I also have them on 120ns as well :D

trip6
20th January 2012, 04:57
I heard that someone here mightbe able to produce for me some 3.9 roms for the A1200 with the appropriate OS3.9 and boing bag 1 & 2 additions to the roms. I own a legal OS 3.9, OS3.1 and legal 3.1 Roms. Is there anyone who can produce these for me? I have neither the time nor epromming equipment myself. Any help would be greatly appreciated. PM or Post here.

mfilos
20th January 2012, 08:34
http://www.amibay.com/showpost.php?p=255574&postcount=124

merlinkv
25th January 2012, 23:04
Hi Marios,

I made some test with the Toshiba TC574200D-120 and I agree with you, these EPROMs are the best ones I used. :thumbsup:

For now I updated the A500 (with KS switch) and the A600 and both works great :)

Tomorrow I will try with the A1200 and the A4K's..... :coffee:

My best wishes as allways my friend

Pablo

mfilos
25th January 2012, 23:53
Awesome my friend!!! Keep us posted :D

merlinkv
27th January 2012, 13:27
Hi again,

Well, my first A600 1MB ROMs works.

Now KS boot screen shows: 3.9.1 / 45.74

Classic WB & WB 3.1 also run good.

but.....

I receive all times one window request with: Insert Volume ENV in any drive.... :blink: , jut clicking on Cancel, all boots without problems.

Any idea to solve this issue?

Tomski
27th January 2012, 13:58
You all may be interested with RemApollo 1.8 version. What is interested in this version that supports 1MB ROM. But so far no one knows how to prepare kick to work - even autor do not remember well, too. Here is a link for download remapollo1.8 (http://www.ppa.pl/programy/remapollo-1.8.html)
and for version 1.7 wich one is requested to upgrade from it : remapollo1.7 (http://68k.aminet.net/package/util/boot/RemAPollo)

mfilos
27th January 2012, 15:54
Thanks for sharing Tomski mate.
Does it requires a special version to be able to kick an 1MB ROM then?

The 1MB ROM procedure isn't something peculiar. It works just fine on burned EPROMS and Loading it via WinUAE.

Storm
4th February 2012, 04:20
Just finished putting all my ROM updates in my new Deneb card and now it boots as a full 3.9 machine :thumbsup: No need for a custom EPROM anymore and far easier to update as well.

drbrain
7th February 2012, 23:33
I've now tried a couple of times burning a regular Kickstart 3.1 (no extra or replaced modules) for my A4000. But they just won't work in my A4000, no boot.

I ripped my Kick3.1 from my A4000 with "transrom >ram:kick31.rom"... tested the rom with WinUAE and it booted to kickstart screen as it should.
I ran "SplitROMIMage kick31.rom SWAP" and it created 2 files:
- kick31.rom.hi (256kb)
- kick31.rom.lo (256kb)

Those where then burnt with my Willem parallel burner and they burnt/verified OK... but no boot when put in my A4000. (I've tried the HI/LO in both sockets, still no luck)

Is there anything obvious I'm missing here? :unsure:

mfilos
7th February 2012, 23:44
first of all... it seems that you want to make a copy of your ROM right?
If so... then why don't you just take the ROMS and perform a READ on Willem and then WRITE to an empty one?

Anywayz... procedure seem just fine. I'd suggest to not use SWAP parameter and instead, use the ByteSwap procedure through Willem.

drbrain
8th February 2012, 08:44
Yes, I want to make sure a plain copy of a 3.1 ROM works for now....
And when I'm sure that works I want to add/replace modules (perhaps make a 3.9 ROM).. so I would like to use all the required programs so I know they work and I learn how to use them :)

I'll try byteswap within the burner program instead...

mfilos
8th February 2012, 08:58
Also don't forget that the EPROMS need to be at worse 120ns of speed.
Anything slower than that won't run on the Amigas.

I definitelly suggest some Toshiba EPROMS that tend to be really resilient. AMD's are ok as well though.

drbrain
8th February 2012, 09:21
I use "AMD AM27C400-120DC" from here http://www.buyicnow.com/fincat.php?cat=98
They should work ok right?

mfilos
8th February 2012, 09:30
Yeah you should be fine mate.

drbrain
8th February 2012, 11:55
Still no luck in burning a rom I splitted myself :(
I tried doing the byteswap in the burning program but that didn't work either, still no boot.

I also tried to read one of the original ROMs and then burn it directly from the buffer.. and that works. It boots fine then...
So clearly I must be doing something wrong when splitting/bruning my ripped ROM :unsure:

merlinkv
8th February 2012, 12:05
Hi,

Under Remus, select "Split & Swap 16 bit" then burn directly the .HI & .LO files.

mfilos
8th February 2012, 12:08
Ok I was thinking one thing....
- 27C400 is an 512KB ROM
- Amiga 4000 uses 2x256KB ROM.

So... MAYBE the problem is that the ROM needs to be full (not sure about it) but I'd suggest to double the info to it.

For example to make a dual Kickstart with 1.3 and 3.1 you need to double the 1.3 (being 256KB) and join it with the 3.1 (being 512KB) to form the 1MB ROM to burn to an 27C800 EPROM.

I'd make 2 tests if I were you.
1. Make the ROM (512KB) then double it on the Amiga and the SplitROMImage it and burn it.
2. Make the ROM (512KB) then SplitROMImage it and then on PC, double each file and burn it.

drbrain
8th February 2012, 13:06
@merlinkv
Just tried that... still no boot.

@mfilos
How do I double a file?

merlinkv
8th February 2012, 13:18
@merlinkv
Just tried that... still no boot.?

If possible, I will check again this evening/night and inform you.

jvdbossc
8th February 2012, 13:31
My supplier can be mailed and rom speed can be selected

http://www.buyicnow.com/fincat.php?cat=98

Probably copy + but wait for mfilos since I see you had some bad luck already. copy file1 + file2 output.out

mfilos
8th February 2012, 14:47
Yeah it's something like that.
For example under DOS you can double it like this:

C:\> copy kick256 /B+kick256 /B Kick512 /B

/B option indicates that the file is binary cause if you don't you'll have a file that is 1KB lol.

Under Amiga it must be something similar that I'm gonna check and report back.

SpeedGeek
8th February 2012, 19:29
Also don't forget that the EPROMS need to be at worse 120ns of speed.
Anything slower than that won't run on the Amigas.


You do not need 120 ns ROM's and unless you over-clock your motherboard and want to use the shortest ROM timing. I use 150 ns ROM's with my A3000 ROM speed jumpers set to the shortest timing and I've over-clocked my A3000 motherboard to 30 MHz with no problems. In fact you could use 250 ns ROM's at the standard 25 MHz clock speed with the longer ROM timing.

mfilos
8th February 2012, 19:48
U the man SpeedGeek mate. I was just told for quite some time now that 120ns was the fastest speed for Amiga EPROMS.
Nice to know that this is an urban legend. :)

jvdbossc
8th February 2012, 19:52
I had a 150 NS roms in my A500 they did NOT WORK properly. I think it depends.

SpeedGeek
8th February 2012, 20:00
@ jvdbossc

You probably had a ROM compatability problem rather than a ROM timing problem. A zero wait state Zorro2 cycle (or 7 MHz Gary ROM cycle) takes 560 ns! (Although data on read cycles is latched 1/2 clock before cycle end + 1/2 clock (68000) address valid time = 420 ns). Should be no problem with 250 ns ROM's on a A500!

@mfilos

Notes: J150, J151: Rom Timing
The rom timing circuit provides four different speed settings to match the output enable, and access timing of the system roms.
To set the jumpers, determine the output enable time, and access times for the roms you wish to use. The rom must have lower values than for the setting you select.
System standard roms have Toe = 110 ns, and Tacc = 250 ns.

CLK J151 J150 Toe (min) Tacc (min)
16 Mhz 2-3 2-3 157 ns 250 ns
16 Mhz 2-3 1-2 220 ns 312 ns
16 Mhz 1-2 2-3 282 ns 375 ns
16 Mhz 1-2 1-2 345 ns 437 ns
25 Mhz 2-3 2-3 90 ns 160 ns
25 Mhz 2-3 1-2 130 ns 200 ns
25 Mhz 1-2 2-3 170 ns 240 ns
25 Mhz 1-2 1-2 210 ns 280 ns

Note: The A4000 has only one ROM timing jumper!

jvdbossc
8th February 2012, 20:06
You can be right. I will test your theory :roll::thumbsup: Meaning buy a few slow ones..

SpeedGeek
8th February 2012, 21:00
@ jvdbossc

From my 2.04 ROM upgrade kit instructions:
- A500 motherboard rev. 3 and 5 connect (jumper) ROM pin 1 to pin 31
- A500 rev. 6A and above cut or remove jumper from ROM pin 1 to pin 31

P.S. Please don't spend your hard earned money just to test my theory! ;)

drbrain
9th February 2012, 10:41
Yeah it's something like that.
For example under DOS you can double it like this:

C:\> copy kick256 /B+kick256 /B Kick512 /B

/B option indicates that the file is binary cause if you don't you'll have a file that is 1KB lol.

Under Amiga it must be something similar that I'm gonna check and report back.

Wow.. that did the trick :bowdown:

I just split my ripped ROM with "splitromimage" and doubled both HI and LO with the command above.
ByteSwapped in the Willem program and burned.. now it works :thumbsup:

Thanks for all the help!!!!!!

Oh and btw.. the "LO" ROM goes in "U176" and "HI" in "U175" on the A4000 motherboard.

Perhaps this solution should be copied to the first post of this thread...

mfilos
9th February 2012, 15:46
Thanks for the feedback mate.
I'm glad it worked for you :)

I already edited the first post plus my Blog entry for it :)

Cheers

jvdbossc
9th February 2012, 23:10
@ jvdbossc

From my 2.04 ROM upgrade kit instructions:
- A500 motherboard rev. 3 and 5 connect (jumper) ROM pin 1 to pin 31
- A500 rev. 6A and above cut or remove jumper from ROM pin 1 to pin 31

P.S. Please don't spend your hard earned money just to test my theory! ;)

I need to know.. for me the glass is half full or half empty, but next local meeting we are going to do a workshop. Although credit people is important - I do not wan't to give wrong information to people...

Jaymz
10th February 2012, 20:30
Wow! fancy doing a few and selling to the community? (If we prove we have the OS 3.9 & 3.1 ROMS of course).

I am just NOT technical! LOL!

:thumbsup:

drbrain
11th February 2012, 13:00
I've now made my very first custom ROM following the guide.. a 3.9 ROM for my A4000 (to bad it won't support 1MB ROMs as space is very limited with 512KB)

It worked at first try... fantastic... no more extra reboot :D

SpeedGeek
11th February 2012, 16:04
I've now made my very first custom ROM following the guide.. a 3.9 ROM for my A4000 (to bad it won't support 1MB ROMs as space is very limited with 512KB)

It worked at first try... fantastic... no more extra reboot :D

Get yourself a thru-hole 84 pin PLCC socket and pre-drilled experimenters PC Board. Then read this thread and pay some attention to protek's post:

http://www.amibay.com/showthread.php?t=21720

merlinkv
19th April 2012, 09:40
Hi Marios, my friend :)

Due lack of space I want to burn a dual ROM 1.3-3.1 for one of my A600s.. I have all needed materials.. 27C800, switch, cables, programmer.,....

I knew you have realised this hack in the past... where I can find detailed instructions (mounting & programming) ?

Maybe here? Sorry I'm a bit lost :picard ... too many post in this thread :)

Thanks in advance

Pablo

mfilos
19th April 2012, 15:21
No worries Pablo my friend.
You require both the 1.3 kickstart (256KB image) and the 3.1 kickstart (512KB image) for your A600. Then you do the following:
Open a DOS prompt and issue the following command:

C:\> copy /b kick13.rom + /b kick13.rom + /b kick31.rom DualKick.bin

This will double the 1.3 image to be 512KB and also add the 3.1 image. The output file "DualKick.bin" should be 1MB of space.

Only thing you're left to do now is to fire up your Willem software and open the image (DualKick.bin) and then perform an "Byteswap" operation and Burn to your 27C800.

That's all :)

After the image is burned you need to lift the Pin1 of the EPROM, mount the EPROM to the A600 and wire the Pin1 to the middle pin of an 3pin switch (on/off/on).
The other 2 pins should be wired to GND and to +5V (with an 4k7 resistor between).

One side of the switch is 1.3 Kickstart and the other side the 3.1 Kickstart. Just be sure you won't switch with the Amiga open :)

I have a schema on my Blog as well, if you have an ACA630, and you want to disable ACA simultaneously on 1.3 mode or enable simultaneously on 3.1 mode!
http://mfilos.blogspot.com/p/dual-kickstart-switch.html

Give a feedback once you're ready for me to be happy I helped :)

merlinkv
19th April 2012, 18:06
Hi Marios my friend,

Thanks a lot :thumbsup:

I will try to buy a batch of different switchs this weekend :)

Best wishes

Bad_Ad84
19th April 2012, 18:18
You can use a on/off switch too. Resistor between 5v and pin 1, switch to pin 1 and ground.

Basically is a pull up resistor, when switch is on its logic low, off is high (pulled up by resistor).


Sent from my iPhone using Tapatalk. Please excuse any crazy auto corrects or lack of detail (links to info sources)

Bad_Ad84
22nd April 2012, 15:10
I followed your guide (many thanks!)

And the amiga (and WinUAE) will boot to the Kickstart 3.9 screen.

However, when it attempts to boot from floppy or HDD - it will just reboot over and over...

Have you seen this before?

Any suggestions? :)

Edit:

I think it might be my scsi.device...

Think ive fixed it, burning new roms

merlinkv
23rd April 2012, 09:38
Hi Marios, my friend :)

Yesterday I've burned my first 3.9 BBx 1MB ROMs for my A1200 PPC following your great tutorial. System boot incredibly fast and works great :thumbsup:

Only one issue I have found.... If I want to made a clean install of WB 3.1 all times I get the Ramlib error and systems hungs..... Maybe it's a Stack problem? Which module is the best to increase the default Stack size at boot time?

Of course I can Install 3-1-3.9 under WinUAE and then reinstall the CF-HDD on my A1200. But sometimes I like to do "classic" installations using the FDDs & CD on my Amiga's. :roll:

All the best

Pablo

mfilos
23rd April 2012, 10:09
Yep, the ramlib error is typical while loading the previous OS version (3.1).

Sadly you can't use WB 3.1 with the 3.9 Kickstart Pablo my friend. Only OS3.9.
I dunno what module is incompatible (I guess it could be the workbench.library).

merlinkv
23rd April 2012, 11:01
Tahnks for the answer my friend. :)

OK, I will try... Maybe I can find the solution.... :roll:

johnim
23rd April 2012, 12:30
hi guys i had the ram lib error i think it was the scsi.device too

merlinkv
23rd April 2012, 13:26
hi guys i had the ram lib error i think it was the scsi.device too

Mmmmmm.... the scsi.device? Maybe... I will try this evening/night

Thanks John :thumbsup:

InsertDisk3
13th June 2012, 15:13
Hi guys, is it not possible to pack/chrunch the library/devices in the ROM?

mfilos
13th June 2012, 18:16
What for? To earn some space?
You can use 1MB ROM for a lot of ROM modules without hassle :)

Apart from that, even if you could pack the ROM modules, wouldn't the Amiga need a method of unpacking them from the ROM in order to use them?
I seriously doubt that it can be done but whoever knows better can correct me.

InsertDisk3
14th June 2012, 14:43
Yes, for more "space" on a A4k 512MB Rom.
Without the workbench.library on Disk you can not boot form this.
And for 1MB Rom in A4k you must make a mega hardware hack.

FOL
14th June 2012, 14:47
Yes, for more "space" on a A4k 512MB Rom.
Without the workbench.library on Disk you can not boot form this.
And for 1MB Rom in A4k you must make a mega hardware hack.

Nope you cant pack them. Unless remus is altered to do so, abit like Deneb does.
You can always put the workbench library on the HDD, it will run fine.

SpeedGeek
14th June 2012, 15:26
Yes, for more "space" on a A4k 512MB Rom.
Without the workbench.library on Disk you can not boot form this.
And for 1MB Rom in A4k you must make a mega hardware hack.


WTF? This is a mega hardware hack? (GAL chip + PLCC socket(s) + .1uF cap + small PCB)

http://www.amibay.com/showpost.php?p=274602&postcount=40

Bad_Ad84
14th June 2012, 15:43
He's not selling the PCB's though.

(but its still not a difficult mod)

SpeedGeek
22nd June 2012, 15:45
** NEWS UPDATE **

I've been using 1MB 3.9 ROM's in my A3000/040 for 8 months now and it took me this long to realize Doobrey's "DummyCDstrap" hack does NOT provide cache enabled access to extended ROM! http://eab.abime.net/images/smilies/banghead.gif

So if you have a 1MB ROM(s) and a 68040 or 68060 and want cache enabled for extended ROM here are a few options for you!

1) Add this command from http://www.sinz.org/Michael.Sinz/Enforcer/Enforcer.lha to user startup: MMU address $E00000 size $80000 cache noshow

2) Install MMULib from http://aminet.net/util/libs/MMULib.lha and add this to MMU-config: Setcachemode 0xE00000 size 0x80000 ROM WRITETHROUGH

3) Downgrade your 68040 or 68060 to a 68030! http://eab.abime.net/images/smilies/laughing.gif

Enjoy!

mfilos
22nd June 2012, 21:48
AFAIK DummyCDstrap only had meaning for PPC accelerator (might be wrong though).
Thanks for the informative post as always SpeedGeek :D

SpeedGeek
23rd June 2012, 01:38
mfilos my friend welcome back to Amibay! :) Just in case the Remus documentation is not clear, here is a little more detailed info from a recent email I received from Doobrey (email address' removed for privacy):

"Hi Kevin,
...
DummyCDstrap is only used to get around a problem with some 68040/68060 libraries. Some of them setup the MMU to block reading the 512KB ROM @ E00000 unless it finds a resident called 'cdstrap' (pure coincidence, the CDTV has a memory card slot that uses the same address as the 'extended' ROM) so DummyCDstrap doesn't actually 'do' anything itself, it's just a placeholder for the name...

Jeff"

diskers
10th July 2012, 21:50
Hi everone,
I have perhaps a dump question i made a A1200 3.1 with some mods but i cant remember where each rom goes is lo is going at the bottom, near the end of the keyboard and case and hi above it or otherwise. :unsure:

mfilos
11th July 2012, 12:13
If you check my guide you will see that it says at some point:


Ok for testing your Kickstarts now make sure... That you insert the EPROM burned from LO file into the top Kickstart socket...
...and the EPROM burned from HI file into the low Kickstart socket.


So...
- LO file --> Top Kickstart socket
- HI File --> Low Kickstart socket

diskers
11th July 2012, 17:04
Thanks a lot
I wasn't sure for the A1200 I thought that you were refering to the A4000 only, and I wasn't sure if it's the same. Sometimes better ask than be sorry :)

ByteRyder
21st September 2012, 11:12
@mfilos
Thank you so much for a great great guide my friend. It's really fun to play around with the maprom function with ACA-1231 running 1MB custom ROM. :)

I have followed your guide instructions step by step so my ROM is very similar to yours. I'm only finding a couple of issues so far;

- The popup menus added by ClassicWB39 have disappeared.

- If I copy any new font to FONTS: and run Fixfonts almost all fonts can't get recognized by workbench, only a couple default ones work and it won't let me use any new fonts.

Any clues as to why this happens?

Apart from that, workbench is really fast and responsive.

Thanks again!!! :)

Rakeim132
22nd September 2012, 02:45
Question : is it possible to burn EPROMs with a USB programmer like THIS ONE (http://www.ebay.com.au/itm/True-USB-Willem-ECU-EPROM-BIOS-SPI-universal-Programmer-/310332493508?pt=AU_B_I_Electrical_Test_Equipment&hash=item4841420ec4)?

Reason is to find a PC with DB25 parallel port now a days is not easy...

Thanks.

rkauer
22nd September 2012, 06:09
Yes, you can use a USB programmer. But not those that only have USB power: those are horse poo.

Rakeim132
22nd September 2012, 08:24
Ha thanks. Can you suggest one model ?

merlinkv
22nd September 2012, 09:11
Question : is it possible to burn EPROMs with a USB programmer like THIS ONE (http://www.ebay.com.au/itm/True-USB-Willem-ECU-EPROM-BIOS-SPI-universal-Programmer-/310332493508?pt=AU_B_I_Electrical_Test_Equipment&hash=item4841420ec4)?

Reason is to find a PC with DB25 parallel port now a days is not easy...

Thanks.

Hi mate,

I don't know now, but in the past I've bought the same programmer and I had very bad experiences with 27C400 & 27C800 EPROMs.

Finally I sell the GQ-4X and I bought one Wellon VP-590. It works like a charm not only for suitable Amiga EPROMs also for many different EPROMs, EEPROMs. ...... without adapters. Ah! and works fine under Win x86 or x64.

Best wishes & good look :thumbsup:

Rakeim132
22nd September 2012, 15:00
Thanks mate. Not cheapos, these ones...

merlinkv
22nd September 2012, 21:46
Thanks mate. Not cheapos, thoses ones...

Yes I know that :lol:

I you want a programmer to use only few times you can find cheap ones elsewhere....

But if you want a programmer for "daily" use and for a wide variety of chips, it is advisable to buy some in the upper-middle range.

I have bought my VP-590 as a recommendation from @stachu100 (thanks my friend). For my needs is the most appropriate and I'm very happy with the purchase.

bitcpy
24th September 2012, 03:46
I personally have been using Xeltek products for many years and have a Xeltek Superpro 3000U that does all of my EPROM programming.

I've owned my Xeltek 3000U for 7yrs I believe, and it has been super-reliable and never given me an ounce of trouble.

The one I have has been replaced with a more powerful model but I would suggest even trying to grab a bargain on eBay. The 3000U does everything and it is pretty fast.

http://www.xeltek.com/pages.php?pageid=258



Thanks mate. Not cheapos, these ones...

alexh
26th September 2012, 12:19
I'm creating some OS3.9 ROM's for my Amiga 1200.

Is it worth examining this guide and looking at using newer versions of some files the unofficial AmigaOS 3.9 BB3 & 4?

mfilos
26th September 2012, 16:24
Definitely Alexh.
Personaly I'm using many of the newest BB3/BB4 modules for my A600 even when using a beefed 3.1 Kickstart and not an 3.9 one :)

I can certainly post some of the modules I have in my collection and are useful and stable to use (like PeterK's icon.library, DonAdan's dos.library, Doobrey's scsi.device etc).

Rakeim132
27th September 2012, 08:25
Thanks everyone for your inputs about EPROM burners models which works well.

Perhaps a bit off-topic but it's hard to make EPROMS without the equipment. :D

alexh
27th September 2012, 15:25
If you're running AmigaOS3.1 when using this guide, do you need to install something else to get the ARexx scripts to run from Remus?

I have rmh.library and rxasl.library installed in DH0:Libs but nothing happens when I selected Make_1MB_ROM.rx

Nevermind, I read the Make_1MB_ROM.rx script and worked out


Remus/tools/Make1MegROM STD=RAM:39normal.rom EXT=RAM:39extended.rom TO=RAM:alex.rom MACHINE=A1200 BYTESWAP

mfilos
27th September 2012, 17:07
Alexh iirc you also need rxtoolkit.library (it's on the same archive as rmh/rxasl) and also popupmenu.library.

I made an archive some time ago with all the required files which you can get from here:
https://dl.dropbox.com/u/939939/Remus_Required_Files.lha

It's easy as you done to see the script yourself hehe :)
I did that as well when I wanted to disect/byteswap an 512KB image for an A4000 which the Arexx script didn't support \o/

alexh
27th September 2012, 18:00
I installed everything in the dropbox in dh0:LIBS. There must be some component missing for a fresh OS3.1 install?

My ROM's burned and I get the KS3.9 boot screen but CF card in A1200 IDE is not booting.

Perhaps I screwed up the patching of scsi.device or patching of FastFileSystem? :(

I tested my ROM image in WinUAE but it must boot using UAE.device or something?

mfilos
27th September 2012, 22:06
Will create a stock 3.1 installation tomorrow mate and try and see what's the matter with Remus and what is needed for sure.
I'll let you know what my finding are here :)

Concerning booting, I use on WinUAE, UAE under HD controller and never had an issue with it.
You don't need to patch scsi.device or FastFileSystem (patching is only needed for scsi.device for 1.3 Kickstart).
You only need to put them in the correct order in Remus. I'd recommend some newer scsi.device like Doobrey's 44.2 or Toni's/Chris's 43.45. Latest stable version of FFS is 45.16 from BB4.

gseb
6th October 2012, 18:49
Hello,
I created the 2 roms set as pro instruction (for A1200). I then create one rom choosing A2000 in arex button because I wanted to kicksoft the created rom with blizkick....
The normal and extended rom are booting fine under winuea.

Blizkick give me an error at boot, "blizkick failed return error 10.

Is blizkick able to kicksoft this created 3.9 rom ?

Thanks in advance for the help.

Edit : I found the answer here : http://www.amibay.com/showpost.php?p=327281&postcount=7

I will have to burn...

jvdbossc
4th November 2012, 15:56
Marios, the boot delay for a hard disk what module does it dictate? Is that scsi.device? Is there anyway to thinker with that delay? I find it way to long to be honest.

mfilos
4th November 2012, 18:23
@gseb
You can use a custom 3.9 kickstart with BlizKick. You just need to make it 512KB leaving out the Workbench.library (which can reside in Libs).

@jvdbossc
I dunno if it's the scsi.device or an exec or anything else.
You can decrease that delay easily with SpeedyIDE module, or NoIDE module if you don't use IDE at all (SCSI from accelerator)

NMI
4th November 2012, 19:41
Brilliant thread! And a great "Thank You!" to everyone contributed with the software and suggestions.

But, I must be missing something, or quite a lot actually...
I can't find the 1MB_ROM Blizkick module mentioned in the first post?


Then I read on and found that using the exec.library from BB4 made the module obsolete, great!
But I can't find any exec.library in BB4??? :blink:


How do I find the files I'm missing?
Or, what is the current recommended file list to use for an a1200 OS3.9 ROM?

jvdbossc
4th November 2012, 19:53
txs:thumbsup::thumbsup:

mfilos
4th November 2012, 20:16
But, I must be missing something, or quite a lot actually...
I can't find the 1MB_ROM Blizkick module mentioned in the first post?
...
Then I read on and found that using the exec.library from BB4 made the module obsolete, great!
But I can't find any exec.library in BB4??? :blink:
...
what is the current recommended file list to use for an a1200 OS3.9 ROM?
The 1MB_ROM module is included on the default Remus installation under Other/Blizkick folder
I'd strongly suggest to use the Exec from BB2 as it's troublefree and you only need to use the 1MB_ROM module which is tiny anyway :)

There is not a recommended file list as you can put whatever you want in the ROM and try based to your needs.

For example my current Kickstart 3.9 ROM for my A600 has the following:



BB2 modules
- exec.library 45.20 (from BB2)
- bootmenu 44.7(68020) (from BB2)
- filesystem 45.16 (from BB2)
- input.device 50.26 (from BB2 patched by Remus)
- ram-handler 44.24 (from BB2 patched by Remus)

BB3/BB4 modules
- console.device 44.10 (from BB3/BB4)
- datatypes.library 44.48
- shell 45.27 (from BB3/BB4)

PeterK's modules
- icon.library 46.4.264 (from PeterK)
- workbench.library 45.132 (patched 45.131 by PeterK)

DonAdan's modules
- battmem.resource 40.0 (from DonAdan)
- filesystem.resource 46.0 (from DonAdan)
- mathffp.library 41.0 (from DonAdan)
- misc.resource 38.0 (from DonAdan)
- potgo.resource 38.0 (from DonAdan)
- workbench.task 40.0 (from DonAdan)

Some new modules
- scsi.device 44.2 (from Doobrey)
- intuition.library 41.0 (patched intuition from 3.9 kick)
- hrtmodule 2.33

BlizKick/Remus modules
- BBlank (from BlizKick)
- NoClick (from BlizKick)
- PatchMath020 (from Remus installation)
- romfixes2 (from Remus installation)


Btw... in order to use an 512KB beefed Kickstart 3.9 ROM you'd need to leave outside the ROM the large Workbench.library so you'd need to put WBFind module instead inside the ROM.
That module just tells your Amiga to look for Workbench.library to your LIBS folder instead :)

Hint: Not a bad idea, when you want to make a Dual 1.3/3.9 Kickstart being able to toggle by a switch! \o/

nivalis
22nd November 2012, 01:48
Great guide, made myself a custom rom for blizkick on my a1200 ;)

mfilos
22nd November 2012, 11:24
Thanks a lot for your comment mate.

I made some minor editing to the first post concerning some more info about A4000 kickstart ROMS (needing WBFind module in order to locate 100% correctly the workbench.library in LIBS).
Also removed the ROMUpdate module (from the list of BB2 modules) as it's not needed in custom ROMS and can sometimes create problems if present.

Keep up burning and softkicking peepz :P

TheDark
26th January 2013, 17:10
Hi,

I am interesting to do this upgrade to kickstart v3.9, i have some questions :

- Does this upgrade have any interest with Amiga 500 or A2000 ?
- What are the most usefull benefit to put a kickstart 3.9 instead of a 3.1 into A500/A600/A1200 or A4000 ?
- Does this upgrade is better than the other named "Romy" for A4000 ?
- Where to have can i purchase 3.9 Roms ?

Thks for your advise.

roy_bates
26th January 2013, 18:03
Hi,

I am interesting to do this upgrade to kickstart v3.9, i have some questions :

- Does this upgrade have any interest with Amiga 500 or A2000 ?
- What are the most usefull benefit to put a kickstart 3.9 instead of a 3.1 into A500/A600/A1200 or A4000 ?
- Does this upgrade is better than the other named "Romy" for A4000 ?
- Where to have can i purchase 3.9 Roms ?

Thks for your advise.



sorry about this,the last question on your list will never be answered as its against site rules and any other site for that matter.

mfilos
26th January 2013, 19:59
@TheDark

Does this upgrade have any interest with Amiga 500 or A2000 ?
It sure does, but only if you don't want the extra restart that Amiga OS3.9 BB2 Update does OR if you want to use newer modules than the ones provided with older Kickstarts.


What are the most usefull benefit to put a kickstart 3.9 instead of a 3.1 into A500/A600/A1200 or A4000 ?
Answered that in the previous question.


Does this upgrade is better than the other named "Romy" for A4000 ?
Romy for A4000 is just a project that enables an A3000 or A4000 to be able to use 1MB Kickstart ROMS (or even bigger in the future).
A600/A1200 can handle 1MB ROMS by default, and iirc A500/2000 can handle it as well, by getting one signal from Garry as well.


Where to have can i purchase 3.9 Roms ?
Kickstart 3.9 can't be sold as Kickstart is still under copyright.
That's the reason I made this thorough guide, for anyone to be able to make such a custom ROM.
If you don't have a programmer, there is no problem to make the ROM and when buying empty ROMS telling the seller to burn your image to it.

Storm
27th January 2013, 04:07
mfilos, where did you get the DonAdan modules from?

mfilos
27th January 2013, 09:08
mfilos, where did you get the DonAdan modules from?

There you go mate :)
http://wt.exotica.org.uk/test.html

Storm
27th January 2013, 11:32
Thanks mfilos. I love tweaking :thumbsup:

Update: It looks like many of the files aren't on his site now.

Something I have noticed in my custom rom is a file called 'bonus'. Hex reading the file show A4000 bonus.bonus 40.1 (15.2.93)
I have also deleted the ROMupdate file as you said it's not needed with all the other updates. Since there is no rom update files anywhere now, is it necessary to still add the NOROMUPDATE to setpatch?

TheDark
29th January 2013, 10:38
Hi,

Thks to all for you answer.
Can someone advise me concerning the hardware needed to create my custom roms so ?
Which programmer and eprom model does i need ? (mark/label/models)
Someone know a good website for deal with it ?
How much does it cost to me ?

Best Regards.

roy_bates
29th January 2013, 10:50
for a 1200 say for instance, you could use a willam programmer and two 27c400 eproms about 150ns.

price varies from supplier to supplier,try to shop around

TheDark
29th January 2013, 16:03
What kind of Eprom does i need for A500 / A600 ?
Someone have good url/weblink for purchase it with programmer ?

Thks.

mfilos
29th January 2013, 19:15
You just need an El'Cheapo programmer found on eBay (something like this (http://www.ebay.co.uk/itm/PCB5-0-Willem-EPROM-Programmer-PIC-BIOS-Ship-from-USA-/360573486748?pt=LH_DefaultDomain_0&hash=item53f3dac69c&_uhb=1), but with a little search you might find a cheaper one localy) plus an 16bit adapter with DIP40 or DIP42 socket (like this (http://www.ebay.co.uk/itm/EPROM-16bit-Adapter-DIP42-Willem-EPROM-Programmer-E17-/200544515741?pt=UK_BOI_Electrical_Test_Measurement_Equipment_ET&hash=item2eb162769d&_uhb=1) for example)
For an A500/600/2000 you need 40pin EPROMS like 27C400 (512KB) or 42pin EPROMS like 27C800 (1MB).

Storm
30th January 2013, 08:00
Something I have noticed in my custom rom is a file called 'bonus'. Hex reading the file show A4000 bonus.bonus 40.1 (15.2.93)
I have also deleted the ROMupdate file as you said it's not needed with all the other updates. Since there is no rom update files anywhere now, is it necessary to still add the NOROMUPDATE to setpatch?

Has ROM Guru got an answer to this question?

mfilos
30th January 2013, 23:49
Bonus module exists only in A4000 and A3000 ROMS (and there is also an updated version from Don Adan) but I certainly don't know what exactly it does :)

SpeedGeek
31st January 2013, 00:57
The primary purpose of the Bonus code is to configure up to 16MB of motherboard Fast memory. When the first A3000s shipped with Kickstart 1.4 there was not enough room in the 256KB 1.x for the Bonus code and scsi.device Resident modules. ;)

Storm
31st January 2013, 07:29
Thanks SpeedGeek and mfilos for your answers :thumbsup:

psychoman
18th April 2013, 10:55
Hi, and thanks a billion for this sweet howto!
I have now baught an willem programmer and burned my first custom rom, but without any joy at all :/ so i erased the eprom and verified that they where clean, everything ok! so I tought that maybe the romīs Im trying to program is to slow, so I made copies of my original 3.1 roms from my amiga in the willem programmer and burned them to the eprom and guess what, it booted straight away! no problem at all, am i missing something? I did follow everything point to point, made sure the exec module was inserted first in low rom and romheader and dummycdstrap first in hi rom and let remus do the byte swap for me, but one thing that is strange is that my copied roms from the willem programmer is 1mb (1024kb) each and those from remus is 512kb, this might be normal, everything above the 512 kb is just 0's I guess? but it aint anything like that it has to be something there, iīm actually a little bit confused why the copied roms from willem is 1024kb while the rom itself should be 512kb, i'm going to burn my custom roms again to see if there might have been something wrong with the first programming, if not, i'm kinda clueless and would appreciate any help that i might have done wrong, did this before posting, still no joy.. and i accendently damaged my original hi rom! :wooha: :Doh: :/ ohh, the rom from remus is tested and works perfectly in winuae as main and extended, so since they work in winuae and the eproms works with my copied original rom i'm just confused right now :/

going to fetch another original 3.1 roms and another setup of burnable eprom and see what happens, :thumbsup: for this sweet howto! (i used m27c800 eprom's)

roy_bates
18th April 2013, 11:05
Hi, and thanks a billion for this sweet howto!
I have now baught an willem programmer and burned my first custom rom, but without any joy at all :/ so i erased the eprom and verified that they where clean, everything ok! so I tought that maybe the romīs Im trying to program is to slow, so I made copies of my original 3.1 roms from my amiga in the willem programmer and burned them to the eprom and guess what, it booted straight away! no problem at all, am i missing something? I did follow everything point to point, made sure the exec module was inserted first in low rom and romheader and dummycdstrap first in hi rom and let remus do the byte swap for me, but one thing that is strange is that my copied roms from the willem programmer is 1mb (1024kb) each and those from remus is 512kb, this might be normal, everything above the 512 kb is just 0's I guess? but it aint anything like that it has to be something there, iīm actually a little bit confused why the copied roms from willem is 1024kb while the rom itself should be 512kb, i'm going to burn my custom roms again to see if there might have been something wrong with the first programming, if not, i'm kinda clueless and would appreciate any help that i might have done wrong, did this before posting, still no joy.. and i accendently damaged my original hi rom! :wooha: :Doh: :/ ohh, the rom from remus is tested and works perfectly in winuae as main and extended, so since they work in winuae and the eproms works with my copied original rom i'm just confused right now :/

going to fetch another original 3.1 roms and another setup of burnable eprom and see what happens, :thumbsup: for this sweet howto! (i used m27c800 eprom's)


are you trying to make a duel boot system?

the eproms you should of used are 27c400.

psychoman
18th April 2013, 11:21
no, just custom 3.9 roms with poseidon from cold boot :) i've heard the 27c800 works just as well?, they did work with a straight copy of my original rom

mfilos
18th April 2013, 11:24
Hi mate and thanks for the nice comments.
First of all you aren't telling us what system you are using for the ROMS so I guess it's the A1200 I see on your signature :)

The custom ROM you're making is 1MB (one normal 512KB file and one extended 512KB file). Of course these 2 files need to be combined and not used individualy through Remus 1MB ROM Arexx script.

Since you're using an 27C800 as you said, you're getting a total of 2MB ROM size (2x 1MB Banks) as opposed to 27C400 that is 512KB alas you're having a correct 1MB ROM (2x 512KB banks).
So... you'd need to double the HI and LO images (since they are 512KB 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 kick_a1200.rom.hi /B+kick_a1200.rom.hi /B kick_a1200_1MB.rom.hi /B
C:\> copy kick_a1200.rom.lo /B+kick_a1200.rom.lo /B kick_a1200_1MB.rom.lo /B

That way you created 2 new files (kick_a1200_1MB.rom.hi and kick_a1200_1MB.rom.lo) which now you can burn to the 27C800 EPROMS just fine :)

psychoman
18th April 2013, 12:56
Hi mate and thanks for the nice comments.
First of all you aren't telling us what system you are using for the ROMS so I guess it's the A1200 I see on your signature :)

The custom ROM you're making is 1MB (one normal 512KB file and one extended 512KB file). Of course these 2 files need to be combined and not used individualy through Remus 1MB ROM Arexx script.

Since you're using an 27C800 as you said, you're getting a total of 2MB ROM size (2x 1MB Banks) as opposed to 27C400 that is 512KB alas you're having a correct 1MB ROM (2x 512KB banks).
So... you'd need to double the HI and LO images (since they are 512KB 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 kick_a1200.rom.hi /B+kick_a1200.rom.hi /B kick_a1200_1MB.rom.hi /B
C:\> copy kick_a1200.rom.lo /B+kick_a1200.rom.lo /B kick_a1200_1MB.rom.lo /B

That way you created 2 new files (kick_a1200_1MB.rom.hi and kick_a1200_1MB.rom.lo) which now you can burn to the 27C800 EPROMS just fine :)

Thank you so very much! I guessed it was something that the roms is 1mb and only 512kb bin files was programmed to them!, i'm at work for the moment but will do this first thing when getting Home :-) im sure it will work after that :-) again thanks a lot!, i'll post the results when done

psychoman
18th April 2013, 20:42
Still no go go :/ currently erasing the eproms again and burning my original 3.1 ones since i damaged my original Hi rom i canīt just quick change, i hope i havent damaged anything else in my amiga :S (i putted the hi rom in the bottom and not in the top pins as it should be, since the 27c800 have all the pins i missplaced it thinking it was the eprom and just when i started i realized it was the original i rom putted in, it was instant fry of the hi rom :/ ) i guess i might have screwed the motherboard up :S

---------- Post added at 18:42 ---------- Previous post was at 17:33 ----------

I have now tested to burn my original roms and the amiga refuses to boot, I guess I blow the motherboard with the rom placed wrong, going to test it some more tomorrow and see if I can get it booting without mediator, but since the mediator is powering my amiga and itīs a really custom made tower I' m using I'm not going to do it tonight, for now, I'm just letting it R.I.P

roy_bates
19th April 2013, 09:20
Still no go go :/ currently erasing the eproms again and burning my original 3.1 ones since i damaged my original Hi rom i canīt just quick change, i hope i havent damaged anything else in my amiga :S (i putted the hi rom in the bottom and not in the top pins as it should be, since the 27c800 have all the pins i missplaced it thinking it was the eprom and just when i started i realized it was the original i rom putted in, it was instant fry of the hi rom :/ ) i guess i might have screwed the motherboard up :S

---------- Post added at 18:42 ---------- Previous post was at 17:33 ----------

I have now tested to burn my original roms and the amiga refuses to boot, I guess I blow the motherboard with the rom placed wrong, going to test it some more tomorrow and see if I can get it booting without mediator, but since the mediator is powering my amiga and itīs a really custom made tower I' m using I'm not going to do it tonight, for now, I'm just letting it R.I.P






just to make you feel a bit better,you wont hurt the amiga putting the hi/lo roms in the wrong socket(it just wont boot) but it will hurt the roms/motherboard if you insert it into the socket wrong(wrong way round,no space to left etc with 27c400)

or if you put the eproms in the socket in the programmer wrong and try to program them,it will most likey kill them as it takes a minimum of 12.5 volts to burn a eprom.

Rakeim132
19th April 2013, 16:00
But you don't have the original Roms ??? These can't be damaged, can they ?

Rakeim132 / Seb132

mfilos
19th April 2013, 16:10
Ofc they can be damaged...

First of all... The kickstart socket has +5V in Pin21 for 27C400 or Pin22 for 27C800 as you can see from the pinout bellow
http://www.plazma-dergi.org/dergi/04/chunk/figure/amiga_eprom/27C400.PNG http://nintendoallstars.w.interia.pl/romlab/m27c800.gif

As roy_bates said... by putting the ROM in the opposite position you're doing no harm as the system simply won't start (blank screen).
By inserting the ROM in reverse order... you're just giving +5V to A17 for 27C400 or A18 for 27C800 not to mention a total mess in signals.

BLTCON0
19th April 2013, 22:02
Ofc they can be damaged...
...
By inserting the ROM in reverse order... you're just giving +5V to A17 for 27C400 or A18 for 27C800 not to mention a total mess in signals.

And why would this damage the ROM?

roy_bates
19th April 2013, 22:19
Ofc they can be damaged...
...
By inserting the ROM in reverse order... you're just giving +5V to A17 for 27C400 or A18 for 27C800 not to mention a total mess in signals.

And why would this damage the ROM?



i think what mfilos is trying to say is that if the rom or eprom was upside down 5+ volts would be sent down the address line.

rkauer
19th April 2013, 22:23
EPROM gates are open-collector and normally low, feeding +5V directly on a gate will burn it permanently, rendering the chip useless.

BLTCON0
19th April 2013, 23:04
Rakeim132 was talking about original ROMs though, not EPROMs.
Anyway, what I'm saying is that feeding +5V to A17 will just drive A17 permanently high, just like it is anyway when the CPU is executing code in the upper half of the ROM (in which case A17 will be driven high by the CPU). Can't see the harm there.

stachu100
19th April 2013, 23:12
Can't see the harm there.
We are just humans - we all do mistakes.
Electrical current will never do mistake.

rkauer
19th April 2013, 23:35
+5V does not have current limitation, so it will burn the track internally forever.

mfilos
20th April 2013, 08:17
Exactly! Alas we tend to put an 4.7K resistor to Pin1 of Kickstart socket ( A17 or A18 ) in case something bad happens :)