Software for building custom Kickstart

[motorollin]

fiat1100d wrote:
Interesting... Who knows if AmigaOS ROM Update contains an updated version of the CD32 Exec too?

I don't know. Just open the ROMUpdate in Remus and it will show all the different versions of exec and which architecture they are designed for. If there's not a CD32 specific version and you really must have a 1MB ROM, then you will have to use the 3.1 version of CD32 exec.

fiat1100d wrote:
Well I had actually missed the "shell", which is a required component :-) As for the operations, I do them under DOS with the utilities of my burner.

Ahhh, that would explain it :-)

fiat1100d wrote:
Now I have a 512 KB 3.9 ROM containing all the A1200-related updates from OS 3.9 Boing Bag 2, less the workbench.library loaded from hard disk thanks to FindWB from A4000T ROM, plus some BlizKick fix.

Congratulations :-)

fiat1100d wrote:
Next step, the A4000T release  8-)

I would be interested to hear how you get on with this, since I will hopefully be changing my A1200 for an A4000D fairly soon. Are the chips the same?

--
moto

[Doobrey]

motorollin wrote:
The only way to get more than 512KB in your Kickstart ROM is if you use exec from the CD32 ROM (which does have a 1MB ROM).

Have you had any success with a 1MB ROM yet?

BTW, a couple of things I've found out with regards to Remus.
1. Don't add the LocalFast Blizkick module, it doesn't work from inside the ROM
2. The CD32 exec doesn't display a guru on reset, it just restarts as if nothing happened. I've done a patch to modify all other exec's to allow a 1MB ROM to work, I'll stick it on the site later if anyone's interested.

Oh well, back to messing about with CDTV and CD32 extended ROMS  :headwall:

[motorollin]

@Doobrey
I haven't tried it yet. The thought of dismantling my tower, removing/erasing/reflashing/replacing the ROMs, then rebuilding the tower is too scary to even think about at the moment. The one thing I've learned about Amigas over the years is that if they're working, don't mess with them :-) Mind you, I suppose I could BlizKick the 1MB ROM to test it. Hmmm......

I would definitely be interested in the patch to allow 1MB ROM using the A1200's exec, as I don't have a CD32 to rip the ROM from. If you upload it, let me know please :-)

--
moto

[Craven1200]

would it be possible to add the  ata3.driver from the fastata package to a rom image ?

[jj]

that is spooky, was just replying to ask that very question
craven

[Craven1200]

great minds ......

[motorollin]

I don't think so. That driver is an executable programme, not a ROM module. It might be possible to modify the driver so it is BlizKick-able, which would mean you could insert it in to a ROM image. But I don't think it will work in its present form.

--
moto

[fiat1100d]

motorollin wrote:
I would be interested to hear how you get on with this, since I will hopefully be changing my A1200 for an A4000D fairly soon. Are the chips the same?

Ok it works on A4000T too. Yes the chips are the same, I use 27C400 EPROMs, filled with two copies of the ROM...

Doobrey wrote:
2. The CD32 exec doesn't display a guru on reset, it just restarts as if nothing happened. I've done a patch to modify all other exec's to allow a 1MB ROM to work, I'll stick it on the site later if anyone's interested.

I would be very interested, since in that way I could have everything in ROM without having to load from hard disk, plus some more storage space in case I install new hardware with ROMmable drivers :-)

[Doobrey]

Craven1200 wrote:
would it be possible to add the  ata3.driver from the fastata package to a rom image ?

I don't have a fastata/powerflyer, but if the driver is anything like the one for their 4xEIDE'99 interface,  not easily done  :-(

For a start, it's not 'rommable' code, it'll only run in RAM (easy enough to write a wrapper to copy it from ROM to RAM and start it though)
But IIRC, it loads a prefs file from ENV: ,that'll require a bit of patching to bundle the driver and prefs file together and make the driver take its settings from there..
But that'll probably incur the wrath of Elbox

[Doobrey]

motorollin wrote:
I would definitely be interested in the patch to allow 1MB ROM using the A1200's exec, as I don't have a CD32 to rip the ROM from. If you upload it, let me know please :-)

OK, just uploaded it to the usual place.
Just add the patch to the buildlist, it only tweaks exec and so doesn't take any space up in the ROM, and works with all v40+v45 execs (and Piru's exec44b4 too)

[fiat1100d]

Thank you, will try as soon as I can, and hopefully 1 MB ROM will work, that would be VERY nice! :-D

[alexh]

Doobrey we appreciate everything you've done for this area. I have made my ROMS but I cannot get the chips out of my board without a chip-pulling tool (Normally I use a screwdriver, but they are stuck in so damn tight and I dont want to fubar my new A4k-CR)

[J-Golden]

I don't have the means or the know how to make these beasts, but I really want one in my A4000T!!!


Is it leagal to sell a set to me?  If so, I would really be interested...

[TjLaZer]

So what kind of ROMs have you guys made?  I was playing around last night and got it working but had to remove workbench.library.  Is that a big deal?  When I tried it in WinUAE I had to remove MCP and it nagged there was no wb.lib!

[fiat1100d]

Well yesterday evening I tried making a 1 MB ROM for the A1200 and it didn't work, got a black screen :-(

As for no workbench.library, it was standard with A4000T (space was needed for the built-in A4091 device) so its ROM has a small component called FindWB which is supposed to look for workbench.library in the LIBS drawer. With newer Amiga OS, however, an updated workbench.library is loaded so the one built into ROM is not required really.

[jj]

@ doobrey

Yeah we had better not play around with the ata3 driver, or it will probable cause some code to wipe are harddrive or summon demons or somehting of that ilk